Documentation Index
Fetch the complete documentation index at: https://docs.yattacorp.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Overview
The Bitcoin smart contract ecosystem has several approaches to enabling programmability. Here’s how NEXUS compares to other protocols.Quick Comparison
| Feature | NEXUS | OP_NET | Alkanes | Arch | Spark |
|---|---|---|---|---|---|
| Architecture | Metaprotocol | Metaprotocol | Metaprotocol | Separate chain | Payment Channels |
| Smart Contracts | Full WASM | Full WASM | WASM | Full WASM | No |
| Multi-Chain | BTC + ZEC + DOGE | BTC only | BTC only | BTC only | BTC only |
| Verification | ZK + BitVM2 | Optimistic | Indexer consensus | ZK Proofs | Channel state |
| Cross-Contract Calls | ✅ Yes | ✅ Yes | ✅ Yes | ✅ Yes | ❌ No |
| Encrypted Mempool | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No |
| Stealth Addresses | ✅ Yes | ❌ No | ❌ No | ❌ No | ❌ No |
| Unified Liquidity | ✅ V2 | ❌ No | ❌ No | ❌ No | ❌ No |
| Native ZK Verification | ✅ Zcash | ❌ No | ❌ No | ❌ No | ❌ No |
| User Self-Custody | ✅ 2-of-2 + Exit | Varies | ✅ Yes | Bridge | ✅ Yes |
Detailed Comparisons
NEXUS vs OP_NET
NEXUS vs OP_NET
OP_NET is a Bitcoin metaprotocol for smart contracts.Similarities:
- Both are metaprotocols (not L2s)
- Both support WASM smart contracts
- Multi-chain: NEXUS supports Bitcoin, Zcash, and Dogecoin. OP_NET is Bitcoin-only.
- Native ZK on Zcash: Groth16 proofs verified on-chain (no fraud proof delay).
- Unified liquidity: Cross-chain swaps between BTC/ZEC/DOGE in V2.
- BitVM2 fraud proofs: Permissionless challenges with bisection game.
- Pre-signed exits: Users always have unilateral exit capability.
NEXUS vs Alkanes
NEXUS vs Alkanes
Alkanes is a WASM-based smart contract protocol on Bitcoin.Similarities:
- Both are metaprotocols on Bitcoin
- Both support WASM smart contracts
- Both have cross-contract calls
- Full contract support: NEXUS enables complex DeFi contracts (Uniswap V3, lending protocols, DAOs). Build any contract you can imagine with full WASM capabilities.
- Multi-chain: NEXUS works on BTC, ZEC, DOGE. Alkanes is Bitcoin-only.
- ZK verification: NEXUS uses ZK proofs on Zcash. Alkanes relies on indexer consensus.
- Unified liquidity: Cross-chain swaps between BTC/ZEC/DOGE in V2.
- BitVM2 fraud proofs: Permissionless challenges with bisection game.
- Pre-signed exits: Users always have unilateral exit capability.
- EIP-1559 fee market: Dynamic base fee with predictable pricing.
- Rich SDK: Solidity-compatible patterns (Mapping, SafeMath, ReentrancyGuard).
NEXUS vs Arch Network
NEXUS vs Arch Network
Arch is a Bitcoin L2 using ZK rollup architecture.Similarities:
- Both support full smart contracts
- Both use ZK proofs for verification
- Metaprotocol vs separate chain: NEXUS is a metaprotocol (no separate consensus). Arch runs its own chain with a sequencer.
- Multi-chain: NEXUS supports BTC, ZEC, DOGE. Arch is Bitcoin-only.
- Native ZK verification: NEXUS leverages Zcash’s on-chain Groth16 verification.
- No bridge risk: NEXUS vaults are 2-of-2 multisig with pre-signed exits. Cross-chain bridges carry different trust assumptions.
- Unified liquidity: Cross-chain swaps in V2.
NEXUS vs Spark Protocol
NEXUS vs Spark Protocol
Spark is a Bitcoin payment channel protocol (Lightning-like).Similarities:
- Both enable fast Bitcoin transactions
- Both use pre-signed transactions for security
- Smart contracts: NEXUS supports full WASM contracts. Spark is payments-only.
- No channel management: NEXUS doesn’t require channel opening/closing.
- Multi-chain: NEXUS works on BTC, ZEC, DOGE. Spark is Bitcoin-only.
- DeFi: NEXUS supports AMM, tokens, lending. Spark is for payments.
- No liquidity lockup: Spark requires locking funds in channels.
- Instant finality for payments
- Lower fees for simple transfers
- More mature payment routing
NEXUS Unique Features
1. Multi-Chain Unified Liquidity (V2)
NEXUS is the only protocol that unifies liquidity across Bitcoin, Zcash, and Dogecoin:2. EIP-1559 Dynamic Fee Market
NEXUS implements a full EIP-1559 fee market - the first Bitcoin metaprotocol to do so:- Dynamic base fee that adjusts with block utilization (40% target)
- Priority fees for faster inclusion
- Predictable fees - no more fee spikes or stuck transactions
- Fee estimation API with slow/standard/fast/instant tiers
- 12.5% max change per block - smooth transitions, no volatility
3. Encrypted Mempool (MEV Protection)
NEXUS encrypts all transactions before submission. Content is hidden from everyone — including node operators — until block inclusion. This prevents:- Sandwich attacks on AMM swaps
- Front-running profitable contract calls
- Transaction snooping before execution
4. Stealth Addresses (On-Chain Privacy)
Every wallet on NEXUS can publish a stealth meta-address. Senders generate unique one-time addresses per transaction — observers cannot link transactions to the same wallet. Supports both transfers and contract calls. Uses ERC-5564 Dual-Key protocol with 1-byte view tags (filters 99.6% of non-matching scans client-side).5. Parallel Mempool with Lock-Free Validation
High-throughput transaction processing:- Multi-threaded validation workers - parallel signature verification
- Lock-free submission queues - no contention bottlenecks
- Batch insertion - reduced lock contention for mempool writes
- Signature verification cache - LRU cache prevents redundant crypto ops
- Per-address nonce tracking - concurrent nonce management
- Backpressure handling - graceful degradation under load
6. True Self-Custody with Vaults
Every NEXUS vault provides:- 2-of-2 multisig: User + protocol keys required for normal operations
- Pre-signed exit: User always holds a pre-signed withdrawal transaction
- 2-week timelock: Exit transactions have a timelock for fraud proof window
- 1:1 backing: L1 balance = NEXUS balance always verifiable
7. Full WASM Programmability with Advanced Features
Unlike token-focused protocols, NEXUS supports:- Cross-contract calls (XCC) - contracts can call other contracts
- Delegate calls - execute code in caller’s context
- Factory pattern - deploy contracts from templates (
xcc::deploy_template) - Value transfers - send native tokens with calls
- Bitcoin SPV proofs - verify BTC transactions on-chain
- L1 block data access - read Bitcoin/Zcash/Doge block hashes
8. Solidity-Compatible SDK
Familiar patterns for EVM developers:9. Contract Templates for Factory Patterns
Deploy child contracts without storing bytecode:- AMM factories - deploy new trading pairs
- Token factories - create new tokens
- Proxy patterns - upgradeable contracts
- Reduced gas costs - no bytecode storage in factory contract
When to Use NEXUS
| Use Case | Best Choice |
|---|---|
| Multi-chain DeFi | ✅ NEXUS |
| BTC/ZEC/DOGE swaps | ✅ NEXUS |
| Complex smart contracts | ✅ NEXUS |
| Fast ZK-verified finality | ✅ NEXUS (Zcash) |
| Simple BTC payments | Spark/Lightning |
| Runes token trading | Alkanes |
| Bitcoin-only separate chain | Arch |
Summary
NEXUS differentiates through:- Multi-chain: Only protocol spanning BTC, ZEC, and DOGE
- Native ZK: Leverages Zcash’s on-chain Groth16 verification
- Encrypted mempool: MEV and front-running protection on every transaction
- Stealth addresses: On-chain privacy for transfers and contract calls
- Unified liquidity: Cross-chain swaps via intent exchange (V2)
- True self-custody: 2-of-2 vaults with pre-signed exits
- Full programmability: Arbitrary WASM contracts with cross-contract calls