Running a Node
A RISCy node validates transactions and blocks on a UTXO chain derived from Nexa, with an added RISC-V VM for smart-contract execution. Nodes communicate over a peer-to-peer (P2P) overlay network, the same general design Nexa inherits from the Bitcoin lineage.
Node binaries and release packages are under active development. Commands below are placeholders and will be finalized as builds ship.
Requirements
Hardware and OS requirements are TBD. As a rough starting point, expect requirements similar to a Nexa full node; final specs will be published here.
- OS: Linux / macOS (TBD)
- Disk: TBD
- RAM: TBD
- Network: open P2P port (TBD)
Install
# Coming soonRun
# Coming soonNetwork parameters
Values labeled (Nexa) are inherited and may be tuned before mainnet. Values marked TBD are RISCy-specific and not finalized.
| Parameter | Value | Notes |
|---|---|---|
| Ledger model | UTXO | Inherited (Nexa) |
| Consensus | Proof-of-Work | Inherited (Nexa) |
| PoW hash | Elliptic-curve multiplication + SHA-256 | Nexa spec |
| Target block time | 2 minutes | Nexa spec / TBD |
| P2P transport | TCP/IP overlay network | Inherited (Nexa) |
| Network magic | TBD (Nexa main net is0x72271221) | TBD for RISCy |
| Default P2P port | TBD | TBD |
| Default RPC port | TBD | TBD |
| Native coin | RISCY | — |
Security model
RISCy is secured via Drivechain (BIP-300/301):
- BIP-300 — hashrate-escrow that lets the sidechain inherit Bitcoin’s security budget.
- BIP-301 — blind merged mining, letting Bitcoin miners secure RISCy with no additional work and no separate token staking.
Connecting to the network
# Coming soonSeed nodes, testnet endpoints, and the August 21, 2026 fork details will be listed here as they are finalized.
Next steps
- Deploy a smart contract once your node is running.
- Read the Nexa protocol specification for base-layer networking and consensus details RISCy inherits.