This release brings several updates to Dojo parts:
- updated Node.js docker images to v20
- updated Tor to v0.4.8.9
- updated Fulcrum to v1.9.7
- updated Bitcoin Core to v26.0
There are also two minor fixes
- wrap unconfirmed transaction processing in try/catch
- update DB table banned_addresses to allow bech32
These bugfixes are not critical for a casual Dojo user.
New API endpoint
In this version, we also added a new
/seen endpoint which an API consumer can use to easily check if an address (or list of addresses) have been used in the past. This is not checked against Dojo tracker database but against an indexer (addrindexrs/fulcrum/OXT) and thus doesn't require addresses in question to be tracked by Dojo. You can check the docs here.
New option for BTC-RPC Explorer
A new configuration option has been added for BTC-RPC Explorer - users are now able to turn off the
slow-device-mode which is used by default. Users with more performant devices can choose to switch
off in their
As always, we are very grateful for users that provide us with valuable feedback, such as adding this feature.
Exclusion of incompatible clients
Starting with this release, it will not be possible to use Knots fork of Bitcoin Core when connecting to an external bitcoin node because Dojo will actively refuse to make an RPC connection to such node.
For users with bitcoind installed by Dojo (via docker), bitcoind will now periodically scan connected peers and ban those that are detected as Knots. This feature can be turned off by setting
This feature was added to protect our users whose privacy-enhancing transactions such as tx0 or BIP47 notification would not be relayed properly because of non standard policies set by default on Knots nodes.
As always, you can find the release here https://code.samourai.io/dojo/samourai-dojo/-/releases/v1.22.0 as well as link to full changelog.