Release 1.7.0 · perawallet/connect

What's new

Pera browser extension, on by default — connect now talks to the extension through its window.pera provider instead of ARC-27, and no longer needs experimental: true. When the extension is installed, the modal lists it first; pass shouldPreferExtension: false to leave it out. getPeraProvider() and the provider types are exported, and experimental is still accepted but gates nothing (#213)
transactionSigner — an algosdk TransactionSigner, so Pera drops straight into AtomicTransactionComposer with one wallet prompt per group (#212)
resolveArc60Signer() — returns the auth address for rekeyed accounts, so ARC-60 payloads name the key that actually signs (#209)
algod option — send connect's account lookups to your own nodes instead of the public AlgoNode endpoints (#214)

Pera's WalletConnect session is now stored under its own PeraWallet.WalletConnect key, so it no longer overwrites or deletes the sessions of other WalletConnect v1 wallets on the same site. Existing sessions are migrated on first load (#210)
When config.json can't be reached, connect falls back to a Pera-hosted bridge instead of the retired bridge.walletconnect.org (#211)
Pera Web messages are only accepted from the Pera Web tab connect opened, on the configured origin, and a connect callback with invalid addresses is rejected (#219)
signTransaction now checks the wallet's answer on every transport: one signed transaction per slot to sign, in group order, each matching the requested txID. Behaviour change: a short or mismatched answer used to be returned as-is and now throws SIGN_TRANSACTIONS (#219)
The package no longer includes the gitleaks binary that 1.7.0-beta.1 and beta.2 shipped by mistake. 1.7.0 is 0.74 MB unpacked, down from 30.9 MB (#217)

README: documents the WalletConnect v1 transport and exactly what signData signs (#216), and how to use connect with use-wallet through @perawallet/use-wallet-pera (#218)

Full changelog: v1.6.1...v1.7.0