diff --git a/spec/002_xdai_migration.md b/spec/002_xdai_migration.md
index 2b67611..817ca65 100644
--- a/spec/002_xdai_migration.md
+++ b/spec/002_xdai_migration.md
@@ -22,9 +22,24 @@ with a connector weight (target Reserve Ratio) of 0.25 (25%) and an inital price
 (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 (xDAI reserve) Sarafu. Roughly 8Million Sarafu_1 in wallet will be replaced with Sarafu_2
 
 ### Workflow
+
+> 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