Polkassembly Logo

OpenGov
This proposal was still in progress when Polkassembly was archived. The status shown here is frozen and may not reflect the final on-chain outcome.
View All Small Spender

ComputeFlux: Polkadot AI Adoption & dotUSD Utility Pilot

inSmall Spender
a day ago
Deciding

Making AI Computing a Real-World Use Case for Polkadot's Native Stablecoin
Funding Requested: 16,384 USDC
Duration: 3 Months
Proposer: ComputeFlux Team

  1. Overview
    ComputeFlux is building an OpenAI-compatible AI gateway connecting users, developers, and AI agents to multiple AI models and computing resources through a unified interface.
    We propose a 3-month pilot to bring practical AI services to the Polkadot ecosystem, with a particular focus on creating a real-world payment use case for dotUSD.
    Through wallet-based onboarding, subsidized AI usage credits, developer APIs, and dotUSD payment integration, we aim to make Polkadot-native assets useful for accessing AI computing services.
    Our goal: Turn Polkadot wallets into gateways for AI services, and dotUSD into a practical payment option for AI computing.
  2. Why Polkadot & dotUSD?
    Polkadot is developing its native stablecoin, dotUSD, to support a broader on-chain economy.
    However, stablecoin adoption requires more than liquidity and trading. It also requires useful products and services where people can spend it.
    ComputeFlux aims to make AI computing one of those services.
    AI inference and developer APIs are natural candidates for stablecoin payments because computing resources are consumed on a usage-based basis.
    This pilot aims to create:
    Real dotUSD utility: Purchase AI credits using dotUSD.
    Developer payment use cases: Fund AI API consumption with dotUSD.
    Repeatable economic activity: Enable ongoing payments tied to actual AI computing usage.
    Wallet-native access: Connect the existing SubWallet login experience with AI services and payments.
    The objective is not simply to distribute incentives, but to test whether Polkadot-native payments can support sustained demand for useful digital services.
  3. Existing Progress
    ComputeFlux has already established an early technical foundation within the Polkadot ecosystem.
    SubWallet Integration — Completed: Users can already log in to ComputeFlux using SubWallet.
    Working AI Platform: An early AI gateway and testing environment are available.
    Polkadot Products Devnet — Deployed: ComputeFlux has been deployed as a Product on the Polkadot Devnet and indexed by DotMetrics.
    Open-Source Smart Contracts: Initial smart contract infrastructure has been published for Polkadot testnet experimentation.
    Community Discussion: ComputeFlux has been publicly discussed on the Polkadot Forum since July 2026, with progress updates and community feedback.
    This Treasury request builds on existing development rather than starting from scratch.
  4. Pilot Deliverables
  5. dotUSD Payment Integration
    Develop and test a working dotUSD payment flow enabling users to purchase ComputeFlux AI credits through supported Polkadot infrastructure.
    The pilot will validate wallet interaction, payment verification, credit settlement, and transaction reporting.
  6. Polkadot AI Usage Credits & Payment Pilot
    Provide subsidized AI usage credits for Polkadot users and developers while supporting controlled dotUSD payment experiments.
    This will allow participants to experience AI services with minimal initial cost and evaluate dotUSD as a payment method.
  7. Developer APIs & Integration Support
    Provide OpenAI-compatible API access, documentation, and integration examples to help developers build AI-powered applications.
  8. Ecosystem Engagement & Public Reporting
    Engage Polkadot communities and developers, document integration experiments, and report actual AI usage and dotUSD payment activity.
  9. Pilot Targets
    Metric3-Month TargetNew registered users500Active AI users100Developer/API users50AI integration experiments10Ecosystem collaborations5dotUSD payment integration1 working pilotdotUSD payment transactions & volumePublicly reportedMeasurement: Active users must complete successful AI inference requests. Developer adoption requires authenticated API usage. Integrations and collaborations must have documented outcomes.
    dotUSD transactions will be measured separately from promotional credits, including successful payments, total payment volume, and repeat payment activity.
    These are targets, not guaranteed outcomes.
  10. Budget
    CategoryAmountSharePolkadot AI Usage Credits & dotUSD Payment Pilot8,192 USDC50%Product Development & Integration4,096 USDC25%Community Engagement & Outreach2,457.60 USDC15%Infrastructure & Operations1,638.40 USDC10%Total16,384 USDC100%50% of the requested funding directly supports ecosystem AI usage and the dotUSD payment pilot.
    The pilot allocation will support subsidized AI consumption, payment testing, and eligible participant incentives. Technical development of the payment integration will be funded through the Product Development & Integration allocation.
    The final report will distinguish promotional credits, test payments, and genuine user-funded dotUSD transactions. Any conversions into dotUSD and remaining funds will be disclosed.
  11. Timeline
    Month 1 — Onboarding & Payment Development
    Launch Polkadot-focused onboarding, begin dotUSD payment integration, and recruit initial users and developers.
    Month 2 — Payment Pilot & Adoption
    Test dotUSD-funded AI credits, expand API access, support developer experiments, and publish a progress update.
    Month 3 — Evaluation & Reporting
    Validate the payment workflow, measure AI usage and dotUSD transaction activity, document ecosystem integrations, and publish a final report.
  12. Transparency & Accountability
    ComputeFlux will publish a progress update and final report covering:
    Registered users, active users, and API adoption
    AI credits distributed and consumed
    dotUSD payment transactions, volume, and repeat usage
    Documented developer experiments and collaborations
    Budget utilization and remaining funds
    Results will distinguish subsidized activity from genuine user-funded demand, with privacy-conscious reporting and on-chain transaction evidence where applicable.
    Any future expansion or funding request will be evaluated separately based on actual pilot results.
  13. References
    Live Platform: https://test.computeflux.ai
    Official Website: https://computeflux.ai
    Polkadot Forum Discussion: https://forum.polkadot.network/t/computeflux-the-first-openai-compatible-ai-gateway-for-polkadot/17990
    Full Proposal: https://docs.google.com/document/d/15GxOiw2Qfl9i8AqG4xR8YMdHtctT1LRdryRpXKHz7kc/edit
    Open-Source Smart Contracts: https://github.com/computeflux/revive-contract
    dotUSD Governance Referendum: https://polkadot.subsquare.io/referenda/1944
    X: https://x.com/computefluxAI
    Closing
    Polkadot needs real applications where its native assets can be used, not just held or traded.
    ComputeFlux proposes a focused, measurable pilot to make AI computing one of those applications.
    With 16,384 USDC over three months, we aim to connect Polkadot wallet users, dotUSD payments, and practical AI services—while generating transparent evidence of adoption and economic activity.
    Real AI usage. Real dotUSD utility. Measurable ecosystem growth.

