My tor version:
$ tor --version
Feb 14 13:55:44.415 [warn] Tor was compiled with zstd 1.3.8, but is running with zstd 1.4.4. For safety, we'll avoid using advanced zstd functionality.
Tor version 0.4.5.5-rc.
This version of tor, from Debian buster-backports, is from Mon, 08 Feb 2021 08:12:45, that's very new - apt changelog shows:
tor (0.4.5.5-rc-1~bpo10+1) buster-backports; urgency=medium
* Rebuild for buster-backports.
* Remove dh-runit build dependency and --with-runit and --with-runit for backport.
-- Peter Palfrader <weasel@debian.org> Mon, 08 Feb 2021 08:12:45 +0100
libzstd versions:
$ dpkg -l | grep zstd
ii libzstd-dev:amd64 1.4.4+dfsg-3~bpo10+1 amd64 fast lossless compression algorithm -- development files
ii libzstd1:amd64 1.4.4+dfsg-3~bpo10+1 amd64 fast lossless compression algorithm
But that shouldn't be a problem, its just compression library.
I don't have any 0.21.0 peers:
bitcoin-cli getpeerinfo | grep subv
"subver": "/Satoshi:0.20.0/",
"subver": "/Satoshi:0.18.1/",
"subver": "/Satoshi:0.20.1/",
"subver": "/Satoshi:0.20.1/",
"subver": "/Satoshi:0.20.1/",
"subver": "/Satoshi:0.20.1/",
"subver": "/Satoshi:0.20.1/",
"subver": "/Satoshi:0.20.0/",
"subver": "/Satoshi:0.20.1/",
"subver": "/Satoshi:0.20.0/",
Also all outbound peers are Tor v2 onion hidden services, not v3, example:
2021-02-14T14:45:01Z New outbound peer connected: version: 70015, blocks=670586, peer=88, peeraddr=(16-character onion address).onion:8333 (block-relay)
No long v3 addresses have been observed, I checked all log files. My own tor hidden service works:
2021-02-14T10:49:35Z tor: Got service ID (very long onionddress), advertising service (very long onionddress).onion:8333
2021-02-14T10:49:35Z AddLocal(very (long onionddress).onion:8333,4)
Also,
https://bitnodes.io/ see my node if I query my onion address on port 8333, I think that's very good. Anyway, still can't get any inbound connections.
DM your onion address and I can try to connect from my node to check if it works.