Call for Testers: Taquito v25.2.0-rc0 & @ecadlabs/beacon-sdk v4.9.0-ecad-rc.0 (Lifecycle & Type-Safety Overhaul, Faster Pairing, No More Half-Open Stalls, 7 Locales + RTL, Accessibility, and Tezos X)

We are preparing the stable release of Taquito v25.2.0 (paired with @ecadlabs/beacon-sdk v4.9.0) and are inviting dApp developers, wallet teams, and community members to test the release candidates @taquito/*@25.2.0-rc0 (published on the npm next dist-tag across all @taquito/* packages) and @ecadlabs/beacon-*@4.9.0-ecad-rc.0 (published on the npm beta dist-tag).

Project status. Taquito and @ecadlabs/beacon-* are unfunded projects maintained by ECAD Labs. Releases continue on a best-effort basis; protocol-tracking and critical security and reliability releases remain a priority.

Beacon connects a Tezos dApp to your wallet. In Taquito 25.2.0 and Beacon 4.9.0, the connection layer has undergone a major lifecycle, transport, and type-safety refactor: it gets a pairing QR onto the screen sooner, eliminates multi-minute half-open Matrix /sync stalls when waking a device or switching tabs, gives users time to unlock their phone and review a request without premature dApp timeouts, and tells the dApp when the wallet has received a request. Wallet prompts follow the browser language automatically across seven built-in locales (with RTL layout and WCAG keyboard accessibility), and dApps can display which wallet will receive the next request.

You can try the new wallet UX, language/theme switching, large-payload timing, and protocol inspector live right now on the Shadownet test dApp:

Try the RC in your dApp

Faster QR pairing, recovery after a tab wakes up, and faster large-message encoding come with the upgrade. If you use a coding assistant, open it in your dApp repository and paste either prompt. The short version gets you running. The extended version also puts the new wallet APIs to work in your existing UI.

Pre-prepared quick upgrade prompt for your agent

Upgrade this Tezos dApp to the Taquito 25.2.0-rc0 release candidate using its existing package manager. Pin the Taquito packages we already use that ship this RC, update the lockfile, and verify the resolved versions. If we use @taquito/beacon-wallet, it already brings in Beacon 4.9.0-ecad-rc.0. Align any direct @ecadlabs/beacon-* dependencies we already use with that version.

Check our connect and signing flows for short app-side timeouts that can report failure while the wallet is still waiting for approval. Where we ask users to check their wallet, show its name from getWalletInfo() when available. Run our existing checks and give me a short Shadownet checklist for pairing, rejecting a request, and approving one after switching tabs.

Extended prompt for wallet UX, recovery, and testing

Upgrade this Tezos dApp to Taquito 25.2.0-rc0 and apply the changes below wherever they improve a flow we already have. Start by locating our package manifests, wallet setup, account state, and the screens users see while signing. Use our existing framework, package manager, and UI conventions.

  1. Dependencies and wallet setup. Pin our direct Taquito packages that ship 25.2.0-rc0, refresh the lockfile, and check the resolved versions. @taquito/beacon-wallet supplies the matching Beacon packages. Align any direct @ecadlabs/beacon-* dependencies we use to 4.9.0-ecad-rc.0. If we offer WalletConnect, verify that pairing uses our own Reown project ID and works from our dApp’s origin. Preserve other wallet providers and network settings.
  2. Show users where to look. Use getWalletInfo() to name the active wallet in our confirmation UI, for example “Check Kukai to confirm.” Fall back to “Check your wallet” when metadata is missing. Refresh the label after restoring a session or switching accounts, and clear it on disconnect. Subscribe once per wallet lifecycle and release listeners on teardown so reconnecting produces one notification per event.
  3. Make pending requests understandable. Review our timers and retry buttons. Beacon gives permissions a 60-second default and lets signing and operation requests stay pending. Where we show progress, distinguish “Request sent,” “Wallet received your request” on ACKNOWLEDGE_RECEIVED (if (ack.correlated)), and the actual approval or rejection. Some wallets may respond without a separate acknowledgement. If our product requires a local deadline, handle LATE_RESPONSE_RECEIVED and surface any returned operation hash so users can check the result before retrying.
  4. Give users a recovery path. Use isBeaconError() and the typed error fields to distinguish a user declining, an unreachable wallet, and a rejected operation. Preserve useful RPC error details (err.data on TransactionInvalidBeaconError, filtered with isTezosRpcError). If Beacon deactivates an invalid saved account, clear stale connected UI and offer Reconnect. If we already have a support or debug view, use getConnectionInfo() and getPendingRequests() there to help explain a stalled request.
  5. Fit the chooser to our app. Keep browser language detection as the default. If our app already has a language or theme preference, apply it when creating the wallet and sync subsequent changes with setLocale() and setColorMode(). Check Arabic RTL, keyboard-only pairing, Escape, and focus returning to Connect.
  6. Verify the user journey. Run our typecheck, build, and relevant tests. Give me a short real-wallet Shadownet checklist covering fresh pairing, a restored session, rejection followed by retry, and approval after leaving the tab long enough to unlock a phone. If our app sends large contract parameters, include one representative payload. Report what passed, what still needs a person with a wallet, and which files changed.

If you try the RC, we would like to hear which wallet and browser you used, which flow you tested, and what happened. For a stalled request, one particularly helpful detail is the last step you saw: request sent, wallet acknowledged, or response received.

1. Eliminating Half-Open /sync Stalls, Faster Pairing, and 375x Faster Large Payload Serialization

  • No more 4-to-5-minute half-open Matrix /sync stalls (beacon-sdk#204, #207): Previously, waking a laptop or phone from sleep, backgrounding a browser tab, or having a proxy/NAT silently drop an idle HTTP/2 or HTTP/3 stream could leave Matrix /sync long-polling hung for 4 to 5 minutes until OS TCP keepalive eviction, freezing incoming signing prompts or responses even while outbound sends succeeded. Beacon now enforces a client-side /sync fetch timeout and immediately refreshes when a tab regains focus, becomes visible, or comes back online.
  • First-relay Matrix pairing (beacon-sdk#265): Beacon starts pairing as soon as the first healthy Matrix relay responds rather than blocking on a slow or stalled peer relay. In a controlled Chromium test with one healthy relay and one stalled relay, the median time from clicking Connect to seeing a usable QR fell from 10.31 seconds to 0.55 seconds (and with two healthy relays, from 0.81 to 0.55 seconds, across three fresh browser contexts per condition). The chooser also shows progress while it prepares the QR.
  • 375x faster large Base58Check message serialization (beacon-sdk#257): Large contract parameters used to leave the browser busy converting a wallet message for seconds at a time. In Chrome, encoding an operation containing a 128 KiB Micheline string fell from 31.5 seconds to 84 milliseconds, and decoding fell from 18.9 seconds to 28 milliseconds (measuring serialization alone; wire format stays 100% compatible with existing wallets). You can test 1 to 256 KiB sign and operation payloads against your own wallet at Taquito Playground .

2. Seven Built-In Languages (with RTL Layout) and WCAG Keyboard Accessibility

  • 7 built-in locales with browser auto-detection and runtime switching (beacon-sdk#246, #253, #256):
    • Human-reviewed (status: 'human-reviewed'): English (en), German (de), and Polish (pl) (thank you to David Kaminski (@dvkam) for contributing the reviewed Polish translation and refining the German terminology).
    • AI-generated drafts open for native-speaker review (status: 'ai-draft'): French (fr), Spanish (es), Japanese (ja), and Arabic (ar, with automatic right-to-left dir="rtl" layout).
    • Beacon detects the browser language automatically, and dApps can switch languages or light/dark themes at runtime (wallet.setLocale('ar'), wallet.setColorMode(ColorMode.DARK)). Play with the live language and theme switcher at Taquito Playground .
  • Help Beacon sound natural in your language: If you would phrase a prompt differently, tell us which language you used, the wording you saw, and what you would say instead, or edit a translation directly on GitHub: TRANSLATIONS.md. New languages are welcome too.
  • WCAG / WAI-ARIA keyboard navigation and focus management (beacon-sdk#247): The chooser supports light and dark themes, role="dialog", aria-modal="true", Tab / Shift+Tab focus trapping, Escape-to-close, focus restoration, visible keyboard focus outlines, screen-reader live announcements, and prefers-reduced-motion. See the keyboard demo and wallet API examples.

Kukai confirmation in Japanese with the close button on the right

The same confirmation in Arabic with the close button on the left

3. Major Lifecycle Refactor, Type-Safety Debt Paydown, and Non-Expiring Requests

  • Deep lifecycle ownership & strict TypeScript 6 / ESLint 10 overhaul: Over 230 source files across Beacon were refactored to unify request correlation, pairing ownership, multi-tab leader/follower routing, and storage lifecycles so cancelled pairings, disconnects, and tab switches settle callers cleanly and cannot overwrite a newer session. Legacy Transport<any> and untyped callback, storage, and logger boundaries were replaced with strict TypeScript 6 types, discriminated PermissionResponseInput and StoredAccountInfo unions, typechecked test and tooling suites (beacon-sdk#249, #270), and ESLint 10 gates across both Beacon and Taquito.
  • Non-expiring signing and operation requests by default (beacon-sdk#126): If it takes a minute to unlock your phone and review an operation, the dApp used to be able to report a timeout while the approval was still on your screen. Signing and operation requests now stay pending by default (permission requests still default to 60 seconds). DApps that choose their own deadline (requestTimeoutMs) can listen for BeaconEvent.LATE_RESPONSE_RECEIVED and use the transaction hash to tell the user what happened.
  • See which wallet is connected (await wallet.getWalletInfo()): DApps can call await wallet.getWalletInfo() on a Taquito BeaconWallet to read { name, icon, deeplink, type } for the active wallet without opening a pairing prompt.

Temple icon beside the connected account balance and address

4. Typed BeaconError Subclasses, Connection Observability, and the Beacon Inspector

  • 12 typed BeaconError subclasses & isBeaconError() (beacon-sdk#174, #179, #245): Request methods reject with concrete BeaconError subclasses (AbortedBeaconError, TransactionInvalidBeaconError preserving RPC error .data alongside isTezosRpcError(), PeerUnreachableBeaconError, etc.) carrying errorType, errorOrigin ('wallet' | 'local'), title, and description, plus typed WalletConnect pairing failure reasons ('origin-not-allowed', 'relay-unreachable', 'timeout', 'initialization-unavailable').
  • Connection health and pending-request inspection (beacon-sdk#176, #206): DApps can call await wallet.getConnectionInfo() (health: 'ok' | 'degraded'), wallet.getPendingRequests(), wallet.subscribeToMessages(), and subscribe to TRANSPORT_STATUS_CHANGED, WAITING_FOR_WALLET_ACK, and INVALID_ACCOUNT_DEACTIVATED. Pass uiOptions: { enableToasts: false } to suppress built-in progress toasts.
  • Did the wallet receive my request? (Beacon Inspector): The Beacon Inspector in the Vue test dApp puts outgoing requests, wallet acknowledgements, responses, and transport changes on one timeline. Follow the request ID to see whether the wallet acknowledged the request and where any wait occurred, or export the trace for debugging: https://shadownet.dapp.taquito.io/

5. Elsewhere in Taquito 25.2 (Plus Today’s v25.1.2 / v25.1.3 Security Rollup)

  • Detached signing, Smart Rollups in the Wallet API, and tz5 wallet permissions: Wallets can prepare manager operations for detached signing (#3480), dApps can originate Smart Rollups (including private rollup whitelists, #3486) and submit rollup messages and batches through the Wallet API (#3483), and Beacon permission responses now accept tz5 (mdpk) ML-DSA-44 accounts (beacon-sdk#271).
  • Paginated big-map reads & two-step block polling: Applications can page through finite big-map values in a single RPC request (#3485, #3523). Block polling checks the head hash before fetching the full block, reducing repeated RPC work (#3482).
  • BLS (tz4), BIP39 helpers, and Sapling: Aggregate-key BLS proof-of-possession signing (#3484, #3492), BLS shell RPC endpoints (#3474), BLpk packing in michel-codec (#3540), English BIP39 mnemonic key derivation without a signer (#3479), opt-in randomized Sapling output ordering (#3499), and custom Sapling boundData construction (#3533).
  • Tezos X (@taquito/tezosx): The optional, experimental @taquito/tezosx package prepares unsigned Michelson-to-EVM and EVM-to-Michelson calls for compatible Tezos X kernels (#3531), alongside Tezos X synthetic operation hash derivation in @taquito/utils (#3529).
  • TZIP-16 verification, RPC resilience, and browser-native bytes: TZIP-16 metadata reads now verify SHA-256 digests with IPFS gateway fallback (#3506). HTTP requests keep timeouts active across body reads (#3502) and retry transient 502/503/504 gateway errors (#3500) as well as native Firefox/WebKit network failures (#3461). Browser paths no longer rely on unguarded global Buffer polyfills (#3512, #3547).
  • Security and encoding hardening (also shipped on stable latest today in v25.1.2 and v25.1.3):
    • @taquito/sapling (GHSA-6r9w-cxjj-5776): SaplingTransactionBuilder now samples a fresh commitment trapdoor (rcm) for every deposit, payment, and payback output and a fresh spend randomizer for every input (#3587, #3588, GHSA-6r9w-cxjj-5776).
    • @taquito/local-forging (GHSA-9wjf-4grc-2g2h): LocalForger.parse() now slices bounded sub-buffers matching the declared 4-byte length prefix when decoding smart_rollup_originate whitelist fields, governance proposals, and BLS signature_v1 proofs, and rejects unknown public key hash tags or truncated inputs (#3581, #3582, #3583, GHSA-9wjf-4grc-2g2h).
    • @taquito/signer: Preserves leading zero bytes when exporting 32-byte ECDSA keys and copies caller byte buffers before signing (#3584).

David Kaminski (@dvkam) contributed across Beacon, rollups, signing, and conformance tests. Thank you to Rahul Saxena (@saxenism) of Bluethroat Labs (GHSA-6r9w-cxjj-5776) and byfor (@byfor8) (GHSA-9wjf-4grc-2g2h) for their responsible security disclosures, to Martin at Tezos Domains for feedback on metadata verification and wallet timeouts, and to Klas Harrysson at Kukai for the encoder regression report. Cumulative Taquito changes and credits.

3 Likes