As a consequence, Bitcoin is saddled with a variety of features which are cumbersome, onerous, restrictive, and impair its ability to innovate, all in service of a longer-term or more overarching goal. In this article I’ll cover a few of the tradeoffs where Bitcoin opted for the unpopular or more challenging path, in pursuit of an ambitious long-term objective:
Joule’s interface is just the start of automatic payments while browsing the web with Lightning. There’s currently ongoing discussion of how to programmatically request, configure, and inspect allowances via WebLN, a discussion of using the HTTP 402 response code for payments (that could be done automatically), and new features that would make programmable auto-payments more feasible (e.g. customizable LND macaroons.)
When a researcher has discovered a solution to a problem, they share their proposed changes with other protocol developers. This sharing could be in the form of an email to the bitcoin-dev mailing list, a formal white paper, and/or a Bitcoin Improvement Proposal (BIP).
ontrol how much information we have about your holding…t every hardware wallet uses the
m/44'/... BIP32 namespace to organize your addresses and balances. When you use such a hardware wallet on our platform, we export public keys from the
m/45'/... namespace. This means that we have no idea what your self-custody addresses or balances are outside our platform. You can even customize this BIP32 path when you upload your public key, giving you even greater ability to control how much information we have about your holdings.
…proven “cloud cryptonetwork services” is a separate decision with its own thesis and due diligence. The idiosyncratic risk of all of the “cryptonetwork tokens” are a strict superset of Bitcoin’s, if Bitcoin has a fundamental reason it can not function — regardless of any reasonable changes to its network consensus rules — then that flaw would inherently be shared with any other “cryptonetwork token”.