Why Publishing a Proof Costs Money

Publishing a CardanoWall proof costs money because a gateway pays real costs on your behalf. Every published proof needs a Cardano transaction, and the network charges a fee to include it. Proofs that carry a file also need that file stored, and storage has a real per-byte cost. On top of those pass-through costs, CardanoWall adds a service margin so the hosted gateway — the thing that funds the wallets, prices the conversion, submits the transaction, and waits for confirmation — can keep running.

The short version: the Label 309 standard is open and free to read, implement, and verify against. Publishing still consumes resources, and someone has to pay for them.

What are you actually paying for?

You are paying for a publishing service, not for the proof itself.

A Label 309 proof is more than a line of text in a web form. To turn your content into an on-chain record, the gateway does real work:

quotes the cost before you commit;
uploads public content or encrypted ciphertext when a file is involved;
pays the storage cost for those bytes;
builds a Cardano transaction;
pays the network fee;
submits the transaction and waits for confirmation;
handles retries, reorgs, and failures;
indexes the record into the public feed;
updates your account balance;
exposes status through the web app, the API, or the command-line tool.

Some of that is direct network or storage cost. The rest is operational cost. A hosted gateway has to cover both, because both are real.

What goes into the price?

The price breaks down into three practical parts:

The Cardano network fee.
The storage cost, when a file is involved.
The service margin.

The network fee is what Cardano charges to anchor the transaction. The gateway estimates it precisely from the actual transaction it is about to build, so the figure you see reflects the real submission, not a rough guess.

The storage cost applies only when bytes need to be stored through the gateway's storage path. A hash-only record carries almost nothing, so it costs almost nothing to store. A sealed file proof, by contrast, puts encrypted bytes into storage, and those bytes are priced by size.

The service margin is the gateway's markup over those pass-through costs. It covers operations, infrastructure, the funding rails that keep wallets topped up, exchange-rate risk, monitoring, support, and the ordinary business cost of running a hosted service.

Why does CardanoWall quote a price first?

Because the real cost depends on live conditions, and you should see the number before you commit to it.

Cardano fees, storage prices, the ADA and AR exchange rates, the record size, the file size, and the number of recipients all feed into the final figure. Rather than charge you a price you never saw, CardanoWall's gateway issues a quote: it computes the cost from a live exchange-rate snapshot, locks that price for a fixed window, and lets you review and submit without the number moving underneath you.

The quote currently stays valid for 15 minutes. If it expires before you publish, the app silently fetches a fresh quote — it never makes you reload the page or re-enter your work. The new price may differ if the market moved, but that is honest: it is better than charging a stale price for a transaction whose real cost has changed.

The exchange rates that price a quote come from live market data, never from a hardcoded fallback. If that data is briefly unavailable, the gateway tells you pricing is temporarily unavailable and asks you to retry, rather than inventing a number and mis-billing you.

What is the service margin, and why isn't it zero?

CardanoWall currently applies a default service margin of 50% on top of the combined network and storage cost, with a minimum floor of 10% so that any discount or per-account override still can't price the service below a sustainable level.

These are configuration values for CardanoWall's hosted service today — not a property of the standard, and not fixed forever. Label 309 itself says nothing about price. Any operator who runs a gateway sets their own margin, and CardanoWall may offer different terms to specific accounts, partners, or open-source maintainers who help the ecosystem.

A margin of zero isn't realistic for a hosted service, because the costs don't vanish just because the proof standard is open. Even charging only the exact network fee, an operator still faces:

buying and holding ADA to pay Cardano fees;
funding the Arweave storage rail in advance;
exchange-rate conversion and keeping rates fresh;
failed and retried operations;
account-balance management;
payment-processor fees;
monitoring, infrastructure, and security operations;
support and abuse handling;
capital tied up in funded wallets.

A 0% hosted margin would mean someone else subsidizes every publish, until the service quietly becomes unreliable. The point of the markup is transparency, not opacity: you are paying for a running service, not just for a blockchain fee.

What does it cost if I only publish a hash?

A hash-only proof is the cheapest kind you can publish.

It stores no file through the gateway, so there is no per-byte storage cost — only the Cardano transaction and the margin around running the publish flow. This is the right choice when you already host your own files, or when all you need is a public, timestamped commitment to a digest. Hashing a 4 GB video and publishing only its hash costs the same as hashing a one-line text file: the proof is the digest, and the digest is a fixed size.

