What is Saelis?

Saelis is an experimental metaprotocol being developed on Kinetiq's Elysium, an EVM-compatible Arbitrum Orbit Layer 2 connected to the Hyperliquid ecosystem. It defines how a specific kind of onchain data, the Sigil, should be written, read, validated and composed.

#What is a metaprotocol?

A blockchain protocol defines consensus, execution and state: which transactions are valid and what they change. A metaprotocol sits above that layer. It does not change the chain's rules. Instead, it defines an additional set of rules for interpreting data the chain already records.

In practice, a metaprotocol consists of three things:

1. A format. A precise description of what a protocol record looks like, so that it can be recognized among all other chain data.
2. Interpretation rules. Deterministic logic that turns an ordered sequence of records into state, for example "this Sigil references that one" or "this address holds this balance".
3. Indexers. Software that reads the chain, applies the rules and exposes the resulting state to applications.

Because the rules are deterministic, anyone running a conforming indexer against the same chain history should arrive at the same state. The chain provides ordering and data availability; the metaprotocol provides meaning.

#Why build above Elysium

Saelis builds on Elysium rather than introducing its own chain. Elysium provides the properties a metaprotocol depends on:

• Canonical ordering. Elysium produces 100 ms canonical blocks. Ordering is the foundation of deterministic interpretation.
• Standard EVM tooling. Elysium runs stock ArbOS. Wallets, viem, ethers, Foundry and Hardhat work unchanged, so Sigils can be created and read with familiar tools.
• Low-cost transactions. Fees are paid in HYPE, Hyperliquid's native asset. Inexpensive transactions matter when individual data records are published as separate pieces.
• Ecosystem alignment. Elysium settles to HyperEVM and is co-located with HyperCore. Saelis inherits a direct connection to the Hyperliquid ecosystem.

#Sigils and inscriptions

Sigils are conceptually inspired by blockchain inscriptions: arbitrary data attached to transactions and given meaning by offchain indexers rather than by smart contracts.

Saelis keeps that core insight and departs from it in three ways:

• Structure first. Many inscription systems treat content as an opaque blob with a content type. A Sigil is designed as a structured record with defined fields for identity, metadata and relationships.
• Relationships are part of the model. References between Sigils are a first-class concept, not an application-level convention layered on afterwards.
• Standards are pluggable. Interpretation is delegated to standards such as ELC-20. The base protocol does not assume that a record is an image, a token or a collectible.

#A modular data model

Composability comes from keeping each piece small and well defined. A Sigil does not need to contain an entire application. It needs to contain one meaningful unit of data and, optionally, references to the other units it relates to.

This has practical consequences:

• Incremental construction. A larger structure can be published over time, piece by piece, by one author or many.
• Reuse. A single Sigil can be referenced from more than one assembly.
• Independent verification. Each piece can be validated on its own before the structure it belongs to is evaluated.

#Pieces and larger structures

The relationship between an individual Sigil and the structure it belongs to is the central idea of Saelis. A piece has value on its own; an assembly is what emerges when pieces are connected through references and interpreted together.

#What Saelis is not

• Saelis is not a new blockchain. It runs on Elysium.
• Saelis is not a smart contract platform. It defines data formats and interpretation rules.
• Saelis is not an NFT collection or a token launcher. Some standards may describe assets; the base protocol does not.
• Saelis does not, by itself, guarantee permanent storage of offchain content. See Sigils.