LatticePrime

Demo

About

Lattice Prime is a tokenised bond marketplace on Hedera that brings sealed-order trading, privacy-preserving eligibility, coupon payments, and collateralised financing into one platform. It tackles a core challenge of on-chain finance: making market activity verifiable while controlling what the venue reveals about participants’ trading intentions. At its core, Lattice Prime features: 🔒 Sealed-Order Markets: Investors commit orders before revealing their terms, then trade through uniform-price auctions with partial fills, collateral backing, cancellation, and expiry. A built lender-interest board adds selective liquidity discovery without exposing an entire lending strategy. 🎩 Zero-Knowledge Eligibility: Participants prove that credentials satisfy KYC, jurisdiction, and validity requirements without publishing the underlying credential details. Eligibility grants are account-bound and expire with their authorised epoch. 💰 Coupons and Repo Financing: A complete coupon lifecycle covers payment calendars, funded distributions, Merkle-backed entitlements, and protected claims. The financing module supports funded lending offers, bond collateral, haircuts, repayment, margin calls, collateral top-ups, and default recovery. 💠 Accountable Disclosure: Policies define what information the venue may publish, at what detail, and when. Budgets account for repeated disclosures, while verifiable receipts and a Hedera consensus audit trail make both publication and deliberate silence inspectable. 🔭 Oracles and Observatory: Valuation and reference-rate feeds support pricing, coupons, and margin checks. State-based monitoring surfaces risk even when events are withheld. Scheduled actions support lifecycle obligations and oracle finalisation. ⚖️ Explicit Market Rules: A versioned rulebook, transparent fees, Merkle-backed policy commitments, governed updates, trading halts, transfer pauses, and targeted freezes make market controls accountable. 🤖 Lattice Claw: A companion trading private-agent prototype adds constrained execution and verifiable decision evidence, with its public interface remaining a preview (prototype style only). The web app connects these capabilities through Markets, Portfolio, Financing, Eligibility, and Issuer screens. Built extensions are distinguished from enabled functionality, including financing that requires a compatible vault deployment. Lattice Prime also addresses a subtle market failure: silence must not trap funds or hide risk. Its demonstrated cancellation flow preserves refunds when disclosure budgets run out, while the observatory tracks obligations independently of published events. The result is a bond market designed to account for its money, its rules, and its silence.

How it's made

The core idea came from an observation in private marketplace institutions the runners on that idea I kept seeing that what is to be private in a trade, or why are products just toggling shut information using ZK? That drove the core concept, what if privacy was abstracted into a scaled concept? Not a "lets make another dark pool", I drew privacy as a scale. I started with a ZK outline, then shaped it around a marketplace for Hedera ATS bonds, where disclosure becomes an explicit policy decision. The scope was the information the venue publishes, with rules people could inspect and verify. Cryptography is strict. ZK is strict. Smart contracts are strict. Privacy could still have degrees. That became the disclosure lattice. So I went ahead and vibecoded an entire regulated institutional finance and not just DeFi, that Hedera can run. Governed disclosure limits and per-epoch budgets. Around it, I built commit-reveal orders, uniform-price auctions, and repo financing using ATS partition holds for bond collateral. Circom and snarkjs generate PLONK eligibility proofs, verified onchain against credential and policy requirements. Merkle proofs support coupon entitlements and committed policy parameters, while Hedera Token Service supplies the coupon cash token. The hardest question was what happens when the disclosure budget runs out. Blocking someone’s cancellation refund because the venue cannot publish another event would be a terrible outcome. I separated recovery from publication and built an observatory that reads contract state, because an unpublished margin call still matters. HCS records the disclosure evidence, while Node.js, the Hiero SDK, and Mirror Node tooling independently check it against transactions. The clearest demo became two cancellations: both refunds succeed, but only the first publishes a venue event. There were practical surprises too. An early deployment mixed Ethereum-style value units with Hedera’s tinybars, making the required deposit enormous. I measured the conversion and corrected the parameters. The oracle combines auction evidence, a valuation model, signed dealer quotes, and reference-rate data. HSS handles scheduled lifecycle actions and bounded oracle checks, with retries and manual fallbacks. The frontend uses HTML, CSS, JavaScript, and ethers, with generated deployment bindings and Vercel hosting. I checked the system through Foundry tests, fuzzing, client checks, and Hedera testnet runs, including failed proofs, stale feeds, and exhausted disclosure budgets.