Bitcoin Core

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 security and operational guidance create separate rpc users for separate applications or environments store rpc credentials in a secrets manager rotate or delete rpc users that are no longer needed keep bitcoin core access server side do not depend on wallet rpc methods unless explicitly supported for your node verify network, node type, rpc, and zmq behavior before going live related pages node backed infrastructure docid\ zx2rflnnfmmh8ixlmcxbavoltage infrastructure api docid\ mkkcrwcnbxlczedmvyylsnode security docid\ rlda4beej5rlbld3jm2qlresources docid\ uldxo3 oydlivaxfda5lk