v0.21.0 testing

MarcoFalke commented at 8:13 am on December 3, 2020: member

Link to announcement:

Let us know which version you tested on which operating system.

If you find an issue, please search Github for known issues first and then open a new Github issue. This meta issue should not be used to report bugs, as a single thread makes it impossible to track more than one topic.

See Release Notes for a list of changes, and testing reports for earlier releases (v0.19.0), for an idea what to test.

Release schedule: #18947

MarcoFalke added the label Tests on Dec 3, 2020

hebasto commented at 10:49 am on December 3, 2020: member

v0.21.0rc2 on ODROID-HC2 (arm7) + Armbian (based on Focal) without GUI – works fine.

v0.21.0rc2 on Linux Mint 20, Tor-only mode – no incoming connections to my v3 hidden service since 2020-11-27

jonatack commented at 5:24 pm on December 3, 2020: member

I’m happy to addnode to anyone who is testing 0.21 with tor v3 so you can see an inbound connection. Ping me on bitcoin-core-dev IRC.

decryp2kanon commented at 1:12 am on December 5, 2020: contributor

v0.21.0rc1 on Ryzen + Debian 10 (buster), normal GUI – works fine include IBD

ghost commented at 9:32 am on December 5, 2020: none

0.21.0rc2-x86_64-linux-gnu Bitcoin-QT on Debian 10 (Buster) (Intel KVM) starts and runs ok. No inbound connections with onlynet=onion to v3 Onion service.

jonatack commented at 7:05 pm on December 5, 2020: member

0.21.0rc2 downloaded binary running on Debian 5.9.11-1 (2020-11-27) x86_64 GNU/Linux running tor v3

jarolrod commented at 0:23 am on December 7, 2020: member

Tested (0.21rc2) torv3, signet, and gui IBD on Arch Linux 5.8.16. Tested gui and IBD on FreeBSD 12.2, and macOS 10.15.7. Everything I tested works fine. @hebasto I was able to connect to your (among other) Torv3 node in my testing.

GhostOfSatoshi commented at 5:21 am on December 7, 2020: none

v0.21.0rc2 on Win2016 (up to date) Works fine so far (without Tor)

mjdietzx commented at 5:42 pm on December 11, 2020: contributor

0.21.0rc2-osx.dmg downloaded binary works on macOS Big Sur (Version 11.0.1) ✅

jarolrod commented at 11:30 pm on December 11, 2020: member

0.21.0rc2-osx.dmg downloaded binary works on macOS Big Sur (Version 11.0.1) white_check_mark

There’s a new release candidate (rc3) and binaries

jonatack commented at 0:01 am on December 12, 2020: member

0.21.0rc3 downloaded binary running on Debian 5.9.11-1 (2020-11-27) x86_64 GNU/Linux running tor v3

mjdietzx commented at 1:46 am on December 12, 2020: contributor

0.21.0rc2-osx.dmg downloaded binary works on macOS Big Sur (Version 11.0.1) white_check_mark

There’s a new release candidate (rc3) and binaries

🚨 0.21.0rc3-osx.dmg downloaded binary, does not work on macOS Big Sur (Version 11.0.1). When it opens: "Bitcoin Core" is damaged and can't be opened. You should move it to the trash

achow101 commented at 1:52 am on December 12, 2020: member

0.21.0rc3-osx.dmg downloaded binary, does not work on macOS Big Sur (Version 11.0.1). When it opens: "Bitcoin Core" is damaged and can't be opened. You should move it to the trash

This is a known issue and we are actively ~~beating our heads against Apple’s walled garden wall~~ debugging this issue. See the super long discussion that we are having on IRC, starting around 11:09

jsarenik commented at 5:55 pm on December 13, 2020: none

rc3: 0.21.0rc3-x86_64-linux-gnu.tar.gz mainnet, testnet, signet (all with latest master C-Lightning on top), no GUI

fanquake pinned this on Dec 16, 2020

sangaman commented at 1:22 pm on December 16, 2020: contributor

I’m using rc3 on an arm7 ODROID HC1 on Ubunut 18.04 with lnd & electrs and peercfilters enabled, so far so good.

