Permanent Storage

When you publish on Rising Tide, the record of that work - what it is, who made it, who owns each numbered edition, and how every payment split - is written on-chain at the moment of publication. That record is permanent. It cannot be altered or deleted by anyone, including the Rising Tide team, and it does not depend on any app or server to keep existing.

What is permanent from the moment you publish

• The work itself, as a product - its contract lives on-chain, under your publishing identity rather than a platform account
• Every numbered edition - who collected it, when, and every transfer since
• The economics - the revenue splits you set, executed and recorded with each collect

All of this is retrievable from the public chain without going through Rising Tide.

Saved: where the artwork lives day to day

The moment a piece finishes rendering, Rising Tide saves it. That saved copy is what the apps, wallets and link previews read - fast, current, and always there.

Saving is automatic and it never fails for lack of room. You do not do anything, and you do not pay for it.

Saved is a resting state, not a queue. Most editions live there quite happily.

Save As: your own permanent copy

Permanent storage is a decentralized network designed to keep data readable forever. Writing your edition into it is called Save As, and it is something you do, not something we do for you.

That distinction is the whole design. The copy is signed with your key, so what lands there is yours in the strongest sense the technology allows: it does not depend on us, and we could not remove it if we wanted to.

Here is how it goes:

1. Turn on storage on your Storage page. Rising Tide creates a storage key that belongs to you - you can export it - and it comes with free room to write with.
2. Choose an edition you own and pick Save As. Your key signs the copy, right there in your browser.
3. Your edition points at it. Once the permanent copy is verified complete and readable, your edition's on-chain record is pointed at it.

After that:

• The copy is permanent - once written it can never be deleted or altered by anyone
• It does not need us - the piece is retrievable directly from any public gateway, with no login and no intermediary
• It is checked before it is pinned - a copy that would be broken forever is refused, and you try again rather than being left with a dead link
• You can Save again - a fresh copy, whenever you want, with your edition pointed at the new one. Every copy written along the way stays readable forever

Only the public record is saved this way. Anything the protocol treats as private - a private note left with a collect, for example - never leaves protocol storage.

Room, and what it costs

Your storage key comes with a free lifetime allowance, and it is generous: enough for a couple of hundred editions. The Storage page shows what is left in a number you can actually use - roughly how many more pieces it will hold.

Adding room with a card is not offered yet. Most people never come close to the allowance.

Turning it on for everything

There is a switch on the Storage page that runs Save As for you on editions you own, as they become eligible. It uses the same key and the same free room; the only difference is that you are not clicking each time.

Finding your permanent copies

The Hub's Storage page has an Arweave section listing each item you have written there, with its transaction ID, live confirmation status and a copy button. That ID is all anyone needs to retrieve the piece from any public gateway, today or decades from now.

That one section is named for the storage network the protocol uses today, because the ID it shows you is only meaningful on that network. Everywhere else these pages say permanent storage, because which network holds the copy is a choice - and more than one will be offered.

The three records, plainly

• The chain - the permanent record of what exists, who owns it, and what was paid. Written at publication, never changeable
• The saved copy - the everyday copy that powers the apps: fast, current, always reflecting the latest state. Ours to keep working
• The permanent copy - the frozen copy you wrote with your own key: permanent, independent, and readable even in a world where Rising Tide is gone

Publishing puts you on the first two. Save As adds the third, and the third one is yours.

If you signed in with your own wallet

Save As works, and you sign it yourself: Save As on an edition asks your wallet to sign the write, the way it signs anything else you do here. There is no storage key made for you, because your wallet is the key.

What you do not get is the automatic part. The switch that runs Save As for you, and the step that points an edition at its permanent copy once one is verified, both need a key Rising Tide can sign with on your behalf, and yours is not. Save As by hand on each edition you want a permanent copy of; the Storage page shows which ones have one.

Two things hold either way. Everything you publish is still saved, exactly as it is for anyone else. And your work is still permanently recorded on chain from the moment you publish; the third copy, the one under a key of your own, is the one you write by hand.