TradeTrust primary sources — 2026-05-12

Project status in this pass

• The strongest accessible primary materials in this pass were the main TradeTrust README, tradetrust-core, the TradeTrust CLI README, and the creator tutorial.
• No standalone whitepaper surfaced through the accessible primary-source path used here.
• The key discovery was that TradeTrust should be cataloged as a higher-layer transferable-record and title-transfer framework, not only as another verifiable-document library.

Primary-source snapshots

1) Main TradeTrust README

• URL: https://raw.githubusercontent.com/TradeTrust/tradetrust/master/README.md
• Key excerpts/signals:
  • Describes TradeTrust as an attestation and notary framework for any document types on the blockchain.
  • Says TradeTrust can publish Merkle-root proofs on Ethereum or use digital signatures without paying Ethereum transaction fees.
  • Exposes wrapping, signing, schema validation, signature verification, data retrieval, and obfuscation flows.
• Why it mattered:
  • This source shows TradeTrust inherits the lower-layer document-attestation model, but by itself it would be easy to mistake the project for only an OpenAttestation-style framework.

2) tradetrust-core README

• URL: https://raw.githubusercontent.com/TradeTrust/tradetrust-core/main/README.md
• Key excerpts/signals:
  • Presents one branch for ordinary verifiable documents via document stores and another for transferable records via token registries.
  • Shows token-registry deployment and minting flows for transferable records.
  • States that minting creates a Title Escrow with initial owner and holder.
  • Describes title-transfer methods such as nominate and transferBeneficiary, and frames them as the way ownership moves for transferable records.
• Why it mattered:
  • This is the strongest primary-source reason to keep TradeTrust separate from OpenAttestation: it adds a genuine transfer-control layer with beneficiary/holder/title-escrow semantics.

3) TradeTrust CLI README

• URL: https://raw.githubusercontent.com/TradeTrust/tradetrust-cli/master/README.md
• Key excerpts/signals:
  • Lists commands for document-store issuance and revocation as well as token-registry issuance/minting.
  • Includes title-escrow actions such as change holder, nominate change of owner, endorse transfer of owner, reject owner/holder changes, and return/accept/reject return to issuer.
  • Notes that transferable records should be wrapped individually because each is minted to a unique title escrow representing beneficiary and holder entities.
• Why it mattered:
  • The CLI surface confirms that TradeTrust is operational workflow infrastructure for document transfer states, not only a verification library.

4) Creator tutorial

• URL: https://raw.githubusercontent.com/TradeTrust/creator-tutorial/main/README.md
• Key excerpts/signals:
  • Describes itself as a guide for creating, deploying, and managing transferable documents using the TradeTrust framework.
  • References related projects including Token Registry and TrustVC.
• Why it mattered:
  • This is a useful primary signal that the project expects developers to stand up full transferable-document flows, not merely inspect already-issued files.

Working conclusion

TradeTrust is best cataloged as transferable-record and title-transfer infrastructure layered above verifiable-document tooling. The decisive clue is the explicit split between ordinary document attestation and transferable-record control through token registries, title escrows, beneficiary-versus-holder roles, and endorsement/rejection/return workflows. That makes TradeTrust a better comparison point for tokenized-document and document-title systems than a generic credential or document verification label would suggest.