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

Governance Discussions xGov Proposals
1

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)

image
image1920×804 255 KB

image
image1920×977 324 KB

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

2

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

3

@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?)

4

Hey @michaeltchuang
Everyone knows we are friends and working on some projects together but as an xgov council memeber I need to be just and fair and in that sense I think these proposals are becoming a little more frequent and more of asking funds for experimental work rather than retroactive rewards for impactful products with proven records.
Given the fact that on this very subject you already have near 350K of retroactive funding I suggest you withdraw this one and give it a little rest till it becomes a mature product instead of asking for funding on your roadmap as it progresses because this IMHO violates the nature of xgov retroactive program as it is not designed to fund envevours but to reward practical usability and impact.
Sadly, I must say it is a NO for me on this proposal.

Keep grinding legend and you know I am a fan of your work

5

@emg110 - I totally get where you’re coming from, and I appreciate the honesty.

Just to clarify, my team has only received 300K Algo from xGov so far (200K for a PQ-supported mobile wallet in 2025Q3 and 100K for adding PQ to Liquid Auth in 2025Q4). Even with that funded work completed, most major Algorand dApps still don’t support PQ (lsig) accounts. To me, getting PQ working with use-wallet and the xGov/Lora websites is still a win for ecosystem and logical next step. What’s the point of a PQ wallet if you can’t actually use it with main AF ecosystem apps?

I know we won’t see massive adoption until Pera joins the PQ party, but I’ve already got a working deliverable ready to go (see the screenshots) and I’m using/depending on it. That said, if everyone feels it makes more sense to wait and submit a proposal once the v5 version is merged and more mature, I’m totally fine with that too.

With the xGov treasury getting tighter, I’d still like to keep the proposal active so the community and broader xGov council can help decide if this is something worth funding right now (I already paid for the 100A proposal fee anyways) so my team can deliver future PQ-related work faster. No hard feelings at all if you think this PQ work is too experimental

6

Thank you for being a real professional about this. I really appreciate it.
The PQ account and transactions system is not finalized and as Chris Peikart mentioned as well , there is still engineering work to be done and what is available is considered POC and not finalized approach therefore what ever built atop will be considered experimental and may undergo changes when the AF protocol engineering team releases the final PQ TXN and PQ Wallet techs. This is why Pera did not yet approached it. This being said, what ever we build on current approach may be considered experimental work not production-ready. This was my reason to call it experimental work and more integrations on experimental work do not seem to be strategically sound.
Also that is the reason major dapps did not yet been considered for migration because the migration signal should come from the protocol not the ecosystem. Based on all of these, any work done regarding this, although precious, cannot be considered sustainably impactful and usable.
And indeed the decision will be upto xgovs and we only are having fair and honest discussions here.
Once again I need to assert that your work is precious and I personally believe AF should take it under its wings and fund it as a valuable experiment, but my opinion was regarding compatibility with the current retroactive bucket of xgov program only because it is simply not usable or beneficial for other users or devs in the ecosystem yet.

Finally, and for the sake of clarity on this discussion and for the record, I admire your work in the sense of great experimental work but believe that this xgov bucket is not aimed at funding ongoing development or experimental roadmaps. I wish soon new buckets get added to xgov by AF to fund this kind of great work too, and then this proposal would shine there.

To test this and find out if I think wrong, I suggest you send a PR to Pera Android and Use-Wallet since your work on Android and Use-Wallet integration is 100% ready and delivered (according to this proposal and the previous proposal, which got funded) . If those PRs get merged, then it shows I was wrong and I will take my word back and support your proposal on that 100% and strongly because then it will become impactful, subject to massive use and ideal match for current xgov retroactive funding IMHO.