Skip to main content
NEXUS Protocol

​
What is NEXUS?

NEXUS is a unified smart contract execution layer for proof-of-work blockchains — starting with Zcash and expanding to Bitcoin and Dogecoin. Today, none of these chains have native smart contracts. NEXUS adds a fully programmable layer on top, anchored to the security of the underlying L1. You can run DeFi applications, create tokens, deploy AMMs, and more — all backed by real ZEC, BTC, or DOGE held in on-chain vaults. No new token. No separate chain. No bridges to trust. Your Zcash stays on Zcash. NEXUS gives it smart contract superpowers.

Quick Start

Deploy your first smart contract on Zcash in 5 minutes

SDK Reference

TypeScript and Rust SDK documentation

CLI Reference

Command-line tools for developers

RPC API

Complete JSON-RPC endpoint reference

​
Launch Status

ChainStatusVaultDeposit Confirmations
Zcash✅ LiveTransparent t-addr (P2SH 2-of-2)10 blocks (~12.5 min)
Bitcoin🔄 Coming soonTaproot (P2TR)6 blocks (~60 min)
Dogecoin🔄 Coming soonP2PKH + CLTV3 blocks (~3 min)
Zcash is first because it has native Groth16 ZK proof verification built into its protocol — the only UTXO chain that can verify zero-knowledge proofs on-chain natively. This means NEXUS achieves true cryptographic verification on Zcash, not just economic security. Bitcoin and Dogecoin follow using ZK-STARK proofs with BitVM2.

​
Key Features

Write programs in Rust, compile to WebAssembly (WASM), and deploy to NEXUS. Your contract runs on the Zcash execution layer today. The same contract code will work identically when Bitcoin and Dogecoin join the unified execution layer.What you can build: Token launches (NEP-20), DEXs (AMM V3 concentrated liquidity), lending protocols, NFTs, gaming, micro-payments — any DeFi primitive.Your ZEC stays in a Zcash vault. Contracts move vZEC (a 1:1 representation of your deposited ZEC). No wrapped tokens from untrusted bridges.
NEXUS on Zcash uses two independent security layers:
  • Groth16 ZK proofs: Every state update includes a mathematical proof verified directly by Zcash nodes. This is native — Zcash already has this verification built in from Sapling.
  • Economic bonds + fraud proofs: Operators post collateral on Zcash L1. Invalid state can be challenged by anyone; the fraudulent operator loses their bond.
Your funds are in a 2-of-2 multisig vault — NEXUS cannot move them without your key. If NEXUS stops working entirely, you can always recover your ZEC via the escape hatch (~2 weeks timelock, no permission needed).
NEXUS ships two privacy features in V1, live now on Zcash:Stealth Addresses — Every transaction generates a unique one-time recipient address. Nobody watching the chain can link your transactions together. You scan for incoming transactions locally with your private key — no data leaves your device.Encrypted Mempool — Transactions are encrypted with ECDH + ChaCha20-Poly1305 before submission. Miners cannot read what your transaction does until it’s in a block. This prevents MEV front-running and sandwich attacks.These are separate from Zcash’s native shielded pool (z-addr), which is planned for V2.→ Stealth Addresses · Encrypted Mempool
Every user gets a personal vault address on each supported chain. Deposit ZEC to your Zcash vault.How vaults work:
  • Deposit ZEC → receive vZEC (virtual ZEC) on NEXUS
  • Use vZEC in smart contracts, DeFi, swaps
  • Withdraw any time → burn vZEC, receive ZEC back on Zcash L1
  • L1 vault balance always equals NEXUS balance (1:1, verifiable by anyone)
  • Emergency exit: if NEXUS becomes unresponsive, wait ~2 weeks and withdraw on your own — no permission needed
When Bitcoin and Dogecoin join, the same model applies: BTC → vSAT, DOGE → vDOGE.→ Learn about Vaults
Create fungible tokens on NEXUS with the NEP-20 standard — equivalent to Ethereum’s ERC-20. NEP-20 tokens work with all NEXUS AMMs, wallets, and contracts automatically.Launch a token in minutes: set the name, symbol, decimals, and initial supply. Tokens are backed by vZEC and can be traded, staked, or used as governance mechanisms.→ NEP-20 Token Standard
Today (V1), Zcash is live. Bitcoin and Dogecoin are joining the unified execution layer next.Once all three chains are live, V2 will introduce intent exchange — describe what you want (“swap 1 ZEC for at least X BTC”) and a network of solvers compete to fill it at the best rate:
  • No slippage surprise: Price is locked at intent creation
  • No counterparty risk: All-or-nothing execution
  • Cross-chain atomic: you get what you asked for or nothing
  • MEV protection: intents prevent front-running by design
→ Unified Liquidity

​
Glossary: Key Terms

L1 = the original blockchain (Zcash, Bitcoin, Dogecoin). L1 is the source of truth — all state is ultimately anchored here.L2 = a layer built on top to add features. NEXUS is a metaprotocol layer — it processes transactions and posts state summaries back to L1, inheriting L1 security.
A standard L2 (like Ethereum rollups) has its own separate chain with its own consensus.NEXUS is a metaprotocol — no separate chain. It interprets Zcash/Bitcoin/Dogecoin transactions, processes them according to NEXUS rules, and writes state summaries back to those same chains. All data is ultimately anchored to L1.There is no bridge to hack — your ZEC sits in a Zcash vault, secured by Zcash’s own rules.
Virtual tokens representing your deposited assets on NEXUS — always 1:1 backed with the L1 chain:
  • vZEC: 1 vZEC = 1 zatoshi worth of ZEC deposited into your Zcash vault
  • vSAT: 1 vSAT = 1 satoshi of BTC (when Bitcoin joins)
  • vDOGE: represents deposited DOGE (when Dogecoin joins)
These are not new tokens — they are fully redeemable for the underlying L1 asset at any time.
Programs that live on-chain and run exactly as written. NEXUS contracts are written in Rust and compiled to WebAssembly (WASM). Once deployed, no company controls them — anyone can call them, all outcomes are transparent, and the code is permanent.
A way to prove a computation was done correctly without revealing all the inputs. NEXUS uses Groth16 ZK proofs (on Zcash) to prove all transactions were processed correctly. These are verified directly by Zcash nodes — the only UTXO chain with this capability natively.
A backup spending path built into every vault. If NEXUS becomes unresponsive, you can broadcast a pre-signed exit transaction after a ~2-week timelock and recover your ZEC directly on Zcash — no permission from anyone required.
For a complete list of technical terms, see the Glossary.

​
GitHub

RepositoryPurpose
yattacorp/nexus-sdk-typescriptTypeScript SDK — connect, deploy, call, vault, stealth
yattacorp/nexus-contract-templateFull contract template — SDK vendor, build pipeline, tests

​
Next Steps

Quick Start

Deploy your first contract on Zcash in 5 minutes

Contract Template

Clone the official template — SDK, build scripts, tests included

Deposit ZEC

Deposit ZEC to start using NEXUS

Architecture

Understand how NEXUS works under the hood