Legion grant application

[Deadends]

Project Abstract

LEGION is a proof of concept for a next-generation zero-knowledge authentication protocol designed to eliminate the weaknesses of conventional identity systems. Instead of relying on passwords, OAuth tokens, or mTLS certificates which can be stolen, forged, or leaked LEGION enables users and services to authenticate through cryptographic proofs that never reveal underlying secrets.

The protocol introduces a lightweight, high-performance Halo2 proof system capable of running in browsers, mobile devices, and distributed microservice environments. Authentication is expressed through challenge-bound ZK proofs, ensuring that each login is verifiable, non-replayable, and mathematically tamper-proof. This allows organisations to adopt a secure-by-design access model while maintaining sub-millisecond latency and horizontal scalability across millions of users.

The first implementation of the protocol consists of a WASM-based client that demonstrates real-time, zero-knowledge proof–based authentication for APIs, applications, and cloud-native services.

Grant level

• Level 1: Up to $10,000, 2 approvals
• Level 2: Up to $30,000, 3 approvals
• Level 3: Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

• The application template has been copied and aptly renamed (project_name.md).
• I have read the application guidelines.
• Payment details have been provided (Polkadot AssetHub (USDC & DOT) address in the application and bank details via email, if applicable).
• I understand that an agreed upon percentage of each milestone will be paid in vested DOT, to the Polkadot address listed in the application.
• I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
• The software delivered for this grant will be released under an open-source license specified in the application.
• The initial PR contains only one commit (squash and force-push if needed).
• The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
• I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is:
  @_______:matrix.org (change the homeserver if you use a different one)

[github-actions]

CLA Assistant Lite bot All contributors have signed the CLA ✍️ ✅

[Deadends]

I have read and hereby sign the Contributor License Agreement.

[keeganquigley]

Hi @Deadends thanks for the application. This is really cool tech, but my main concern lies around funding. I wouldn't recommend relying on W3F follow-up grants for support, as its not a surefire thing. Can you elaborate on your plans for funding after the grant is completed?

[Deadends]

Hi @Deadends thanks for the application. This is really cool tech, but my main concern lies around funding. I wouldn't recommend relying on W3F follow-up grants for support, as its not a surefire thing. Can you elaborate on your plans for funding after the grant is completed?

Hi Keegan,

Thanks for raising this it’s a fair concern. I want to be clear that I am not viewing this grant as a bridge to indefinite funding, but rather as targeted funding to deliver a finished public good.

A self-contained artifact, not a service

Legion is intentionally architected as a finished protocol artifact, not a live service. The outcome of this grant is a complete, usable zero-knowledge authentication primitive (circuits, verifier, and SDK) that can be deployed by any parachain or dApp.

No recurring costs:
The protocol is client-side (prover) with a minimal verifier that can be deployed off-chain today and moved on-chain where appropriate. There are no centralized services to operate, no SaaS components, and no infrastructure that requires ongoing funding to remain functional.

Durable utility:
Once the circuits are audited and the SDK is released, the software remains usable indefinitely without requiring continuous maintenance funding.

Demand-driven future development

I agree that relying on follow-up W3F grants for basic survival is not a viable strategy. Any post-milestone work would be strictly demand-driven:

• Adoption-led: If parachains, wallets, or governance platforms adopt Legion, they will naturally drive demand for specific improvements or extensions.
• Ecosystem-native funding: For future feature work (e.g., ZK optimizations or specialized integrations), I would prioritize Polkadot Treasury bounties (such as ZK or infrastructure/tooling bounties), aligning costs directly with the network value provided rather than relying on the W3F grants program.

Summary

After the grant is completed, Legion does not require external funding to remain usable or maintained. The delivered software is a complete protocol artifact, not a service, and can be adopted indefinitely without my ongoing involvement. Any future development would be optional and driven by demonstrated ecosystem demand, rather than being required for the project’s survival.

If the ecosystem later requests specific extensions or optimizations, those would be pursued selectively through ecosystem-native mechanisms such as Treasury bounties or targeted grants, but Legion itself does not depend on them.