Supported and used in production by Purse. Bcoin is an advanced fullnode implementation of bitcoin. Bitcoin txid 1 was designed to make Bitcoin accessible.
Optimized Engineered from the ground-up to create scalable, flexible, and efficient production-ready systems. Secure Bcoin is consensus conforming and adheres to the strict security standards of the original implementation maintained by Bitcoin Core. Production Bcoin is the first fullnode implementation built specifically for production systems at scale. Originally created to be used as backend infrastructure for Purse. Built-in Accounting Large scale e-commerce company processing many transactions?
Bcoin has wallet accounting built right in, making user fund management even easier. Written from Scratch Developing applications that natively utilize bitcoin’s powerful financial network can be difficult, even for seasoned developers. Bcoin abstracts out the most difficult components of bitcoin development — allowing you to focus on creating great functionality, with hardened security at its core. Consensus Tested Consensus aware, bcoin conforms to all consensus measures present in Satoshi’s reference implementation. Bcoin can even be used to mine on the bitcoin mainnet, and has successfully been used to mine blocks on it as well.
Industry Trusted Companies like Ripio, Bitpay and Purse have built bitcoin utilities and tools on bcoin that are now core components of their infrastructure for large-scale daily use by consumers. With bcoin, companies can quickly begin work on robust, future-ready Proof of Concepts to be deployed on the bitcoin mainnet. Advanced Account Management Bcoin makes managing a large number of user addresses and accounts more seamless. Scale to millions of addresses and manage user funds with ease, without having to worry about key migrations as your business grows. Both are already implemented and ready for testing and experimentation.
It’s phenomenal work and I’m in awe of what and his colleagues have pulled off. This article summarizes my first thoughts about the correct way a Bitcoin client should enable its operator to issue transactions. It is based on my reflexion as well as my experience in broadcasting dozens of hand-crafted transactions for which the bitcoin-core built-in wallet repeatedly demonstrated its ineptitude. As it currently stands, the wallet is an embedded part of the reference implementation.
The job of the node is to connect to others via the Internet, and to exchange information with them. The job of the wallet is to prevent others from connecting via the Internet, which makes the tension quite evident. The wallet, which uses the previous pieces to create transactions, sign and broadcast them. Query the UTXO for unspent outputs given a set of addresses. While the latter doesn’t present much implementation challenges, the former is a whole different story, depending on the particular way it is implemented. Obviously this means the transaction history for addresses can’t be directly queried from the node without a full blockchain rescan. Whatever the approach, the node simply has to output UTXOs, and receive signed transactions as input for broadcast.