Open format · Governed network

ANYPAYLOAD.ONE OPENNETWORK.

OpenPayload is a neutral transport for application-defined data. Payloads move off-chain; chain-published policies coordinate who may handle them, where they may go, and the boundaries every participant follows.

Explore the protocol →Start building ↗
FORMAT / OPENDATA / OFF-CHAINPOLICY / ON-CHAIN
LIVE ROUTEOP/001
OPENPAYLOADFORMAT-NEUTRAL ENVELOPE
{ }EVENT.JSON2.4 KB
0101CHUNK.BIN64 KB
≈STATE.STREAMLIVE

CONTENT IS APPLICATION-DEFINED
CONTROL IS PUBLICLY RESOLVABLE

01 / THE PROTOCOL

The format stays open.
Intent gains structure.

OpenPayload separates the thing being moved from the rules that shape its journey. Applications own their data model. The network supplies identity-aware transport and a shared control plane.

DATA PLANEOFF-CHAIN

Arbitrary payloads move at network speed.

Events, binaries, commands, telemetry, multipart packages, and encrypted application data travel through Directory, Relay, and Cache services.

CONTROL PLANEON-CHAIN

Intent and authority publish as shared state.

Identity, service records, scoped delivery intent, version history, and infrastructure commitments are finalized once and resolved consistently.

02 / OPEN BY DESIGN

Bring your own
meaning.

OpenPayload defines the transport boundary, not your product category. The envelope is stable; the content remains yours to invent.

01JSON / CBOR

Structured events

Move application-defined events without forcing every system into a platform-owned schema.

02BINARY / CHUNKS

Files and media

Break larger payloads into verifiable parts and route them through the same open transport surface.

03STREAM / SIGNAL

Telemetry and state

Carry sensor readings, device state, logs, and live updates across intermittent edges.

04COMMAND / CUSTOM

Formats not invented yet

Keep the network neutral so builders can define new envelopes without waiting for a central roadmap.

03 / ONE RESOLVED DECISION

Structure without
owning the payload.

The network resolves finalized intent once for a delivery attempt, then carries the same bounded decision across permitted services without putting payload content on chain.

01

Encapsulate

Wrap any application payload in a signed, bounded envelope.

02

Resolve

Select the most specific finalized intent for the destination context.

03

Bind

Carry one policy decision and its boundaries through the delivery attempt.

04

Deliver

Let each permitted service apply the same scoped outcome.

APPLICATION→OPEN ENVELOPE→FINALIZED DECISION→BOUNDED SERVICES→DESTINATION

04 / CHAIN-PUBLISHED POLICY

Publish intent. Carry one decision.

A policy can express several context-aware delivery outcomes under one version. The network selects the most specific applicable intent from finalized state, keeps it inside shared safety bounds, and carries that decision through the delivery. Relays, caches, archives, and destinations apply the same outcome instead of reinterpreting changing state at every hop.

  • 01 Scoped intent for an identity or Persona
  • 02 Deterministic selection across multiple rules
  • 03 Delivery, retention, and replication stay bounded
  • 04 One resolved version governs each delivery attempt
POLICY CAPABILITYFINALIZED
ONE DECISION. EVERY HOP.
SCOPEidentity + Persona context
SELECTmost specific applicable intent
BOUNDlimits may narrow, never widen
DIRECTpermitted services + fallback behavior
CONTINUEsame finalized decision through delivery

Conceptual capability view. Public payload contents and application logic remain outside policy state.

05 / GOVERNANCE LOOP

Publish once.
Coordinate everywhere.

Finalized intent coordinates compatible services without publishing payload contents or handing control to a central operator.

01

Propose

Publish a new policy, authority, or network parameter.

02

Finalize

Validators establish one canonical, authorized state.

03

Carry

Bind the selected version and boundaries to one delivery attempt.

04

Enforce

Compatible services apply the same outcome at the data plane.

06 / COMMUNITY-OPERATED

One network.
Distinct roles.

OpenPayload distributes responsibility across services that can evolve independently while following the same public state.

01

Directory

Resolve identity, keys, services, and applicable scoped intent.

02

Relay

Select and carry the finalized outcome while moving live payloads.

03

Cache

Provide policy-limited transient custody when endpoints are unavailable.

04

Validator

Finalize shared state and attest verifiable participation.

CONCEPT BRIEF / 01

Open research sensor network

See arbitrary field observations move under project identity and chain-published collection policy.

Read the architecture →CONCEPT BRIEF / 02

Policy-directed payload relay

See identity, scoped intent, multipart envelopes, and bounded services compose into one resolved delivery.

Read the architecture →
APPLICATION OVERLAY / 03
T
Talaria Chatdid:openpayload:…hello
LIVE

Ready when you are.

Hello, open network.

DELIVERED · NOW
IDENTITYRELAY / LIVE
ANDROID ALPHAMANDOLARE LLC

Talaria Chat App

Mandolare LLC's messaging overlay demonstrates how a focused application can use OpenPayload identity, live relay delivery, and transient routing.

Build an overlay ↗APP STORES · COMING SOON

07 / BUILD IN THE OPEN

Define the payload.
Share the rails.

Build applications, operate infrastructure, publish policy, and help shape an open network for data that does not fit inside someone else's box.

Read the quickstart ↗Review the source →