Weekly Edition for Thursday, Nov 1
Originally published by BitcoinOptech on newsletter #19
Bitcoin Core #14451
Allows optionally building Bitcoin-Qt without support for the BIP70 payment protocol and adds a deprecation warning indicating the default support may be removed in a future release. The CEO of BitPay, which is the largest user of BIP70 (but which wants to use a different version of the protocol), indicated that they supported Bitcoin Core removing BIP70. Developers seem to be in favor of removing the protocol for security reasons and because it’s seeing declining use. The BIP70 dependency on OpenSSL resulted in the emergency release of Bitcoin Core 0.9.1 in 2014 as a result of the heartbleed vulnerability, and it is expected that removing it will eliminate the risk of future similar vulnerabilities.
Bitcoin Core #14296
Removes the deprecated addwitnessaddress RPC. This RPC was added in version 0.13.0 to enable testing segwit on regtest and testnet before it was activated on mainnet and built into the wallet. Since version 0.16.0, Bitcoin Core’s wallet has supported getting addresses directly using the regular getnewaddress mechanism.
Bitcoin Core #14468
Deprecates the generate RPC. This method generates new blocks in regtest mode but it requires getting new addresses from Bitcoin Core’s built-in wallet in order to pay them the mining block reward. A replacement method, generatetoaddress was introduced in version 0.13.0, which allows any regtest wallet to generate an address that will be paid the block reward. This is part of an ongoing effort to allow as many RPCs as possible to function without the wallet in order to improve test coverage of non-wallet nodes as well as to ease a future possible transition to fully separating the wallet from the node.
Bitcoin Core #14150
Adds key origin support to output script descriptors. Besides allowing you to pass an additional argument to the scantxoutset RPC, this doesn’t currently add any features to Bitcoin Core—but it will enable using key origin with BIP174 PSBTs and watch-only wallets when those parts of the software have been updated to use descriptors. See Newsletters #5, #7, #9, #12, and #17 for previous discussion of output script descriptors. Key origin support makes it possible to use extended pubkeys that have been exported from an HD wallet that uses BIP32 hardened derivation for protecting ancestor private keys, which helps make output script descriptors compatible with most hardware wallets.
Ensures that LND doesn’t leak information about any of its peers that aren’t advertising themselves as public nodes.
Adds the server-side communication protocol for watchtowers along with many tests verifying its proper operation. Correct use of the LN protocol requires regular monitoring of which transactions get added to the block chain, so watchtowers are servers designed to help defend the payment channels of users who expect to be offline for an extended period of time. As such, watchtowers are considered to be a key feature for enabling wider adoption of LN by less advanced users. However, a standard specification for watchtowers has not been agreed upon by the multiple implementations of LN, so LND is only putting this feature out for initial testing and is restricting its use to testnet.
- Merged PRs: 1
- Opened PRs: 2
|79||Update bip79 to require Access-Control-Allow-Origin support - link||Merge PR|
|32||Can not install bip32 library in nodejs project. Got MsBuildError - link||Open PR|
|159||bip-0159: Fix NODE_NETWORK_LIMITED threshold - link||Open PR|
- Merged PRs: 2
- Opened PRs: 4
- Opened Issues: 1
|7||BOLT 7: readability fixup - link||Merge PR|
|2||BOLT2: both nodes send
|✗||Specify valid signature hash flags (SIGHASH_ALL) - link||Open PR|
|3||BOLT 3: fix private key in internal part - link||Open PR|
|✗||Clarify temporary_channel_id’s acceptable usages - link||Open PR|
|7||BOLT 7: Push the sending of announcements_signatures back a little (amended wording) - link||Open PR|
|✗||Fee requirement for closing_signed is unclear - link||Open Issue|
- Merged PRs: 5
- Opened PRs: 0
- Opened Issues: 0
|✗||Add Amoveo [VEO] to list - link||Merge PR|
|✗||Add FUSION(FSN) at 288 - link||Merge PR|
|✗||Adding NRG - Energi code - link||Merge PR|
|✗||Add FIO (Foundation for Inter-Wallet Operability) - link||Merge PR|
|✗||added FreeCoin (FREE) - link||Merge PR|
WalletWasabi version Wasabi v1.0: Stable Release released.
The 1.0 Release of Wasabi is finally here. This release intentionally does not contain any feature updates, only reliability and performance improvements. Most noticeably on OSX.
- Where is Wasabi’s working directory located? Configuration, wallet and similar files can be found in
%appdata%\WalletWasabifolder on Windows and in
~/.walletwasabifolder on Linux/OSX.
- Can I use my own Tor instance, instead of Wasabi’s built in one? If you already have Tor, and it is running, then Wasabi will try to use that first, if it is not running, then Wasabi will use its built-in Tor. If you are running a Tor daemon not on the default port, then you can configure it in Wasabi’s Tools/Setting menu. If Wasabi is using your Tor daemon, then bear in mind that some Linux distributions’ package repositories ship with out of date Tor. In that case, either remove or shut down that Tor of yours or make sure it’s not out of date: Check Tor version:
tor --version. If it’s not at least
0.3.2.2, then see this writeup on how to update it.
- Why are the binary sizes so big? Wasabi is using client side filtering and these filters must be synced before using the wallet. The size of these filters are currently about 90MB. These filters are included with the binaries to avoid initial wallet syncing.
Installing Wasabi is straightforward. However, if you still couldn’t manage it, please take a look at the Installation Instructions guide.
If you want to build Wasabi from source code or update the source code check out these instructions.
- Expose the Tor website to the clearnet: http://wasabiwallet.io
- Buy code signing certificate to avoid warnings at Windows installation. https://github.com/zkSNACKs/WalletWasabi/issues/688 https://github.com/zkSNACKs/WalletWasabi/commit/a909b9718a116d94dc908886a6ce98dcfaceb5f0
- Rework OSX rendering. This makes the UI responsive. https://github.com/zkSNACKs/WalletWasabi/commit/7ca487738a271b15eced2c6e12e7be3cfead97f0 https://github.com/zkSNACKs/WalletWasabi/commit/63c35bf06ff47c89570adccb6a07ed8869cee9e4 https://github.com/zkSNACKs/WalletWasabi/commit/c52441ba95ce80e41c1c33ca9299dc91ca16e91f https://github.com/zkSNACKs/WalletWasabi/commit/4d2bd0e60aac9b69c579f0676e6c913d85db7f4c https://github.com/zkSNACKs/WalletWasabi/commit/4d5afbb1a0339170faac549969e782ded4cd6729 https://github.com/zkSNACKs/WalletWasabi/commit/8b304be1f26765b6a713e025e28097f66f2394ca https://github.com/zkSNACKs/WalletWasabi/issues/720 https://github.com/zkSNACKs/WalletWasabi/pull/736
- Create documentation: “A Technical Overview of Wasabi Wallet, Future Ideas, Plans and Strategy” https://github.com/zkSNACKs/Meta/
- Fix issues regarding fetching blocks from legacy (non-segwit nodes) https://github.com/zkSNACKs/WalletWasabi/commit/e3298d6055a5e9b9a28c249dc0aff63fceac8372 https://github.com/zkSNACKs/WalletWasabi/commit/9ce9395075ba29d0cca6fd408f35a2b96e7383c9 https://github.com/MetacoSA/NBitcoin/issues/568 https://github.com/zkSNACKs/WalletWasabi/pull/738
- Improve “Cannot close the application dialog” and explain closing it is not the end of the world https://github.com/zkSNACKs/WalletWasabi/issues/725 https://github.com/zkSNACKs/WalletWasabi/issues/730 https://github.com/zkSNACKs/WalletWasabi/commit/2da5b5f186240c217d10abf8aeb5ed7d86baf41a
- Monitor and restart Tor process when it crashes https://github.com/zkSNACKs/WalletWasabi/issues/747 https://github.com/zkSNACKs/WalletWasabi/commit/eba37ba943cf402a65fd42187e16f466771f0d0a https://github.com/zkSNACKs/WalletWasabi/commit/2c5b8ca124108997ce171035c27e25d19e3eb1d4 https://github.com/zkSNACKs/WalletWasabi/commit/393733c3abd5230ff0ac4e99c4f7bc2c04033c74 https://github.com/zkSNACKs/WalletWasabi/pull/749
- Clear mempool periodically https://github.com/zkSNACKs/WalletWasabi/issues/416 https://github.com/zkSNACKs/WalletWasabi/issues/743 https://github.com/zkSNACKs/WalletWasabi/commit/bd28638044c15bc313c6fe1478698a38ebf71bf8
- Automagically select the best coins to mix https://github.com/zkSNACKs/WalletWasabi/issues/753 https://github.com/zkSNACKs/WalletWasabi/commit/f5b190f707d6fad99169410aeafa52637ebaa512
- Optimize estimated minimum mixed amount and auto dequeuing https://github.com/zkSNACKs/WalletWasabi/issues/757 https://github.com/zkSNACKs/WalletWasabi/commit/abd9b81502d065ace0e237193f764e192a58292b
- Fix website refresh issues https://github.com/zkSNACKs/WalletWasabi/issues/762 https://github.com/zkSNACKs/WalletWasabi/commit/8163d63342aca04f9861eb7c680a076e612c3af3
- Try to tackle a once in a month random banning of everyone from coinjoin https://github.com/zkSNACKs/WalletWasabi/issues/716 https://github.com/zkSNACKs/WalletWasabi/commit/d729b65f95b422abb2e88195a0a6d52db7e97f24
- Fix issues regarding Arch Linux https://github.com/zkSNACKs/WalletWasabi/issues/758 https://github.com/zkSNACKs/WalletWasabi/pull/766 https://github.com/zkSNACKs/WalletWasabi/commit/5942111e8a3bb9feccf3aef55d9e26dc2049d72b
- Resolve Linux (GTK) warning https://github.com/AvaloniaUI/Avalonia/pull/2006
- Detect outdated Tor in known outdated Linux distros https://github.com/zkSNACKs/WalletWasabi/commit/ce5e7445c4323742eb7eb7eec89b00901412f331
- Enable dequeue when Internet is down https://github.com/zkSNACKs/WalletWasabi/commit/24b1c70c2f771276926fcd880769737defd3b981
- Fix bug: “wallet shutdown was slow if Internet went down” https://github.com/zkSNACKs/WalletWasabi/commit/c38d4c79d8f8fc2494fef54a603558565c605a4c
- Handle HEAD requests https://github.com/zkSNACKs/WalletWasabi/commit/a8b3806a6c9487f642846044fa459eef481f3644
- Update filters checkpoint https://github.com/zkSNACKs/WalletWasabi/commit/c62a76df62d90394ffe6243e63a5ad7f9f793ffc