Weave Code
Bips Laravel Package
bitcoin/bips
Comprehensive collection of Bitcoin Improvement Proposals (BIPs) in one place. Browse specifications for Bitcoin standards, consensus rules, wallets, and protocols, with the full text and history of each BIP for quick reference and research.
Bitcoin Improvement Proposals
Frequently asked questions about Bips
- Can I use bitcoin/bips to validate Bitcoin transactions in a Laravel app?
- Yes, the package provides BIP-compliant tools like BIP-70 (payment protocol) and BIP-32 (hierarchical wallets) for transaction validation. You’ll need to integrate it with Laravel’s service container and handle cryptographic operations via ext-sodium. For full validation, pair it with Bitcoin Core RPC or a block explorer API.
- What Laravel versions does bitcoin/bips support?
- The package officially supports Laravel 5.8+ (PHP 7.4+). Older versions may require polyfills for typed properties or runtime checks. If you’re on Laravel <5.8, test thoroughly as dependency injection patterns differ. PHP 8.x is recommended for performance.
- How do I configure bitcoin/bips for testnet vs. mainnet?
- Use the `BIPNetwork` class to set the network type (e.g., `BIPNetwork::TESTNET`). Override this in Laravel’s `config/bitcoin.php` for environment-specific setups. The package auto-adjusts address formats and consensus rules based on the selected network.
- Does bitcoin/bips work with Laravel’s service container?
- Absolutely. Bind BIP classes (e.g., `BIP32`, `BIP70`) as singletons in a service provider. Example: `app()->bind(BIP32::class, fn() => new BIP32(BIPNetwork::MAINNET));`. For facades, create a `BipFacade` to abstract operations like `Bip::deriveKey()`.
- What extensions are required, and how do I install them?
- The package mandates `ext-sodium` (for cryptography) and `ext-gmp` (for large-number math). Install via PECL: `pecl install gmp sodium`, then enable in `php.ini`. For Docker, add `RUN docker-php-ext-install gmp sodium` to your `Dockerfile`. Missing extensions will throw fatal errors.
- Can I use bitcoin/bips for Lightning Network or other non-Bitcoin assets?
- No, this package is **Bitcoin-only** and focuses on BIPs like BIP-32 (wallets), BIP-70 (payments), and BIP-143 (SegWit). For Lightning Network, use specialized libraries like `lnurl-rust` or `lightning-network/lightning`. The package lacks support for altcoins or sidechains.
- How do I test BIP operations in Laravel’s PHPUnit?
- Mock BIP classes (e.g., `BIP32`) in tests to avoid cryptographic overhead. Use Bitcoin Core’s test vectors to validate outputs. Example: `assertTrue(BIP32::validateMasterKey($testVector));`. For edge cases, test malformed inputs (e.g., invalid base58 addresses) with `expectException(BIPException::class)`.
- Are there alternatives to bitcoin/bips for custom BIP implementations?
- For lower-level control, consider `bitcoin-php/bitcoin`, which offers a broader Bitcoin toolkit but lacks BIP-specific abstractions. If you need to extend BIPs (e.g., BIP-47 for multi-sig), `bitcoin-php/bitcoin` provides more flexibility. However, `bitcoin/bips` is the canonical reference for compliance.
- How do I handle BIP versioning if Bitcoin Core updates a BIP?
- Monitor Bitcoin Core’s [BIPs list](https://github.com/bitcoin/bips) for changes. The package follows semantic versioning, so major updates may require code reviews. For critical apps, backport BIP changes manually or fork the package. Laravel’s config caching can memoize BIP operations to mitigate runtime overhead.
- Can I use bitcoin/bips in production without Docker?
- Yes, but ensure `ext-sodium` and `ext-gmp` are installed system-wide. Verify with `php -m | grep sodium,gmp`. For production deployments, use Laravel’s `config('bitcoin.cache')` to store expensive BIP operations (e.g., script validation) and set up monitoring for cryptographic failures.
Weaver
How can I help you explore Laravel packages today?