# Use-Wallet - Open-Source Wallet Integration Library for Algorand (xGov Proposal 3247418179) **URL:** \ **Category:** xGov Proposals\ **Created:** [October 6, 2025, 4:21pm UTC](https://forum.algorand.co/t/use-wallet-open-source-wallet-integration-library-for-algorand-xgov-proposal-3247418179/14975 "2025-10-06T16:21:23Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![fisherman.algo](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/fisherman.algo/32/3578_2.png) [@fisherman.algo](https://forum.algorand.co/u/fisherman.algo)\ **Post date:** [October 6, 2025, 4:21pm UTC](https://forum.algorand.co/t/use-wallet-open-source-wallet-integration-library-for-algorand-xgov-proposal-3247418179/14975/1 "2025-10-06T16:21:23Z")
Hi all! We are submitting [this proposal](https://xgov.algorand.co/proposal/3247418179) for Use-Wallet maintenance. Use-Wallet is an open-source, framework-agnostic wallet integration library maintained by TxnLab. It enables Algorand dApps to seamlessly integrate with multiple wallets including Pera, Defly, Exodus, Lute, Kibisis, and WalletConnect. It can be used in any modern front-end stack, with official adapters for[React](https://txnlab.gitbook.io/use-wallet/framework/react),[Vue](https://txnlab.gitbook.io/use-wallet/framework/vue), [SolidJS](https://txnlab.gitbook.io/use-wallet/framework/solidjs), and[Svelte](https://txnlab.gitbook.io/use-wallet/framework/svelte). With UseWallet’s hooks and utility functions, you can: - Easily add or remove wallet support with a few lines of code - Configure each wallet provider as needed for your application - Allow users to easily switch between active accounts and wallet providers - Sign and send transactions - Restore sessions for returning use From November of 2022 through the present, the TxnLab team actively maintained and enhanced Use-Wallet to ensure reliability across the Algorand ecosystem. This includes: - Ongoing maintenance and compatibility updates with evolving SDKs and wallet providers - Addition and improvement of wallet adapters for broader ecosystem coverage - Enhancements to developer documentation, guides, and examples - Responding to developer issues and providing community support Use-Wallet functions as a public good. It is free, open-source, and used by a wide range of dApps across the Algorand ecosystem. Use-Wallet requires sustained maintenance to ensure it’s providing the optimal experience for developers and users. This proposal requests 175,000 ALGO in retroactive funding to cover the 7-month period of maintenance and development from June 1, 2024 through December 31, 2024. Our previously awarded xGov grant for Use-Wallet was for January 2024 - May 2024 [https://github.com/algorandfoundation/xGov/pull/186](https://github.com/algorandfoundation/xGov/pull/186) We are happy to answer any questions the community might have. ---
**Author:** ![LoafPickle](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/loafpickle/32/3441_2.png) [@LoafPickle](https://forum.algorand.co/u/LoafPickle)\ **Post date:** [October 7, 2025, 9:10pm UTC](https://forum.algorand.co/t/use-wallet-open-source-wallet-integration-library-for-algorand-xgov-proposal-3247418179/14975/2 "2025-10-07T21:10:30Z")
Easy yes vote here ---
**Author:** ![aper\_nft](https://avatars.discourse-cdn.com/v4/letter/a/a9a28c/32.png) [@aper\_nft](https://forum.algorand.co/u/aper_nft)\ **Post date:** [October 8, 2025, 8:01am UTC](https://forum.algorand.co/t/use-wallet-open-source-wallet-integration-library-for-algorand-xgov-proposal-3247418179/14975/3 "2025-10-08T08:01:09Z")
This open-source program is probably the most widely used library on Algorand among programs developed by the community, providing benefits to almost everyone, regardless of whether they are developers or users. Even if someone is not an Algorand user, anyone active in the Web3 space likely understands the importance of WalletConnect. Without this library, each dApp project would need to implement wallet connections individually. This would likely cause development costs for each dApp to skyrocket. Moreover, beyond reducing development costs, this library is essential for the Algorand Foundation to promote that blockchain solutions can be easily developed on Algorand, and it also serves as a promotional asset. This proposal concerns the maintenance of this public good, and it seems that the updates proposed for the period from June 1, 2024, to December 31, 2024, include the following (extracted and summarized from GitHub; please note that there may be inaccuracies): > v3.0.0-beta.8 – v3.0.0-rc.3 > Migrated Pera Wallet provider to Pera Connect v2 (breaking change) > Added features: Magic provider, Custom provider, AVM provider > Network switching support, WalletConnect response handling improvements > Updated framework adapters, reactive algodClient support in Vue > > v3.0.0 > Complete library rewrite (monorepo, TypeScript) > Framework adapters for React, Vue, Solid.js > Network switching and developer tooling improvements > > v3.1.0 – v3.2.1 > Added reactive algodClient for SolidJS > Fixed Webpack issues and Next.js example > Stability improvements for WalletConnect and internal store > Added CONTRIBUTING.md, updated dependencies > > v3.3.0 – v3.4.0 > Added new network fnet, resetNetwork option in WalletManager > Fixed Vue app initialization issues > > v3.5.0 – v3.7.2 > Added logging feature to WalletManager > Added networks: voimain, aramidmain; Biatec Wallet support > WalletConnect v1 session management, removed circular imports, active network chain ID fix > > v3.8.0 – v3.10.1 > Mnemonic session restoration > WalletConnect backup limited to Defly and Pera > Added Liquid Auth provider > Webpack fallback for wallet dependencies > Fixed KMD empty password handling, added tests > Updated dependencies (pnpm, TypeScript, etc.) > > v3.11.0 – v3.11.1 > Custom password prompt for KMD/Mnemonic > Prevented WalletConnect v1 session data collisions > > v4.0.0-beta.1 – v4.0.0-beta.3 > Migrated to algosdk v3.0.0 > Added network configuration builder, Defly Web extension wallet, Pera Discover browser auto-connect It seems to me that xGov grants are precisely intended to cover the development of such public goods. Therefore, I suspect there are very few, if any, who would want to reject this proposal. I myself consider it a highly reasonable proposal. Now, this leads to a discussion for the future: we need to think about how public goods can be made sustainable over the long term. The xGov program relies on the Algorand Foundation’s funding. The ALGO held by the Foundation is expected to be depleted around 2030. In other words, there is a very high likelihood that resource allocation to public goods through the xGov program will cease. By the time this happens, public goods must be financially self-sufficient, and I believe the xGov program should be designed to transition gradually toward that goal. Of course, there are other possibilities for strengthening grant funding itself, such as the Algorand Foundation issuing new ALGO or alternatives beyond the supply cap, implementing mechanisms to collect usage fees from users directly for public goods, or having revenue-generating companies or projects within the Algorand ecosystem contribute resources. The current Use-Wallet proposal is directly related to the maintenance of public goods within this discussion. I would like to have a discussion—including xGov voters and users without voting tickets—about how the costs should be covered through the xGov program, on what schedule, and whether this is appropriate. ---
**Author:** ![Geralt](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/geralt/32/3841_2.png) [@Geralt](https://forum.algorand.co/u/Geralt)\ **Post date:** [October 18, 2025, 12:29pm UTC](https://forum.algorand.co/t/use-wallet-open-source-wallet-integration-library-for-algorand-xgov-proposal-3247418179/14975/4 "2025-10-18T12:29:36Z")
Yes from me. The ecosystem needs well maintained open-source tooling for developers who want to build on Algorand. I’ve not used this myself, but I’m aware of it and the github repository. Frontend is the wildwest and can be difficult to keep up with over time. A well documented library with support for popular frameworks certainly helps reduce the amount of effort required to start building. ---
**Author:** ![PurePension](https://avatars.discourse-cdn.com/v4/letter/p/74df32/32.png) [@PurePension](https://forum.algorand.co/u/PurePension)\ **Post date:** [October 18, 2025, 4:03pm UTC](https://forum.algorand.co/t/use-wallet-open-source-wallet-integration-library-for-algorand-xgov-proposal-3247418179/14975/5 "2025-10-18T16:03:15Z")
Thank you. it’s a yes from me. ---
**Author:** ![emg110](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/emg110/32/3996_2.png) [@emg110](https://forum.algorand.co/u/emg110)\ **Post date:** [October 28, 2025, 7:39am UTC](https://forum.algorand.co/t/use-wallet-open-source-wallet-integration-library-for-algorand-xgov-proposal-3247418179/14975/6 "2025-10-28T07:39:23Z")
Most simple judgment ever: Surely a big YES! Good and effective work should always be rewarded to grow. ---
**Author:** ![algotables.algo](https://sea2.discourse-cdn.com/flex016/user_avatar/forum.algorand.co/algotables.algo/32/4060_2.png) [@algotables.algo](https://forum.algorand.co/u/algotables.algo)\ **Post date:** [November 11, 2025, 4:31pm UTC](https://forum.algorand.co/t/use-wallet-open-source-wallet-integration-library-for-algorand-xgov-proposal-3247418179/14975/7 "2025-11-11T16:31:50Z")
Please be sure to vote if you haven’t already. 🙂