-
Notifications
You must be signed in to change notification settings - Fork 31
Status Token Registry: Default Supported Tokens for Status Wallet #18
Comments
This might be a perfect incentive to burn some SNT, what do you think ? Allowing all SNT to get a token listed on the registry burn the SNT on succesful addition. |
Yes! This is what I've been advocating for some time. "Burn, burn with me love" ;) |
Well the idea of bribes and community voting could still remain, this would just be an initial listing fee (I'd prefer it being pegged to usd). I remember paying 5 or 10 usd to get a chrome extension on the web store for example - it's quite a common strategy it seems ;) |
There is no fixed "fee" to register, instead a faculty "bribe" can be placed with the request. This bribe is divided by half, where half is divided in between who voted (no matter if yes or no). Editing a registry is possible, but will fall into democratic vote again, with a possible "bribe" incentive. The request to edit must come only from registrant, but the registrant should be able to forcefully changed by SNT democratic vote through a "curator delegate topic". |
We could use 0xProject Token Registry, as they are our parteners, or make it user-selectable if want Status Token Registry or 0xProject, as they will be ABI-compatible in between each other, as following ethereum/EIPs#22 |
Closing this as its gone stale. Feel free to re-open if its still relevant or if there is someone working on it. |
@andytudhope Are you working on this? |
Preamble
Summary
Create a Token Registry owned by SNT holders
Vision
Token Registries may get bloated with worthless tokens, leading to high processing in wallet load, to solve this, a Token Registry controlled by SNT holders would be deployed for use in #3 , where the addition of tokens would only happen upon approval of a SNT holders quorum. Any change on the registry should also happen upon SNT holders quorum.
To incentive SNT holders to accept a registry, the registrant can place a bribe to distribute among all yes-voters and Status Network reserve.
Swarm Participants
Requirements
Goals & Implementation Plan
Minimum Viable Product
Goal Date:
Description:
Iteration 1..N
Goal Date:
Description:
Supporting Role Communication
Post-Mortem
Copyright
Copyright and related rights waived via CC0.
The text was updated successfully, but these errors were encountered: