> For the complete documentation index, see [llms.txt](https://paper.chainopera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paper.chainopera.ai/tokenomics-and-protocol-design/looking-ahead-evolution-to-an-l1-ai-chain.md).
# Looking Ahead: Evolution to an L1 AI Chain
ChainOpera has already progressed from building a collaborative AI ecosystem to creating a transparent model for measuring contributions and developing the Proof-of-Intelligence (PoI) consensus framework. These achievements provide the technical foundation for a blockchain tailored to collaborative AI, where contributions can be validated, resources coordinated securely, and AI services delivered reliably at scale.
Looking ahead, we are positioning this foundation to evolve into a native Layer-1 AI chain. This would fuse blockchain consensus with core AI operations (model training, inference, and multi-agent workflows) so that decentralized coordination and large-scale AI execution operate as one.
As the network matures, we envision it expanding into self-governing AI subnets that interconnect with other ecosystems, delivering AI infrastructure, services, and tokenized value on a global scale—ultimately fueling the path toward crypto AGI.
---
# 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://paper.chainopera.ai/tokenomics-and-protocol-design/looking-ahead-evolution-to-an-l1-ai-chain.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.