TradeTrust Concepts

This section explains the core TradeTrust concepts used by BlockPeer Trade APIs, without requiring Integrating Systems to implement TradeTrust directly.

What is TradeTrust (in this context)

TradeTrust is an open framework for creating verifiable, transferable electronic trade documents that are legally aligned with UNCITRAL MLETR.

BlockPeer Trade APIs generate and manage documents that conform to TradeTrust standards.


Electronic Transferable Records (ETRs)

An ETR is a digital document that:

  • Represents a transferable trade instrument
  • Exists in a single authoritative form
  • Can be transferred or endorsed
  • Has a clear controller at any point in time

Examples:

  • Electronic Bill of Lading (eBL)
  • Electronic Promissory Note (ePN)

Token Registry

A Token Registry is the control layer for ETRs.

It:

  • Records who controls a document
  • Enforces transfer and endorsement rules
  • Maintains the current state of each document

Each eBL / ETR is issued against a registry.


Roles & control

TradeTrust defines roles such as:

  • Issuer
  • Holder
  • Beneficiary
  • Owner

BlockPeer Trade APIs allow Integrating Systems to:

  • Assign roles
  • Query current role status
  • Transfer control between roles

Endorsement & transfer

ETR lifecycle actions include:

  • Transfer of holding
  • Nomination of beneficiary
  • Endorsement of ownership
  • Rejection of transfers
  • Return to issuer

Each action:

  • Requires End User approval
  • Preserves document singularity
  • Updates the TradeTrust control state

Verification

TradeTrust documents can be independently verified to confirm:

  • Document integrity
  • Issuer identity
  • Current controller
  • Valid endorsement chain

BlockPeer provides verification APIs, but documents remain verifiable outside BlockPeer as well.


Why this matters

  • Interoperability across platforms
  • No vendor lock-in
  • Legal recognition under MLETR
  • Bank-grade trust and auditability

Summary

  • Trade APIs operate on TradeTrust-compliant ETRs
  • Integrating Systems use REST APIs
  • End Users approve actions via redirect + passkeys
  • BlockPeer orchestrates, not controls