sarn

Your AI agent, set in stone. Its definition and skills inscribed on solana, byte for byte.

[sarn @sarndotfun]

Sarn launches today on Solana mainnet.

Write an agent, lay it on-chain byte for byte, and it's sealed for good. Then summon it: chat on its page, or pull it into Claude Code or Cursor. No platform fee.

https://t.co/15DxBcTo0O

[sarn @sarndotfun]

Forever is getting cheaper.

Solana is cutting rent per byte in five steps, from 6,960 lamports to 696. Step 2 is live: 5,080.

An 18 KB agent on Sarn: 0.129 SOL of rent before, 0.094 today, about 0.013 after the last step. Sarn's fee: 0.

https://t.co/15DxBcTo0O

[sarn @sarndotfun]

Last, the cost and the point of no return.

Review shows the exact total from the RPC: rent, Metaplex's create fee, network fees. Then you tick "public and permanent."

Bytes go in chunk by chunk. Until the seal, close the draft and the rent comes back. After it, no key is left.

[sarn @sarndotfun]

Forever cuts both ways.

A sealed stone can't be edited, so Sarn checks before the first byte is written: a pasted key blocks the lay, and content is checked against the exact bundle hash.

Until the seal, you can close the draft and get the rent back.

https://t.co/15DxBcTo0O

[sarn @sarndotfun]

Then the content.

Before a single byte goes on-chain, the bundle gets a content check, and the verdict is saved against its SHA-256.

The seal is only co-signed for a passing verdict on that exact hash. Change one byte after the check, and there's no seal.

[sarn @sarndotfun]

Sealed, not silent.

Every agent on Sarn can be summoned: chat with it on its page, or pull it into Claude Code or Cursor with one command.

The CLI checks every byte against the chain before it writes a single file.

[sarn @sarndotfun]

That's the whole check: two accounts, one hash, one empty list.

The Sarn CLI will run it before it writes a single file to your machine, and every stone page will rerun the hash in your browser.

But you'll never need us to run it.

[sarn @sarndotfun]

Don't trust us. Check the stone.

Every agent laid on Sarn will be checkable by anyone, with nothing but a Solana RPC and SHA-256. No Sarn server in the loop.

Here's the whole check, step by step

[sarn @sarndotfun]

Step 5. Check the number.

The stone attribute comes from the collection's mint counter. Sarn's verify_seal instruction checks it in the same transaction that creates and seals the stone.

Two people laying at once can't both get No. 418. No gaps, no duplicates.

[sarn @sarndotfun]

https://t.co/nrgkKZ22uA