Shielded note layer
Separate development contracts implement Poseidon notes, Groth16 verification and spent-note checks in local tests. This website does not execute them. Asset-binding and independent review gates remain.
Inside the design KRYPTA / SWAP
A separate swap experience for KRYPTA. Inspired by VeilSwap, designed around adaptable execution instead of a single pool standard.
RESEARCH PREVIEW / NO LIVE PRIVATE SWAPS
Understand the privacy boundariesFictional tokens. Fixed sample prices. No wallet, funds, chain connection or privacy protection.
This updates fictional balances in this tab only. No deposit, shielded note, proof, signature or onchain transaction is created.
Ready to explore. Reloading clears all fictional balances and receipts.
YOUR PAPER ACTIVITY
Browser-local records, not transaction hashes, settlement receipts or proof of privacy.
SEPARATE FROM THE ORDER BOOK
A proposed separation of responsibilities. Compatibility belongs in adapters, not inside a single DEX hook.
Separate development contracts implement Poseidon notes, Groth16 verification and spent-note checks in local tests. This website does not execute them. Asset-binding and independent review gates remain.
V2 pair and typed V3 router adapters exist in development source, with bounded routes and actual balance checks. Their local fixtures do not establish live-venue compatibility.
Development contracts reconcile received assets before creating an output commitment. Real-proof tests and client recovery helpers are separate from this browser’s paper receipts.
COMPATIBILITY BY DESIGN
VeilSwap informs the direction. KRYPTA Swap proposes a venue-independent note layer with individual adapters. Every live integration needs its own address verification, testing and independent review.
Python references model v2, a bounded v3 price range and RFQ inventory. Separate Solidity code implements experimental V2/V3 adapters. This page runs neither backend; no KRYPTA adapter is deployed. Fee choices here are made-up examples.
Broad compatibility is a design goal, not universal support. Arbitrary call targets and unlimited token approvals are not part of the proposed interface.
PRIVACY, WITH THE BOUNDARIES VISIBLE
Onchain swap execution still leaves public traces. A production system must state exactly what it hides, from whom, and under which assumptions.
CURRENT WEBSITE: NO TRANSACTION PRIVACYTHE PATH TO PRODUCTION
No real funds, wallet connection or mainnet contract is enabled here.
Token selection, fixed-rate estimates, example tolerances, quote expiry and disposable paper receipts.
Experimental contracts and a real proof path exist. Asset-binding review, live venue validation, production custody/recovery, relayers and independent audits remain required.
Robinhood mainnet is live. KRYPTA still needs its own deployment, venue-address validation, asset support, bridge review and legal checks before enabling funds.
Sources: Robinhood Chain connection details · Uniswap v4 deployments. The chain and venue exist; KRYPTA Swap is not deployed. This is a KRYPTA design preview, not an official Robinhood product or an assurance of privacy, liquidity or performance.