> For the complete documentation index, see [llms.txt](https://atochaprotocol.gitbook.io/atocha-protocol-wiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atochaprotocol.gitbook.io/atocha-protocol-wiki/atocha-mainnet.md).
# Atocha Mainnet
## Atocha Mainnet Introduction
Atocha Protocol Mainnet is essentially the official version of the publicly run appchain (application specific blockchain) for the puzzle game community. In other words, all the transactions that took place on the protocol will forever be recorded on the blockchain itself like any other protocol. This includes the transfer of assets, creation of puzzles, solving a puzzle, sponsoring puzzles, claiming rewards and more.
### Where to Find Atocha Mainnet?
You can view the Atocha Protocol Mainnet details:
### Key Terminology Definition
[**Bridge**](https://mainnet.oct.network/bridge/near/atocha): This is a bridging infrastructure for the users to cross the assets from [Near Wallet](https://wallet.near.org/) to [Polkadot JS Wallet ](https://polkadot.js.org/extension/)as most of the appchain’s applications are to be connected via Polkadot JS Wallet.
[**Explorer**](https://explorer.mainnet.oct.network/?appchain=atocha#/home): Similar to any other blockchain explorer like [Etherscan](https://etherscan.io/), you can find the specific transaction through transaction ID to verify.
[**Anchor**](https://explorer.mainnet.near.org/accounts/atocha.octopus-registry.near): As Atocha Protocol is part of the appchain hosted on Octopus Relay (side chain of Near Protocol), there should be a transactional record as well on the Near Protocol side. This is the part of records where Octopus Network is transacting with Near Protocol on behalf of Atocha Protocol.
**Current Era**: The running days of the appchain. 1 era equals 1 day.
**Era Reward**: This is the total rewards that will be distributed to the validators per day.
**RPC Endpoint**: An **RPC** (remote procedure call) **endpoint** is like a node’s address: it’s a URL which requests blockchain data can be sent to a specific site. You can understand it as a reader who helps you to convey and interpret the data from a record book.
[**Function Spec**](https://github.com/atocha-protocol/atocha-octopus-chain/blob/master/atocha-function-spec.md#solve-a-puzzle): This is a public record of all the function mechanisms that Atocha team has developed and is available in the current version of the protocol. This is essentially the function list that the protocol can perform.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## 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, and the optional `goal` query parameter:
```
GET https://atochaprotocol.gitbook.io/atocha-protocol-wiki/atocha-mainnet.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.