Octez.connect v4.8.6 Security hardening, Protocol U support and bug fixes

Update (22 Jun 2026) — Octez.connect 4.8.6 is released, it fixes an important iOS bug in 4.8.5 which made connecting to Kukai iOS app impossible.

:tada: Octez Connect v4.8.6 — Release and Test Validation Report

We’re excited to share that Octez Connect v4.8.6 is released with few bug fixes, protocol U support. See changelog for details.
This version been thoroughly tested with both manual and automated testing is ready for community use. Below is a detailed breakdown of the verification work, so you can build with confidence.

Validation Methodology

To make sure 4.8.5 is drop-in safe for the Taquito ecosystem, we ran a layered test suite covering both the SDK itself and the most common dApp + wallet combinations on Tezos.

  1. Taquito integration branch
    We used Taquito PR #3424, which removes all internal Beacon patches and routes @taquitotaquitotaquitotaquitotaquitotaquitotaquitotaquitotaquitotaquitotaquitotaquitotaquitotaquitota@tezos-xuitotaquito/beacon-w@tezos-xllet t@tezos-xtezos-xrough @tezos-x/octez.connect@4.8.5. Every
    test below was run against locally built packages from that branch.

  2. Manual end-to-end wallet matrix
    Following a simple test plan with following two wallets and a sample dapp:

  • Temple wallet on Chrome — full operation matrix
  • Kukai wallet on Firefox — connect / transfer / sign smoke set + cross-browser parity
  1. Real-world dApp regression using taquito sample dapp (Taquito playground)
    Cloned the public Taquito Test dApp (Vue), repointed package.json to the local Taquito PR branch build, and ran the full automated suite: npm run
    test.

Results@taquito


:white_check_mark: Phase A — Automated checks

  • @taquito/beacon-wallet unit suite (29 tests): PASS
  • Browser-import smoke — Chromium: PASS
  • Browser-import smoke — Firefox: PASS

:white_check_mark: Phase C — Wallet operation matrix

Legend: Temple/Chrome · Kukai/Firefox

  • TC-01 Connect / permissions — :white_check_mark: · :white_check_mark:
  • TC-02 Active account — :white_check_mark: · :white_check_mark:
  • TC-03 Reveal (first op on fresh account) — :white_check_mark: · :white_check_mark:
  • TC-04 Transfer — :white_check_mark: · :white_check_mark:
  • TC-05 Sign payload — :white_check_mark: · :white_check_mark:
  • TC-06 Origination — :white_check_mark: · :white_check_mark:
  • TC-07 Contract call (counter increment) — :white_check_mark: · :white_check_mark:
  • TC-08 Batch (2 transfers, one approval) — :white_check_mark: · :white_check_mark:
  • TC-09 Delegation (set baker) — :white_check_mark: · :white_check_mark:
  • TC-10 Disconnect + reload — :white_check_mark: · :white_check_mark:

:white_check_mark: Phase D — Cross-browser + persistence

  • TC-11 Kukai on Firefox + dApp on Chrome (TC-01/04/06/07) — :white_check_mark:
  • TC-12 Session persistence across page reload — :white_check_mark:
  • TC-13 Network-mismatch handling — :white_check_mark:

:white_check_mark: Taquito Test dApp (Vue) regression suite

  • npm run test against the PR #3424 build → 46 / 51 automated tests passing :bullseye:
    • sapling tests needed a config change in vite.config.js to allow packages from local taquito branch. after which the tests passed
    • staking and delegating tests passed after manually connecting the dapp to wallet. automated tests were creating a self delegated wallet.
    • All the tests were run manually from Taquito playground and they passed (chrome, temple wallet)
3 Likes

Did you test Kukai and Temple mobile?
What about Kukai Web on Desktop and Mobile browsers?
And where’s Safari in the test matrix?

4 Likes

thanks for pointing it out. Yes, we tested following matrix in addition

a. Safari browser: Dapp on safari and
A. Kukai on safari browser
B. Temple safari extension

b. mobile browser: Dapp on mobile browser
A. Kukai on mobile browser (Chrome)
B. Temple android App

All the manual tests in the test-dapp-vue were tested against these combinations (except bridge). All of them passed except following on the kukai (as kukai does not support these operations)

  1. increase_paid_storage
  2. register_global_constant
  3. Fail loop (wallet throws an error saying invalid payload)
    Following shadownet addresses were used in testing
    Address 1
    Address 2
    Address 3

We could not test from Kukai iOS app on shadownet because we were unable to connect to the IOS app, either from our dapp. It gave one error " the network “Shadownet” does not match" I believe its the test network chain id mismatch. We are in touch with kukai regarding the same.

2 Likes

As discussed on the proto-ecosystem call this morning, this version of octez.connect doesn’t work with Kukai iOS because of the walletconnect version incompatibility. I understand you need to do another release of octez.connect to resolve that.

I will postpone the switch of Taquito to use octez.connect until after I do the U protocol support release of Taquito. I don’t want to ship them at the same time, as what we have in Taquito ( GitHub - ecadlabs/beacon-sdk-taquito-patches: Taquito's patched fork of Beacon SDK. Tracks upstream with bug fixes needed for @taquito/beacon-wallet releases. · GitHub ) is stable.

Cheers,

-Jev

4 Likes

Temple has a safari extension?

Ledger + Kuaki iOS has been a special kind of broken for a while now. Please test that and bring back clear signing.

Hi @jevonearth ,
We have released a bug-fix release v4.8.6 which fixes this Kukai iOS compatibility issue. We have also verified that the fix does not have regression on above tests. I have updated the taquito PR with new version of octez.connect.

4 Likes