3.2 KiB
x/bDAI Migration spec
- Authors: Will Ruddick will@grassecon.org
- Date: 2020.04.22
- Version: 1
- Status: Pre-draft
Rationale
We want to give donors and community members a way to contribute to and cash-out from Community Inclusion Currencies with National Currency. By connecting to a reserve that is stable to the US dollar called x/bDAI we bring some stability and the ability for many to support local communities. We also enable any CICs that have bDAI as a reserve to convert to any other CIC with bDAI as reserve.
Before
Currently we are using a virtual reserve a generic ERC20 token. We have 2 Million of those reserve tokens against 8 Million Sarafu issued (the current Kenyan CIC). (Call those Sarafu_1 or S1)
After
We have 40,000 DAI to bridge to a bDAI token and put as the reserve and are looking at minting (16Million) tokens (called Sarafu_2 S2) with a connector weight (target Reserve Ratio) of 0.25 (25%) and an inital price of roughly 100 Sarafu to 1 xDAI (USD stable) (Note that the 100 Sarafu to 1 xDAI will approximate the Kenyan Shillings to USD rate)
Implementation
Each existing user should have a completley new wallet and private key for security reasons and be given the same balances they currently have with the new (bDAI reserve) Sarafu. Roughly 8Million Sarafu_1 in wallet will be replaced with Sarafu_2
Workflow
- Bridge bDAI to DAI on BloxBerg
- Setup an onserver node on BloxBerg
- Synch db <->Blockchain - ensure synronization between our db (USSD interface) and blockchain
- (delayed) Finalize any contract changes to Bancor Suite (such as Depth Bump)
- Understand all Public vs Private (owner owned) Functions - Make all contracts as permissionless as possible
- Create group of govenors on a multi-sig wallet with the power to assign the facilitator address of all blockchain contracts (Bancor Suite).
- Security checkes
- Deploy contracts to create Sarafu_2, set inital variables - deposit reserve and mint tokens
- Migration - New wallets for users - Replicate user accounts with new token Sarafu_2 - ensure private keys are safely stored
Variables
- Synch variables, - synch frequency - and limitations
- Contract variables (reserve ratio (0.25), reserve amount (40k bDAI), number of Sarafu_2 (16Million), convert fee 0.005 (0.5%))
- Migration speed - how often is synching done between USSD db and blockchain
- 3rd party Fiat <-> bDAI conversion costs and speed
Interface
This migration will all be done at code and command line level, while some testing can be done on the platform gui
Testing
- Check bDAI to DAI on bridge on BloxBerg
- Test observer node on BloxBerg for dashboard
- Check db<->blockchain synch - verify they are synched and we can do external transactions and handle RPC failure
- Token Governance
- Contract deplyment - conversions, transfers all work as expected
- Migration - new wallets match old wallets
- Store old blockchain wallet IDs (as a list with older POA and xDAI wallets)