Bitcoin Core

7 min

Voltage can host Bitcoin Core infrastructure for teams that need direct Bitcoin base-layer access.

Use this page when your application needs a managed Bitcoin Core node for chain data, mempool visibility, peer/network data, RPC calls, or event-driven Bitcoin infrastructure workflows.

When To Use Bitcoin Core

Use Bitcoin Core when your application needs direct access to Bitcoin base-layer node data, such as:

blockchain and network information

mempool and peer data

transaction and block lookups

event-driven block or transaction notifications, if ZMQ is enabled for your node

managed Bitcoin Core infrastructure for production workloads

Do not use a Voltage-hosted Bitcoin Core node as a hot wallet. Treat it as infrastructure for node access and chain data, not as a place for application custody.

What Voltage Provides

Voltage manages the infrastructure required to run the Bitcoin Core node and exposes connection details for approved access methods.

The current dashboard provides:

node status and current block height

node details and system usage

RPC users and a dedicated RPC host

selected settings and the rendered bitcoin.conf

peers

logs

Deployment Options

The current dashboard offers full and pruned nodes on mainnet, testnet, and Mutinynet. Availability depends on the team's current product access and plan, so use the choices shown for the team in the dashboard.

Before choosing a node type, confirm whether your workload requires:

full chain history

a pruned node

transaction index support

custom peer behavior

a specific Bitcoin Core version

mainnet or a test or sandbox network

Do not promise a fixed startup or synchronization time. Initial startup can vary with network and snapshot availability.

RPC Access

Bitcoin Core RPC access lets a server-side application call supported Bitcoin Core methods against the hosted node.

A current RPC setup uses:

a dedicated RPC user

an RPC password

the dedicated RPC host shown in the Voltage dashboard

port 8332 for mainnet, 18332 for testnet, or 38332 for Mutinynet

Store RPC credentials in secret storage. Do not expose them in client-side applications, mobile apps, logs, screenshots, or public repositories.

Adding or deleting an RPC user updates node configuration and restarts the node.

Wallet-dependent RPC methods should not be assumed available. Confirm current method availability before designing wallet-dependent workflows.

ZMQ Access

ZeroMQ can be useful for event-driven workflows such as block or transaction notifications.

The current Connect page lets an operator enable or disable ZMQ. Changing this setting restarts the node.

Use the endpoint and connection material shown by the current product. Do not copy the old TLS-proxy endpoint or example repository until its current support status is verified.

Settings, Peers, And Logs

The current Settings page exposes selected mempool, indexing, peer, network, seed, whitelist, and debug options, plus the rendered bitcoin.conf. Saving settings restarts the node.

Use the dashboard to:

inspect node status and sync progress

review network and peer behavior

confirm whether transaction indexing or mempool settings match your workload

review logs during setup or troubleshooting

Change low-level settings only when you understand the Bitcoin Core behavior and have a rollback plan.

Relationship To Lightning Nodes

A Voltage-hosted Lightning node does not require customers to manage a separate Bitcoin Core node for ordinary LND application integration.

If your architecture requires a dedicated Bitcoin Core node, a Lightning node connected to a specific Bitcoin Core node, or base-layer data access alongside Lightning workflows, confirm the current supported architecture with Voltage before implementation.