Apillon Proposal changing course: From Treasury to Bounty

The Polkadot community raised a few legitimate concerns regarding the Proposal; hence some structural changes were made to the funding…

Apillon Proposal changing course: From Treasury to Bounty

The Polkadot community raised a few legitimate concerns regarding the Proposal; hence some structural changes were made to the funding scheme.


As a strong advocate for community building and Polkadot ecosystem collaboration, the Apillon team decided to follow the path aligned with the backers’ preference — a pivot onto the Bounty road to enhance community overview, governance power, and co-ownership.

Throughout proposal fine-tuning, the team engaged in countless dialogues at live events, online deliberations, and debates with ecosystem alliances (ChaosDAO, Polka Häus, just to name a few), as well as preliminary discussions on Polkassembly and Polkadot Forum — all dissecting Apillon’s transition to an open-source infrastructure on Polkadot and its impact on the space.

Thanks to community engagement and invaluable feedback, we kept our finger on the pulse and got a clear sense of the general sentiment. We sat down to systematically address second thoughts and pain points and, ultimately, adjusted the Proposal to respect all gathered remarks.

👉 The change: Apillon Proposal moves from Treasury to Bounty section.

Bounty funding to reward past work

Changing course in the Polkadot funding schemes brings the following:

  • Alignment with recently launched OpenGov funding schemes: In the initial version of the Proposal, Apillon would have been placed on the Big Spender track in the Treasury scheme. With respect to OpenGov procedures, the requested amount has now changed from USD to DOT and has been properly adjusted. This slightly changed the total funding amount to compensate for the DOT price volatility and treasury section placement.
  • More control to the governance and treasury community: Directly addressing the concerns raised in the public discussion phase, the Bounty funding tranches are considered rewards for completing preset milestones. The individual Child Bounties are managed by up to five curators who would oversee the ongoing procedures, review milestones and hold Apillon accountable. In other words, Apillon would not own nor have control over the Bounty wallet account but would only get rewarded with Bounty funds after the completion of set goals.

Every other aspect of the Proposal remains as is.


It’s a team’s work. Ecosystem growth even more so.

We are truly grateful for all the feedback garnered in the past weeks — it has been both extensive and beneficial.

On the way to true decentralization, the Web3 communities have established pathways to communicate their needs and created incentives to secure them. It is only right for ecosystem catalysts to pay attention, respect what they have to say and adjust accordingly.

How ecosystem engagement helped steer the way of the Apillon Proposal
A mere week has passed since the Parachain Summit and Polkadot Decoded events in Copenhagen, where we had the…

The discussion remains open on Polkassembly and Polkadot Forum until early next week, and we invite everyone to join in and share their views on the remodel of our Proposal. Every feedback counts.


⧓ About Apillon

The Apillon platform serves as a unified gateway to the Web3 services provided by linked Polkadot parachains. Following the multi-chain vision, Apillon powers the transition of developers to Web3, simplifying its adoption in the real economy, and expanding its versatility as the ecosystem grows. With Apillon, Web3 services are within reach for every developer, regardless of their background and experience with blockchain technology.

Website | Wiki | GitHub | Twitter | Telegram | LinkedIn | Reddit