Transitioned the micro-billing session vault for Android & iOS to an Algorand escrow smart contract (that supports Algo25, HD, PQ Falcon24 lsig accounts). This smart contract is inspired by this session vault draft spec ( Tempo Session Intent for HTTP Payment Authentication ). It has been designed to be generic and the smart contract can be used by any other project (e.g. not limited to video streaming context).
We are requesting 88,888 ALGO in retroactive funding for three months of high-intensity development (April - June 2026). This work was successfully delivered over five iterative releases (v3.202602.4 through v3.202602.8) in alignment with our 2026Q2 roadmap. The requested funding will be reinvested in future quarters to improve Liquid Stream use case further. We will also be updating the escrow smart contract to support PQ Falcon native accounts when it’s released to testnet (should be in near future). Also, investigating if using a lsig approach will be cheaper to operate for a session vault is also on the roadmap this summer.
About the Team
Tony Chuang is a team member at Michael T Chuang LLC building Algorand related projects. He’s helping submit this project on behalf of the team led by Michael T Chuang, who has a decade of mobile development experience. A couple of other part-time volunteers/contractors also assist at Michael T Chuang LLC on this project when they have time to help.
Michael T Chuang currently serves as a member of xGov Council and will abstain from voting on this proposal within xGov Council to prevent conflict of interest.
To start of the proposal discussion, below are some of my thoughts about this proposal, with some relevant comments also in the related proposal 3618757149:
It would be interesting to hear how these deliverables contribute towards the user-friendly, chain-agnostic video streaming app for the retail market, which was mentioned as an idea/goal of the previous proposal. Any ideas when that will be available? I would prefer the xGov retroactively funded a full app rather then incremental developments, which are difficult for individual xGovs to try out and see the benefits first-hand.
Compared to the previous proposal, the metrics nicely increased. Do you know if this is related to the new introduced features and/or do you have any insights how is the work being used more broadly?
It would be interesting to hear how these deliverables contribute towards the user-friendly, chain-agnostic video streaming app for the retail market, which was mentioned as an idea/goal of the previous proposal. Any ideas when that will be available? I would prefer the xGov retroactively funded a full app rather then incremental developments, which are difficult for individual xGovs to try out and see the benefits first-hand.
The escrow smart contract is deployed on-chain, and the corresponding Android and iOS apps are currently in public beta for anyone who wants to play with the technical demo first-hand.
The previous proposal was limited to Android-to-Android streaming, this (proposal) deliverable enables iOS-to-Android cross-compatibility. We also moved to an on-chain escrow session vault, which provides a security upgrade over the old method of tracking session vault balances locally on a creator’s device.
Integrating this escrow model did require a temporary trade-off…video streaming is currently specific to Algorand now till we can iron out all the kinks (chain-agnostic Liquid Auth still functions perfectly fine under the hood). It also introduced some app video streaming UX friction and throughput challenges with prolonged streaming usage (fees, multi-threading issues, etc) that we are actively working through as we slowly scale up this summer.
If anyone else in the community is working on high-throughput micro-billing, where heavy request-batching is necessary to settle transactions 24/7/365 efficiently (e.g. by the block or small time increments), please reach out. I would love to collaborate and discuss/compare architectures
Compared to the previous proposal, the metrics nicely increased. Do you know if this is related to the new introduced features and/or do you have any insights how is the work being used more broadly?
I think the bump in metrics is mostly due to the Algorand Foundation’s recent push toward their post-quantum (PQ) roadmap combined with AF tweets mentioning funded xGov proposals. Since our project is one of the few active Algorand projects that actually supports PQ accounts, it may have put us on the radar for certain audiences….so it’s likely a mix of real interest from other Falcon PQ devs, plus some automated indexers and developer bots that track those specific keywords whenever repo updates roll out.
Since this is additional ask for a project that was already funded in the past, given there are new features, i would like to see some sort of other metrics than provide dones. While github activity has objectively increased, the demo app users seem to be in roughly same range as it was in April. Is there any other “social” metric you can share to show additional traction and would make easier decision for me personally in terms of warranted continous funding of the project?
@simonb Since this is additional ask for a project that was already funded in the past, given there are new features, i would like to see some sort of other metrics than provide dones. While github activity has objectively increased, the demo app users seem to be in roughly same range as it was in April. Is there any other “social” metric you can share to show additional traction and would make easier decision for me personally in terms of warranted continuous funding of the project?
We intentionally don’t track any user analytics or telemetry for privacy reasons, so we don’t have many user metrics to share.