grassrootseconomics
/
cic-docs
5
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Update 002_xdai_migration.md

This commit is contained in:
Will Ruddick 2020-06-19 04:20:28 +00:00
parent ac945b2bda
commit 40c04175bf
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
spec/002_xdai_migration.md
View File

@ -29,10 +29,17 @@ Each existing user should have a completley new wallet and private key for secur
> lash: what's meant by public and private functions here?
> will: I'm just considering what should be private=internal=only the owner can use vs public functions ....
> Also can we make some of the internal/private functions permissionless post creation (i.e. remove them/ block the doors) ... Upgradability?
> lash: private keys: should we take the opportunity of setting up deterministic wallets? perhaps even on the platform we may want to shuffle private keys once in awhile.
> will: Yes and no. For now on the platform we really want easy trackability to track donor impacts .... I would leave this for the web wallet etc. I just want to make sure the private keys are all secure - who has access etc.
> lash: what is a "facilitator address"?
> Will: Lets remove this - see depth_bump comments
1. Synch db <->Blockchain - ensure synronization between our db (USSD interface) and blockchain
1. Finalize any contract changes to Bancor Suite (such as [Depth Bump](https://gitlab.com/grassrootseconomics/cic-docs/-/blob/master/spec/003_depth_bump.md))
1. Create Public vs Private Functions - Contracts as permissionless as possible