Propose an update to an asset
Some of the properties of an asset can be changed through governance. Those fields are: withdrawal and deposit limits, and the asset's quantum.
The underlying contract, asset name and symbol cannot be changed.
Requirementsβ
You will need:
- A connected Vega wallet, with your wallet name and public key to hand
- A minimum of whichever is larger, associated with that public key: πgovernance.proposal.asset.minProposerBalance (π20000 tokens) or πspam.protection.proposal.min.tokens (π2000 tokens)
- Familiarity with governance on Vega, particularly assets at a protocol level
You should also share your proposal idea in the Asset Proposals forum section β before submitting it to the network.
After a new asset vote passes, the change has to be submitted to the asset bridge on Ethereum. Until it has been submitted, no one can start depositing that asset. See the tutorial for how to do that.
Anatomy of an update asset proposalβ
The key inputs on an update asset proposal are as follows.
In addition to the parameters you want to change, you must include the existing parameters from the original new asset proposal, even if they are not being changed.
Rationale requires a title and a description. They are free-text fields that describe the purpose of the proposal. Within the description, include links with more information about your proposal (such as to the IPFS content or forum post) that voters can reference to learn more about the asset proposal.
Field | Description | Example |
---|---|---|
asset ID | Unique Vega ID for the asset (string) | |
quantum | The minimum economically meaningful amount of the asset (string). This should be the amount of the asset roughly equal to 1 USD. It is used in a number of ways by the protocol but only requires precision to an order of magnitude level. For example, if one BTC = 26,583 USD, then in this case a quantum of 1 / 25,000 or 0.00004 is sufficient. Converted to asset decimals it would be 40000000000000. | 1000000000000000000 |
withdrawThreshold | The maximum you can withdraw instantly. All withdrawals over the threshold will be delayed by the withdrawal delay, which can be seen on the ERC-20 bridge per asset. Setting this to 1 means all withdrawals will be subject to the delay. It's measured in asset decimals, so 1 is the smallest increment of the market's asset. | 1 |
lifetimeLimit | The lifetime deposit limit per public key, in asset decimals. Users are able to opt out of this functionality using the exempt_depositor write function on the ERC20 contract if they wish to. Suggested value: equivalent of 10,000 USD | 10000000000000000000000 |
Templates and submittingβ
In the tabs below you'll see:
- Annotated example describing what each field is for
- JSON example that can be shared with the community and then submitted with the governance dApp β
- Command line examples for different operating systems
Replace the example data with the relevant details before submitting.
- Annotated example
- Governance dApp (JSON)
- Command line (Linux / OSX)
- Command line (Windows)
{
rationale: {
title: "Update asset",
description: "Proposal to change withdrawal threshold for asset"
},
terms: {
updateAsset: {
// Asset ID the update is for. (string)
assetId: "ebcd94151ae1f0d39a4bde3b21a9c7ae81a80ea4352fb075a92e07608d9c953d",
changes: {
// Minimum economically meaningful amount in the asset. (string)
quantum: "1",
erc20: {
// Maximum you can withdraw instantly. All withdrawals over the threshold will be delayed by the withdrawal delay.
// Thereβs no limit on the size of a withdrawal (string)
withdrawThreshold: "10",
// Lifetime limits deposit per address.
// This will be interpreted against the asset decimals. (string)
lifetimeLimit: "10",
}
}
},
// Timestamp as Unix time in seconds when voting closes for this proposal,
// constrained by `minClose` and `maxClose` network parameters. (int64 as string)
closingTimestamp: 1685553047,
// Timestamp as Unix time in seconds when proposal gets enacted if passed,
// constrained by `minEnact` and `maxEnact` network parameters. (int64 as string)
enactmentTimestamp: 1685639447,
}
}
- Copy the JSON example below into a text editor.
- Replace the placeholder values with those you want for the market.
- Submit your proposal on the governance dApp β.
- Check you can see your proposal under Open Proposals on the governance dApp β.
{
"rationale": {
"title": "Update asset",
"description": "Proposal to change withdrawal threshold for asset"
},
"terms": {
"updateAsset": {
"assetId": "ebcd94151ae1f0d39a4bde3b21a9c7ae81a80ea4352fb075a92e07608d9c953d",
"changes": {
"quantum": "1",
"erc20": {
"withdrawThreshold": "10",
"lifetimeLimit": "10"
}
}
},
"closingTimestamp": 1685553047,
"enactmentTimestamp": 1685639447
}
}
- Copy the command line example below into a text editor.
- Replace the placeholder values with those you want in the proposal.
- Connect to your Vega wallet and use the command line to submit your proposal.
- Check you can see your proposal under Open Proposals on the governance dApp β.
./vegawallet transaction send --wallet YOUR-WALLETNAME --pubkey YOUR-PUBLIC-KEY --network NETWORK-NAME '{
"proposalSubmission": {
"rationale": {
"title": "Update asset",
"description": "Proposal to change withdrawal threshold for asset"
},
"terms": {
"updateAsset": {
"assetId": "ebcd94151ae1f0d39a4bde3b21a9c7ae81a80ea4352fb075a92e07608d9c953d",
"changes": {
"quantum": "1",
"erc20": {
"withdrawThreshold": "10",
"lifetimeLimit": "10"
}
}
},
"closingTimestamp": 1685553047,
"enactmentTimestamp": 1685639447
}
}
}'
- Copy the command line example below into a text editor.
- Replace the placeholder values with those you want in the proposal.
- Connect to your Vega wallet and use the command line to submit your proposal.
- Check you can see your proposal under Open Proposals on the governance dApp β.
vegawallet.exe transaction send --wallet YOUR-WALLETNAME --pubkey YOUR-PUBLIC-KEY --network NETWORK-NAME ^
"{^
\"proposalSubmission\": {^
\"rationale\": {^
\"title\": \"Update asset\",^
\"description\": \"Proposal to change withdrawal threshold for asset\"^
},^
\"terms\": {^
\"updateAsset\": {^
\"assetId\": \"ebcd94151ae1f0d39a4bde3b21a9c7ae81a80ea4352fb075a92e07608d9c953d\",^
\"changes\": {^
\"quantum\": \"1\",^
\"erc20\": {^
\"withdrawThreshold\": \"10\",^
\"lifetimeLimit\": \"10\"^
}^
}^
},^
\"closingTimestamp\": 1685553047,^
\"enactmentTimestamp\": 1685639447^
}^
}^
}"
Votingβ
All proposals are voted on by the community. To vote, community members need, at a minimum, the larger of π1 token or π1 token associated with their Vega key.
Your proposal will need participation of π9% and a majority of π66%, so having community support is essential.
Building support is down to you. Share your proposal in the Asset governance section β of the forum. You may also wish to share on Discord β.
Proposers who invite feedback, engage with comments, and make revisions to meet the needs of the community are more likely to be successful.
Enactmentβ
If successful, the proposal will be enacted at the time you specify in the enactmentTimestamp
field.