Connecting Post-Quantum accounts to xGov/Lora website using Liquid Auth and Use Wallet v4 (Proposal #3450330087)

Let’s discuss my Liquid Stream proposal - Connecting Post-Quantum accounts to xGov/Lora website using Liquid Auth and Use Wallet v4

Link to xGov Proposal - Connecting Post-Quantum accounts to xGov/Lora website using Liquid Auth and Use Wallet v4 | xGov

Overview:
We built a wallet that supports post-quantum lsig accounts last summer (2025Q3), and then in the fall (2025Q4) we added PQ support for it to Liquid Auth. Both were recently xGov funded work. In 2026Q1, we integrated this code using use-wallet to a forked version of Lora and xGov website. The goal was to get a falcon PQ lsig account that was participating in mainnet consensus (https://allo.info/account/J62IXMLXYRPFE3ZPHQGNUZI6R6O5GOCAQEKVZLOKVMPQZZNCZTL6NHIEB4) to become an xGov member. This was the deliverable.

Results:
Our falcon PQ lsig account (J62IXMLXYRPFE3ZPHQGNUZI6R6O5GOCAQEKVZLOKVMPQZZNCZTL6NHIEB4) is now a valid xGov member ( Profile: J62IXMLXYRPFE3ZPHQGNUZI6R6O5GOCAQEKVZLOKVMPQZZNCZTL6NHIEB4 | xGov ) as part of 59m committee (you can search https://github.com/algorandfoundation/xgov-committees/blob/main/data/mainnet-v1.0-wGHE2Pwdvd7S12BL5FaOP20EGYesN73ktiC1qzkkit8\_/subscribed-xGovs/56000000-59000000.json ). This PQ lsig account has not voted on mainnet proposals yet since none of the 59m committee proposals are active…but we will verify next month (even if our voting power isn’t much, more symbolic).

We also got this setup working for Lora Transaction Wizard, but our recommendation after doing this dev work is that we should keep PQ falcon lsig support simple (limit to 16 txns or one group) right now until we can add native support for falcon PQ accounts. This way we avoid complex batching from adding dummy transactions and ensures a cleaner developer experience and more maintainable codebase.

Here are screenshots of it working (xGov & Lora with PQ account)

For the web libraries we created (listed in additional info), this work currently exists as a stable fork for PQ accounts. Rather than merging into use-wallet v4, we plan to polish and then integrate these features directly into the use-wallet v5 release scheduled for Spring/Summer 2026 (that Doug from NFD and Michael Feher from AF is leading).

We are requesting 88,888 ALGO in retroactive funding for two months of high-intensity development (January – February 2026). This work was successfully delivered over ten iterative releases (v3.202601.2 through v3.202601.11) in alignment with our 2026Q1 roadmap.

About the Team

Michael T Chuang has over a decade of mobile development experience serving as a tech lead at Marvel/Disney/ESPN on numerous Android and analytics projects, followed by several years as a paid open-source contributor at various startups. A couple of other part-time volunteers/contractors also assist Michael on algorand-related projects when they have time to help. Michael currently serves as a member of xGov Council and will abstain from voting on this proposal within xGov Council to prevent conflict of interest.

A big thank you to Urtho for hosting many of these liquid auth services/websites. A lot of testing/research we’re doing wouldn’t be possible without his support

Additional Info:

Forked Repos
xGov repo: GitHub - algorandecosystem/xgov-beta-web at feat/liquid-auth-falcon24 · GitHub
Lora repo: GitHub - algorandecosystem/algokit-lora at falcon24-support · GitHub
use-wallet repo: GitHub - algorandecosystem/use-wallet: A framework agnostic wallet integration library for Algorand dApps · GitHub
liquid-auth-use-wallet-client repo: GitHub - algorandecosystem/liquid-auth-use-wallet-client: Contains UI elements and certain logic for the helper class used with the Liquid wallet. · GitHub
liquid-client repo: GitHub - algorandecosystem/liquid-auth-js: Liquid Auth TypeScript Client · GitHub

npm libraries

https://www.npmjs.com/package/@algorandecosystem/use-wallet/v/4.7.0-beta.1

https://www.npmjs.com/package/@algorandecosystem/use-wallet-react/v/4.7.0-beta.1

https://www.npmjs.com/package/@algorandecosystem/liquid-auth-use-wallet-client/v/1.5.1

https://www.npmjs.com/package/@algorandecosystem/liquid-client/v/1.0.0

Companion Wallet App
Android - https://play.google.com/store/apps/details?id=com.michaeltchuang.walletsdk.demo
Repo - GitHub - michaeltchuangllc/algokit-walletsdk-kmp: KMP version of AlgoKit Wallet SDK · GitHub

Forked dApp Website
https://xgov.pg.nodely.dev/ (uses custom provider in normal v4 use-wallet library)
https://lora-usewallet.pg.nodely.dev/ (uses forked use-wallet library)

Metrics:
50+ unique repo cloners, 574+ repo clones

1 Like

@michaeltchuang Would you mind clarifying for which repos do the metrics apply to?
Did you see any use beyond the conducted test?

@uhudo answer to your questions

Would you mind clarifying for which repos do the metrics apply to?

for the metric i listed - I just pulled the github traffic stat from GitHub - michaeltchuangllc/algokit-walletsdk-kmp: KMP version of AlgoKit Wallet SDK · GitHub repo at the time of proposal creation. The typescript repos have only a handful of clones on top of that.

Did you see any use beyond the conducted test?

I’m interested in keeping a PQ account active in mainnet consensus and as an active xGov member (partly to be an early adopter and for the symbolic marketing ‘win’ of showing it can be done). I’ll keep this forked code around running for use-wallet v4 (since that’s how i interact with xGov website for my own PQ accounts to keep it registered and voting on xGov proposals)…at least until we get proper PQ lsig support through use-wallet v5 initiative (summer/fall 2026?)