Axiom explained: trustless historical on-chain data and ZK coprocessing
Thread518 words
Explains how Axiom uses ZK proofs to let smart contracts trustlessly read historical Ethereum data and run compute over it, via a Read, Compute, Verify flow, with use cases like trustless payments and oracle queries.
Key claims
Until now dApps had no trustless way to query historical on-chain data
Every Axiom query result ships with a ZK validity proof verified on-chain
Axiom compute is not shared between dApps, so it can exceed on-chain VM limits
0/ few are aware that until now, there was no trustless way for dApps to query historical on-chain data 馃く
a 馃У on how @axiom_xyz will use #zk tech to change this (0/18) 馃憞
1/ in the world of #DApps, accessing historic data or performing complex on-chain computations often poses challenges
2/ @axiom_xyz steps in here, supercharging DApps by providing trustless access to all on-chain data and offering arbitrary expressive compute over it, thanks to zero-knowledge proofs
3/ zero-knowledge proofs bring powerful trustless computation to the table, holding significant potential for improving user experiences in blockchain applications. However, their implementation and use remain intricate, creating barriers for widespread application
4/ @axiom_xyz is designed to bridge this gap. Much like oracles, smart contract developers can query Axiom for functions of historic on-chain data.
5/ @axiom_xyz processes these queries trustlessly on-chain, enabling developers to leverage zero-knowledge proofs without having to construct ZK circuits themselves
6/ before diving further, let's briefly talk about archive nodes though. These are blockchain nodes that store all historical data, serving as vital reservoirs of comprehensive transaction histories
7/ they allow full access to past states, proving essential for analyzing and querying the blockchain's historical data.
however, so far there was no trustless way for dApps to query historical on-chain data from these nodes
that's where @axiom_xyz enters the picture
8/ @axiom_xyz operates via three steps: Read, Compute, and Verify. In the Read phase, it utilizes zero-knowledge proofs to trustlessly read block headers, states, transactions, and receipts from any #Ethereum block...
9/ ...granting smart contracts access to comprehensive archive node data, which usually lies beyond the #EVM's reach
10/ the Compute phase follows, where @axiom_xyz applies verified computations to the ingested data
11/ this includes functions like analytics (sum, count, max), cryptography (signature verification, key aggregation), and machine learning (decision trees, neural network inference), operations typically too cumbersome for blockchain VMs
12/ lastly, the Verify phase ensures each @axiom_xyz query result comes with a zero-knowledge validity proof, attesting to the accurate reading of on-chain data inputs and the correctness of all computations
13/ the @axiom_xyz smart contract verifies this proof, making the result trustlessly available for downstream applications.
14/ @axiom_xyz's capacity to read raw #Ethereum data allows it to scale DApps without the need to migrate state to a rollup. Moreover, as compute on @axiom_xyz isn't shared between DApps, @axiom_xyz can handle computations too large for any on-chain VM
15/ potential early use cases for @axiom_xyz include trustless payment to protocol participants based on their on-chain behavior, updating #DeFi parameters using historic data, trustlessly enforcing off-chain governance votes, and making oracle queries for on-chain data trustless
16/ the potential applications of @axiom_xyz are extensive and indicate promising prospects for the future of #DApp development.
17/ by addressing data accessibility and complex computation challenges on-chain, @axiom_xyz can significantly augment blockchain consensus via zk proofs, similar to the relationship between GPUs and CPUs
18/ definitely an exciting use case for zero knowledge proofs XX XX
tagging some zk frens 馃馃憞
@0xSalazar
@schmiddominik1
@Louround_
@0xkhan_
@thesaint_
@Flowslikeosmo
@wacy_time1
@DeFiMinty
@ShivanshuMadan
@chilla_ct
@Swagtimus
@daddysether
@kunalgoel
@redvelvetzip
@hmalviya9
@georgethms1
@AlphaInsiders
@0xDinoEggs
1 image on X