Beacon Performance Issues With AirGap, Kukai & Galleon — Beacon SDK v2.2.5 Release
Beacon Network nodes have been moved to a new infrastructure and dApp developers should update to the latest release of the SDK.
In the last few days we saw an uptick of load on the Beacon infrastructure resulting in some users experiencing extended loading times of their requests with AirGap, Kukai and Galleon.
The Infrastructure Upgrade
To resolve the degraded performance the decision was made to move the Beacon Nodes to a new infrastructure. The migration was completed on Monday 21st of April at 20:00 CET. After the migration we saw huge improvements in the response time in our tests.
The Problem
A bit later, we received reports where some users that had an existing connection were no longer able to get their requests prompted in their AirGap, Kukai or Galleon wallets.
Although the complete database was migrated, we saw that some users were unable to rejoin their existing session.
Important to note, there is no security issue, this fix only concerns connectivity problems.
The Solution
As the caching of previously established connection was aggressively handled by the Beacon SDK, the only solution on the user side, as mentioned in the workaround, was to clear the local storage.
With Beacon SDK v2.2.5 the caching was adapted, if a connection cannot be established the SDK will recover itself automatically and establish a new connection without user interaction.
npm i @airgap/beacon-sdk@2.2.5If you are a dApp developer you should update to Beacon SDK v2.2.5 at your earliest convenience.
As of the time of writing Kukai has already updated their wallet as well as some dApps.
The Workaround
As a workaround if your dApp was not able to update yet, you can clear the local storage of your dApp and connect again with AirGap or Kukai.
In Chrome or Brave you can do the following: Right Click in the dApp > Inspect > Applications > Storage > Clear Site Data, refresh the page and then try to Sync again.
The Near Future
When Beacon was initially developed the vision was to improve the reliability and security through the Beacon Network. Based on the matrix protocol best known from Element, the Beacon Network is built on an encrypted and decentralized peer to peer communication layer.
In a next step in the next few days we will scale the Beacon Network ourselves by providing additional nodes and provide more details for the community on how to run a Beacon Node and join the network to further decentralized an ensuring we can onboard the next wave of users.
Thanks
Many thanks go out to all the users that provided us with feedback and a special thanks goes to Klas from the Kukai team for helping us with the debugging and testing!
Do you want to try Beacon?
You can try out Beacon by using Spire or any other Beacon compatible wallet and hic et nunc, tzcolors or numerous other dApps.
👉 Beacon Website
👉 Beacon SDK / Beacon SDK Documentation
👉 Spire
👉 Beacon Example dApp
Do you have any questions about Beacon? Join our new Discord or directly reach out to us.
Interested in a secure wallet solution for Tezos ? Take a look at AirGap.
Beacon Website | GitHub | Discord | AirGap Website | Twitter
