Skip to content

Testnet Clear Cathode 3.2

Pre-release
Pre-release
Compare
Choose a tag to compare
@gingervik gingervik released this 21 Jan 07:42
· 100 commits to master since this release
testnet_3.2
72ea418
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Features:

  • When a crash occurs we'll ask politely to submit the technical details, that will allow us to investigate the issue and improve app's stability
  • The app responsivity became much faster and usage feel became smoother due to significant architectural rework
  • Transaction details screen, address/contact details screen, tag create/update screen, payment proof screens were redesigned
  • Transactions history can be exported and saved on the device
  • On transactions screen, multiple transactions can be selected

Improvements:

  • Transactions can be searched by Kernel ID (from the Transactions screen)
  • Loading bar works smoother and is a bit more informative
  • When changing the language the app doesn't need to be restarted anymore

Fixes:

  • Many fixes of typos, explanatory messages, elements placements, colors - all to make the app more eye-pleasing and more intuitive to use.

Known limitations:

  • When restoring your funds in automatic mode, verify that your most recent transaction (from any device) was completed at least 1 hour ago. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.
  • When restoring your funds with your specific node, verify that the node is fully synchronized with the blockchain before starting the restore procedure. Otherwise, your restored balance may be incorrect and additional restore procedure will be required.

Points to mention:

  • DO NOT SIMULTANEOUSLY RUN TWO WALLETS INITIATED FROM THE SAME SEED PHRASE. No funds will be lost in any case, please read this article for full details.
  • If you really want to run two wallets (read: geek mode), initiated from the same seed phrase, make sure each wallet is connected to the node configured with the owner key (which is derived from the seed phrase).
  • Even if two wallets are connected with such a node which is properly configured with the owner key, the transaction history will not be syncronized among them (each wallet will see the correct balance but only its own transaction history).
Assets 3