> For the complete documentation index, see [llms.txt](https://aionet.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aionet.gitbook.io/docs/aionet-overview/quickstart.md).

# Overview

{% hint style="info" %}
If you’re using a mobile device, tap the menu icon in the top-left bar to access the navigation.
{% endhint %}

AIONET is an on-chain membership ecosystem built on Sui, designed as a trust-minimized coordination layer for participation, identity, and BTC-focused utility.

Rather than operating as a traditional Web3 product or financial platform, AIONET introduces a structured environment where users interact through access, contribute through verifiable activity, and progress through transparent on-chain systems. It brings together identity, engagement, and utility into a unified framework where participation is not driven by speculation, but by alignment and contribution.

At its foundation, AIONET replaces fragmented user experiences with a cohesive system. Access is granted through non-transferable NFT memberships, ensuring that participation is tied to identity rather than capital or market dynamics. Each user operates through a persistent on-chain profile that records progression, activity, and contribution over time, forming a verifiable digital identity within the ecosystem.

The system is designed to function without reliance on centralized control or discretionary decision-making. All core mechanisms are deterministic and governed by predefined logic, allowing users to interact with full transparency and predictability. Smart contracts define the rules of participation, while automation ensures that execution remains consistent and trust-minimized.

AIONET is non-custodial by design. Users retain full control over their assets at all times and interact with system utilities through permissioned, rule-based mechanisms. There are no pooled funds, no hidden intermediaries, and no dependency on off-chain trust. Every interaction is structured to preserve user sovereignty while enabling meaningful participation.

Beyond access and infrastructure, AIONET introduces a model where engagement and contribution are central to the system. Users do not simply enter and observe — they build identity, gain experience, and participate in an evolving ecosystem. Progression is not abstract; it is recorded, measurable, and directly connected to governance, access, and opportunity within the platform.

Importantly, AIONET is not designed as an investment platform or a speculative layer. It does not offer ownership, equity, or guaranteed financial outcomes. Instead, it provides structured access to on-chain systems, including a BTC-focused utility layer, within a transparent and controlled environment.

In this sense, AIONET functions as more than a product. It is a coordination layer where users, contributors, and systems interact under a shared set of rules, aligned by participation rather than speculation. Its purpose is to create a sustainable and transparent environment where users can engage with Web3 infrastructure in a way that is understandable, verifiable, and built for long-term use.

<figure><img src="/files/0JMpjfl0Hi55BxkJwRWM" alt=""><figcaption></figcaption></figure>


---

# 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:

```
GET https://aionet.gitbook.io/docs/aionet-overview/quickstart.md?ask=<question>
```

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.