Rotki v1.34.3 - Clean Cryptic Plumage
·
1331 commits
to develop
since this release
v1.34.3
LefterisJP
Lefteris Karapetsas
This tag was signed with the committer’s verified signature.
Description
rotki v1.34.3 is a patch release containing improvements and bugfixes made in the last week. The most important changes concern fixing two really annoying bugs that 1.34.2 introduced.
- Constant generation of snapshots. 1.34.2 introduced a bug where snapshots were taken very frequently without respecting your settings. This will no longer happen.
- Since 1.34.2, detected tokens per address were randomly forgotten when history was pulled again. This should no longer happen.
Some smaller bugs were also fixed and some improvements made.
For more information check the detailed changelog below 👇
Downloads
Upgrade is highly recommended. Download the binary for your OS from below:
- Linux
- OSX
- arm64
- x86_64
- Standalone Backend
- Windows
Optionally, you can also verify the integrity of the aforementioned binaries using the following checksums:
- Linux
- OSX
- arm64
- x86_64
- Standalone Backend
- Windows
Action items
Due to the bug with the token redetection it's recommended to redetect tokens for all your addresses per each EVM chain you use. For more info on how check the docs: https://docs.rotki.com/usage-guides/accounts-and-balances.html#token-detection
New Features
- Generic events can now be created or imported with location being bitcoin, bitcoin cash, polkadot and kusama.
Bug Fixes
- Importing events with generic import will no longer create a fee event if the fee is zero. Before it was not creating one only if fee was omitted.
- Fix an error introduced in 1.34.2 that was creating snapshots more frequently than expected.
- #8350 Users will no longer be able to add duplicate names for an address for all evm chains to the address book.
- Eigenlayer native restaking exited balances residing in eigenpod will no longer be double counted.
- #8397 Active/exited validators will now be propely displayed and filtered for validators that are tracked but the withdrawal address is not. This applies to protocols such as eigenlayer.
- #8414 Detected tokens will no longer randomly disappear from a tracked address if new events are processed.
- It will now be possible to refresh counterparty data if loading initially fails.