Hello,

You've done a great job. I'd like to share my questions:

- Do you have any financial statements showing how the funds were used in the previous proposal?

- Could you please detail the specific infrastructure costs you're mentioning?

Thanks


The report submitted by the previous administration does not contain any expense invoices or receipts that could allow verification of the expenses incurred. This is a very important element to improve transparency regarding the use of funds.

PolkaWorld votes AYE 

Based on their activities, website, and Twitter presence, we believe Polkadot Africa has successfully laid the groundwork for Polkadot’s presence on the continent. Given that the budget is reasonable, we support this initiative’s continued development. In summary, we believe this proposal deserves support for the following reasons:

1.Clear Strategic Relevance to the Ecosystem

Africa is one of the most promising regions for Web3 growth globally, yet Polkadot’s developer reach, local engagement, and brand awareness remain limited in the area. This proposal aims to bridge that gap through consistent IRL events, education programs, and localized BD efforts—laying the foundation for a developer network and narrative system tailored to Africa.

2.Proven Track Record and Reliable Execution

The team has already organized over 45 in-person events, attracting more than 3,000 participants, and successfully onboarded local developers to the Polkadot Blockchain Academy (PBA) and global hackathons. Their work spans education, SDK guidance, Runtime contributions, and community building—demonstrating solid delivery capability.

3.Clear Budget Structure and Role Distribution

The proposed budget is well-structured, with detailed breakdowns of roles, compensation, working hours, travel, and infrastructure costs—meeting expectations for transparency and good governance. The team composition covers key areas such as DevRel, regional ops, content, design, and developer support, showing strong potential for sustained progress.

4.Developer-Centric & Sustainable Strategy

The proposal emphasizes a structured journey of developer activation → retention → engagement, supported by workshops, bootcamps, and mentorship programs. This reflects a focus on building a long-term, stable local tech community, rather than relying on one-off events—ensuring ecosystem sustainability.

5.Establishing a Regional Node to Support Global Collaboration

The team actively collaborates with W3F, Collectives, DAO bounties, and other ecosystem initiatives, while also planning to expand to seven countries. This effort will create a multi-lingual, cross-regional foundation for collaboration within the Polkadot community—supporting future tech pilots, product feedback, and governance participation.

