Skip to documentation
Reality-grade bankingDocumentationOpen implementation
Documentation contents

Assets & market

Publish, share and preserve an Original

Make the intended work public while keeping sealing, funding, local adoption and anonymous delivery distinct.

Reviewed 2026-10-25 · SDK 129.0.0Read Markdown ↗

Review the public payload

Public-original creation deliberately publishes the authored original, cover, attachments, full text and public details. Inspect them before creation. Supplied credits and descriptions remain their own claims; publishing a work does not grant rights that its source does not establish. Private account execution receipts and identity authority are outside ordinary public-original publication.

  1. Review the composer

    Check the exact original and every public attachment/text field.

  2. Create the source

    Use the selected public or backed path.

  3. Save original proof

    Preserve the canonical artifact before depending on a public link.

  4. Check public delivery

    Use the actual completed or pending result and its existing continuation.

Read the completion message

Sealing and public delivery answer different questions
DisplayMeaning
Your asset is sealed.The canonical source is retained.
Public delivery is pending…Local sealing/adoption is complete, anonymous delivery is not yet established.
Public delivery needs attention…Delivery requires resolution; the original remains retained.
Your asset is public.Required public document/discovery completion is established.

Retry the same source

Retry public delivery uses the retained artifact, digest and placement. For a backed asset it continues after the original funding result rather than creating another financial operation. If funding itself is unknown, Continue creation resolves that exact request first. Immediate appearance in your local profile/Market does not independently establish that an anonymous visitor can already retrieve the work.

Share the actual public route

Open the completed asset page or profile and use its supported public link. A canonical original remains the authority behind the public view. Media playback can use the supported public stream while complete independent proof stays available separately. A supported embed/player presents the same source; it is not a new issuer, ownership certificate or grant to access private material.

Preserve later inspection

Keep complete original bytes and supporting source relationships. A screenshot, edited media export or image service that strips carried proof can no longer stand in for that Original. A public proof records its evidence at the admitted coordinate. Removing a future update or changing a public view does not erase already distributed genuine sources. Treat media codec support, host delivery and future publication as specific boundaries rather than reasons to replace original proof with a weaker display.

Implementation sources

Inspect the exact path.

Source links retain revision 6c5d582. Read the documented operation and assessment scope alongside its code.