philipglazman commented at 3:37 pm on December 16, 2020: none

0.21.0rc3 for Alpine Linux works fine

0xB10C commented at 10:34 pm on December 17, 2020: member

0.21.0rc3 compiled from source, Ubuntu 20.04 + i3: tested mainnet, testnet, and signet. created a descriptor wallet in qt, tested torv3 with addnode, and checked if anchors.dat is created on shutdown and removed on startup.

I’ve noticed the “Advanced options” label being cut-off in the wallet creation dialog.

edit:

The label Is not cut-off when running the binaries and qt looks quite different in general. Guess I have a different qt5 version locally.

jonatack commented at 10:47 pm on December 17, 2020: member

@0xB10C pinged me and I verified not seeing the text issue on rc3 binary or master from source (Debian, without i3)

hebasto commented at 11:37 pm on December 17, 2020: member

@0xB10C

0.21.0rc3 compiled from source, Ubuntu 20.04 + i3: tested mainnet, testnet, and signet. created a descriptor wallet in qt, tested torv3 with addnode, and checked if anchors.dat is created on shutdown and removed on startup.

I’ve noticed the “Advanced options” label being cut-off in the wallet creation dialog.

Mind testing https://github.com/bitcoin-core/gui/pull/155 ?

dhruv commented at 1:49 am on December 18, 2020: member

Tested using these instructions

Hardware: MacBook Pro (13-inch, 2018) OS: macOS Catalina 10.15.7 (19H2) RC: bitcoin-0.21.0rc3

Tests:

Created a descriptor wallet(loaded the sqlite file and ran some sql queries)
Ran tor via docker and connected over Torv3 (saw tor v3 peers)
Connected to common signet (saw one connection; used faucet; saw unconfirmed balance)
Ran through the anchors test(checked anchors.dat created with clean shutdown, disappears on startup; also that it is not created with unclean shutdown)

MarcoFalke referenced this in commit 3dd3f7c0af on Dec 18, 2020

sidhujag referenced this in commit b1e56504e0 on Dec 18, 2020

glozow commented at 10:05 pm on December 18, 2020: member

0.21.0rc3 compiled from source, macbook pro 2019, macOS Catalina 10.15.7

also went through this doc - descriptor wallets, torv3, signet, anchors worked nicely

LarryRuane commented at 10:54 pm on December 18, 2020: contributor

Tested using these instructions.

Hardware: Oracle VirtualBox VM 12GB, host: Windows 10 Dell XPS-15 laptop
OS: Ubuntu 18.04
Release: bitcoin-0.21.0rc3 built from source (with wallet and gui)

Tested (everything except Tor):

new descriptor wallet, both GUI and command-line
ran signet GUI, tapped the faucet, received, sent payment to someone else, received!
- first send attempt failed with fee estimation error, so I restarted with -fallbackfee and then it worked
- Tried several qt features, like peers and command windows, all worked as expected
tested anchor, file created and removed as expected, ran the following script both before and after restarting, and the results matched:

0src/bitcoin-cli getpeerinfo | jq '[.[]|select(.connection_type == "block-relay-only")|.addr]|sort'

jamaljsr commented at 11:49 pm on December 18, 2020: none

0.21.0rc3 compiled from source on MacBook Pro (16-inch, 2019) running MacOS Big Sur v11.0.1

Followed this test script. Tested descriptor wallets, torv3, anchors. No issues.

Tried signet via bitcoind and GUI, both failed to connect to any peers. Followed instructions on Bitcoin Wiki. Possibly an issue with my system but I was able to get peers/headers/blocks on mainnet, mainnet+tor, and testnet. Not sure how to troubleshoot further.

Edit: found signet issue in #20637 so safe to ignore.

hebasto commented at 8:00 am on December 20, 2020: member

In the GUI the detail view shows disconnected peer’s info. See https://github.com/bitcoin-core/gui/issues/158

mjdietzx commented at 8:48 pm on December 21, 2020: contributor

Edit: this behavior is correct and expected ✅ - so I’m crossing out my comment

~~One thing I noticed while testing that doesn’t look quite right (I’ll provide a summary of all the testing I’ve done once I finish).~~

