search

zeko-labs / zeko

Zeko: zk-Rollup for Mina, a succinct blockchain
https://zeko.io
Apache License 2.0
23 stars 3 forks source link

Implement voting to force account updates #160

Open L-as opened 4 months ago

L-as commented 4 months ago

Consider that we have total $ZEKO, and need m $ZEKO to force an account update. The $ZEKO token owner must keep track of the total supply, and a proof is done by a multisig consisting of all who chose to vote, weighted by their stake, proven by Merkle tree openings to the accounts on both outer and inner ledger. Thus, outer ledger must somehow be tracked by using a network precondition on L1 in $ZEKO token owner account. To prevent DOS attacks that keep updating it, the action state keeps track of which outer ledger hash to use. Since you can match on any of the last 5 ones, we have 5 outer ledger hashes we can choose from. You can only use the latest action from the chosen action state.

L-as commented 4 months ago

Different types of account updates might need different proportions of the total stake, e.g. freezing Zeko temporarily might need only 1/3, but doing a vk upgrade might need 2/3.