A bill of lading is a document of title: whoever holds the original controls the goods in transit. Tokenizing it as a non-fungible token lets that title pass digitally — from carrier to shipper, to the exporter’s and importer’s banks, to the consignee — with every endorsement recorded and no paper couriered around the world. Legal recognition of electronic transferable records has advanced significantly, making e-BLs one of the most practical real-world tokenization use cases.
NUVZ built an e-BL tokenization platform on Hedera. This guide walks through how it works.
Key takeaways
- One NFT per e-BL — uniqueness mirrors the single original paper bill.
- Documents follow a verifiable format (we used Open Attestation) with encrypted details passed between holders.
- Each holder verifies and endorses with a digital signature; title changes are recorded on-chain.
- On surrender, the token moves to an expiry account, becomes non-transferable, and the goods are released.
- Company verification (registration, EORI, VAT, DUNS) and role-based permissions are as important as the token.
The problem with paper
Paper bills travel by courier between multiple parties and countries. Delays cause demurrage and storage charges; lost or forged bills lead to fraud and disputes; banks financing trade must physically handle documents. Digitising the document without solving uniqueness does not help — a PDF can be copied. A token solves uniqueness.
How title moves
- Issue: the carrier creates the e-BL in Open Attestation format; an NFT representing it is minted into the issuer’s Hedera account and the issuance is recorded on Hedera.
- Transfer: the NFT and encrypted e-BL details move to the next holder’s wallet; the receiver verifies the document and ownership changes.
- Endorse: each holder — shipper, exporter bank, importer bank, importer — receives, verifies and endorses with a digital signature.
- Surrender: the token moves to an expiry account, can no longer be transferred, the token registry is updated and the consignment is released.
Platform components
| Layer | Implementation |
|---|---|
| Ledger | Hedera mainnet with Hedera Token Service (HTS) and Hedera Consensus Service (HCS) |
| Token | NFT per e-BL; document in Open Attestation format |
| Middleware | Core functions and hash engine, wallet services, REST API, Hedera SDK |
| Data | Mirror node API, off-chain database, optional IPFS |
| Wallets | Platform-managed, software and hardware wallets |
| Application | Web front end for company admins and users; REST API for carrier systems |
Onboarding and permissions
- Companies verified at registration using registration, EORI, VAT and DUNS numbers.
- Each company and user receives a Hedera wallet.
- Roles define who may create, view, transfer or surrender e-BLs.
Benefits
- Days or weeks removed from document transit.
- Lower courier, demurrage and fraud costs.
- Banks can finance trade against a verifiable, unique digital title.
- A complete audit trail of endorsements for disputes and compliance.
Beyond bills of lading
The same pattern applies to warehouse receipts, promissory notes, bills of exchange and other transferable trade documents — and to trade-finance instruments tracked until retirement, another area we have built for.
Who holds the e-BL at each stage
| Stage | Holder | Action |
|---|---|---|
| Shipment loaded | Carrier | Issues e-BL, mints NFT |
| Documents presented | Shipper | Receives, verifies, endorses to exporter’s bank |
| Letter of credit | Exporter’s bank | Verifies, endorses to importer’s bank |
| Payment | Importer’s bank | Verifies, releases to importer after payment |
| Arrival | Importer / consignee | Surrenders e-BL to carrier |
| Release | Carrier | Moves token to expiry account, releases cargo |
Each transfer is a verifiable on-chain event, giving every party — and auditors — a complete chain of title.
Security and privacy design
- Encrypted payloads: e-BL details are encrypted and shared only with the current and authorised holders.
- Hash anchoring: the document hash on-chain proves the payload hasn’t been altered.
- Digital signatures: endorsements are signed by authorised users of verified companies.
- Role-based access: users can only perform actions their role allows.
- Key options: platform-managed wallets for convenience; hardware wallets for high-value endorsers.
Integrating with carrier and bank systems
A REST API lets carriers push e-BL data from their booking and documentation systems, while banks can integrate endorsement steps into trade-finance workflows. Mirror-node APIs provide fast read access to token history for dashboards and compliance checks.
Frequently asked questions
Recognition depends on jurisdiction and the governing contract. Many trade frameworks and laws now recognise electronic transferable records; parties also agree to e-BL rules contractually.
An NFT guarantees there is exactly one current holder, verifiable by all parties without a central operator controlling title.
The token moves to an expiry account where it cannot be transferred again, and the registry shows it as surrendered.
Yes. Banks in the chain hold and endorse the token, giving them a verifiable position for trade finance.
Most frameworks allow switching to paper in exceptional cases; the token is then surrendered or cancelled to prevent duplicate titles.
Each company and user receives a wallet, but platform-managed options mean users interact through a normal web interface.
NUVZ is the RWA and Web3 engineering brand of ESS ENN Associates (est. 1993). Our team has designed and shipped tokenization platforms for real estate, education loans, solar PPAs, energy, carbon credits, bank deposits and trade documents. About us · Case studies
This article is for general information only and is not legal, tax or investment advice. Token standards evolve — always confirm the current status of an ERC at eips.ethereum.org and take advice from qualified counsel in each jurisdiction before issuing tokens.