You can read more [here](https://southern-manicure-6ee.notion.site/1672-Treasury-Proposal-Polkadot-Africa-Builder-and-community-growth-West-and-East-Africa-regions--233a3c644fba8076be0ceee0b3f361ca?source=copy_link).

Dear Proposer,

Thank you for your proposal. Our **first** vote on this proposal is **NAY**.

The **Medium Spender** track requires **50% quorum (at least 5 aye votes) and simple majority of non-abstain votes** according to our [voting policy v0.2](https://docs.permanence.io/voting_policy/voting_policy_v0.2.html), and any referendum in which the **majority of members vote abstain receives an abstain vote**. This proposal has received **zero aye and three nay** votes from **ten available members**, with **four members abstaining**. Below is a summary of our members' comments:

> The referendum was met with criticism, with several comments citing the proposal’s broad scope and the full-year funding approach as problematic. Reviewers noted the impressive community engagement and event numbers but deemed the large sums requested insufficiently paired with clearly defined short-term milestones. They recommended dividing the proposal into shorter intervals with quarterly benchmarks and clear key performance indicators to track progress, instead of a continuous annual commitment. Concerns were also raised about expenses related to mentors, travel, and infrastructure, and about verifying the accuracy of the financial figures, which ultimately led to an overall negative outcome.

The full discussion can be found in our [internal voting](https://voting.opensquare.io/space/permanence/proposal/QmauwiHEmFH6e8Q2pTZzwf7uRVcdKce8CkRpnfH5Bjjr8L).

Please feel free to contact us through the links below for further discussion.

Kind regards, Permanence DAO Decentralized Voices Cohort IV Delegate 📅 [Book Office Hours](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://polkadot.subsquare.io/user/15ubZj6T7NUYyQw6j4XBkEMJ2vew5w9kqKEcN1QG7Z1weKDV/votes)

Dear Proposer,

Thank you for your proposal. Our **second** vote on this proposal is **ABSTAIN**.

The **Medium Spender** track requires **50% quorum (at least 5 aye votes) and simple majority of non-abstain votes** according to our [voting policy v0.2](https://docs.permanence.io/voting_policy/voting_policy_v0.2.html), and any referendum in which the **majority of members vote abstain receives an abstain vote**. This proposal has received **zero aye and three nay** votes from **ten available members**, with **six members abstaining**. Below is a summary of our members' comments:

> Members acknowledged the initiative’s visible progress and its contribution to growing the community and builder engagement in Africa but raised concerns regarding the proposal’s broad scope and one-year funding timeframe. Comments reflected apprehension over the large funding ask and the difficulty in verifying the reported achievements, with several suggesting that staged funding via quarterly or half-yearly submissions would allow for more effective performance monitoring through clear KPIs. Although there was some support for the initiative’s continued development, caution was expressed about potentially excessive expenses for mentors, travel, and infrastructure maintenance, resulting in a tendency to lean away from full approval.

The full discussion can be found in our [internal voting](https://voting.opensquare.io/space/permanence/proposal/QmauwiHEmFH6e8Q2pTZzwf7uRVcdKce8CkRpnfH5Bjjr8L).

Please feel free to contact us through the links below for further discussion.

Kind regards, Permanence DAO Decentralized Voices Cohort IV Delegate 📅 [Book Office Hours](https://cal.com/permanencedao/office-hours) 💬 [Public Telegram](https://t.me/permanencedao) 🌐️ [Web](https://permanence.io) 🐦 [Twitter](https://twitter.com/permanencedao) 🗳️ [Delegate](https://polkadot.subsquare.io/user/15ubZj6T7NUYyQw6j4XBkEMJ2vew5w9kqKEcN1QG7Z1weKDV/votes)

TruthDAO votes AYE

In the current sluggish market, continuing to build the community and market presence is a top priority.

From their events, website, and Twitter activity, I believe Polkadot Africa has already laid an initial foundation for Polkadot on the continent. With a reasonable budget, it deserves support to keep growing!

This proposal’s budget structure is clear and well-balanced — detailing roles, salaries, work hours, as well as travel and infrastructure costs — aligning with expectations for transparency and good governance.

See more feedback [here](https://voting.opensquare.io/space/truthdao/proposal/QmPZqnK2KWeL8HhepEJXns5xnedsKFLmrfqJMphgmaMm97).

📖[Truth DAO Governance Statement](https://southern-manicure-6ee.notion.site/Truth-DAO-Manifesto-0-0-1-1e9a3c644fba807fb88ef3eb5adc711b?pvs=4)

💭 Contact: open@truthdao.cn, [Telegram](https://t.me/truthdao_public)

🗳️ [Delegate](https://polkadot.subsquare.io/user/13dVYCGL27HhTWaAby3gAVPQkSqbGAyHQfdeUxsttDZi6afh/posted/referenda)

JAM DAO voted NAY on this Proposal

The proposal was met with some skepticism from JAM DAO members. Key concerns included:

Lack of justification for budget allocation, particularly $28.8K for an unnamed DevRel working part-time over a year. Some members felt this deviated from the more effective practice of requesting event-specific funds via the Events Bounty track.

Doubts were raised about inflated engagement claims and whether tangible outcomes justify the $350K ask, with a specific critique of $48K reserved for infrastructure.

A member called for stronger track records and measurable impact from previous hackathons organized by the proposers before committing additional funds.

Despite support in principle for grassroots community efforts, the DAO ultimately rejected the proposal due to budget opacity and unclear ROI.

We have reflected on the feedback on this current proposal, and we will put out an updated proposal with the following parts updated:

* **Shortened duration:** We will be requesting 6 months of activities instead.
* **Success metrics/KPIs:** Some members wanted to see an overview of KPIs. This will now be available in the milestones section.
* **Updated compensation:** Some members were concerned about compensation, and others are concerned about the team size. We will make adjustments accordingly.

**Scope:** Some community members were worried that the scope is too big, and others said it's too small.
The scope will remain intact; however, we will take smaller steps and increase them gradually. These will be reflected in the KPIs.

We are putting out a new proposal soon and have pulled out the pre-image on this one. We request you vote nay on this one.

- Shortened time from original plan to 6 months  
- Added success goals (KPIs) in milestones  
- Changed payment and team size based on feedback  
- Kept same goals but will start small and grow  
- Asking to vote "no" on current plan  
- New plan coming soon

assetKind

amount

beneficiary

validFrom

Rejected

Submitted

DecisionDepositPlaced

DecisionStarted

medium_spender

Based on community feedback, pls vote nay

root

whitelisted_caller

wish_for_change

staking_admin

treasurer

lease_admin

fellowship_admin

general_admin

auction_admin

referendum_canceller

referendum_killer

small_tipper

big_tipper

small_spender

big_spender

Origin able to dispatch a whitelisted call.

Origin for signaling that the network wishes for some change

Origin able to cancel slashes and manage minimum commission.

Origin for spending up to 10,000,000 DOT from the treasury as well as generally administering it.

Origin for managing the composition of the fellowship.

Origin able to spend around 250 DOT from the treasury at once.

Origin able to spend around 1,000 DOT from the treasury at once.

Origin able to spend around 10,000 DOT from the treasury at once.

Origin able to spend around 100,000 DOT from the treasury at once.

Origin able to spend up to 1,000,000 DOT from the treasury at once.