Progress Summary
February 2026
Highlights
- Added session keys to Web Authenticator, letting apps sign routine actions automatically without a wallet popup each time — rolling out December’s session key work across the full product stack
- Redesigned the contract table browser in Unicove giving users a cleaner way to inspect on-chain data, alongside a reworked transaction summary page
- Set up automated testing for Roborovski v2 and fixed a memory bug that caused crashes, keeping the tools reliable as development continues
- Built chat and forum prototypes that combine session keys, Web Authenticator sign-in, and live streaming to showcase real-time apps on the network
Unicove
Building on January’s Roborovski v2 work, Unicove continued receiving steady updates throughout February. The contract table browser was redesigned to handle large data fields more gracefully, making it easier to explore what is stored on-chain. Transaction summary pages were reworked with clearer sections and a table layout, and the default time allowed to complete a transaction was increased.
Unicove also added support for premium account names and improved how multisig proposals load — proposals now pull from a faster source first, then fall back to the chain if needed. Several display fixes improved how decoded activity data appears. The wallet listing was updated to reflect the rebrand from EOS Wallet (MetaMask) to Vaulta Wallet, matching the network’s new name.
Web Authenticator — Session Keys
Session keys arrived in the Web Authenticator, building on the session key feature introduced in December at the developer-tools level. With session keys, an app can get a temporary, limited-purpose key that signs certain actions on behalf of the user — for example, moves in a game — without requiring approval for every single action.
Alongside the feature, security rules were added to tell apart trusted requests (from a known app window) and unknown ones (from a shared link). A detailed discussion explored how to verify app identity in the future, with the idea of a registry where trusted apps earn a verified badge. The Web Authenticator wallet plugin also gained multichain support and improved popup positioning.
Roborovski v2
Following January’s open-sourcing, February focused on making Roborovski v2 more stable. An automated testing setup now runs checks on every code change, catching problems early. During that work, a memory bug was found and fixed that had been causing out-of-memory crashes. The live-streaming piece was separated into its own service, and new lookup endpoints were added for usage stats and individual actions.
New Prototypes
Several experimental projects appeared in February. A chat prototype and a forum prototype were created as proof-of-concept apps that tie together Web Authenticator sign-in, session keys, the new resource tools, and Roborovski’s live streaming. A light account demo explored no-account addresses that can receive tokens without creating a full blockchain account, with a companion token faucet for testing.
WharfKit Updates
Session key support spread across multiple WharfKit libraries. The Session Kit adopted a newer transaction submission method with better error reporting. The core Antelope library standardized how errors from that method are handled. The Resource Provider received a major rewrite on both the server side (cosigning, usage tracking, contract cache rewrite) and the client plugin (smarter fee calculations that account for memory costs). The autocorrect plugin fixed a precision issue, and the co-signing plugin received a compatibility fix.
Summary
Shipped updates across 14 repositories with 4 new projects created. February focused on rolling session keys out across the product stack, redesigning contract browsing and transaction pages in Unicove, stabilizing Roborovski v2 with automated testing, and prototyping real-time apps that demonstrate the full toolkit working together.