search

JoinSEEDS / seeds-smart-contracts

Smart contracts for SEEDS - A Regenerative Civilization Building Game.
https://docs.google.com/document/d/1C4w9Ol8VGabCIcQDVPDrwcTRoJXBqhrb7VjslwQbUGU/edit#heading=h.6f4sxygso816
MIT License
20 stars 6 forks source link

Design: Single contract for multiple rainbow tokens? #454

Open alexprate opened 2 years ago

alexprate commented 2 years ago

Q: Should we hold all the rainbow tokens on a single contract? Note that a token is defined by a name AND a contract.

Challenge 1: Uniqueness of the name of a token. Only 7 characters all caps are allowed. Fairly quickly, we might find communities willing to call their community token the same as an already existing community token. As we have them in the same contract, then the creation of this token will not be possible.

Challenge 2: Evolving the contract (adding a feature for example) may impact all the communities at once. What is the update and deployment processes?

Challenge 3: Moving away from the rainbow contract to another contract if the community decides to do so. What is the process and complexity? Will the tokens be destroyed in the rainbow contract and recreated in the new contract by an administrative action? What about the data held in the contract, how do we make sure to not impact other communities?

alexprate commented 2 years ago

@n13 As agreed yesterday in the currency working group, we will use the rainbow contract. We are aware that these challenges will appear in the future but it seems premature to address these at this point. Closing this task for now.