~~I have a watch-only wallet. Everything works properly. But when I run getwalletinfo in Console for this wallet:~~

Everything is correct in the UI, and txcount is correct in the returned json response. However, balance is incorrect (it is not 0). Since I didn’t find any open issues related to this, and I found this while testing v0.21.0 I’m sharing here.

mjdietzx commented at 1:24 am on December 22, 2020: contributor

I’ve been testing/using on master, pulling pretty regularly, since v0.21.0rc1. MacBook Air 2020

macOS Catalina

installed from source (gcc), IBD, basic command line tests, basic gui tests, create encrypted wallet in gui, send and receive from encrypted wallet (reported and fixed 8008ef770f3d0b14d03e22371314500373732143), import watch-only / skeleton wallet, send via PSBT (created in gui, signed on device, broadcasted in gui) and receive to watch-only, testing a bunch of random stuff in GUI (ie viewing peers, simple commands in console), checking recent transactions in the mempool, transaction received notifications work, and general use of wallet, switching between and opening/closing wallets

then I updated to macOS Big Sur v11.0.1

installed from source (both gcc and clang), bunch of random stuff in gui (ie testing keyboard shortcuts for things like masking values), pretty much all the same tests as I list above

Then I installed the tagged release v0.21.0rc3, built from source (clang), and went through this script except for the Signet tests (thanks @adamjonas), all worked ✅

stackman27 commented at 9:45 pm on December 22, 2020: contributor

0.21.0rc3 compiled from source, Ubuntu 20.04.1 LTS, Windows 10 64bit

went through this doc- descriptor wallets, torv3, anchors worked very well,

Emzy commented at 3:23 pm on December 23, 2020: contributor

0.21.0rc3 downloaded from https://bitcoincore.org/bin/bitcoin-core-0.21.0/test.rc3/bitcoin-0.21.0rc3-osx.dmg macOS 10.15.7 (19H2)

I was able to run the wrongly signed rc3 binary from the .dmg after setting an extended attribute via:

0sudo xattr -rd com.apple.quarantine /Applications/Bitcoin-Qt.app

went through the Testing Guide (created a descriptor wallet, connected over Torv3, ran through the anchors test). All worked well. I only tested Bitcoin-qt.

hebasto commented at 7:07 pm on December 23, 2020: member

Observing a regression in v0.21.0rc3 comparing to v0.20.1: the option -onlynet=ipv4 (both in command line and in bitcoin.conf) does not work as expected.

In v0.21.0rc3 (and in current master) providing -onlynet=ipv4 does not prevent outgoing Tor connections.

0$ src/bitcoind -help | grep -A 4 onlynet
1  -onlynet=<net>
2       Make outgoing connections only through network <net> (ipv4, ipv6 or
3       onion). Incoming connections are not affected by this option.
4       This option can be specified multiple times to allow multiple
5       networks.

EDIT: possibly, at the moment of adding -onlynet=ipv4 my addrman was full of onion addresses only (not sure, as have no backup).

jonatack commented at 7:24 pm on December 23, 2020: member

@hebasto this may possibly be what @Saibato has been describing for some time; see https://github.com/bitcoin/bitcoin/commit/39858289583cc11fdcefbc8e8716ff09855049a7 which I ended up dropping from #19961 because the issue surprised people but it should probably either be fixed or documented.

jonatack commented at 7:29 pm on December 23, 2020: member

e.g. see this comment #19961 (review). I’m opening a PR for the doc updates that were dropped.

Edit: done in #20757.

hebasto commented at 8:38 pm on December 23, 2020: member

@jonatack

@hebasto this may possibly be what @Saibato has been describing for some time; see 3985828 which I ended up dropping from #19961 because the issue surprised people but it should probably either be fixed or documented.

What changes in the code did cause such a change in the client behavior?

jonatack commented at 8:48 pm on December 23, 2020: member

@hebasto I haven’t dug into it but see #19358 I think

pinheadmz commented at 1:06 am on December 24, 2020: member

OSX 10.14.6 (Mojave) testing v0.21.0rc3 at 9ae536d36, built from source.

