> 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/publish-your-docs-1.md).

# Why the SUI Network?

Why AIONET DAO Is Built on Sui

AIONET is built on Sui because its architecture aligns directly with the system’s core design principles: non-custodial ownership, deterministic execution, scalable participation, and long-term sustainability.

Rather than selecting a blockchain as a deployment layer, AIONET is structured around capabilities that require a specific type of infrastructure. Sui provides these capabilities natively, allowing the system to be implemented in a way that is both secure and coherent.

At the foundation of this alignment is Sui’s object-centric model. Unlike traditional account-based architectures, Sui treats assets as programmable objects with clearly defined ownership and permissions.

→ Learn more about Sui’s architecture:\
<https://docs.sui.io/concepts/object-model>

This enables precise control over how assets behave and interact - a requirement for AIONET’s design.

The system relies on non-transferable memberships, persistent identity profiles, and internal utility mechanisms that must operate without ambiguity or unintended transferability. On Sui, these elements can be implemented cleanly, without relying on complex or fragile smart contract patterns. Access passes, reputation layers, and internal point systems can all be defined with strict ownership rules, reducing both technical complexity and potential attack surfaces.

Scalability is equally important. AIONET is designed as a high-interaction environment, where users continuously engage with the system through progression, participation, and governance.

Sui’s architecture supports this model through:

* parallel transaction execution
* high throughput
* low and predictable fees

→ Technical overview:\
<https://docs.sui.io/concepts/sui-architecture>

This allows AIONET to deliver a smooth, uninterrupted user experience without introducing cost barriers that would limit participation.

Security is another fundamental reason for building on Sui. The network is based on the Move programming language, which enforces strong guarantees around asset safety and ownership.

→ Move language fundamentals:\
<https://docs.sui.io/concepts/sui-move>

Assets cannot be duplicated, unintentionally lost, or mismanaged due to common smart contract vulnerabilities. This aligns directly with AIONET’s trust-minimized philosophy, where system integrity is enforced at the architectural level.

Beyond technical considerations, Sui provides a strong strategic foundation. Its focus on consumer-grade Web3 applications and growing ecosystem creates an environment where systems like AIONET can scale globally while maintaining usability and clarity.

For AIONET, which operates with an EU-first mindset, this is particularly important. The ability to combine transparency, user control, and clearly defined system boundaries supports long-term sustainability without conflicting with evolving regulatory expectations.

In this context, Sui is not simply a technical choice - it is an architectural match.

It enables AIONET to operate as intended: a non-custodial, identity-driven, and participation-based ecosystem, where access, governance, and utility can scale efficiently without compromising security, user experience, or long-term viability.

***