Developer Council 2025 10 31 - algorandfoundation/technical-adoption-committee GitHub Wiki

Developer Council Meeting Summary — 2025-10-31


1. Post-Quantum LogicSig & Falcon Implementation

Goal: Discuss the rollout and implications of post-quantum (Falcon) logic signatures, including mobile integrations and potential standardization.

Discussion Highlights

  • Implementation Status

    • Falcon logic signatures are now accessible across CLI, Android, and iOS (via Go Mobile).
    • Sample app supports Falcon account creation, transactions, key registration, and block proposals.
  • Deterministic Keys & HD Wallets

    • 24-word BIP-39 mnemonics used for key generation (compatible with Falcon).
    • True HD derivation (multiple public addresses from one seed) is not possible with Falcon cryptography.
    • Proposed derivation schemes (e.g., using counters) don’t offer privacy and were discouraged.
    • Rekeying Falcon logic sigs to ED25519 accounts is technically possible but not recommended.
  • Strategic & Adoption Perspective

    • Falcon is promising but not yet final — NIST is still reviewing lattice-based schemes.
    • Early standardization is risky; current efforts should remain experimental.
    • Consensus: leverage Falcon as a showcase for Algorand’s technical leadership (e.g., demo at the India Summit).
    • Potential marketing value in being the first chain to show a functional post-quantum wallet.

Action Items

  • AF’s team to draft an ARC formalizing the Falcon reference implementation.
  • Michael to maintain the mobile demo app and add transaction types on request.
  • Keep Falcon as an experimental feature for visibility while standards evolve.

2. ARC-89 – ASA Metadata Registry Update

Presenter: Cosimo Bassi

Key Updates

  • Specification considered mature after multiple review rounds.
  • Active work on the reference implementation repository with CI/CD, tests, and SDK integrations (on-chain + off-chain).
  • Plan to release on testnet/staging for public testing and feedback.
  • Simplified validation: metadata registry will not enforce ARC compliance (e.g., ARC-3) — issuers self-declare compliance.
  • Dependency: awaiting ARC-90 (URI scheme) finalization to close ARC-89.

Next Step:
Continue development and open the repo once a minimal working implementation is ready.


3. ARC-90 – Unified URI Scheme

Discussion Highlights

  • Merges previous URI schemes (ARC-19, ARC-26) into one unified format.
  • Discussion around syntax validation — preventing malformed formats like trailing “+” or duplicated ARC numbers.
  • Plan to introduce stricter regex validation and standardize URI composition rules.

Next Step:
Merge in draft status, before finalization.


4. ARC-60 – Wallet Arbitrary Signing API Update

  • Review postponed — Bruno Martins to revisit next council.
  • Expected on the next meeting’s agenda once available.