Followed the guide at https://github.com/adamjonas/bitcoin-core-rc-testing/blob/121720-testing-instructions-refinement/docs/v0.21/testing-0.21rc2.md

Made a descriptor wallet, connected to TorV3 peers, synced to default Signet!

make check passed but test_runner had two failures:

0feature_nulldummy.py --descriptors               | ✖ Failed  | 93 s
1wallet_groups.py --descriptors                   | ✖ Failed  | 384 s

investigating… Ok, tests ran fine outside of runner. The errors look like rpc timeouts

n1bor commented at 8:50 pm on December 26, 2020: none

Create new wallet in Windows defaults to un-encrypted wallet. Seems odd default.

Sjors commented at 11:44 am on December 30, 2020: member

@n1bor see discussion in https://github.com/bitcoin-core/gui/pull/96

Rspigler commented at 4:47 am on January 6, 2021: contributor

Compiled (GCC) v0.21.0rc5 in Qubes 4.0 in a Debian 10 StandaloneVM on Purism hardware

Tested descriptor wallet creation, TorV3, Signet (received and sent - fee estimation didn’t work?), and Anchor Connections.

sipa commented at 4:53 am on January 6, 2021: member

Signet (received and sent - fee estimation didn’t work?)

Fee estimation can’t work without a substantial amount of transactions making it into the mempool and getting confirmed.

ellemouton commented at 4:48 pm on January 6, 2021: contributor

Followed these instructions. Compiled 0.21.0rc3 from source on OSX 10.14 Mojave. Tested descriptor wallets, Tor3 and anchors. All went smoothly 😎

hebasto commented at 5:33 pm on January 7, 2021: member

Noted a regression in QTabWidget on macOS Big Sur 11.1 (Light Appearence):

master (3a6acd1772100d71de45355381d0d6ccf1320748):
gitian build downloaded from https://bitcoincore.org/bin/bitcoin-core-0.21.0/test.rc5/ (a window is focused):

NOTE: I’m using a VM for testing, so asking other contributors to check this issue on native macOS.

UPDATE: it is not a regression in 0.21.0 as 0.20.1 behaves the same. It seems an issue of Big Sur + Qt 5.9.8 combination. Btw, Qt bug tracker has a long list of QTabWidget bugs on macOS.

UPDATE 2: the issue has been already submitted by @jonasschnelli in https://github.com/bitcoin-core/gui/issues/136.

jarolrod commented at 5:49 pm on January 7, 2021: member

@hebasto confirming the QTabWidget regression on native macOS Big Sur 11.1. On Big Sur 11.1, this bug can be found on the previous release candidates and even on the 0.20.1 release. I cannot replicate on my macOS Catalina 10.15.7 machine. Another interesting thing about this bug is that if you click on another window, the text will reappear.

Confirming Regression (Big Sur 11.1)

Clicking on another Window, Text Reappears (Big Sur 11.1)

lscarrol commented at 10:00 pm on January 7, 2021: none

0.21.0rc5, Manjaro 20.2.1

Doc is sound, Tested descriptor wallets, torv3, and anchors

hebasto commented at 10:03 pm on January 7, 2021: member

Regarding visual issues on Big Sur: https://github.com/bitcoin-core/gui/pull/177.

ghost commented at 3:18 am on January 8, 2021: none

macOS Catalina (10.15.5), built tag v0.21.0rc5 from source, upgraded from a previous version I use occasionally on this computer (v0.19.99.0-225aa5d6d)

Followed 0.21 RC Testing Guide, ran through everything except signet - so far so good.

Only thing I noticed was on first boot was a mempool file problem:

 02021-01-08T02:28:56Z loadblk thread start
 12021-01-08T02:28:56Z torcontrol thread start
 22021-01-08T02:28:56Z Bound to 127.0.0.1:8333
 32021-01-08T02:28:56Z Bound to 127.0.0.1:8334
 42021-01-08T02:28:56Z init message: Loading P2P addresses...
 52021-01-08T02:28:56Z Loaded 48217 addresses from peers.dat  170ms
 62021-01-08T02:28:56Z ERROR: DeserializeFileDB: Failed to open file /Volumes/Samsung750/Bitcoin/Mainnet/mainnet/anchors.dat
 72021-01-08T02:28:56Z 0 block-relay-only anchors will be tried for connections.
 82021-01-08T02:28:56Z init message: Starting network threads...
 92021-01-08T02:28:56Z net thread start
