Skip to content

Testnet - Eager Electron 5.1

Pre-release
Pre-release
Compare
Choose a tag to compare
@gingervik gingervik released this 22 Oct 07:43
· 110 commits to master since this release
testnet_5.1
d32e390

TL;DR Release Highlights:

  • Offline transactions add the option to use offline addresses: no need to wait for the receiver to come online anymore!

Features:

  • Enabled Offline transactions through the Lelantus MW protocol implemented at the last hard fork.
  • For Offline transactions new “offline” addresses are supported: it includes all the necessary information for 10 payments so that a receiver doesn’t need to talk to the sender to create a transaction. Once the ten payments run out, the sender wallet will automatically request more payments from the receiver using SBBS. In case the Receiver is not online and not responding, the Sender wallet will show an indication that there are no more payments left and the user will request a new address using an external channel.

Improvements:

  • The loading screen will be shown in fewer cases, so you’ll see your Beams faster

Fixes:

  • Many under-the-hood bug fixes you don’t want to know about, as Beam “just works”

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 synchronized among them (each wallet will see the correct balance but only its own transaction history).
Assets 2
Loading