feat: add AlgoVoi wallet provider

[chopmob-cloud]

Summary

• Adds AlgoVoi as a named wallet provider (WalletId.ALGOVOI)
• AlgoVoi is an Algorand + Voi browser extension wallet with native x402 HTTP payment support
• The implementation calls the ARC-0027 compliant window.algorand provider directly — no external SDK dependency required
• Extension: AlgoVoi on GitHub

Changes

• types.ts — Add ALGOVOI = 'algovoi' to WalletId enum, WalletMap, and WalletOptionsMap
• algovoi.ts — New AlgoVoiWallet class extending BaseWallet
  • Detects the extension via window.algorand?.isAlgoVoi === true
  • Falls back to listening for algorand#initialized event if not yet injected
  • Implements connect(), disconnect(), resumeSession(), signTransactions()
  • Handles both algosdk.Transaction[] and Uint8Array[] input formats
  • 3-minute timeout for provider detection
• index.ts — Export AlgoVoiWallet
• utils.ts — Register in createWalletMap()
• algovoi.test.ts — Unit tests for connect, disconnect, resumeSession, metadata

dApp usage

import { WalletId, WalletManager } from '@txnlab/use-wallet'

const walletManager = new WalletManager({
  wallets: [WalletId.ALGOVOI, WalletId.PERA, WalletId.DEFLY]
})

Test plan

• All 475 existing tests pass (no regressions)
• New AlgoVoi tests pass (connect, disconnect, resumeSession, metadata)
• pnpm build succeeds for @txnlab/use-wallet package
• Manual: Install AlgoVoi extension + test with a dApp using use-wallet

[chopmob-cloud]

Hey @drichar — just wanted to check in on this one. AlgoVoi is a browser extension wallet for Algorand and Voi with native ARC-27 support, and getting it into use-wallet would really help with dApp compatibility across the ecosystem (a few Voi dApps are already waiting on this to land before they can add AlgoVoi support).

No pressure at all — just appreciate any review when you get a chance. Happy to address any feedback or changes needed. 🙏

[chopmob-cloud]

Bumping this for visibility — wanted to share some context on where this fits in a wider rollout.

What's shipped since this PR was opened

Since submitting this PR, AlgoVoi has launched full implementations across three payment protocols:

Protocol	Status	Links
x402 (HTTP Payment Protocol, spec v1)	✅ live	x402.org ecosystem listing #2022
MPP (IETF draft-ryan-httpauth-payment)	✅ live	tempoxyz/mpp #556
AP2 (Agentic Commerce, AP2 v0.1)	✅ live	google-agentic-commerce/AP2 #218

All three are smoke-tested with real on-chain USDC payments across Algorand, VOI, Hedera, and Stellar.

eCommerce platform adapters

AlgoVoi also has payment gateway adapters for 17+ eCommerce platforms (WooCommerce, Shopify, PrestaShop, Magento, OpenCart, and more), all open-source:
👉 chopmob-cloud/AlgoVoi-Platform-Adapters

Why use-wallet matters here

The AlgoVoi browser extension is the user-facing wallet that completes the loop — dApps built with use-wallet can sign the on-chain payment transactions that x402/MPP/AP2 require. Without WalletId.ALGOVOI in use-wallet, dApp developers building payment-gated flows on Algorand have to roll their own integration.

Happy to answer any questions or make changes if the implementation needs adjusting for the v4 API.

[chopmob-cloud]

Quick check-in — coming up on three weeks since the last bump.

Since then AlgoVoi has expanded to seven supported chains (Solana and Tempo joining Algorand, VOI, Hedera, Stellar, Base) and the browser-extension wallet was just listed under Wallet Providers in awesome-algorand (#181, awaiting maintainer review).

A native wallet provider in use-wallet would help dApps using the library pick up AlgoVoi flows cleanly across that 7-chain surface.

Happy to make any changes the team would like to see — no rush, just wanted to flag it's still relevant on our side. Cheers.

[drichar]

Sorry for the delay @chopmob-cloud! When the PR was opened I was preparing for the stable v5 release. My thinking was that we would wait and migrate the AlgoVoi provider to its new wallet adapter pattern, where it would be a standalone package instead of living inside the core library.

Shifting priorities have delayed the v5 release and my focus was elsewhere. I should have contacted you sooner.

We can get this merged and cut a new v4 release but I think it would make more sense to have you migrate AlgoVoi to its own adapter package now so it's ready for the v5 stable this month.

What do you think?

[drichar]

Here's the Lute v5 adapter package as an example: https://github.com/TxnLab/use-wallet/tree/v5/packages/wallets/lute

NPM: https://www.npmjs.com/package/@txnlab/use-wallet-lute

[chopmob-cloud]

Many thanks for the feedback, happy to wait, if it makes the transition easier, we are rolling out additional chains etc over the coming week or two, but if we need to make any code changes, they can be integrated very quickly.

Thank you

[drichar]

Part of the reasoning behind this transition is to give wallet maintainers ownership of their wallet adapter packages. While in the initial v5 release most of these will still be @txnlab/ packages under our NPM org, the goal is to have wallets that are actively maintained take control of their respective packages.

(This also drastically reduces the bundle size of the core library)

If you want to take this approach and publish your own package for AlgoVoi, I'd be happy to help with the migration from what you have here. I'll add it to the v5 docs for discoverability when it's ready.

[chopmob-cloud]

Thanks again for the detailed response — really helpful context on the v5 direction.

Happy to take ownership of the package. We've gone ahead and built and published the standalone adapter:

npm: https://www.npmjs.com/package/@algovoi/use-wallet-algovoi

Usage:

import { algovoi } from '@algovoi/use-wallet-algovoi'

const walletManager = new WalletManager({
  wallets: [algovoi(), pera(), defly()]
})

Test coverage:

• 10 smoke tests — API surface, factory shape, metadata, icon
• 15 unit tests — connect, disconnect, resumeSession, signTransactions against a mocked window.algorand
• 20 e2e simulation tests — full WalletManager → AlgoVoiAdapter → window.algorand chain including late provider injection, timeout, and signing edge cases
• 45/45 passing, clean build

Follows the Lute package structure exactly — peer deps on @txnlab/use-wallet ^5.0.0 and algosdk ^3.0.0, ESM-only output via tsdown, no external client dependency (talks directly to the ARC-27 window.algorand provider).

Happy to make any adjustments you need before adding it to the v5 docs.