Background and Motivation:

The Polkadot Marketing Bounty was launched to accelerate ecosystem growth by funding community-led outreach initiatives. In late 2024, a revamped “Marketing Bounty 2.0” was approved with a committed set of curators who worked with good faith and a 200,000 DOT monthly budget. Its mission was to drive awareness for Polkadot in a transparent, accountable manner. The curator’s work and alignment with Polkadot’s mission are appreciated.

Over the past year, various community discussions and governance reflections have raised the need to reassess how the network approaches marketing, as part of a broader effort to uphold the integrity and sustainability of treasury spending. Like many decentralized experiments, it’s natural for initiatives to evolve as we learn together. Within this context, the Web3 Foundation and its Funding Committee, in alignment with OpenGov’s values, have committed to protecting the treasury by ensuring all ongoing programs align with strong, outcome-driven frameworks.

The current moment offers a chance to reflect. While some initiatives under the bounty have shown promise, the overall structure presents challenges in measuring return on investment at scale. Continuing to allocate substantial treasury resources without a clearer strategic and evaluating framework is increasingly difficult to justify in light of our shared responsibility for prudent treasury management.

Rationale:

Closing the Marketing Bounty now is a prudent step to safeguard Polkadot’s treasury and refocus on effective strategies. This proposal, initiated under the guidance of the W3F’s Funding Committee, aims to immediately terminate Bounty #33 (Marketing) before further funds are expended.

We acknowledge the efforts of the current bounty team and long-term contributions and attempts to promote Polkadot. Our proposal is to close the Marketing Bounty in order to better align resource use with the community’s current goals.

Given the bounty’s significant burn rate with outcomes that remain difficult to quantify, the most responsible course is to halt this spending until a better path is defined. This pause will prevent further depletion of the treasury.

Crucially, closing the bounty does not mean abandoning marketing or growth efforts for Polkadot. It means resetting our approach. It is also in keeping with OpenGov’s ideals of iterative improvement - when something isn’t working, we fix or replace it rather than continuing the status quo.

Path Forward & Encouraging Community Initiatives:

We propose to close the Marketing Bounty and invite the community to pause and reassess the best path for ecosystem growth. This closure would immediately stop all new spending from the bounty and return unspent allocated funds to the treasury for other uses. No further budget refills or new campaigns would be initiated. The Funding Committee and W3F will work to ensure an orderly wind-down in accordance with on-chain governance processes.

Going forward, the Funding Committee and the Web3 Foundation will collaborate with the community to review the structure and performance of other long-running bounties as well, ensuring that treasury-funded initiatives remain effective, measurable, and aligned with OpenGov’s evolving priorities.

Moreover, this action is not a rejection of marketing as a whole, but a call to improve how we fund and execute it. We remain optimistic that Polkadot’s community can develop more effective, accountable frameworks for spreading awareness of the network.

We welcome community input on how we should approach ecosystem growth and marketing accountability going forward.

