But the biggest flaws as npub180cvv07tjdrrg… noted in that thread is the unwieldiness of the Blockchain especially Ethereum. I mitigate that by;
1. I don't bloat the Blockchain state so the expense doesn't get out of hand.
2. I use the Blockchain for as little computation as possible to keep the cost low.
3. I only use a smart contract to track an accumulator of previous submitted opaque data.
4. I use Rootstock which is a merge minded PoW chain, so I can have a super light client to find the fork choice.
5. Once I get the light client proof of the latest blocks, I read the accumulator from the contract state, all of that is merkle binary tree stuff, so very light.
6. I ask nodes for the state of any ID, and they give me;
A) the state.
B) a merkle proof from the state to the root of the entire IDs set merkle tree.
C) a ZK STARK proof that given a history that accumulates into the accumulator hash from step 5, you should get a full state with the merkle proof from step B.
This way, light clients don't even have to download the history, neither the history of Bitcoin, nor Rootstock, nor the events published on Rootstock.
At least this is the rough plan, I still need to prove that all this actually works
1. I don't bloat the Blockchain state so the expense doesn't get out of hand.
2. I use the Blockchain for as little computation as possible to keep the cost low.
3. I only use a smart contract to track an accumulator of previous submitted opaque data.
4. I use Rootstock which is a merge minded PoW chain, so I can have a super light client to find the fork choice.
5. Once I get the light client proof of the latest blocks, I read the accumulator from the contract state, all of that is merkle binary tree stuff, so very light.
6. I ask nodes for the state of any ID, and they give me;
A) the state.
B) a merkle proof from the state to the root of the entire IDs set merkle tree.
C) a ZK STARK proof that given a history that accumulates into the accumulator hash from step 5, you should get a full state with the merkle proof from step B.
This way, light clients don't even have to download the history, neither the history of Bitcoin, nor Rootstock, nor the events published on Rootstock.
At least this is the rough plan, I still need to prove that all this actually works