102021-01-08T02:28:56Z dnsseed thread start
112021-01-08T02:28:56Z addcon thread start
122021-01-08T02:28:56Z opencon thread start
132021-01-08T02:28:56Z msghand thread start
142021-01-08T02:28:56Z init message: Done loading
152021-01-08T02:28:56Z Waiting 300 seconds before querying DNS seeds.
162021-01-08T02:29:27Z Failed to deserialize mempool data on disk: CAutoFile::read: end of file: unspecified iostream_category error. Continuing anyway.
172021-01-08T02:29:27Z loadblk thread exit

But continued just fine and didn’t show back up again, maybe a coincidence.

pkrasam commented at 5:33 am on January 8, 2021: none

Hardware: MacBook Pro OS: macOS Big Sur v11.1 (20C69) RC: 0.21.0rc5 binary Tests: Completed

created a descriptor wallet,
connected over Torv3,
ran through the anchors test,
all of ^ + looking forward to trialling Signet

calkob commented at 4:55 pm on January 8, 2021: none

v0.21.0rc3 Windows 10 Bitcoin-qt

Had the warning below pop up a few times at the start of testing whilst trying to create wallets. couldnt find a reproducible scenario to pass on. all i can think is that this wasnt a fresh build there was already wallets in the wallet file with a db.

all other tests ran fine

wallet test

Sjors commented at 5:00 pm on January 8, 2021: member

@calkob did you experiment with descriptor wallets before you tested this release?

calkob commented at 5:32 pm on January 8, 2021: none

@calkob did you experiment with descriptor wallets before you tested this release?

I dont think i had run this build before today but now that you mention it i am doubting myself. Could that be an answer for the warning?

Sjors commented at 5:52 pm on January 8, 2021: member

If you’ve ever used the master branch or any of @achow101’s recent wallet pull requests, your ~/.bitcoin/wallets dir may contain descriptor wallets. Those have been changed a few times, so you might have an old incompatible version lying around.

nomo-nomad commented at 8:44 am on January 9, 2021: none

MacBook Pro running macOS 11.1 Big Sur, testing 0.21rc3 compiled from source

✅ Successfully created a descriptor wallet from qt GUI and in the terminal/CLI ✅ Anchors.dat appears on clean shut down and disappears on node startup ✅ Successfully connected to Torv3

Not sure if I missed a build option – but bitcoin-qt is showing that it’s using Berkeley DB not SQLite

scgbckbone commented at 9:04 pm on January 11, 2021: none

@nomo-nomad do you have sqlite installed?

scgbckbone commented at 10:09 pm on January 11, 2021: none

acer aspire E15 Intel Core i5-6200U 4.15.0-130-generic #134-Ubuntu SMP Tue Jan 5 20:46:26 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux Ubuntu 18.04 build from source (v0.21.0rc5)

Successfully created a descriptor wallet from qt GUI and in the terminal/CLI OK
Anchors.dat appears on clean shut down and disappears on node startup OK
Successfully connected to Torv3 FAIL

debug.log (during startup):

02021-01-11T21:43:24Z torcontrol thread start
12021-01-11T21:43:24Z tor: Authentication cookie /var/run/tor/control.authcookie could not be opened (check permissions)

i tried to add user that runs bitcoind/bitcoin-qt to debian-tor group and also add write permission for group members to /var/run/tor/control.authcookie - none helped

tor version:

0tor                 0.3.2.10-1     amd64          anonymizing overlay network for TCP

no V3 addresses in Peers window (maybe because of ongoing attack?)

i have this in my torrc:

0HashedControlPassword <n:password>
1ControlPort 9051

tor socket open (netstat -nltp):

0LISTEN      0            128                     127.0.0.1:9050                   0.0.0.0:*          
1LISTEN      0            128                     127.0.0.1:9051                   0.0.0.0:*

haegwan commented at 10:23 pm on January 11, 2021: none

Tested based on @jarolrod’s guide. It was very easy to follow. Thanks!

