Private & Confidential
A demonstration and discussion document
Trusted Trade · Concept to Implementation

From a trusted-trade concept
to a working, verifiable system.

How the Kaspa Industrial Initiative mapped the trusted-trade infrastructure described in the IDC white paper onto its existing KiiWORKS platform, and proved the controls at consensus on a public blockchain.
Prepared by the Kaspa Industrial Initiative
Proof of concept · public test network · audit and legal opinion in progress
Kaspa Industrial Initiative · Trusted Trade01 / 12
Private & Confidential · Discussion Document
01Executive summary

The trusted-trade infrastructure has been built, and demonstrated end to end.

  • The IDC white paper set out a trusted-trade model for SME corridors: a controlled title record, an escrow lock, an assurance certificate, and expedited dispute finality. The Kaspa Industrial Initiative has implemented it.
  • We did not start from a blank page. KII mapped the requirements onto KiiWORKS, the platform's existing trade-document, identity, evidence and dispute capabilities, and re-based them onto a public blockchain (Kaspa) where the controls are enforced by consensus rather than asserted by a platform.
  • All four controls are live on a public test network, with every acceptance and every rejection independently checkable. A duplicate sale of the same title is rejected by a second, independently operated node. The double-spend problem, closed at the protocol layer.
  • A sceptic verifies the evidence in a browser, with no software to install and no trust in us.
Status, stated plainly. This is a proof of concept on a public test network. Independent security audit and a legal opinion under ADGM and English law are scoped and not yet complete. The mechanism is proven; the pathway to production is a known, finite list.
Kaspa Industrial Initiative · Trusted Trade02 / 12
Private & Confidential · Discussion Document
02The brief

The information provided: a concept for making cross-border SME trade provable.

The IDC white paper frames a real market problem, an SME "trust tax" of costly instruments, slow document checks, title risk and unpredictable dispute resolution, and proposes a four-stage answer.
01
Prove

Verify identity, authority, goods, inspection, quality and origin into a validated title packet.

02
Control

Create the documentary title instrument and escrow-lock it so it cannot be duplicated or double-sold.

03
Protect

Issue the assurance and warranty workflow, and only once the title is escrow-locked.

04
Close

Resolve release-blocking disputes through a pre-agreed, evidence-first pathway to a defined outcome.

The proposition is sound. As presented, however, each control is a platform feature, a promise the operator makes. The white paper's own plan reserves a design sprint to select the technology and design the controls. That is the gap the Initiative closed.

Kaspa Industrial Initiative · Trusted Trade03 / 12
Private & Confidential · Discussion Document
03The complication

A trust layer is only as strong as what enforces it.

  • Every control in the brief can be built as a database record an operator asserts, or as a rule a public network enforces. The difference is the entire value of an assurance product.
  • If the platform can silently override its own controls, so can a compromise of the platform. Buyers, banks and insurers price that risk in.
  • The one property no assurance layer of this class has reliably delivered is that its guarantees hold even against its own operator.
"Not a standalone technology project, a monetisation layer on infrastructure AD Ports already owns."
The IDC white paper. The concept is deliberately technology-agnostic. Choosing and proving that technology is exactly where a working implementation earns its place.

The Initiative's thesis: enforce the controls where no operator can override them, on a public, proof-of-work blockchain, using capability the platform already had.

Kaspa Industrial Initiative · Trusted Trade04 / 12
Private & Confidential · Discussion Document
04The starting asset

We did not start from zero. KiiWORKS already carried the capability.

The trusted-trade brief maps almost one to one onto components already engineered in KiiWORKS. The implementation was a re-basing exercise, not a greenfield build.
Trade documents

A typed family of electronic trade documents: bill of lading (MLETR-eligible), waybills, letter of credit, certificate of origin, invoice, packing list, warehouse receipt.

Title lifecycle

The MLETR control state machine: endorsement, surrender, amendment, change of medium. The reference logic for a transferable record.

Legal-entity identity

GLEIF vLEI: the credential hierarchy binding a controller to a legal person, with revocation.

Evidence and assurance

Signed, anchored evidence packaging: a bundle a counterparty can verify without platform access.

Dispute and deadlines

An obligation and time-bar engine: the machinery behind expedited, evidence-first dispute finality.

Screening and provenance

Sanctions screening and geo-attestation (proof of place and existence) for the origin and compliance layer.

Kaspa Industrial Initiative · Trusted Trade05 / 12
Private & Confidential · Discussion Document
05The mapping

From the brief, to KiiWORKS capability, to an enforced control.

Requirement in the briefKiiWORKS capability drawn onWhat was built, and where it is enforced
Title instrument (DTI)Trade-document family and MLETR lifecycleA Controlled Trade Record whose singularity and exclusive control are properties of a public-chain covenant, not a database row Live
Escrow lockTitle lifecycle control statesA consensus-enforced lock: a locked record's transfer is rejected by the network, not by the app Live
Assurance certificate (DTC)Evidence and assurance packagingAn Assurance Certificate the network refuses to issue unless the record is escrow-locked first. The wrong order is unspendable Live
Dispute finalityDispute and deadline engineA determination that releases the escrow lock at consensus. The evidence pack verifies offline and names any tampering Live
Identity and originvLEI identity, screening, geo-attestationController bound to a legal person; issuer signatures verified; a zero-knowledge compliance proof checked in-consensus Live
The Initiative's product marks are its own (Controlled Trade Record, Assurance Certificate). The IDC marks are referenced only to map the brief to the implementation.
Kaspa Industrial Initiative · Trusted Trade06 / 12
Private & Confidential · Discussion Document
06Execution

