OP_NET Nodes
Introduction
OP_NET Nodes are full‐featured Bitcoin clients extended to run OP_NET smart contracts, manage token state, and power decentralized applications—without changing Bitcoin’s core rules. By combining Bitcoin Core’s UTXO handling with a lightweight WebAssembly runtime, OP_NET Nodes:
- Validate Bitcoin transactions exactly as before, ensuring full compatibility with Bitcoin Core and other nodes.
- Execute Wasm contracts off‐chain, deterministically applying state changes before anchoring results in standard Bitcoin transactions.
- Index token balances and contract data, letting wallets and dApps query your account or contract state in real time.
Storage Requirements
Archive mode only: A production‐ready OP_NET Node must keep every historical UTXO and contract state. Plan for at least 5 TB of fast SSD space to store Bitcoin’s full archive plus OP_NET data.
Why Run an OP_NET Node?
Running an OP_NET Node provides several advantages:
- Full Control: Direct interaction with the OP_NET environment for deploying contracts and managing UTXOs.
- Enhanced Security: Use your node to validate transactions and ensure trustless interactions.
- Decentralization: Contribute to OP_NET's distributed ecosystem.
- Development Environment: Test and debug smart contracts locally before deploying to mainnet.
Types of OP_NET Nodes
- Archive Node: Stores the entire Bitcoin blockchain and OP_NET data for full interaction.
- Full Node: Hosts the entire Bitcoin blockchain and processes all OP_NET interactions. (Coming Soon)
- Lightweight Node: Relies on trusted full nodes for blockchain data while focusing on OP_NET-specific interactions. (Coming Soon)
Node Selection
For development purposes, a lightweight node is usually sufficient. Use a full node for enhanced security and decentralized participation.
Networks Supported
OP_NET Nodes support multiple environments: Full List