ZKTX Platform

Robinhood Chain has a new privacy layer. ZKTX is live onchain. ZKTX brings shielded transactions to standard ERC-20 tokens. Assets enter a token-backed vault, then move through encrypted notes authorized by zero-knowledge proofs. 🔒 Shield existing RH tokens inside the vault 📝 Note secrets stay encrypted on your device ↗️ Accepted proofs can travel through a gas-funded relayer ⚙️ For trading, ZKTX supports RFQ settlement and sliced market orders Official information: CA: 0x8de45f5cb60bd659ebbaa50d9765608ff1eb48f6 Web: zktx.tech App: zktx.tech/app Docs: zktx.tech/docs.html X: nitter.gq/zktxtech GitHub: github.com/vincenzofamoso/zk…

ZKTX keeps private balances and note ownership inside a shared proof system. Public chain activity still reveals deposits, withdrawals, vault trades and timing. Read the privacy model and current deployment status at zktx.tech/docs.html $ZKTX

ZKTX links public lifecycle events to Robinhood Chain Blockscout. Deposits, execution slices, settlements and withdrawals can be checked against the chain while private note ownership remains encrypted.

The current proof architecture covers seven actions: deposit, transfer, withdrawal, RFQ swap, order cancellation, market order and market settlement. Each circuit checks one defined state transition for the vault.

Each supported market execution can create lasting $ZKTX demand through the protocol fee. The burn path buys ZKTX during the transaction and sends the acquired tokens to permanent removal.

The documented protocol fee is 1.5% of market activity. A 0.5% allocation supports execution. The remaining 1% funds an atomic purchase and permanent burn of ZKTX.

Routing changes need time for review. The architecture includes delayed activation for new adapters and route controls around supported assets. This gives users a visible window before new execution code becomes active.

$ZKTX routing is modular. Approved adapters connect the vault to supported venues on Robinhood Chain while the proof system keeps the user’s private input inside the vault flow.

A private order can carry a cancellation secret. Presenting that secret authorizes cancellation through the matching circuit, which prevents an unrelated wallet from removing the order.

ZKTX also defines an RFQ path for shielded swaps. A maker can fill a private order against committed terms. The proof checks the exchange while settlement produces new notes for the participants.

Settlement follows the amount the route returned onchain. The received assets become a fresh private output. Unspent input can return through an encrypted refund note.

Market privacy improves when several users have active slices in the same window. The vault becomes the visible trader while individual orders overlap inside its execution schedule.

The documented market flow divides an order into a variable number of execution slices. A typical order uses between three and seven. Each slice lands in a separate block, which reduces the value of one-shot order matching.

ZKTX is designed to reach existing Robinhood Chain liquidity. Direct V3 execution is used where available. Compatible V4 and multihop routes can pass through approved routing adapters.

A shielded sell consumes a private token note. The vault executes through supported Robinhood Chain routes, then settles the received WETH or USDG into an encrypted note for the user.

A shielded buy starts from a private WETH or USDG note. When market execution is enabled, the ZKTX vault routes the order through Robinhood Chain liquidity. Proceeds settle into a new encrypted token note.

Each private note is backed by real ERC-20 reserves held in the vault. Proofs authorize how those claims move. The contract enforces the accounting that keeps issued notes aligned with available assets.

The ZKTX relayer simulates valid proof transactions before broadcasting them. It can also pay Robinhood Chain gas for private actions. Users avoid exposing a separate gas wallet for every move inside the pool.

The Merkle indexer follows vault commitments and prepares membership paths for the browser. A proof can then show that a spendable note belongs to the accepted tree root without identifying its leaf.

ZKTX proofs are created in the browser. The circuit checks note ownership, conservation of value and valid state transitions. The chain receives a proof that can be verified without reading the hidden inputs.

Private custody comes with recovery responsibility. Keep the encrypted note backup and the wallet that derives its key. Those two items provide the recovery path.