If you attach files, seal content, or publish larger records, the cost rises, because the gateway then has more bytes to store and more record data to anchor.

What does it cost to attach an encrypted file?

This is where storage becomes part of the price.

For a sealed proof, the file is encrypted on your device before anything leaves it. The on-chain record commits to the hash of the plaintext and points to the ciphertext, which is stored on Arweave through the gateway. Those encrypted bytes have a real per-byte cost, so a larger sealed file costs more to publish than a smaller one.

There is a small free-storage allowance — currently the first 100 KiB (102,400 bytes) — so that tiny records, manifests, and identity envelopes don't accrue a storage charge at all. Only the bytes beyond that allowance are priced. As always, the gateway's quote is the authoritative figure for any given publish.

Does CardanoWall charge to verify a proof?

No. Verification is meant to work without trusting CardanoWall at all, so charging for it would defeat the purpose.

Anyone can verify a Label 309 record from public data: the transaction metadata from a public Cardano explorer, and — where relevant — the content bytes, signatures, ciphertext, keys, or Merkle material. The CardanoWall website makes that convenient, but the open-source SDKs and command-line tool verify the same records with no CardanoWall account and no CardanoWall server in the path.

A hosted product can reasonably charge for publishing, accounts, storage, or API usage. What it must never do is make a proof meaningful only because a paid server says so. Publishing is the service; verification stays portable. (For where a proof's guarantees end, see what a proof does not prove.)

Can I avoid CardanoWall's service margin?

Yes — by not using CardanoWall as your hosted operator.

Because the gateway is open source, a developer or company can run their own Label 309 gateway, fund their own Cardano and storage wallets, and publish standard records through their own infrastructure. The records that come out are identical, and anyone can still verify them with no dependency on you or on CardanoWall.

That doesn't make publishing free. You still pay the network fee and the storage cost — those are the chain's and Arweave's prices, not CardanoWall's. You also take on everything a hosted operator otherwise handles for you: infrastructure, monitoring, key management, provider relationships, wallet funding, upgrades, and operational risk. What you no longer pay is CardanoWall's service margin, because now you are the operator. If you're weighing that trade-off, it helps to first understand what a Label 309 gateway actually is.

When does running your own gateway make sense?

Self-hosting makes sense when control matters more than convenience. Common cases:

high-volume CI/CD proof pipelines;
companies with strict vendor policies;
regulated or compliance-driven workflows;
internal archives that must avoid an external dependency;
AI provenance systems publishing at scale;
legal-evidence platforms;
products that want their own billing and margin on top;
teams that already operate blockchain or storage infrastructure.

For individuals and many small teams, the hosted CardanoWall service is simply less to run. For organizations with volume or policy requirements, self-hosting may be the better economic and governance choice. The trade-off is convenience versus control — and the answer depends on the workflow, not on the proof, which is the same either way.

Why offer discounts to open source and partners?

Because not every user creates the same kind of value.

Maintainers of important open-source projects, infrastructure partners, research efforts, and public-good integrations can help Label 309 adoption in ways that don't show up as direct revenue. Discounted or partner pricing can make sense for those cases. Even then, the cost floor still applies: a gateway that publishes below cost for everyone is not a gateway that survives.

How should I think about the price?

Think in terms of trust and workload.

If you publish one proof now and then, the price buys convenience: you skip running a gateway, funding wallets, managing a storage provider, and writing publishing code.

If you publish thousands or millions of proofs, the economics shift. You'll likely want one record that anchors thousands of files via a Merkle root, the command-line tool in your automation, per-account terms, or your own gateway.

And if you're proving high-value evidence, the price of a proof is usually small next to the cost of not being able to prove the timeline later.

In short

CardanoWall charges for publishing because publishing has real, unavoidable costs. The hosted gateway pays the Cardano fee and any storage cost, runs the infrastructure, manages balances, handles failures and refunds, and adds a service margin on top — currently a 50% default with a 10% floor, both of which are CardanoWall's configuration rather than anything the standard mandates.

Want convenience? Use the hosted service. Want full operator control and no service margin? Run your own gateway and fund it directly. Either way the records are the same, and anyone can verify them without paying anyone.

The standard is open. The infrastructure still has to be paid for.