Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement Tax 1.2% in all transactions #102

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

vegasmorph
Copy link

Implement part of the on chain proposal 3568

Implement part of the on chain proposal 3568
@vegasmorph vegasmorph changed the title Create Tax 1.2% in all transactions Implement Tax 1.2% in all transactions Jun 7, 2022
@vegasmorph
Copy link
Author

[{
“subspace”: “treasury”,
“key”: “tax_rate”,
“value”: “1.200000000000000000”
},
{
“subspace”: “distribution”,
“key”: “terra1sk06e3dyexuq4shw77y3dsv480xv42mq73anxu”,
“value”: “1.20000000000000000”
},
]

@@ -0,0 +1 @@

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This random file wouldn't be the right place for this. This needs to go in a new param change proposal.

Stop if max_supply =< 10000000
@littlekira01
Copy link

@vegasmorph
Copy link
Author

vegasmorph commented Jun 11, 2022 via email



[{
“subspace”: “treasury”,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I hope you don't mind that I comment on this but these are non-standard double quotes.
Instead of shouldn't these be "?

Copy link

@sann1432 sann1432 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looking good

@vegasmorph
Copy link
Author

vegasmorph commented Jun 11, 2022 via email

@holylance
Copy link

@octalmage Can you merge this PR?
Or should we wait?

@octalmage
Copy link

It’s unfortunately invalid and not how param change proposals work.

@octalmage
Copy link

See this comment: #102 (comment)

@holylance
Copy link

@octalmage Thank you to answer quickly.
I am an Android developer, so I am not familiar with this terra classic repository.
Please understand. But I would like to add this tax system asap.

I think there are two possible options.

  1. You mentioned "a new param change proposal".
    Does it mean that if I make a file like this in the new param change proposal directory, is it enough?

  2. I heard that the tax 1.2 is not a parameter proposal, so one of the TFL developers has to "code" in somewhere in this repository.
    Is it correct? If it is, we have to wait until the developer completes this.

@octalmage
Copy link

@holylance No problem!

  1. This is the wrong repository really. This just contains instructions for joining the network, but not any actual code. So no changes to this repo are needed. param change proposals are an on-chain system to allow you to modify different core parameters. You can see this example where LUNA stakers voted to set the stablecoin tax to zero: https://station.terra.money/proposal/172

This tax rate only effects Terra stablecoins though, and not Luna as can be seen here: https://github.com/terra-money/classic-core/blob/d6037b9a12c8bf6b09fe861c8ad93456aac5eebb/custom/auth/ante/tax.go#L154

  1. So based on the above info if the desired result is to set a 1.2% tax on Luna, that will have to be new code. To say that only TFL devs can make this change is incorrect, the code is all open source and anyone can submit a pull request here: https://github.com/terra-money/classic-core

So one process that could work is to have someone write and test the code, submit as a pull request, then have it reviewed. Once reviewed and merged, you'll need to start a SoftwareUpgradeProposal which you can learn about here: https://docs.cosmos.network/master/modules/gov/01_concepts.html#software-upgrade

@holylance
Copy link

@holylance No problem!

  1. This is the wrong repository really. This just contains instructions for joining the network, but not any actual code. So no changes to this repo are needed. param change proposals are an on-chain system to allow you to modify different core parameters. You can see this example where LUNA stakers voted to set the stablecoin tax to zero: https://station.terra.money/proposal/172

This tax rate only effects Terra stablecoins though, and not Luna as can be seen here: https://github.com/terra-money/classic-core/blob/d6037b9a12c8bf6b09fe861c8ad93456aac5eebb/custom/auth/ante/tax.go#L154

  1. So based on the above info if the desired result is to set a 1.2% tax on Luna, that will have to be new code. To say that only TFL devs can make this change is incorrect, the code is all open source and anyone can submit a pull request here: https://github.com/terra-money/classic-core

So one process that could work is to have someone write and test the code, submit as a pull request, then have it reviewed. Once reviewed and merged, you'll need to start a SoftwareUpgradeProposal which you can learn about here: https://docs.cosmos.network/master/modules/gov/01_concepts.html#software-upgrade

Very Thanks :>

@jamesbsbs
Copy link

@octalmage thanks for your answers
so if @vegasmorph proposes a code that works ,
will you merge the pull request (or will terra team merge it) , or is it a waist of time ( this is not sarcasm, i'm serious).

thanks in advance

@vegasmorph
Copy link
Author

this can only be implemented after the code is merged,not before
{
"title": "Param Change Policy",
"description": "Update tax policy",
"changes": [
{
"subspace": "treasury",
"key": "TaxPolicy",
"value": {"rate_min": "0.012", "rate_max": "0.012",
"cap":{"denom": "usdr", "amount": "10000000" },
"change_rate_max": "0.0"}
},
{
"subspace": "treasury",
"key": "RewardPolicy",
"value": {"rate_min": "1.0", "rate_max": "1.0",
"cap":{"denom": "unused", "amount": "0" },
"change_rate_max": "0.0"}
}
],
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants