SPL-SEAL*

Sealstate

Seal, tokenize, and transfer encrypted private intellect on Solana.

Sealstate is infrastructure for portable, verifiable, encrypted AI state. It gives developers and agents a standardized way to move state between environments, prove what they had and when, and control who can see it.

The core primitive is the capsule — an encrypted, versioned container with cryptographic commitments that bind content to its history. Capsules hold anything: prompts, model weights, agent configurations, training data, research artifacts, or whatever else needs to be sealed, verified, and shared.

The protocol operates at three tiers, each adding a cryptographic or economic property. Seal for encryption and integrity verification. Register to add timestamped provenance and verifiable continuity on-chain. Tokenize to add consumptive, market-priced access. Same capsule format, same encryption, same verification at every tier.
ERC-1251TOKEN STANDARD

SPL-SEAL

A minimal on-chain primitive for publishing encrypted AI artifacts as fungible, burn-gated access tokens. The standard specifies the checkpoint ledger format, redemption mechanics, and off-chain storage conventions — nothing more.

01Checkpoint ledger

An append-only, hash-linked chain of state commitments embedded directly in the program account. Every checkpoint is immutable, time-ordered, and verifiable back to genesis.

02Burn-to-redeem

Tokens are irrevocably destroyed on access. Redemption is consumptive — eliminating the double-spend problem inherent in balance-check access models.

03Off-chain secrecy

The program stores only commitments and pointers. Decryption keys, plaintext, and encryption parameters never appear on-chain.

04One program

A single address serves as fungible access token, continuity ledger, and burn-gated entitlement surface.

ISealFi.ts
interface ISealFi {
  publisher: PublicKey;
  head: Buffer;
  checkpointCount: number;

  publish(
    stateCommitment: Buffer,
    ciphertextHash: Buffer,
    ciphertextUri: string,
    label: string
  ): Promise<TransactionSignature>;

  redeem(checkpointId: Buffer): Promise<TransactionSignature>;
  hasRedeemed(account: PublicKey, id: Buffer): Promise<boolean>;
}

DEPLOYED ON SOLANA

SealFiLaunchFactory

Launchpad — deploys token + Raydium pool

SEALfac...1111 ↗

SealFiVault

Holds LP positions, distributes fees

SEALvlt...2222 ↗

FeeCollector

Platform fee treasury

SEALfee...3333 ↗

SealFiProgram (impl)

SPL-SEAL clone template

SEALprg...4444 ↗

Why it matters

The missing primitive
The missing primitiveTHE PROBLEM

The contemporary internet possesses no credibly neutral mechanism for publishing private computational artifacts with simultaneous guarantees of global addressability, cryptographic integrity, temporal ordering, and programmable access control. Existing infrastructure conflates hosting with authorization: platforms that store files also arbitrate who may retrieve them. SEALSTATE eliminates this conflation entirely.

AI RESEARCH

Epistemic infrastructure

Reproducibility in machine learning remains structurally deficient. SEALSTATE introduces cryptographically committed checkpoints as the fundamental unit of scientific disclosure — each artifact sealed at a deterministic point in time with a hash-linked predecessor chain, creating a tamper-evident lineage independently verifiable without reliance on any institutional intermediary. This architecture natively enables staged disclosure.

Intelligence as a capital asset
Intelligence as a capital assetTOKENIZATION

SEALSTATE reconceives access to evolving AI state not as a subscription managed by a platform, but as a first-class bearer instrument on Solana. Markets can price a capsule token on expected future utility, the cultural significance of the underlying intelligence, and the publisher's demonstrated commitment to shipping high-value checkpoints. The result is price discovery for private information goods.

PRIVACY

Sovereignty over cognitive output

Privacy in SEALSTATE is not a policy layer applied after the fact but the default cryptographic posture of every artifact from the moment of creation. Payloads are sealed client-side before any interaction with the network. Access is mediated exclusively through key envelopes bound to on-chain entitlements — the act of granting or revoking visibility is itself a verifiable state transition.

Flow

Click any step to see how it works. The creator flow tokenizes and seals state. The consumer flow redeems and reconstructs it.

PUBLISHER

→
→
→
Solana

CONSUMER

→
→
→
The flow above illustrates the tokenized path — the most complete configuration. But tokenization is an access control layer, not the fundamental operation. The core is the pipeline: deterministic serialization, encryption, and commitment. That pipeline runs identically with or without a token layer.

Build on seal.

The TypeScript SDK handles the full protocol loop. Seal capsules off-chain, publish to the registry, or tokenize with SPL-SEAL.

seal.ts
import {
  createCapsule, seal, sealAndUpload,
  wrapKeyForRecipient,
  generateEncryptionKeyPair, ArweaveStorage,
} from '@sealstate/sdk';

// Create a capsule — put anything inside
const capsule = createCapsule(
  { model: 'gpt-4o', memory: ['...'] },
  { schema: 'agent-config/v1' },
);

// Seal: serialize → commit → encrypt (no chain)
const sealed = seal(capsule);

// Upload ciphertext to Arweave
const storage = new ArweaveStorage({ gateway: 'https://arweave.net' });
const { uri, receipt } = await sealAndUpload(capsule, storage);

// Wrap key for a specific recipient
const envelope = wrapKeyForRecipient(
  sealed.encryptionKey,
  recipient.publicKey,
  sender.secretKey,
);
npm install @sealstate/sdkView on GitHub →

Learn

SEALSTATE is schema-agnostic. The protocol defines the envelope — serialization, encryption, commitment, continuity — but does not dictate what goes inside.

Prompt Systems

Tokenize access to a living prompt package — system prompt, tool policy, routing logic, eval cases. Holders decrypt the latest version; the author ships updates as new checkpoints.

Agent Identity

An agent exports its full cognitive state as a sealed capsule — identity kernel, execution manifest, memory index. It can be resumed by anyone with the right keys on any compatible runtime.

Model Configurations

Publish encrypted fine-tuning configs, LoRA weights, or inference parameters as a paid stream. Each checkpoint is a new version.

Training Data

Gate access to curated datasets with verifiable provenance and append-only history. Consumers verify data integrity against on-chain commitments.

Research Artifacts

Anchor experiment states on-chain with timestamps, prove priority, and monetize access. Commit sealed results immediately, disclose later.

Custom Schemas

The capsule format is schema-agnostic. If it serializes to JSON, SEALSTATE can encrypt it, commit it, and build a market around it.

Read the documentation →