Following the successful execution of the first 2025 funding cycle, this proposal requests a 6-month top-up for the Paseo Bounty (#37) to ensure uninterrupted operations through Q4 2025 and Q1 2026.

We are requesting ≈ 113,217 DOT (≈ $344,946 at EMA7 = $3.046731) to sustain the ongoing work of the Paseo core group and service providers covering runtime upgrades, validator infrastructure, DevRel support, and continuous testing across parachain and system chain releases.

This top-up ensures operational continuity ahead of the migration to the multi-asset bounty pallet and stablecoin-based funding model planned for 2026. Any unused funds from this period will be returned to the treasury or converted into USDT/C-based once they become available.

📄 Full proposal
📎 Previous top-up proposal
📎 Paseo Bounty (#37)

Hi, this proposal would be the on-chain version of Discussion 3385, but unfortunately Polkassembly miscalculated the payout date due to AH Migration Future Block Calculation. New preimage and proposal coming soon.

Overview

The Hungarian Polkadot DAO proposes a 6-month initiative to cultivate a vibrant Polkadot presence in Hungary and Central-Eastern Europe. The proposal seeks core funding for two dedicated managers ($5200/month/pp compensation) to coordinate activities, while all project-specific work (events, marketing, development) will be funded through existing Polkadot bounties (Events, Marketing, Fast Grants, and Open Source Developer bounties).

Strategic Rationale

Hungary represents an ideal hub for Polkadot expansion due to its combination of high-skilled IT workforce (ranked 5th globally for developers), strong blockchain heritage (home to Web2 successes like Prezi, LogMeIn), high crypto adoption rates (20-26% ownership), and strategic geographic position in Central Europe. The country's historical experience with decentralisation resonates with Web3 values, while its cohesive local crypto community has repeatedly delivered impactful initiatives.

Five Core Objectives

1. Academic Integration: PBA-X in Universities

• Partner with Obuda University (Hungary's top-ranked IT institution with 750+ IT students) to launch a credit-bearing blockchain course using PBA-X curriculum anticipated to start in February 2026
• Target: 25-60 enrolled students gaining official university credits for blockchain education
• Outcome: Creates a precedent for Polkadot-based academic curricula globally; develop implementation playbook for other universities

2. Government & Business Engagement

• Represent Polkadot at 4 business/government events aligned with Polkadot's technical roadmap (PVM/JAM strategies)
• Participate in 4 high-level government discussions on Substrate blockchain adoption for public records and services
• Conduct initial consultations via "Open Office" sessions to help ambitious teams develop ideas and access appropriate funding
• Research DAC (Decentralised Autonomous Company) pilot through independent OpenGov proposal

3. Hungarian-Language Content & Marketing

• Produce 31 media pieces (6 YouTube videos, 25 TikTok skits) promoting Polkadot and Web3
• Collaborate with 6 local influencers across crypto and mainstream platforms
• Publish 12 articles with Hungarian crypto media outlets (Cryptofalka, BitcoinBázis, Cryptoakadémia)
• Host 24 weekly community calls to provide technical support (staking, delegation, account setup)

4. Local Community Resilience & Diversity

• Strengthen the existing cohesive local community by expanding to other cities
• Engaging with non crypto natives

5. Global Community Mentoring and Outreach

• Open Office hours for helping communities becoming DAOs
• IRL community meetup for other Polkadot communities and DAOs

Track Record

The Hungarian Polkadot DAO has demonstrated significant impact since 2021:

• 40+ community events organised (meetups, workshops, hackathons)
• 40+ articles published in Hungarian for local audiences
• Polkadot Day 2024-2025 events with major ecosystem partners (Nova Wallet, Vara Network, KILT, Apillon, Parity)
• Selected for Web3 Foundation's Decentralised Voices Program (Cohorts 3 & 4)
• Open-sourced tools: DAO in a Box framework, OpenGov voting tools, Notion-based DAO management systems
• Government engagement: Presented blockchain use cases (Digital Vehicle Registration) to Hungarian Tax Authority (NAV) and National Council for Telecommunications

Funding Structure

Hybrid approach: Core managers receive monthly compensation from treasury; all project activities route through existing bounties to maintain decentralisation and clarity:

• Events Bounty → Community events, conferences
• Marketing Bounty → Content production, influencer collaborations, integrations and BD
• Open Source Developer Bounty → Infrastructure and software development
• Fast Grants Bounty → Tool and software development

This approach ensures continuous management oversight while avoiding concentrated budget requests and maintaining alignment with Polkadot's strategic priorities.

Leadership Team

• Vikk (Economist, 3+ years organising Polkadot Meetups): Bounty coordination, marketing, university partnerships, event management
• Spectra CryptoVerse (DAOist, 2 years at Aragon Network): Bounty management, financial planning, government relations, reporting

Implementation Timeline

6-month duration starting in January:

• February 2026 (Target) or September 2027 (Latest): PBA-X course launch at Obuda University
• Ongoing: Quarterly engagement, monthly content production, weekly collaboration with local and international communities

Risk Mitigation

Should the university integration fail due to circumstances beyond the DAO's control, the team commits to immediately returning allocated funds to treasury (7,600 USDC for PBA-X subscriptions and coordination fees) along with any other unused funds.

This proposal builds directly on the proven success of Polkadot Africa Builder Program and OpenGuild SEA initiative, adapting their models for Central-Eastern European context while maintaining fiscal responsibility through bounty-based project funding.

Full proposal here.

Ratify Approved Referendum #1768 - execution error due to AH migration

Context: This proposal ratifies the payment for already-approved referendum #1768, which failed to execute due to a technical error during the Asset Hub migration.

Background: Referendum #1768 was successfully approved by the community for Chaotic's critical NFT infrastructure maintenance. However, the execution failed because Asset Rates were not correctly configured after the Asset Hub migration.

Resolution: After consultation with the Web3 Foundation, Parity, and the Polkassembly team, we are submitting this ratification proposal to ensure the approved funding reaches its intended destination. The underlying Asset Rates issue is being resolved through referendum #1787.

Technical Details:

• Original referendum: #1768 (approved)
• Requested amount: $180,000 USDC
• Issue: Asset conversion failure post-AH migration

This is a technical correction to execute an already-approved community decision. No changes have been made to the original proposal scope or budget.

We appreciate the community's patience as we navigate these migration-related technical challenges.

Self-Sovereign Identity Wallet for the Substrate Ecosystem (Android and iOS), a bridge for institutional traditional businesses and governments, to use and rely on web3 technology.

Developed and Proposed by Peranto and Hope Clary Media LLC - establishing Peranto SSI North America in Wyoming, USA

November, 2025

The Aura Wallet is Public Infrastructure with Open- Source Code for Decentralized Identity on Polkadot. We believe technology matters and it is transparency that is required in order to move forward in the Digital Identity space. Our goal is to showcase how this technology can help humanity, through real world needs and fixing real problems.

Peranto is an ecosystem for the transition to a circular economy playground. To achieve this, True Self-Sovereign Identities and its applications must flourish to democratize and make Web3 accessible technologies available for system upgrades, without harm to humanity in the process.

Use cases for identity are boring and endless, and are part of everyday critical operations in Governments, Institutions, Businesses, etc. Usually, the security part is delegated to the server side, the business logic side, which carries problems to the real true owners of their data.

Our Polkadot Web3 ecosystem, powered by the Polkadot SDK, puts the security on the server and client side; this means our approach to a Digital Identity through the Aura SSI Wallet will provide a universal wallet for substrate ecosystems. To empower the $DOT economy our wallet will be using Asset Hub for all payments and as we grow through partnerships we will be bringing additional business models through our verticals onto Polkadot.

The current core team is made up of 3 people from the America’s with a PBA Alumni as our subject matter expert in the Technical Architect leadership role. All agents working on this project are located in different countries of the America’s: United States 2, Mexico 2, and Chile 2, all of us with different experiences and expert backgrounds. All of our skills are needed for the achievement of the current Development and Deployment of this proposal, at precise stages in its lifecycle.

We request the Polkadot Treasury to fund the Development and Real-World Deployment Testing with code fixes of the 2 use-cases for the Aura Wallet’s open-source core as an essential public infrastructure for the Polkadot ecosystem, with the collaboration of our trusted entities and trusted business partners. With World Wide Web Consortium (W3C) standards for DIDs and verifiable credentials currently supported by Kilt Parachain with Polkadot Infrastructure. We will be showing how Web3 comes to life with practicality and problem-solving, as our soul mission.

Our current Roadmap Vertical of Stakeholders and Collaborators:

Aura Wallet fills this gap. Our trusted entities, allies for testing and adoption:

• FlyGateway (USA) - A flight school seeking FAA-aligned digital credentials for pilots and curricular verification approval (acceptance).

Our full cycle production test use case will be conducted with FlyGateway in the United States and follow Federal Aviation Administration (FAA) regulations and standard practices. We hope that through this use case of testing and coding we can bring forth a product that is seamless for the FAA Regulatory Facilitators and the agency (government body).

• Federación de Andinismo de Chile (FEACH) - A national sports federation with 5,000+ members and 50+ clubs, ready to issue verifiable certifications for mountain guides and high-performance athletes.
• Polkadot Ambassador Fellowship (PAF) - A global network needing to vouch for contributions to governance and community building, while preserving privacy and accountability on General Data Protection Regulations (GDPR) metrics.

What Problems Are We Solving?

https://forum.polkadot.network/t/polkadot-ambassador-fellowship-paf-governance-critical-questions-before-on-chain-implementation/14997/8

Sep V0 Peranto Ci.Go Beta Program: Digital Transformation for FlyAdvanced

Chilean Test Aura Proposal

Sustainability Goals:

Our team is focused on financial sustainability for ourselves and for the health of Polkadot, we will be doing this through the initial ask for these funds listed, in addition to seeking out other partners after this initial kick-off phase. Our current focus is listed below for the kick-off phase:

• Regulatory Precedent: First SSI use case in the U.S. through FAA Regulatory Agent FlyGateway. Initial kick off goal with proven tech and data in hand is to onboard 44 License Flight Schools.
• Chilean Mountaineers Product Licensing.

Team Peranto SSI NA, LLC Team:

• Edgar – Founder & Lead Developer: Architecture, open-source development, KILT integration, long-term maintenance.
• Hope Goodman – Product Representative, BD Representative (USA) and Liaison with FlyAdvanced, pilot testing, FAA alignment, product documentation.
• Mike Devine - Business Development and FlyAdvanced Director of Flight Logistics, FAA compliant www.flyadvanced.com

Core Developing Team

• Edgar Salinas - Founder Peranto
• Dev 1 - To be determined
• Dev 2 - To be determined

Team Web3Chile (Peranto FEACH) Team

• Edgar – Founder & Lead Developer: Architecture, open-source development, KILT integration, long-term maintenance.
• Francisco Albornoz – Community Coordinator (Chile): Engagement with FEACH, mountaineer testing, federation standards, product documentation.
• Carolina Palma - Mountaineer expert and FEACH member
• César Escobedo - Product tester for Chile and Mexico

❌ Not Funded by OpenGov (Covered by Partners)

- Full iOS app development (beyond evaluation/testing)

- Branding versions of (Fly Wallet, Andino Wallet)

- Private backend services or infrastructure deployments for specific business cases

- FAA certification costs

- Post-launch support or Service Level Agreements

Seeking OpenGov Support Financially for:

Infrastructure

• Tools, 1 Mac Pro, 1 Android Tablet and 1 iPadOS
• Tester Tools to be useBuilding of 2 Customized SSI Wallet Applications, Android and iOS Apple, for use by non-technical users (pilots, mountaineers)
• Equipment supporat FlyGateway: 2 Android Tablets, 2 iPadOS, 2 Android Phones & 2 iPhones
• Deployment and real-world testing costs

Our commitment is to deliver a wallet for SSI, with Apache 2.0 licensing, with the following characteristics:

• Compliance with regulated environments (e.g., FAA)
• Capable of secure cryptographic presentation
• Extended communication capabilities (NFC, QR, WiFi Connect)
• Supporting $DOT, $USDC (initial tokens), or any native or wrapped token from the Substrate ecosystem (long term)
• Geo Location
• Verifiable Credentials management
• Secure key management through keychain | keystore
• Data Storage within the wallet custody to user only
• Signatory Software - user-flows with substrate crypto primitives
• API configuration within the wallet and the proof of service
• Public GitHub repo, modular architecture, basic DID management (Authentication, Encryption)
• One potential public use case for the Polkadot Ambassador Fellowship (demonstrate a verifiable experience for the agents in the field)
• Stable release of open source for Aura SSI Wallet, full documentation, final UX report.

General Communication Schema

Figure 1. Intended Aura Wallet basic communication flow for API and P2P framework

Figure1 shows the wallet methods for sharing archives and data, being cloud services the last ones to be considered for data redundancy. A feature for any SSI Wallet should be P2P data redundancy, share big files through WiFi connect with the person in front of you, verify the data against the signed metadata, and verify the hash on the blockchain in case it’s timestamped there as well, or communicate with a trusted entity on a secure API for diverse validating services.

Based on real-world demand with our trusted entities stakeholders, built for technology reusability, and designed for global impact, we are focused on turning SSI from theory into practice for Polkadot. This is not a single custom app—it is “Public Infrastructure for Identity on Polkadot”.

Operation Method:

• Multisig 3/3
• Milestones Payments
• Each milestone should begin with an allocation budget for its completion

The signers must evaluate the available resources and Work in Process (WIP); if it fits, they will release Kick off Funding, Contingency, Milestone 1 & Hardware equipment funding required. After Phase 1 Milestone is met a release of Salary Funds along with next Milestone funding should be released. This will allow the team to budget and keep going as Milestones are further met in the development and testing process of the project achieving delivery and documentation.

• The multisig account will have restricted access to the Contingency Drawer after the estimated runway, having two possibilities.
• The team delivered and accomplished all milestones, and the team gets equally rewarded with shares of this drawer automatically distributed into all core connected wallets 3/3, as a bonus.
• If the team didn’t deliver by the estimated runway date. The signers will assess the situation and, based on the viability of the delivery, the drawer will be used to finish the job, or these remaining funds will be returned to the treasury.

Economic Considerations

The team is decentralized, and three countries are involved (Chile, Mexico, and the United States) average income is different, so the living and operational costs vary.

Other Considerations

• Why We Prioritize DIDs & Verifiable Credentials Over Proof of Personhood: Proof of Personhood (PoP) aims to prove that a digital identity corresponds to a unique human being, often for use cases like one-person-one-vote governance or sybil-resistant airdrops. However, PoP does not verify who that person is, nor does it convey any regulated, verifiable attributes—such as a pilot’s license, medical certification, or flight hours.

In contrast, Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs)—as standardized by the W3C—allow trusted issuers (like FlyGateway, acting under FAA oversight) to cryptographically attest to specific, legally relevant facts about an individual. These include:

“This person holds a valid Private Pilot License (PPL),”

“This pilot has a current Class II Medical Certificate,”

“This graduate completed all required flight exams.”

For regulated industries—especially aviation, where compliance, auditability, and legal liability are paramount—uniqueness alone is insufficient. Authorities like the FAA need to verify credentials, not just personhood.

Therefore, our project starts with DIDs and Verifiable Credentials because they:

• Meet real-world regulatory requirements (FAA, KYC, AML)
• Enable selective disclosure (e.g., show PPL without revealing full identity)
• Support revocation and updates (critical for suspended licenses)*
• Are already interoperable with Polkadot via KILT Protocol
• Provide a foundation upon which PoP-like mechanisms can be added—if and when needed.

In short: We need to prove compliance through already established KYC funnels for regulated credentials. We need to prove they are “I am a Licensed Pilot or I have Passed Mountaineer training.” These Credentials are Issued and not proven, just as a human exists.

That’s why DIDs and Verifiable Credentials are the right starting point—and the right public good—for Polkadot’s identity ecosystem.

Less trust, more truth. Dapps, not chains.

🔗 Resources

• Live Signature Document Credential Verifier: https://beta.peranto.app/verify
• Aura SSI Working PoC Demo for Logbooks and Digital Signatures: https://www.youtube.com/watch?v=eOGxZ8nWW3w
• Visual Pitch Deck (PDF): https://docs.google.com/presentation/d/1L16EYEhaEhrldNUodpl8bIzeQUHM2Cmy/edit?usp=sharing&ouid=110353380380132837700&rtpof=true&sd=true
• Technical SOW (FlyAdvanced Beta Program): https://docs.google.com/document/d/1O5_mdxHO4sGH_qXp9N4ojbmgsSt-dDiUPMykKD2BI7g/edit?usp=sharing

Thank you for your time and vision.
We’re not just building tech.
We’re building trust — on Polkadot.

— Edgar Salinas
Founder, Peranto SSI NA, LLC
México | Miami | Wyoming | Delaware | Pensylvania

Context

RegionX Hub is the primary application for interacting with Polkadot’s Agile Coretime model. There is no other project in the ecosystem that fulfills this role, and we are proud to play this key role. At its core, Coretime is the product that Polkadot—and, in the future, JAM—offers. It is very important to have a project that gives users simple, intuitive access to all Coretime-related functionality. We represent the ecosystem in this area, which is why we take development at RegionX very seriously.

We are the only team to have successfully implemented a trustless secondary Coretime marketplace, live on Kusama. The concept of a secondary market was introduced in the Agile Coretime RFCs, and since then RegionX has led the effort and was the first to implement it. 

We are a team that, since Agile Coretime was introduced in RFC-1, has been working toward the goal of providing a web application for managing Coretime in an intuitive way. The Agile Coretime model is quite abstract, and creating a user interface that is both intuitive and easy to understand and use is definitely not a simple challenge. Therefore, we are proud to be the only team so far to have successfully tackled this challenge and to be the leading application for Coretime management.

In the new iteration of the app, called RegionX Hub, we have worked closely with designers to deliver something that not only looks great but is also highly usable for all the different types of users we have identified.

Overall, we believe we are working in a very important area of the ecosystem. With this proposal, we cover the retroactive work completed on the application and implement the requested features and improvements, along with essential updates required following the Coretime chain changes. With RegionX, we aim to represent the ecosystem in the best possible light when it comes to Coretime.

Proposal

This proposal covers a significant amount of work we have delivered since our last proposal. It includes necessary updates following Coretime chain upgrades, as well as key improvements to ensure all pages present the required information and offer an intuitive overview and interface. The proposal also includes other UX and UI improvements that were either requested or identified as missing from the RegionX Hub.

Many of the UI and UX improvements have already been implemented, and their results can be found in the Delivery section.

For this proposal, we are willing to reduce our hourly rate to 70 USD/hour. We are doing this because we believe in the Polkadot and want to keep RegionX Hub active in the ecosystem. We’ve also removed in-depth data analytics and reduced the proposal to only the most essential work and ongoing maintenance.
It’s in the ecosystem’s interest to keep this project live rather than shut it down, so our team has agreed to request the smallest possible cost from the treasury to keep it running.

The project will be made more accessible to outside contributors so anyone can add requested features and contribute to the RegionX Hub.

Full proposal: https://docs.google.com/document/d/1XXrOz-pc4jDsSehIBRQUXHlWKMe5EoylWTKi4wdyj-Y/edit?usp=sharing

Sets DOT asset rates for USDT and USDC. The asset rates were not mapped during the migration and therefore need to be redefined. Since the asset IDs (XCM locations) were not re-anchored, they cannot be used correctly in their current form. Whitelisted by 432.

Context

Asset rates are used to verify the maximum spend amount allowed for each Governance track.
Every track has a maximum permitted spend defined in DOT terms, and the asset rates define the conversion of a given asset relative to them.

This batch includes calls to remove the unmapped asset rates and re-add them using the corrected asset IDs while preserving the same rate values.

Each rate is represented as a Fixed-Point 128-bit unsigned integer, using a divisor of 10¹⁸.
Internally, the type is a wrapper around u128 and decodes accordingly.

Concrete Value

The constant value of 1,000,000,000,000,000,000,000 in the call is the same as before and calculated as:

• DOT denomination: 1e10
• USDC (asset 1337) and USDT (asset 1984) denomination: 1e6
• Precision of the FixedU128 type that stores the value: 1e18

To calculate the ration for 10$ per DOT:
USDC per DOT = 1e10/((1e6*1,000,000,000,000,000,000,000)/1e18) = 10

Treasury Guardian – OpenGov Accountability Layer

The Problem
The Polkadot Treasury suffers from weak accountability, leading to wasteful spending:

• Proposals: Teams often receive large upfront payments (tens or hundreds of thousands of dollars) but frequently under-deliver, abandon projects, or disappear entirely.
• Bounties: Curators are given substantial lump-sum payments upfront, yet many deliver poor results at high cost, with minimal transparency or reporting back to token holders.

Result: Without real accountability, treasury funds are spent inefficiently.

The Fix That Already Exists Today
Scheduled payouts. Instead of one big transfer, we can approve many small future payouts in a single referendum and tie them to real milestones or monthly reporting.

The Missing Piece
Someone actually has to watch and act when a milestone is missed.
Right now → almost nobody does (no-one is incentivised to).

Treasury Guardian = Decentralised Enforcement

• One dashboard showing every upcoming scheduled payout + linked deliverables.
• Anyone spots a missed milestone → a few clicks to propose delay/cancel payout referendum on the Treasurer track.
• Proposer must put up (or convince someone to put up) a 1000 DOT decision deposit – fully slashable.
• If OpenGov approves the cancellation/delay, the guardian gets a small capped reward taken from the saved payout (skin in the game + aligned incentives).

Key Facts

• No special permissions – anyone with a wallet can be a Treasury Guardian.
• No new powers – final decision is still 100% OpenGov conviction voting.
• Delivering teams feel zero extra friction. Late teams get their payouts delayed to ensure delivery before payout. Abandoned projects get payouts canceled to protect the Treasury.

Treasury Guardian vs OG Tracker

• OG Tracker = passive monitoring (expensive and no teeth).
• Treasury Guardian = active enforcement (anyone can trigger real consequences).

The 600k+ funding OG Tracker has received in their last proposal pays for their services for a few more months only. OG Tracker has been the “accountability layer” till now. Has it worked?

This is the new era of OpenGov
Monthly scheduled payouts for bounties + milestone-based payouts for normal proposals are already possible. Treasury Guardian turns that technical possibility into actual accountability by incentivising more eyes on milestone delivery.

Recent Changes Based on Community Feedback

• Removed the last milestone → lower total ask. We will deliver a solid product with engagement first before reassessing future viability.
• The requested reward caps for Treasury Guardians have been implemented and are live.

• AssetHub Migration has been completed and is live.

Something that hasn’t changed

• The proposal remains fully cancellable at every stage if value isn’t delivered.

Milestone Delivery Deadlines:

Milestone 1 (MVP): Dec 20 2025 -> Scheduled Payout: Feb 8 2026

Christmas Holiday (Dec 20 2025 -> Jan 3 2026)

Milestone 2 (Refinement): Jan 31 2026 -> Scheduled Payout: March 22 2026

Milestone 3 (Growth): Feb 28 2026 -> Scheduled Payout: Apr 19 2026

We are passionate about leading the charge to de-risk the Treasury, enhance its efficiency, and better align the interests of token holders and proposers to drive a new era of accountability. We eagerly look forward to collaborating with the Polkadot community and new + existing ecosystem teams to achieve these goals.

Read our full proposal here.

Point of contact: treasuryefficiency@gmail.com

Vote YES if you want real accountability in OpenGov.

This is a ReferendumV2 post. It can only be edited by the proposer of the post 5G3j4TWmVjmHAyGJ7rQ5ziymshXv2XBcHyfQR4NSS1bDM23B.