We made it work, on a public blockchain, enforced by consensus.

The controls are not described. They run. Each is enforced by Kaspa's layer-1 protocol, chosen because a title instrument needs three properties no database gives.
1
One owner, provable everywhere. Not one registry per operator. Singularity is a protocol property.
~10/s
Finality in seconds. Proof-of-work confirmation at roughly ten blocks per second, fees in fractions of a cent.
0
Privileged operators, including us. The controls live where no party can override them. That is what makes assurance sellable.

Advanced protocol features the design demands, covenants, transaction introspection and in-consensus zero-knowledge verification, are live protocol on this network today, not roadmap. The record lives on the layer-1 itself. No bridge, no side-chain, no vendor chain to trust.

Kaspa Industrial Initiative · Trusted Trade07 / 12
Private & Confidential · Discussion Document
07The demonstration

A live demonstration anyone can open, and verify without trusting us.

  • A single trade runs end to end through the five stages, live on the public test network, with every acceptance and rejection recorded and checkable on a public explorer.
  • The headline: a second sale of the same title is rejected by a different, independently operated node than the one that accepted the first. The double-sell, closed at consensus, not by a database check.
  • The assurance certificate cannot be issued before the lock exists. A tampered evidence pack is refused and the altered component named.
  • An independent party verifies the evidence in their own browser. No install, no account, no trust in the Initiative.
The demonstration runs at a link. It narrates itself, and the verification tool runs in the recipient's browser.
A hosted, self-explaining demonstration environment is available for review under confidentiality. Every figure it shows is a real transaction on a public test network.
Kaspa Industrial Initiative · Trusted Trade08 / 12
Private & Confidential · Discussion Document
08Engineering rigour

Built to be examined, not just presented.

The implementation carries the discipline a technical or commercial diligence review will look for.
A
Adversarial testing to exhaustion. Repeated red-team rounds against every control until two consecutive rounds surfaced nothing new. Each control carries a proven rejection of its own violation.
B
Self-audit, disclosed. An internal completeness review examined every claim and recorded 65 findings against our own work, all resolved or explicitly noted. We hand a diligence reader the audit we ran on ourselves.
C
Verifiable evidence. Every external claim traces to a recorded transaction or a re-runnable check. No figure is asserted without a source.
D
A licensable standard. The rules a conforming system must satisfy, and the tests that check them, are packaged as an asset in their own right. The standards layer the corridor model contemplates.

This is the "controls testing, audit records and publishable scorecards" the brief itself calls for, already in place.

Kaspa Industrial Initiative · Trusted Trade09 / 12
Private & Confidential · Discussion Document
09Strategic implication

The technology layer the opportunity needs already exists.

De-risks the pilot

The design sprint's hardest, most uncertain deliverable, proving the controls hold, is already met. The engagement can begin from a working system, not a specification.

Compresses the timeline

Months of "design the controls, choose the technology, build the reference" collapse into an integration and corridor-onboarding exercise.

Owns the trust layer

A defensible, standards-based position: the record lives on public infrastructure, and the conformance standard is a licensable asset around it.

The Kaspa Industrial Initiative is not competing with the trusted-trade proposal. It is the working implementation the proposal now needs.
Kaspa Industrial Initiative · Trusted Trade10 / 12
Private & Confidential · Discussion Document
10Status and path to production

Proven mechanism, finite path, stated without overstatement.

Proven nowEngineering to productionExternal and commercial
Four consensus controls and an in-consensus compliance proof, live on the public test network with recorded evidenceMigration to production infrastructure and a hardened operating environmentIndependent security audit External
Offline, in-browser verifiable evidence; adversarially red-teamed; self-auditedProduction key custody (hardware or threshold), monitoring and continuityADGM and English-law legal opinion on the reliable-system test External
Reproducibility kit for an independent scepticCorridor integrations (single window, warehousing, inspection, banks and PSPs)A named pilot corridor and counterparty External
What the pilot needs now is not code. It is a corridor, counsel, an audit firm and a counterparty. The Initiative has built the half that was missing.
Kaspa Industrial Initiative · Trusted Trade11 / 12
Private & Confidential · Discussion Document
11Recommendation

A short, low-risk step: see the working system, then scope the pilot around it.

  • Review the live demonstration under confidentiality. A hosted environment and a reproducibility kit are ready for a technical reviewer.
  • Position the Initiative's implementation as the technology layer of the trusted-trade proposal to AD Ports, rather than a control set still to be designed.
  • Scope a controlled corridor pilot around the working system. The recommended first corridor and success metrics in the brief apply unchanged.
  • Sequence the external gates, audit and legal opinion, against a named counterparty, so cost follows commitment.
The concept has been proven. The next decision is commercial, not technical.
Kaspa Industrial Initiative · Trusted Trade Infrastructure. A demonstration and discussion document. Contact details on request.
Kaspa Industrial Initiative · Trusted Trade · Private & Confidential12 / 12
1 / 12