Hardware: MacBook Air (M1, 2020) OS: macOS Big Sur v11.1 (20C69) Scope: Only a descriptor wallet creation. Other tests follow.

As others noted, noticed interace glitch both on Light/Dark mode for GUI. https://github.com/bitcoin-core/gui/pull/177

I also tested Japanese - most texts showed fine. Here are few updates I’d make.

“current block height” shown as English
Date format shown as English.

Not sure why it’s showing up in this way as all JP translations should be already resolved on transifex.

jarolrod commented at 9:43 pm on January 12, 2021: member

@haegwan this is a known issue with bitcoin-qt on macOS Big Sur 11.1 built with Qt 5.9.8. It would be useful if you could patch [GUI #177](https://github.com/bitcoin-core/gui/pull/177) (as you linked to it) on top of 0.21rc5 built with Qt 5.9.8 and report back if it fixed the visual glitches for you.

Note: If you build with a more recent version of Qt you won’t see this glitch.

robot-dreams commented at 0:16 am on January 13, 2021: contributor

Also tested based on @jarolrod’s guide, after reading @adamjonas’s post on the importance of testing. Thanks both of you for the awesome articles!

tl;dr Every command line test worked perfectly, didn’t test bitcoin-qt

Hardware / OS

MacBook Pro (Retina, 15-inch, Mid 2015), macOS Catalina Version 10.15.7

Which release candidate

v0.21.0rc5, compiled from source

Flags for configure:

0--without-miniupnpc
1--disable-bench
2--without-gui
3CXXFLAGS="-O0 -g"
4CFLAGS="-O0 -g"

What I tested

I tested everything using an existing data directory (mainnet already synced).

Descriptor wallets (command line)

 0$ bitcoin-cli -named createwallet wallet_name="v0.21.0-rc5-descriptor-wallet" descriptors=true
 1{
 2  "name": "v0.21.0-rc5-descriptor-wallet",
 3  "warning": "Wallet is an experimental descriptor wallet"
 4}
 5
 6$ bitcoin-cli -rpcwallet="v0.21.0-rc5-descriptor-wallet" getwalletinfo
 7{
 8  "walletname": "v0.21.0-rc5-descriptor-wallet",
 9  "walletversion": 169900,
10  "format": "sqlite",
11  "balance": 0.00000000,
12  "unconfirmed_balance": 0.00000000,
13  "immature_balance": 0.00000000,
14  "txcount": 0,
15  "keypoolsize": 3000,
16  "keypoolsize_hd_internal": 3000,
17  "paytxfee": 0.00000000,
18  "private_keys_enabled": true,
19  "avoid_reuse": false,
20  "scanning": false,
21  "descriptors": true
22}

Tor v3 (command line)

 0$ cat bitcoin.conf | grep onion
 1listenonion=1
 2addnode=sxjbhmhob2xasx3vdsy5ke5j5jwecmh3ca4wbs7wf6sg4g2lm3mbszqd.onion:8333
 3addnode=rp7k2go3s5lyj3fnj6zn62ktarlrsft2ohlsxkyd7v3e3idqyptvread.onion:8333
 4addnode=d6jwdcoo2l3gbjps6asgg4nhp2gn5oao3wj333o43ssqnjaliehytfad.onion:8333
 5
 6$ bitcoin-cli -netinfo 4
 7Bitcoin Core v0.21.0rc5 - 70016/Satoshi:0.21.0/
 8
 9Peer connections sorted by direction and min ping
10<-> relay   net  mping   ping send recv  txn  blk  age id address                                                             version
11...
12out  full onion    482    482    2    3    0         4  2 rp7k2go3s5lyj3fnj6zn62ktarlrsft2ohlsxkyd7v3e3idqyptvread.onion:8333 70016/Satoshi:21.99.0(Medea)/
13out  full onion    508    730    2    1    0         4  1 sxjbhmhob2xasx3vdsy5ke5j5jwecmh3ca4wbs7wf6sg4g2lm3mbszqd.onion:8333 70016/Satoshi:0.21.0/
14out  full onion    510    581    0   13    0         4  3 d6jwdcoo2l3gbjps6asgg4nhp2gn5oao3wj333o43ssqnjaliehytfad.onion:8333 70016/Satoshi:21.99.0(h42)/
15...
16                    ms     ms  sec  sec  min  min  min

Signet

 0$ cat signet/bitcoin.conf 
 1signet=1
 2
 3$ bitcoind -datadir=signet
 42021-01-12T22:20:39Z Bitcoin Core version v0.21.0rc5 (release build)
 52021-01-12T22:20:39Z Signet derived magic (message start): 0a03cf40
 6...
 7
 8$ bitcoin-cli -datadir=signet getnewaddress
 9tb1qlz...
10
11# Use faucet at https://signet.bc-2.jp/ to send coins
12
13$ bitcoin-cli -datadir=signet getunconfirmedbalance 
140.00100000

Anchors

 0$ ls anchors.dat
 1anchors.dat
 2
 3$ bitcoind
 42021-01-12T23:14:44Z Bitcoin Core version v0.21.0rc5 (release build)
 5...
 62021-01-12T23:14:56Z Loaded 2 addresses from "anchors.dat"
 72021-01-12T23:14:56Z 2 block-relay-only anchors will be tried for connections.
 8
 9$ ls anchors.dat
10ls: anchors.dat: No such file or directory
11
12# Shut down bitcoind
132021-01-12T23:16:48Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat started
142021-01-12T23:16:48Z DumpAnchors: Flush 2 outbound block-relay-only peer addresses to anchors.dat completed (0.01s)
15...
162021-01-12T23:16:48Z Shutdown: done
17
18$ ls anchors.dat
19anchors.dat
20
21$ bitcoind
222021-01-12T23:17:48Z Bitcoin Core version v0.21.0rc5 (release build)
23...
242021-01-12T23:17:58Z Loaded 2 addresses from "anchors.dat"
252021-01-12T23:17:58Z 2 block-relay-only anchors will be tried for connections.

Bonus: specter-desktop

specter-desktop v1.0.0 is still able connect to the node and load an existing wallet

specter-desktop

robot-dreams commented at 1:40 am on January 13, 2021: contributor

Also repeated the command line tests on a RaspiBolt and once again everything worked great!

Hardware / OS: Raspberry Pi 4 Model B Rev 1.1, Raspbian GNU/Linux 10 (buster) Which release candidate: v0.21.0rc5 binary, ARM (32 bit) What I tested: descriptor wallets, Tor v3, signet, anchors

fanquake unpinned this on Jan 16, 2021

fanquake closed this on Jan 16, 2021

hMsats commented at 6:13 pm on January 22, 2021: none

@jonatack

I’m happy to addnode to anyone who is testing 0.21 with tor v3 so you can see an inbound connection. Ping me on bitcoin-core-dev IRC.

Yes please: l4l6gkjqj4vodcwwooyk5tpnotec6sbk4g3sz4hrfziaiw3pxlv3h5qd.onion

Thanks in advance (ex sumBTC)

jonatack commented at 11:18 pm on January 22, 2021: member

@hMsats done! you should see a tor v3 node in your inbound connections.

hMsats commented at 11:24 pm on January 22, 2021: none

I do! Thanks. This begs (if you haven’t done so already) for an onionv2 and onionv3 in your -netinfo like for ipv4 and ipv6 :-)

jonatack commented at 11:47 pm on January 22, 2021: member

The getpeerinfo#network field that -netinfo reads doesn’t distinguish between v2 and v3 onions; see the Network enum in src/netaddress.h and GetNetworkName() in netbase.cpp.

At any rate, by the next release (v22.0), tor v2 will be essentially EOL.

jonatack commented at 11:50 pm on January 22, 2021: member

(p.s. happy to hear that you are using -netinfo :))

hMsats commented at 8:30 am on January 23, 2021: none

I do, as it gives a really nice overview of all my inbound and outbound connections and type of connections!

MarcoFalke referenced this in commit 11d3b58336 on Jan 27, 2021

jonasschnelli referenced this in commit 02b01651c5 on Jan 28, 2021

DrahtBot locked this on Aug 18, 2022

v0.21.0 testing #20555