One important problem in ethereum that has not yet seen enough love is decentralized marketplaces for providing historical information (logs, txs... basically anything other than current state).
101
283
1,575
Conversation
One example is logs:
1. Client sends message "I want all historical logs for topic X"
2. Provider replies back with logs + Merkle proofs
3. Client re-broadcasts provider's response; if the provider missed a log their deposit can get slashed
This could be done for txs too...
6
10
128
Replying to
Proving the set of logs is complete is very expensive though, isn't it?
1
1
Replying to
Fraud-proving that a set given by someone else is not complete is easy.
I'm explicitly proposing leaning heavily on cryptoeconomics for this.
2
4
if the querier can't read the state, how does it know the fraud proofs are meaningful/slashable?
you're introducing a dependency on the state to the security of the query about the state
4
how do I even know you're bonded without querying the state?
1
I'm assuming clients know the current state; I'm advocating layer-2 infrastructure specifically for learning about *history* here.
2
9
It would it be on-chain provable that the proposed history was/wasn't correct (assuming the disputer had access to off-chain computation), right? Via providing a more complete one or disputing a part of the proposed one.
Yes. The real problem is that a block witness is 10GB+
1
1
Is there a time when the bullet is bitten and the blockchain specific consumer hardware is implemented? Seems like a lot of the issues stem from consumer hardware not being able to support the ever growing state. 10GB+ doesn't seem that bad if comes pre-installed? 🤷🏽♀️
1
Show replies