# Taxonomy

## Standard rollups

Standard rollups (on Ethereum) are validated and settled through smart contracts.

## Sovereign rollups

Sovereign rollups (on Celestia) leverage the base layer protocol for consensus and data availability.

## Enshrined rollups

Enshrined rollups ([domains](/autonomys-network/decoupled-execution/domains.md) on Autonomys) are directly integrated into the core consensus protocol of the underlying blockchain, ensuring the rollup's features and functionality are maintained and enforced by the network's consensus rules. This built-in support enhances the rollup's security, interoperability and adoption, while providing the benefits of a typical rollup, such as increased throughput and reduced transaction fees.

Domains extend Celestia's sovereign rollup model to include shared settlement by default by allowing operators to re-stake (as proposed by Free2Shard and implemented by EigenLayer on Ethereum). Autonomys enshrines the re-staking model within the semantics of the core protocol (unlike EigenLayer, which is implemented through smart contracts).

Although similar to Polkadot parachains, domains support a modular validation framework and permissionless deployment, unlike parachains' monolithic validation model and permissioned deployment. Domains also have shared security and trust-minimized interoperability as they are validated and settled on the consensus chain (unlike Cosmos zones and Avalanche subnets).


---

# Agent Instructions: 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://academy.autonomys.xyz/autonomys-network/decoupled-execution/domains/taxonomy.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.
