Developer Documentation
Developer docs.
Technical integration documentation will live at docs.noane.io when the protocol is ready for integrators.
Direct Answer
What the docs cover.
The NOANE Developer Docs describe how integrators bind a physical asset to a custody record, verify dual-key transfer, and read tamper-evident ownership state. A full public developer reference is in progress; preview access is available through the partner program.
Documentation Index
Protocol documentation.
Documentation is available to Product Design partners and approved integrators. The sections below define the structure of the full integration documentation. Access is available via request.
01
Protocol Overview
Hardware-anchored ownership records for physical assets. How NOANE closes the gap between authentication and ownership-state control.
02
Hardware Binding
How device-associated credentials connect physical assets to ownership records. Supported secure-chip configurations and provisioning models.
03
Dual-Key Transfer
How asset-side proof and owner-side authorization work together to authorize a transfer. Neither signal alone is sufficient.
04
Ownership Record Advancement
How the protocol prevents advancement of the ownership record until required proofs are confirmed for the specific transfer.
05
Transfer Modes
Continuous Enforcement ON and Open Fulfillment. When to use each, integration differences, and compliance considerations.
06
Verification Flow
How a platform, reader, or agent verifies the physical object and record-authorized party in a single round-trip.
07
Operator Integration Layer
Verification Router, Policy Manager, Registry, Reader Authorization, and Event Stream. The integration surface for approved operators.
08
API Access
Planned integration surface for approved partners. REST and event-driven integration for the NOANE protocol layer. No endpoints published at this stage.
09
Security Model
Threat model, failure modes, policy checks, and audit readiness. How the protocol handles adversarial custody environments.
Transfer Modes
Transfer modes.
The protocol supports two transfer modes depending on the custody environment and operator policy.
Mode 01
Continuous Enforcement ON
The asset-side proof and owner-side authorization must both be confirmed for the ownership record to advance. This mode is designed for high-control custody environments where physical asset presence and ownership transfer must co-move. The record does not advance without both signals.
Mode 02
Open Fulfillment
The digital ownership record may enter an interim transfer state, but final verified ownership does not settle until the receiving party confirms asset-side proof through the hardware device. Designed for supply-chain environments where physical handoff and record settlement may not be simultaneous.
Custody Glossary
Custody glossary.
Terms used throughout the protocol documentation. The hierarchy is fixed: authentication identifies the asset, custody is the mechanism that holds and advances the record, ownership is the state the custody record reflects.
Authentication
Confirms that an asset is what the record claims it is. Answers what. Does not answer who holds it or who can transfer it.
Tracking
A historical record of where an asset has been. Answers where. Does not answer who holds it now or who can transfer it next.
Custody
The cryptographic mechanism that records who currently holds the asset and who has the authority to advance the record. The protocol's core function.
Ownership
The state that the custody record reflects at any given moment. Ownership changes only when the protocol advances the custody record under a verified dual-key transfer.
Asset-side proof
A signature from the hardware credential bound to the physical asset, confirming the asset is present at the moment of transfer.
Owner-side authorization
A signature from the current record-authorized party, confirming the right to advance the custody record to a new holder.
Custody record advancement
The protocol-controlled state change in which the on-chain record is updated from the current holder to the next. Conditioned on both proofs for the specific transfer.
Agent-verifiable
A property of the custody record indicating that an autonomous agent can resolve current custody in a single cryptographic round-trip, without human attestation.
Verification Sequence
An agent verifies custody.
The protocol resolves custody in a single round-trip. Five steps, one signature-backed answer.
01
Agent presents asset reference
An autonomous agent submits the asset's hardware identifier and the proposed transfer context to the Verification Router.
02
Protocol resolves custody record
The router queries the on-chain custody record for the current record-authorized owner and the active policy mode.
03
Asset-side proof requested
The hardware credential signs a freshness challenge, confirming the physical asset is present at the verification moment.
04
Policy and authorization check
The Policy Manager confirms the requested operation is permitted under the asset class's transfer mode and that the agent's reader is authorized.
05
Signature-backed answer returned
The protocol returns the current custody state and the conditions under which it would advance. The agent transacts on cryptographic proof, not on a cached claim.
Operator Integration Layer
Operator integration layer.
The operator integration layer exposes the ownership verification flow to approved platforms, brands, and agent workflows without requiring integrators to rebuild the protocol.
01
Verification Router
Routes asset-side proofs, owner authorizations, and transfer-state checks into a single verification flow.
02
Policy Manager
Defines whether a collection, asset class, or integration requires continuous enforcement or open fulfillment.
03
Registry
Maps assets, hardware identities, ownership records, and integration permissions.
04
Reader Authorization
Controls which operators, devices, or environments may initiate verification workflows.
05
Event Stream
Emits registration, binding, transfer, settlement, rejection, and verification events for integrators.
See how operators, platforms, and agents inherit verified custody once a brand integrates. Read the integration topology.
Early Access
Request documentation access.
Product Design partners and qualified integrators can request early access to protocol documentation. Documentation does not include fabricated endpoints or sample code.
Request AccessRelated Research
Architecture-level reference.
For an architecture-level technical reference, see the NOANE Infrastructure Response Paper V2.