grassrootseconomics/cic-docs
5
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
f3a4261941
cic-docs/spec/xdai_migration.md
WillRuddick 069a88f9e5
Update xdai_migration.md
2020-04-23 21:07:13 +03:00

2.4 KiB
Raw Blame History

xDAI Migration spec

Rationale

We want to give donors and community mambers 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 xDAI we bring some stability and the ability for many to support local communities. We also enable any CICs that have xDAI as a reserve to convert to any other CIC with xDAI 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). Sall those Sarafu_1 or S1

After

We have 40,000 xDAI to put as the reserve and are looking at minting 16Million tokens called Sarafu S2 with a connector weight (target Reserve Ratio) of 0.25 (25%) and an inital price of roughly 0.01 Sarafu to a xDAI (USD stable)

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 (xDAI reserve) Sarafu. Roughly 8Million Sarafu_1 in wallet will be replaced with Sarafu_2

Workflow

  1. Synch db <->Blockchain - ensure synronization between our db (USSD interface) and blockchain
  2. Deploy contracts to create Sarafu_2, set inital variables - deposit reserve and mint tokens
  3. Migration - New wallets for users - Replicate user accounts with new token Sarafu_2

Variables

  1. Synch variables, - synch frequency - and limitations
  2. Contract variables (reserve ratio (0.25), reserve amount (40k xDAI), number of Sarafu_2 (16Million), convert fee 0.005 (0.5%))
  3. Migration speed - how often is synching done between USSD db and blockchain
  4. 3rd party Fiat <-> xDAI 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

  1. Check db<->blockchain synch - verify they are synched and we can do external transactions and handle RPC failure
  2. Contract deplyment - conversions, transfers all work as expected
  3. Migration - new wallets match old wallets
  4. Store old blockchain wallet IDs (as a list with old POA wallets)

Changelog