Developer Council 2026 01 09 - algorandfoundation/technical-adoption-committee GitHub Wiki

🧠 Developer Council — Summary (2026-01-09)

1. ARC-89 — ASA Metadata Registry (Singleton App)

  • Cosimo Bassi presented a full implementation of ARC-89, proposing a singleton application acting as an on-chain metadata registry for ASAs.
  • Key motivation:
    • Reduce fragmentation and latency.
    • Store metadata on-chain using one box per ASA.
  • Metadata constraints:
    • Single box (~32 KB max) by design to ensure atomicity and discourage large on-chain payloads.
    • JSON payload, preferably ARC-3 compliant, for explorer and wallet compatibility.
  • Trust model:
    • Only the ASA manager can create, update, or delete metadata.
  • API supports create / replace / delete operations, plus paginated getters due to log-size limits.
  • Decision:
    • ARC-89 will be moved to Last Call.
    • TestNet deployment will remain mutable during Last Call to encourage testing.
  • Action:
    • Stéphane Barroso to update the ARC-89 PR status and announce the Last Call timeline.

2. ARC-89 SDK & Tooling

  • SDK design:
    • Hybrid client combining AlgoKit-generated app client and pure Algorand client.
    • Read operations default to the more efficient Algorand client.
  • Features:
    • ARC-89 and ARC-90 URI helpers.
    • Convenience methods to compute MBR deltas via simulation (create / update / delete).
    • AVM parity mode to simulate contract responses, including pagination behavior.
  • Next step:
    • Translation of the SDK to TypeScript (open for contributors).

3. Metadata Design Constraints & Future-Proofing

  • Strong design principle: no multi-box chaining for metadata.
  • Large or unbounded data should be referenced externally (DID registry, IPFS, AWS, etc.).
  • Backward compatibility:
    • Existing ASAs with immutable metadata hashes are supported by enforcing immutability on registry creation.
  • Consensus:
    • Single-box design is intentional and aligns with AVM-first principles.

4. Liquid-O / LiquidAuth — Post-Quantum Wallet Progress

  • Michael T. Chuang shared updates on a post-quantum, voting-capable wallet using:
    • Falcon accounts (HD and Falcon).
    • Liquid-O demo for signing and account ownership proofs.
  • Current status:
    • Android app working (passkeys and Liquid-O).
    • Server fork operational.
  • Discussion points:
    • Liquid-O roadmap tied to Pera, but potential to integrate earlier into XGov / XGV flows.
    • Liquid-O seen as a peer-to-peer alternative to WalletConnect, leveraging WebRTC.
  • Actions:
    • Michael to focus on iOS implementation next.
    • Bruno Martins to explore enabling Liquid-O on a live TestNet application (starting with XGov).

5. Post-Quantum Caution & Standards

  • Bruno Martins urged caution on widespread post-quantum adoption:
    • Quantum security story not fully mature.
    • Open questions around VRF and key derivation standards.
  • Seed / mnemonic issues remain unresolved for Falcon:
    • No standardized 24-word mnemonic scheme suitable for post-quantum keys today.
  • Consensus:
    • Continue experimentation, demos, and ecosystem visibility without premature standardization.

6. XGoV Architecture & Mobile Clients

  • Michael T. Chuang proposed decoupling XGoV into REST or GraphQL endpoints for better mobile UX.
  • Paweł Pierścionek and M G clarified:
    • XGoV is designed as permissionless front-end to smart-contract interaction, without centralized APIs.
    • A separate centralized backend could be hosted independently if needed.
  • Outcome:
    • No change to XGoV architecture; alternative setups remain possible for demos.

7. Biotech DEX Launch & TestNet Consensus Issues

  • Ludo S announced the launch of their biotech DEX on MainNet.
  • Ongoing issues on TestNet:
    • Blocks not finalizing due to missing agreement votes.
    • Suspected causes include uneven stake distribution, old participation keys, and relay configuration.
  • Debugging actions discussed:
    • Regenerate participation keys (with awareness of delayed activation).
    • Temporarily reduce DNS bootstrap to a single relay.
    • Enable relay debug logs and collect detailed traces.
  • Action:
    • Ludo S to continue investigation and share logs after applying changes.

8. TLDR

  • Cosimo Bassi:
    • Make ARC-89 TestNet deployment mutable.
    • Publish a Jupyter notebook and deeper documentation.
  • Stéphane Barroso:
    • Move ARC-89 to Last Call.
  • Michael T. Chuang:
    • Continue iOS work on passkeys and Liquid-O.
    • Prepare demos targeting the ETH Denver timeframe.
  • Bruno Martins:
    • Sync internally on Liquid-O TestNet integration.
  • M G:
    • Share TypeScript Falcon libraries and X402-related packages.
  • Ludo S:
    • Regenerate participation keys, adjust relay setup, and collect logs.