User does not have to wait for Tor to load to enter the wallet and generate addresses (offline operations). Online operations will not work as a default socks5 proxy value is used with libstackmate which will lead to an error.
Tor now has a dedicated configuration page
Users can not use an external Tor instance
Users can not opt out of Tor (although Tor is default)
TAPROOT
Users can derive a taproot account
COLDCARD
End to end support for ColdCard Air Gapped Operation
Supports file system operations for reading generic.json to create watch only wallet,writing .psbt, and reading .tx file to broadcast transaction hex
BACKUP LATER
Users can backup their wallet (write down their seed words and passphrase) later. This allows them to wait to be in a safe space to backup their wallet, for cases when they want to receive bitcoin immediately after on-boarding./
SINGLE MASTER KEY WALLET
Users can now only manage a single master key wallet from which they can derive a segwit or taproot account.
They will later be able to derive multi-sig accounts from the same master key.
Users cannot import multiple seeds anymore.
GENERAL STABILITY
The wallet is now stable for the most part with a few minor known bugs.
KNOWN BUGS
RECEIVE rotates addresses everytime clicked.
This can lead to unnecessary address index rotation and lead to a messy wallet.
If users create large enough gaps between addresses that receive funds, this could lead to errors in wallet sync. This can be fixed by updating libstackmate to use a larger wallet stop gap, however this comes at the cost of longer sync time. This is not the best approach. We need to figure out how to effectively manage unused addresses and prevent large gaps.
Another alternative is to save a list of all addresses ever generated by the wallet, so users can reuse addresses that they have not used before.
This update brings the following new changes:
TOR
TAPROOT
COLDCARD
BACKUP LATER
SINGLE MASTER KEY WALLET
GENERAL STABILITY
KNOWN BUGS
This can lead to unnecessary address index rotation and lead to a messy wallet.
If users create large enough gaps between addresses that receive funds, this could lead to errors in wallet sync. This can be fixed by updating libstackmate to use a larger wallet stop gap, however this comes at the cost of longer sync time. This is not the best approach. We need to figure out how to effectively manage unused addresses and prevent large gaps.
Another alternative is to save a list of all addresses ever generated by the wallet, so users can reuse addresses that they have not used before.