20833 is the first PR in an effort to implement mempool package acceptance in Bitcoin Core. In addition to review, developers will be encouraged to optionally implement a proof-of-concept that either shows how schnorr or taproot can be integrated into existing software or that demonstrates the new or improved features the proposals make possible. ● Website listing miner support for taproot activation: Bitcoin mining pool Poolin has created a website to help track miner support for activating taproot (including schnorr signatures and tapscript). Andrew Chow notes that as more diverse and complicated scripts become more widely used and for separation of concern reasons, there is no taproot equivalent for xpub/ypub/zpub. Wuille also lists three techniques for infeasible-to-exploit nonce generation, two techniques that are broken, and points out there is a huge gap of techniques in between that are neither known to be secure nor broken. All developers, academics, and anyone else with technical experience are welcome.</<br>r>
Anyone is welcome to contribute by opening issues and pull requests, reviewing newsletters and other material, and contributing translations. It has not yet been decided that BIP8 will actually be used for the activation, so alternative proposals may also be discussed during the meeting or at a subsequent meeting. The expected commitment is four hours a week for seven weeks, with one hour each week being a group meeting and the other three hours being your own independent review of the proposals. See also the discussion summary from the January 12th P2P developers meeting. ● Coinjoins without equal value inputs or outputs: Adam Ficsor (nopara73) started a discussion on the Bitcoin-Dev mailing list about two previously-published papers (1, 2) describing coinjoins Click That Link didn’t use either equal-value inputs or outputs. Discussion was still ongoing at the time of this writing. Any remainder that still needs to be sent can still use other paths. Several recent releases of Bitcoin Core might be re-released with slightly different version numbers so that their Windows binaries can use this certificate. 18956 uses the API on Windows systems to require Windows 7 or later
>
● Wasabi uses a centralized coordinator who organizes every coinjoin made using that software. ● HWI 2.0.2 is a minor release that adds support for message signing with the BitBox02, always uses h instead of ' to indicated BIP32 paths with hardened derivation, and includes several bug fixes. Bitcoin Core has been able to interface with hardware signers using HWI since Bitcoin Core version 0.18. Until this PR, however, the process required use of the command line to transfer data between Bitcoin Core and HWI. 14573 moves various miscellaneous options that opened separate dialogues in the Bitcoin-Qt GUI to a new top-level menu item labeled Window, hopefully making those options easier to find and use. But if you read Tim Bray’s post about it you’ll find that there are at least 5 different specifications of JSON! There have never been many tickets on this subject either before or after Bech32 so not sure this is an important point in making the argument for exchanges to make the switch. These affiliates are monitored specifically not to have large profits. In some cases, this may have been done for privacy benefits (e.g. Bitcoin Core currently tries to match the type of change output to the type of payment output) but, in most cases, this seems like a missed opportunity for wallets to send change to their own bech32 addresses for increased fee s
gs.
This may prevent the software from disclosing an incorrectly-generated signature that may leak information about the private key or nonce used to generate it. This was proposed for use with BIP67 key sorting, in particular as used with the sortedmulti output script descriptor. 20981 has been opened to explore potential use cases for USDT probes in Bitcoin Core now that the framework has been merged. This makes it easy for hooks to only execute in special cases. The new desc fields are not expected to be particularly useful at the moment as they can currently only be used with the scantxoutset RPC, but they will provide a compact way of providing all the information necessary for making addresses solvable to future and upgraded RPCs for Bitcoin Core such as those used for interactions between offline/online (cold/hot) wallets, multisig wallets, coinjoin implementations, and other cases. Also included are our regular sections with releases, release candidates, and recent code changes in popular Bitcoin infrastructure software.