# What is Axiom?
Axiom gives smart contracts **trustless access to the entire history of Ethereum and arbitrary ZK-verified compute over it**. Developers can send on-chain queries into Axiom, which are trustlessly fulfilled with ZK-verified results sent in a callback to the developer's smart contract. This allows developers to build rich on-chain applications without additional trust assumptions.
These docs are for Axiom V2, which is **live on Goerli testnet as of November 2023**. To access docs for Axiom V1, which is live on Ethereum mainnet since July 2023, follow the link to [V1 docs](https://docs-v1.axiom.xyz/).
#### Overview
To fulfill queries, Axiom performs three steps:
* **Read:** Axiom uses ZK proofs to trustlessly read from block headers, states, transactions, and receipts in any historical Ethereum block. All Ethereum on-chain data is encoded in one of these forms, meaning that Axiom can access anything an archive node can.
* **Compute:** Once data has been ingested, Axiom applies verified compute on top. Developers can specify their own computation in a Javascript frontend, and the validity of each computation is verified in a ZK proof. Visit [AxiomREPL](https://repl.axiom.xyz/) or see the [docs](/axiomv2-sdk/developers/axiomrepl.md) to play around with the available compute primitives.
* **Verify:** Axiom accompanies each query result with a ZK validity proof that (1) the input data was correctly fetched from the chain and (2) the compute was correctly applied. This ZK proof is verified on-chain in the Axiom smart contract, and the final result is then trustlessly available for use in your smart contract.
Because they are verified by a ZK proof, results from Axiom have **security cryptographically equivalent to that of Ethereum** and make no assumptions about crypto-economics, incentives, or game theory. We believe this offers the highest possible guarantee for smart contract applications.
#### Integrating Axiom
To integrate Axiom into your application:
* Integrate with Axiom V2 **on Goerli testnet** today to **trustlessly query and process the entire history of Ethereum** from your smart contract.
* Fill out the [early partner form](https://airtable.com/shrdqI16f6EZBNkMA) to discuss ideas with us!
To learn more about how Axiom fits in with smart contract applications, check out [Axiom for Developers](/axiomv2-sdk/developers/axiom-for-developers.md) or see our [Autonomous Airdrop](/axiomv2-sdk/examples/autonomous-airdrop.md) example app.
#### How Axiom Works
Check out [Protocol Design](/axiomv2-sdk/protocol-design/architecture-overview.md) to understand how Axiom works and [ZK Circuits for Axiom Queries](/axiomv2-sdk/protocol-design/zk-circuits-for-axiom-queries.md) to learn more about our ZK circuits. You can learn more about our deployment settings at [Transparency and Security](/axiomv2-sdk/transparency-and-security/kzg-trusted-setup.md)and about zero-knowledge proofs in general at [Zero Knowledge Proofs](/axiomv2-sdk/zero-knowledge-proofs/introduction-to-zk.md).
#### Get In Touch
If you have questions, ideas, or would just like to chat, join the discussion in our [Discord](https://discord.gg/4nDgMUq7Ra) or the technical discussion on [Telegram](https://t.me/axiom_discuss). Our circuit and smart contract code is open-source and available at our [GitHub](https://github.com/axiom-crypto).
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://intrinsic-1.gitbook.io/axiomv2-sdk/introduction/what-is-axiom.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.