Sign in
Each action uses a Fabric certificate for the selected business role. Your instructor holds the signing keys on this teaching server.
Process your order
Use one order throughout. Prices are in cents: 610000 = $6,100.00. Fabric has no Ethereum-style gas fee. Payment records are simulated confirmations.
Control tests: try accepting as MyBikes.com; after factory release, try invoicing 610100 as Specialized.com. Neither attempt should change the order. A rejection during endorsement may never enter a block.
Current order state
No order loaded.
View full order record
Ledger history · Order transactions
Each row is a committed transaction that changed your order. The block-number column identifies the block containing it. Multiple transactions can share a block, and gaps in block numbers can reflect other channel activity. This is your order history, not a list of every transaction on the channel.
| Action / time | Order status | Transaction ID | Block number | Details |
|---|
Decode block JSON
What this lab demonstrates
Org1 represents the buyer side; Org2 represents the seller side. Merida, oracle, bank, and auditor are roles within these organizations, rather than independent organizations in this small deployment. Both peers maintain the channel ledger, but all nodes share one host and administrator.
A delivery report does not prove physical delivery. A Paid status is not an audit opinion. Recording evidenceSufficient=false succeeds because the auditor’s adverse finding is saved. The review leaves the order Paid.