Home/Solutions/Title Transfer
ERC-721 Title Escrow · XDC Blockchain · Atomic Transfer

Transfer document title. On-chain.
In seconds.

DocuShield uses ERC-721 Title Escrow smart contracts to enforce legal ownership of transferable trade documents. Endorse, transfer, and surrender, all atomic, immutable, and legally binding.

Under the hood

How Title Escrow works

When an eBL is issued, a deterministic ERC-721 Title Escrow contract is deployed at a unique address derived from the Token Registry address and the document's merkle root. This contract holds two key roles.

Beneficiary

The party with economic ownership rights, typically the buyer or bank. The beneficiary can nominate a new beneficiary or surrender the document.

Holder

The party with physical possession rights, typically the shipper or freight forwarder. The holder can endorse the document or transfer holdership.

Important:The Token Registry acts as the "carrier" in the ERC-721 sense. When the holder surrenders the eBL, they transfer the token back to the Token Registry, which burns it, confirming the original has been presented exactly once. This prevents double-spending of Bills of Lading.

On-chain Actions

Every transfer event, explained.

Each action is a smart contract call, atomic, irreversible once confirmed, and permanently visible on the XDC block explorer.

Endorse to new beneficiary

Called by: Current beneficiary

Changes the beneficiary address in the Title Escrow. Used when a bank endorses to the buyer, or a buyer endorses to their freight forwarder.

Transfer holdership

Called by: Current holder

Changes the holder address. Used to pass physical document custody from shipper to freight forwarder, or from one bank branch to another.

Nominate new beneficiary

Called by: Current beneficiary

Two-step endorsement, the current holder must also confirm before the change is final. Mirrors the countersignature requirement on traditional BLs.

Surrender to carrier

Called by: Holder

The ERC-721 token is returned to the Token Registry and burnt. The carrier sees the on-chain surrender and releases the cargo. Prevents duplicate presentation.

Reject surrender

Called by: Token Registry (carrier)

The carrier can reject a surrender if the document doesn't match the cargo. The token is returned to the holder, no manual intervention needed.

Comparison

Traditional BL vs. DocuShield Title Escrow

Traditional Bill of Lading
DocuShield eBL
7 to 10 day courier transit
Instant on-chain transfer
3 original copies, any one releases cargo
Single token, one holder at a time
Manual countersignature chains
Smart contract enforces dual-party endorsement
No audit trail for endorsement history
Every transfer permanently recorded on-chain
Fraud risk from lost or duplicated originals
Cryptographically impossible to duplicate
Bank must verify document authenticity manually
3-factor verification in under 5 seconds

Audit Trail

Every transfer. Permanently recorded.

Every on-chain action is logged as a blockchain event, timestamped, immutable, and publicly inspectable. Banks and regulators can verify the complete ownership history of any eBL at any time.

Full endorsement history on XDC block explorer
Timestamp of every transfer event
Wallet address of every beneficiary and holder
Surrender confirmation with block number

eBL Ownership History

Issued2026-04-10 09:14:22 UTC

Issuing NVOCCExporter Co. (Shipper)

Endorsed2026-04-10 11:33:07 UTC

Exporter Co.Trade Finance Bank (Beneficiary)

Transferred2026-04-12 08:02:55 UTC

Trade Finance BankImporter Co. (Holder)

Surrendered2026-04-18 14:47:31 UTC

Importer Co.Token Registry (Carrier)

Live demo · No commitment

Ready to move trade forward?

See DocuShield issue an eBL end to end in seconds. We'll walk through your specific document types and integration needs.

Pilot program for freight forwarders · Running on a public test network, mainnet deployment in progress