Weave Code
Bitcoind Bundle Laravel Package
nbobtc/bitcoind-bundle
Symfony bundle that integrates the nbobtc/bitcoind-php client with Bitcoin Core’s JSON-RPC API, simplifying connection configuration and service injection so Symfony apps can query the daemon for blockchain and wallet operations.
Allows you to use the bitcoind service in a symfony2 project
Frequently asked questions about Bitcoind Bundle
- Can I use nbobtc/bitcoind-bundle in a Laravel application?
- No. nbobtc/bitcoind-bundle is a Symfony2 bundle that registers a Symfony Bundle and expects the Symfony kernel, so it cannot run inside a Laravel application. The only transferable part is the underlying nbobtc/bitcoind-php JSON-RPC client. In Laravel you would wire that client into a service provider yourself, which is roughly a half-day of work.
- What is nbobtc/bitcoind-bundle used for?
- It integrates a Bitcoin Core daemon with Symfony applications through a configurable JSON-RPC client. It exposes the daemon as a service so Symfony apps can query blockchain data, manage wallets, and send transactions using dependency injection and configuration. It is lightweight glue around the nbobtc/bitcoind-php client and contains no domain logic of its own.
- How do I install nbobtc/bitcoind-bundle?
- You would install it with Composer, register the bundle in the Symfony kernel, and configure the daemon host, port, and credentials in Symfony configuration. That process is Symfony-specific and does not apply to Laravel. For a Laravel app, install the underlying client library and bind it in a service provider instead.
- Which Laravel versions does nbobtc/bitcoind-bundle support?
- None officially. The bundle targets Symfony 2.x and PHP 5.5 to 7.x, with a Guzzle-era HTTP dependency that will conflict with contemporary Laravel applications. It also does not fit modern Symfony 5, 6, or 7 applications. Treat it as a code sample rather than a supported Laravel dependency.
- What Bitcoin Core RPC methods can I call with this package?
- The bundle exposes the RPC surface of the underlying nbobtc/bitcoind-php client, covering wallet, blockchain, and network operations. That includes balances, confirmations, transaction lookups, and wallet commands, depending on what your node allows. Always verify each method against the specific Bitcoin Core version on your node, because RPCs are removed and renamed over time.
- How do I configure the Bitcoin Core JSON-RPC connection?
- Configuration covers the daemon host, port, and RPC credentials. In a Laravel application you should source those values from the secret manager and never expose the RPC endpoint publicly. Use TLS or a Unix socket, and restrict access to the node at the network layer.
- Is nbobtc/bitcoind-bundle maintained and safe for production?
- It has around 15 stars, zero dependents, no active community, and no security maintenance for years. Symfony 2.x has been end-of-life since 2018 and PHP 5.x earlier still, so the package should be treated as an unsupported code sample. The larger production risk is operating a Bitcoin Core node, not the PHP package itself.
- What are the alternatives to nbobtc/bitcoind-bundle for Laravel?
- Use the underlying nbobtc/bitcoind-php client or a maintained equivalent such as denpa/php-bitcoinrpc directly, and wrap it in a Laravel service provider. For broader Bitcoin functionality, bitwasp/bitcoin is another option. You can also use a managed Bitcoin Core provider like QuickNode, Blockdaemon, or Chainstack if you do not want to operate a node.
- How should I test Bitcoin Core RPC integration in Laravel?
- Start with a regtest spike to prove the read paths, which should take about two days, then plan a credible testnet rehearsal that takes about two weeks. Mock the RPC client for unit tests and keep integration tests against a real node. Define your confirmation and reorg policy before testing write paths.
- Can I use wallet RPCs like sendtoaddress with this package in production?
- The underlying client can call wallet RPCs, but wallet operations have a much larger blast radius than read-only chain queries and should be treated as a separate review. You need idempotency on the write path, strict credential handling, and method verification against your Bitcoin Core version. If you only need balances, confirmations, and transaction lookups, keep the integration read-only to reduce scope.
Weaver
How can I help you explore Laravel packages today?