RTNC Developer Overview

Key concepts for building tools, services, and integrations around RTNC nodes.

1. Philosophy for Developers

RTNC is designed for straightforward integration: standard JSON-RPC, predictable behavior, and minimal protocol complexity. The goal is to let developers focus on real applications without protocol-level gimmicks or unnecessary economic constructs.

2. Node Interfaces

Developers typically interact with RTNC in three ways:

  • JSON-RPC over HTTP (local, authenticated).
  • Command-line interface (rtnc-cli or equivalent).
  • Reading blockchain data from local storage or indexers.

3. Example JSON-RPC Calls

Exact method names may follow the standard UTXO-based patterns. Examples:

# Get general blockchain info
rtnc-cli getblockchaininfo

# Get network info
rtnc-cli getnetworkinfo

# Get wallet info
rtnc-cli getwalletinfo

# Send a transaction
rtnc-cli sendtoaddress <address> <amount>

Always consult the official RTNC Core help output (rtnc-cli help) once binaries are available.

4. Wallet and Address Handling

RTNC uses public/private key pairs and UTXO-style addresses. Developers should never store raw private keys in logs, analytics systems, or third-party services.

Common patterns:

  • Generate addresses on a secure node.
  • Use RPC to monitor balances and activity.
  • Maintain encrypted wallet backups in secure storage.

5. Indexing and Explorers

For explorers, dashboards, or analytics tools, developers often maintain indexed blockchain views:

  • Enable txindex=1 in rtnc.conf for full transaction indexing.
  • Parse blocks directly or via RPC into a database (e.g., PostgreSQL).
  • Expose higher-level APIs to web or mobile clients.

6. Testnet and Regtest for Development

All experimentation should begin on non-production networks:

  • Testnet for multi-node, public-like behavior.
  • Regtest for rapid, scriptable edge-case testing.

See the Testnet & Regtest Setup guide for details.

7. Security Considerations

  • Never expose RPC ports directly to the internet.
  • Use strong, unique RPC credentials.
  • Harden nodes intended for production environments.
  • Assume mainnet behavior reflects real, irreversible protocol outcomes; test thoroughly on non-production networks first to avoid unintended transactions or misuse.

8. Licensing and Contributions

RTNC Core will specify an open-source license (e.g., MIT-style). Developers are encouraged to contribute documentation, patches, and tools through public repositories following contribution guidelines.