Warehouse Receipts
Control Desk
Work with warehouse receipts in domain terms while the app translates each action into the general OpenETR protocol. This workflow is being built in alignment with the Model Law on Warehouse Receipts (MLWR).
The receipt is a Digital Artifact identified by byte identity: the digest of its exact bytes. Its Anchor Record and later Evidence Events form a Digital Controllable Record (DCR) from which receipt state is derived.
Read-only mode: query receipt DCR evidence and derived state without logging in. Log in to sign records through a warehouse operator or issuer Commitment Profile.
Query Receipt DCR
Upload a warehouse receipt Digital Artifact and verify the OpenETR DCR evidence associated with its byte identity, including derived holder/controller state and lifecycle state.
Create Anchor Record
Publish a signed kind 1415 Anchor Record concerning the byte identity of an already-issued warehouse receipt Digital Artifact. The Anchor begins its candidate DCR; later kind 1416 Evidence Events express transfer, pledge, release, presentation, and lifecycle completion.
Domain Actions
These receipt actions are domain names for signed Evidence Events in an OpenETR DCR. Query or create an Anchor Record first, then use the receipt-state page to transfer, pledge, release, present, or complete the receipt lifecycle.
- Transfer receipt: maps to
openetr transfer initiateandopenetr transfer accept. - Record pledge or lien: maps to
openetr encumberwith the secured party as beneficiary. - Release pledge or lien: maps to
openetr dischargereferencing the encumbrance event. - Present for delivery: maps to
openetr redeemwith the warehouse operator as obligor. - Complete delivery: maps to
openetr terminate-etrafter the receipt lifecycle is complete.
Recognition Boundary
OpenETR validates DCR evidence and derives consequential receipt state under stated rules. MLWR-style law, local enactment, registry rules, contract, and institutional policy decide legal validity, protected-holder status, pledge effect, priority, warehouse obligations, and final recognition.
OpenETR Trivia
In an OpenETR integration, MLWR-style rules belong in a domain adapter and recognition policy rather than in the base wire format.