HypertronWhat Hypertron isPrivacy protocolMerchant paymentsPayments APIDeveloper toolingDirectionWhat will shipWhat exists today
Developer tooling
Private settlement as an integration, not a circuit rewrite.
As the protocol matures, Hypertron will expose reusable SDKs, APIs, and language-specific crates around the machinery that today lives inside our own frontend: note discovery, transaction construction, proof generation, relaying, payment verification, and selective disclosure.
The goal is a developer experience closer to integrating a payment API than implementing a privacy protocol from scratch.
Consumers
What should be able to call this layer.
Hypertron is not trying to win by inventing another cryptographic primitive. The work is making the existing pool easy to consume.
| Integrator | Intended outcome |
|---|---|
| Wallet | A private-send option against the shared pool, without embedding circuit engineering in the wallet team. |
| DEX | Settle a fill privately so the trade amount is not published on the ledger. |
| Payroll | Confidential stablecoin disbursement while deposits and withdrawals stay visible on Stellar. |
| Merchant app | Private stablecoin checkout without learning ZK circuits, via workspace or API today, SDK later. |
| Any application | Call an API or SDK and let Hypertron handle proving, relaying, and disclosure underneath. |
| Surface | Job |
|---|---|
| Note discovery | Scan encrypted blobs, match commitments to on-chain leaves, build a local unspent set. |
| Transaction construction | Select notes in {1, 2, 4}, assemble public inputs, and choose deposit / transfer / transfer_n / unshield. |
| Proof generation | Run Groth16 in a browser worker (or native crate) against the registered proving key. |
| Relaying | Submit a valid private transfer so the customer is not the fee payer (CAP-0015). |
| Payment verification | Confirm a settlement against the pool without holding a spend key. |
| Selective disclosure | Export viewing material, then payment-specific receipts that an auditor can verify independently. |
Current state
The client logic is ours. It is not a third-party SDK.
Today you integrate through the open contracts, the Payments API, or the merchant workspace. There is no published typed client for wallets or DEXes.
- Browser proving, note math, and checkout coin selection live in this frontend and in
prover-wasm. They are not versioned as a public package for integrators. - The pool ABI is already callable: Apache-2.0 contracts on Stellar testnet. A Soroban app can deposit, transfer, and unshield without waiting on the SDK.
- Relaying, client Merkle-root checks, and invoice-bound receipts are still protocol/client work. Packaging them for third parties follows those shipping.