Trade size on a venue that can account for its silence

Trade tokenised bonds. Shield your next move.

A cryptographically robust protocol for trading tokenised bonds or financing against them through a funded repo agreement on Hedera. Prove eligibility without publishing credential attributes and keep order fields sealed until the round closes. The disclosure lattice tracks what the venue publishes and keeps it within a governed budget.

Why it exists

The two accidents

A house that could read the book, or a book nobody could sum.

Institutional trading produced the same failure twice, in opposite directions. Most venues still pick one.

The operator held the cleartext

Crossfinder

$84.3million

Credit Suisse transmitted subscriber orders out of its dark pool to other desks. Confidentiality was a contract term. The machine could read the book anyway.

Nobody held the sum

Archegos

$5.5billion

One fund stacked the same risk across several primes. Privacy worked exactly as sold. No counterparty, and no supervisor, could see the line.

This venue refuses that choice. Size leaves sealed. Disclosure follows a governed scale, not a blunt hide-or-show choice.

29 consensus nodes

Closed before reveal

A plain order reaches every operator before a contract runs.

A hashgraph event carries transaction bodies. Side, price and quantity on a plain book would replicate with it.

Protocol response The commit phase sends one fixed-length hash. The sender, timestamp and bond remain visible; the order fields do not.

Inspect the sealed ticket
228 candidate openings

Closed in the encoding

A small nonce turns a price commitment into a search problem.

A bond price lives in a narrow domain. A weak salt can be enumerated in minutes on a laptop, making the seal decorative.

Protocol response The opening uses a full-scalar-field salt and a fixed domain-separated encoding bound to the committer.

Open the commitment proof
0 overlap

Closed by one clock

There is no instant for reveal-and-cancel last look.

Separate windows drift. A trader who can observe an opening and still pull their own order owns an information option.

Protocol response Cancel closes exactly where reveal opens, both derived from the commitment timestamp.

Watch the round clock
23 account associations

Partially answered

A live institutional token exposes its holder and KYC register.

The public mirror node returns associated accounts, exact balances and per-account compliance status without a credential.

Protocol response Eligibility attributes arrive as a zero-knowledge proof. The resulting account grant and upstream HTS records remain public.

Inspect zero-knowledge eligibility
61 public transfers

8 parties 7 directed edges

Boundary, not a privacy claim

Published fields recombine into a counterparty graph.

Identity, quantity and time were enough to reconstruct a live issuer flow that no primitive field disclosed by itself.

Protocol response The lattice prices derived venue publications. It cannot erase raw HTS transfers already written upstream.

Inspect the disclosure record

One order, two propagation paths

What the book learns, every operator learns.

The book receives a sealed commitment first. Later venue disclosures are accounted for against a published limit.

Sample order BUY 101.25 40,000 salt 0x91…4c

Hypothetical plain book

Cleartext transaction

fields exposed
trader
0x2f…91
side
BUY
price
101.25
quantity
40,000

29operators receive the fields above

Lattice Prime

Sealed ticket

fixed length
sender
0x2f…91
timestamp
consensus
bond
posted
commitment
0x7c3a…9e12
side
absentBUY
price
absent101.25
quantity
absent40,000
salt
absent0x91…4c

29operators receive only the visible fields

The network receives the trader, timestamp, bond and one fixed-length commitment. Side, price, quantity and salt are absent.

At reveal, side, price, quantity, salt and backing become public transaction inputs. The disclosure lattice governs later venue events, not those inputs.

Public activity

Row 15 predicate, now

Cost
1 bit
Remaining
0 / 1
Receipt
charge, then silence

Counterparty identity

Row 12 exact, now

Cost
unmetered
Remaining
not capped
Receipt
ATS transfer

Supervisory risk

Row 14 predicate, now

Cost
1 bit
Remaining
1 / 2
Receipt
HCS charge

These labels describe why each policy row exists, not a private delivery channel. Published venue events are public; the lattice decides whether the venue may publish them and accounts for the disclosure.

The instrument is already a market: Broadridge’s distributed ledger repo printed $7.4tn in August 2026. What it cannot print is a receipt of what it withheld.

How a round runs

Prove, seal, account, verify.

One trader journey from private eligibility to a disclosure record you can check.

  1. 01

    Prove you are eligible

    Prove the required attributes in zero knowledge. Your credential details stay out of the order and financing workflow.

    Open Eligibility
  2. 02

    Send a sealed ticket

    Submit one fixed-length commitment instead of readable order fields. Cancellation closes exactly when reveal opens, and proceeds remain available for you to withdraw.

    Open Markets
  3. 03

    Account for each disclosure

    Each venue publication draws from a governed limit. Once that limit is reached, a valid cancellation still completes while its venue event is withheld.

    Review publication limits
  4. 04

    Verify the venue record

    The disclosure receipt ties published or withheld activity back to the successful transaction and its governed limit. You can check that record against the chain.

    Verify the record

The disclosure lattice

Every disclosure changes what can be known.

A market print can reveal a summary now or exact detail later. Tap the grid to see what this example policy permits.

Illustrative policy

Aggregate now Exact at EOD Your selection Outside policy

Venue publications only. Underlying blockchain activity remains public.

Disclosure policy

How the disclosure lattice works

Permitted cells Candidate closure Outside ceiling
A = ↓(aggregate, immediate) B = ↓(exact, EOD) Combined = A ∪ B

↓ includes the selected cell and every coarser, later cell.

ceiling = A ∪ B actual = ↓(aggregate, immediate)

Within policy Every cell implied by this publication fits within the selected policy.

Allowed iff actual ⊆ ceiling
Contract representation
  • cell index = 6g + t
  • join = A | B
  • meet = A & B
  • permitted = (actual | ceiling) == ceiling
  • excess = actual & ~ceiling
  • 30 cells packed into uint32

Granularity levels describe configured disclosures for one policy row.

Join combines represented permissions or capabilities, not every possible inference.

Timing categories do not themselves schedule publications.

Policy floors do not automatically force publication.

The record

What the venue withheld is verifiable.

A blunt hide-or-show choice does not work for regulated collateral. Each venue publication draws from a governed limit. When that limit is gone, the event is withheld while the valid transaction still completes.

That silence is written to a Hedera consensus topic, so an independent verifier can check it against the transaction and disclosure limit.

The lattice governs venue events. Contract storage, transaction inputs, token transfers, and wallet activity remain public.

Why Hedera

What the trader can rely on.

The chain matters where it changes the trade: entry, settlement, disclosure, and valuation.

Fair entry

Sequenced before it opens

Every sealed ticket receives a consensus timestamp before its order fields are revealed, with no mempool or gas auction ahead of it.

Native settlement

The venue never takes custody

The bond remains a regulated security token, with settlement enforced through native holds rather than a venue-controlled wallet.

Accountable disclosure

Silence leaves a record

Published and withheld venue activity can be checked against the same governed disclosure limit.

Current valuation

Financing reads the network rate

The cash leg uses Hedera’s current exchange rate without writing a persistent collateral mark to the ledger.

The next move

Your next order starts here.

  1. 01

    Qualify privately

    Prove the required attributes without publishing the credential behind them.

  2. 02

    Enter the round sealed

    Submit a fixed-length commitment and open the order after the round closes.

  3. 03

    Leave with a record

    Verify what the venue published or withheld against its disclosure limit.

Hedera testnet only. You will need an ECDSA secp256k1 account with test HBAR. No extension? Open the wallet sheet and watch any address read-only.