removed conversion and multi-token env
This commit is contained in:
parent
d34989184a
commit
c51c2b0df5
@ -23,7 +23,7 @@ Enabeling users to create their own tokens is one of the main goals of CICs. Thi
|
||||
2. The token creation application is audited and signed by all parties (paper form)
|
||||
3. All users in the agreement dial the USSD code and setup an account (with 0 initial balance for new accounts). If they have existing tokens those will simply stay there in their account. *Note that Users with multiple tokens in their account should have an option to switch their active token to trade the other tokens. (see milti-token-env spec)
|
||||
4. GE creates the new token (or mints more Sarafu) and sends it to the users as per the agreement. Also changing their Active token to the new token if one was created.
|
||||
5. Initally conversion between tokens will not be allowed (see conversion below)
|
||||
5. n.b. Initally conversion between tokens will not be allowed
|
||||
|
||||
## Inputs
|
||||
|
||||
@ -48,7 +48,7 @@ Enabeling users to create their own tokens is one of the main goals of CICs. Thi
|
||||
1. to discover the contract addresses on the network you use:
|
||||
1. eth-contract-registry-list
|
||||
1. Put the TOKEN_NAME tokens into the Users wallet (as per agreement)
|
||||
1. All members in the agreement should have their active token set to TOKEN_NAME
|
||||
1. All members in the agreement should have their active token set to TOKEN_NAME (see multi-token spec)
|
||||
|
||||
## Token creation Interface - UX
|
||||
|
||||
@ -65,9 +65,6 @@ Enabeling users to create their own tokens is one of the main goals of CICs. Thi
|
||||
|
||||
|
||||
## Testing
|
||||
1. Ensure conversions are working between tokens when liquidity pools exist and not when they dont
|
||||
2. Test out auto-conversion - one user gets sent a foreign token ... try to convert
|
||||
|
||||
|
||||
## Action items
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user