Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add conf_whitelist module #89

Open
osuketh opened this issue Mar 31, 2019 · 1 comment
Open

Add conf_whitelist module #89

osuketh opened this issue Mar 31, 2019 · 1 comment

Comments

@osuketh
Copy link
Member

osuketh commented Mar 31, 2019

Instead of storing the whitelisted accounts in on-chain, it is stored in off-chain as a Merkle tree by the specific asset maintainer.
In order to ensure the validity for the lists, they need to commit the Merkle root and send zkproof to on-chain. So, the soundness is based on that of zkp. All users need to send merkle proof when they invoke the can_transfer function which returns true only if the sender is in the whitelist(i.e. merkle root corresponding to the asset Id)

@osuketh
Copy link
Member Author

osuketh commented Mar 31, 2019

The maintainer of the whitelist can update the Merkle root whenever they want. It's just the trade-off between their maintenance cost and UX.

@osuketh osuketh changed the title Add whitelist_asset module Add conf_whitelist module Mar 31, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant