Share proof without sharing private authority

Choose the right public proof

A public asset, a selected Vault proof and a complete account proof have different disclosure scopes. A private original can carry access authority or sensitive history and must not be published merely to show an amount. A local export or retained private source is not public sharing; publication is its own deliberate operation.

Publish an account proof deliberately

1. Open Share an account proof

   Choose Review account proof and inspect the exact source/disclosure.

2. Approve the named content

   The approval explicitly covers publishing balances, holdings and full transaction history.

3. Choose future updates separately

   Enable them only if that continuing publication is intended.

4. Create proof image & link

   Keep the published original and its exact reference. A changed source requires new source review.

Control future updates

Public sharing provides Check public sharing and Turn off live updates for future publication behavior. Turning off updates does not retract already distributed copies or erase genuine historical evidence. A source-change refusal cannot silently reuse old approval for new facts. Keep a record of what was approved and the proof coordinate that was shared.

Inspect without taking custody

A recipient can verify the disclosed original in its matching public or standalone reader. They receive evidence, not private account or Vault access. A genuine historical proof remains genuine but does not assert that every holding remains unspent today. A QR identifies a source; it does not create the missing source, publish an unpublished file or authorize a transfer.

• Read public evidence correctly ↗

Protect the private original

• Never post the private Vault bearer PNG when intending to share a public Vault proof.
• Keep Identity Records, phrases, private archives and protected financial sources out of public messages and model context.
• Check original media, attachments and full text before public asset creation.
• Use public-safe references for support, and preserve the exact private source under your own control.
• Treat onward copies as persistent disclosure even after future sharing is disabled.