Authorization Object Network

A distributed object propagation network for authorized state transitions.

Institutions are no longer required.

Most coordination systems retain authorization. Assets are deposited before trading. Permissions are stored before future execution. Authority accumulates inside the coordinating layer whether or not that was the intention.

AON externalizes authorization into independently addressable objects that propagate across a peer-to-peer network. Execution emerges when authorization, conditions, and proofs form a satisfiable graph. No system retains permission on behalf of participants.

Object model

Authorization: explicit, signed permission for a bounded action.
Condition: a requirement that must be satisfied before execution.
Reserve: committed settlement state pending execution.
Proof: evidence that a condition has been met.
Receipt: a record that execution completed.
Revocation: a signed declaration that an authorization is no longer valid.
Namespace Manifest: defines the execution semantics for a namespace.

Namespaces

AON does not define business logic. Namespaces define it. The network transports objects; namespaces determine what those objects mean and how execution occurs.

Two namespaces are implemented in the reference node: aon:csd-usdc for cross-chain settlement between CSD and USDC on EVM, and aon:evm-spot for non-custodial EVM spot trading. New namespaces may be defined and implemented without modifying the protocol.

Participate

Run a node: store and propagate objects, discover executable graphs.
Write an executor: discover opportunities, execute transitions, collect rewards.
Define a namespace: specify authorization semantics for a new environment.
Build a client: publish authorizations on behalf of users.

Resources