> For the complete documentation index, see [llms.txt](https://docs.geode.fi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geode.fi/key-concepts/future-of-geode/chain-sync-avax-draft.md).

# Chain Sync (AVAX) (draft)

### Staking is a chain specific problem.

Every blockchain has a different approach to the Proof of Stake, and every approach requires a different solution to be found.

Currently, there are some implementations that are used to solve chain-specific problems of Avalanche blockchains. These are mostly related to the multi-chain structure of the chain.

With this improvement we are aiming to achieve two things:

* Eliminate chain-specific differences between Portal deployments on Avalanche and Ethereum.
  * Makes development processes easier, allowing us to provide more frequent improvements on the protocol without considering differences within code.
  * Makes onboarding of protocols on different blockchain easier.  
* Increase trustlessness of the Node Operators.
  * Allows us to onboard more Operators.
  * Allows us to decrease costs for Operators.
  * Strengthens Portal. 


---

# 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://docs.geode.fi/key-concepts/future-of-geode/chain-sync-avax-draft.md?ask=<question>&goal=<endgoal>
```

`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.