- What is it-healer/laravel-bitcoin used for?
- It is a Laravel package that connects PHP applications to Bitcoin Core over JSON-RPC and provides a familiar service layer for managing wallets, addresses, and transactions. It also covers BIP39 mnemonic generation and validation for wallet onboarding and recovery flows.
- How do I install it-healer/laravel-bitcoin in a Laravel app?
- Install it with Composer using composer require it-healer/laravel-bitcoin. The package uses standard Laravel package mechanics, including an auto-discovered service provider and publishable configuration, so you can publish the config and set your Bitcoin Core connection details. Check composer.json for any required PHP extensions before rolling it out.
- Does laravel-bitcoin require a running Bitcoin Core node?
- Yes. The package is an integration layer for Bitcoin Core via JSON-RPC, so it expects a reachable node with RPC credentials configured. It does not replace Bitcoin Core or provide a hosted node; you need to run or connect to your own infrastructure.
- Which Laravel and PHP versions does it-healer/laravel-bitcoin 2.0.3 support?
- The v2.0.3 release note does not state a supported PHP and Laravel version matrix, so you should verify the constraints in the package's composer.json before adopting it. The package is described as fitting standard Laravel 10/11 service architecture, but confirm that against your application's PHP version and required extensions.
- What changed in laravel-bitcoin v2.0.3?
- The v2.0.3 release removed the old library that backed BIP39 mnemonic generation and validation. The release note is a single line with no migration guide, changelog detail, or list of removed symbols, so you should diff 2.0.2 against 2.0.3 before upgrading.
- Is v2.0.3 a breaking change even though it is a patch release?
- Removing a dependency can be a breaking change if downstream code referenced that library's classes, exceptions, or config keys, but it can be internal-only if the public contract is unchanged. Because it shipped as a patch without a migration guide, treat it as potentially breaking and review the source diff rather than assuming semantic versioning guarantees.
- How do I verify BIP39 mnemonics after upgrading to 2.0.3?
- Run the official BIP39 reference test vectors against 2.0.3 in an isolated harness. Also check that mnemonics generated by 2.0.2 validate and re-derive identically under 2.0.3 for the same entropy input, since a change in mnemonic output would silently break recovery flows.
- Can I use laravel-bitcoin for wallet onboarding and recovery phrase UX?
- Yes, the package targets BIP39 mnemonic generation and validation, which supports wallet onboarding, key derivation flows, and recovery-phrase UX. For production, verify wordlist integrity, entropy source, checksum bits, and NFKD normalization against the BIP39 specification before relying on it.
- How should I test a Laravel Bitcoin integration safely?
- Use a regtest or testnet Bitcoin Core node rather than mainnet for integration testing, and pin a known-good package version while you validate behavior. For the BIP39 path, combine unit tests against official test vectors with a round-trip check that 2.0.2-generated phrases still validate and derive identically under 2.0.3.
- Should I upgrade to laravel-bitcoin 2.0.3 in production?
- Pin production to the last known-good version, reported as 2.0.2, until you have reviewed the 2.0.2-to-2.0.3 diff and verified BIP39 behavior. If the dependency removal was security-driven, escalate priority and ask the maintainer for the rationale; otherwise batch the upgrade with your next routine dependency cycle after verification.