Comments (1)

a day ago

The applicant has a history of finding various ways to get funding from the Polkadot Treasury, from creating videos to organizing activities for the Chinese community...

When there’s no Treasury funding coming in, they tend to speak negatively about the ecosystem or disappear for months at a time.

I was surprised by what they did with the ComputeFlux project over the past few months, but yeah... some habits die hard.

Still, this project seems like a façade, and the real goal is to secure more Treasury funding. There doesn’t seem to be any genuine intention to make the project self-sustaining or to invest any of their own money.

Vote NAY!

21 hours ago

@14uk...GCEw

We welcome constructive criticism and scrutiny of Treasury proposals, but I would also appreciate it if criticism were based on facts rather than assumptions about people's motives.

First, if you are referring to AIWeb3, our history is publicly documented. We have never hidden the fact that we received Treasury funding in the past, and we have published reports detailing our work and contributions.

More importantly, there have been extended periods when AIWeb3 received no Treasury funding, yet we continued building, producing content, organizing activities, and supporting the Polkadot community.

For example, between December 2024 and April 2025, despite receiving no Treasury funding, our Telegram community grew from 3,384 to 6,688 members, our Discord community from 9,520 to 9,962, and our X followers from 35,244 to 39,968. These figures and our activity records were already publicly shared in our previous proposal:

https://polkadot.subsquare.io/referenda/1545

Second, you claim that we disappeared for months or spoke negatively about Polkadot whenever funding stopped. Could you please provide specific examples or evidence?

Our X account (@aiweb3dao) has continued sharing ecosystem updates, and our Telegram community has remained active. Constructive criticism of Polkadot's challenges should not be confused with abandoning or attacking the ecosystem. We care about Polkadot, and that is precisely why we believe its challenges deserve honest discussion.

Third, ComputeFlux is a real product with ongoing development, not a façade created for Treasury funding. We have already built a working AI platform, integrated SubWallet login, deployed on the Polkadot Devnet, and published technical work before seeking this funding.

Our goal is to build a sustainable AI computing platform with real users, developer adoption, and a viable business model. Treasury support would help accelerate Polkadot-specific integration and adoption, not replace the need for a sustainable business.

You are absolutely entitled to question our proposal, budget, deliverables, and long-term sustainability. We welcome that discussion.

But suggesting that we are acting in bad faith, disappearing whenever funding stops, or building a fake project solely to obtain Treasury money is a serious accusation.

I sincerely ask that you review the publicly available evidence and provide specific examples before making such claims.

We can disagree about whether a proposal deserves funding while still treating each other fairly and respectfully.

Polkassembly is now a read-only archive. Commenting is disabled.

Requested

USDT
16.38K USDT

Voting Period

Decision Period

1 / 28 days

Confirmation Period

0 / 2 days

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

Polkassembly · Archived 2026 · polkassembly.io

Terms and ConditionsTerms of Website
Privacy Policy