New Chains & App Store Launch

Gleec Wallet closes out its 0.9.4 to 0.9.6 release line as a turning point for the Gleec ecosystem. Built on top of komodo-defi-sdk 0.6.0, this line is not a routine maintenance cycle — it is the most feature-dense, performance-conscious, and thoroughly tested set of releases the team has ever shipped. From first-class TRON and TRC-20 token support to in-app migration for users of the original Gleec DEX mobile app, it extends what a self-custodial, multi-chain wallet can do in a browser, on a phone, and on the desktop.

The numbers tell the story. Across dozens of pull requests touching the wallet, the SDK, and the release infrastructure, the team audited a documented 159-issue polish backlog and closed 92 verified fixes, shipped an automated QA runner backed by Docker and Playwright, and introduced runtime-loaded legal documents so compliance policies can update without pushing a new binary. Every screen, every flow, and every error state received attention.

Two New Chains, Zero Custodial Trade-Offs

Users can now activate, receive, and withdraw TRON and TRC-20 tokens directly inside Gleec Wallet — with custom-token import support and full fiat on-ramp coverage mapped into the existing provider flows. This means TRC-20 USDT, the most widely held stablecoin on any chain, is now a first-class citizen in the wallet.

Alongside TRON, the release line introduces complete SIA activation and withdrawal flows, opening the door to decentralized storage payments from the same interface users already know. Both chains are backed by audited SDK-level support, including typed error handling, fee helpers, and token safety checks.

Custom-token import has also been broadened — users can add tokens from supported networks without waiting for an official listing, and the wallet will handle activation, balance display, and cleanup automatically.

Pick Up Exactly Where You Left Off

For users of the original Gleec DEX mobile app, this release line delivers its most personal feature: in-app legacy wallet migration. Update to the new app on Android or iOS and your existing wallets simply appear in the wallet list. Sign in with your old password, and Gleec Wallet decrypts the legacy wallet on-device, imports the seed into the modern wallet engine, and carries your activated coins, address book, language, and display preferences across — no manual seed re-entry, no starting over.

Where an old wallet name or password doesn’t meet the new engine’s requirements, a guided compatibility step asks for a compatible name or a new password before continuing. Once migration completes, the legacy wallet data is securely removed from the device, and migrated wallets are tracked so the same wallet can never be imported twice. If any legacy data remains behind, a dedicated cleanup card in Security Settings shows exactly what is left and why the migrated wallet is now the canonical one.

Everything happens locally: seed phrases are decrypted, migrated, and cleaned up on the device — they never leave it.

The Road to Google Play and the App Store

Versions 0.9.5 and 0.9.6 turn Gleec Wallet into a store-ready mobile product. On iOS, the app now builds under Gleec’s own Apple Developer identity with a dedicated App Store bundle. On Android, 0.9.6 completes the Google Play compliance pass: required advertising-ID declarations, secure out-of-band handling of the Play upload key, and 16 KB memory-page alignment of the native trading engine — the compatibility bar Google Play sets for the newest Android devices. The app targets Android 16, with support back to Android 9.

Combined with the migration flow above, the path is deliberate: when Gleec Wallet arrives on the stores, existing users update in place and keep their wallets.

A Web Codebase Ready for WebAssembly

Under the hood, this release line completed the platform, persistence, and interop work needed to compile Gleec Wallet on Flutter’s WebAssembly runtime — including a move to pure-Dart cryptography that behaves identically in WASM and JavaScript environments. The deployed web app continues to ship on Flutter’s proven JavaScript target today, while WASM enablement is finalised and performance-validated for a future release.

What web users feel right now is the hardening that shipped alongside that work: isolated browser cache adapters and separated file-loader behaviour mean wallet state can no longer bleed between sessions, and malformed responses or transport failures are contained so browser sessions stay responsive.

What’s New at a Glance

A Polish Pass That Touched Everything

The quiet centerpiece of this release line is the cumulative effect of a systematic polish program that reviewed 159 open issues and closed 92 verified fixes across every surface of the wallet. The wallet overview, grouped asset list, price charts, coin addresses, faucet views, and coins manager all received layout, density, and interaction improvements. Trading screens were refined with better swap history loading, clearer maker and taker forms, smarter coin selectors, and more accurate available-balance displays.

Wallet creation and import flows were streamlined with a new import-mode selector, persisted HD wallet preferences, wallet naming guardrails, and better BIP-39 seed suggestions. Settings surfaces now expose richer build metadata, a stealth-mode balance toggle in the summary cards, and cleaner trading-bot controls.

Navigation received a structural update as well: the Swap tab now sits before Buy/Sell in the primary navigation, reflecting how most active users move through the app. Responsive behavior — including logout anchoring, overlay stability on orientation changes, and mobile tab overflow — was hardened across breakpoints.

The polish continues into 0.9.6 with a redesigned wallet coin list: every asset now shows its live market price and 24-hour change beside its name, with holdings — coin amount and fiat value — cleanly right-aligned, on mobile and desktop alike. Market prices stay visible even when balances are hidden, since they are public data, and low-priced assets display extra precision so sub-cent tokens stop rounding to zero.

The release line also refreshes the wallet’s visual identity — new app icons, a new signature purple, and updated social preview cards.

Faster by Architecture, Not by Accident

Performance work in this release line goes deeper than caching a few endpoints. It introduces a stream-first trading model that replaces aggressive DEX polling with managed orderbook and swap-status streams. Preimage, volume, and bridge-depth requests are now cached and deduplicated so that rapid form edits and validations no longer trigger duplicate RPC calls.

Background polling adapts to context: when trading views are idle, refresh intervals slow down automatically. Address prefetching was improved to reduce competing activation work, and activation-state races during wallet startup have been eliminated. The SDK’s own caching and streaming model feeds directly into these improvements, cutting redundant wallet and trading RPC activity at the protocol layer.

Compliance Without Friction

A recurring tension in wallet software is keeping legal documents current without forcing users to update the app. This release line resolves this by loading the EULA, privacy notice, terms of service, and KYC policy at runtime from GitHub-backed content — with dedicated in-app policy pages accessible directly from the settings experience. When regulatory language changes, the wallet reflects it immediately.

Sensitive data handling also improved: seed phrases and private keys are now gated behind explicit visibility toggles with safer copy and QR behavior. Trezor hardware-wallet flows gained clearer cancellation states, non-empty passphrase requirements, and better wallet-mode-only guidance.

What This Means for the Road Ahead

With TRON and SIA support live, store-ready mobile builds, in-app migration for legacy users, and a systematic polish program behind it, the 0.9.4–0.9.6 line establishes the foundation for the next chapter of the Gleec ecosystem. The automated QA infrastructure — complete with a documented build matrix, environment templates, and review prompt packs — means that future releases ship against a repeatable quality bar, not best-effort manual testing. WebAssembly enablement for the web runtime is in active development and will follow in a future release.

For users, the takeaway is straightforward: the wallet is faster, covers more chains, looks sharper, and handles edge cases with more grace than any previous version. For the Komodo and Gleec communities, it signals that the product team is building with the discipline to match the ambition.