<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Domen Ursic on Medium]]></title>
        <description><![CDATA[Stories by Domen Ursic on Medium]]></description>
        <link>https://medium.com/@ursicdomen?source=rss-ef1d28b5a6d6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*JtxUIa7Gruj7ghv5xJ_7LQ.jpeg</url>
            <title>Stories by Domen Ursic on Medium</title>
            <link>https://medium.com/@ursicdomen?source=rss-ef1d28b5a6d6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 19:38:14 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ursicdomen/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Beaten, but not broken. Now off to new highs!]]></title>
            <link>https://medium.com/apillon/beaten-but-not-broken-now-off-to-new-highs-995d0117a232?source=rss-ef1d28b5a6d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/995d0117a232</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[polkadot]]></category>
            <category><![CDATA[kusama]]></category>
            <category><![CDATA[polkadot-network]]></category>
            <category><![CDATA[apillon-news]]></category>
            <dc:creator><![CDATA[Domen Ursic]]></dc:creator>
            <pubDate>Thu, 17 Aug 2023 07:24:07 GMT</pubDate>
            <atom:updated>2023-08-17T07:24:07.561Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sUSKS_00Z4BjcdTfK21Kxw.png" /></figure><h4><em>The key takeaway is that the community agrees on the necessity for a tool that makes Web3 development user-friendly, efficient, and cost-effective. We will go back to the drawing board and make the proposal acceptable for the ecosystem.</em></h4><p><a href="https://polkadot.polkassembly.io/referenda/81">The Proposal #81</a> related saga was one of the most intense learning periods, not only for our team at Apillon but also for the entire Polkadot ecosystem. F*ck it, we tried and we failed. But we gained valuable insights. The proposal sparked numerous debates about Apillon and Web3 development, as well as about the future of our ecosystem and its governance. This holds significant importance for both the Polkadot ecosystem and Apillon as one of its pivotal parts.</p><p>What’s even more noteworthy is that the proposal process highlighted a widespread consensus regarding the necessity of a tool like Apillon if we are to achieve a user-friendly, efficient, and cost-effective Web3 development process. This makes us even more determined to act on what we have learned, rethink the issues that arose during the proposal process, and come back even stronger.</p><p>The number of positive messages in the days following the rejection of the Bounty to back Apillon was unbelievable. It truly touched us, and I would like to thank everyone who reached out with positive words to any of our team members. We appreciate it. We also extend our appreciation to everyone who participated in the process — from DAOs, ecosystem members, and whales to prominent stakeholders within the ecosystem. Our proposal received 10 times the turnout of any preceding proposal, serving as validation of a well-executed deliberation period. Thanks. Your comments — positive or negative — will have an effect on making Apillon better.</p><p>Regrettably, the majority of comments came within the final 72 hours, rendering it impossible for us to make the necessary adjustments to the proposal. But these comments were heard.</p><p><strong>We detect the following key issues that arose:</strong></p><p>⧓ Too much was asked for at once (w/ not enough traction to show for it).</p><p>⧓ Confusion about whether this should be a Bounty proposal or a Treasury ask.</p><p>⧓ Concerns regarding public funding going to fund a for-profit platform.</p><p>⧓ The inclusion of growth expenses (such as marketing costs, conferences, etc.) in the funding ask was questioned.</p><p>⧓ It was not clear what we would do with the NCTR token in the future.</p><p>We already have most of the answers to these issues ready but would appreciate a few more days to discuss them internally before their public release. <strong>During that time,</strong> <strong>we will highly value feedback from the ecosystem once again.</strong></p><p>To sum up, the time and effort we put into Referendum #81 were not in vain. We see some things much clearer than before, thanks to all the discussions and debates we had since we published the proposal.<strong> We will make sure this will make Apillon better and more in line with the vision, values, and needs of the Polkadot ecosystem.</strong></p><p>Now it’s time to return to the drawing board, refine the Proposal to align with the expectations of the ecosystem, and continue to build what we believe to be an essential tool for future developers.</p><h3>⧓ About Apillon</h3><p>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.</p><p><a href="https://apillon.io/">Website</a> | <a href="https://wiki.apillon.io/">Wiki</a> | <a href="https://github.com/Apillon-web3">GitHub</a> | <a href="https://twitter.com/apillon">Twitter</a> | <a href="https://t.me/Apillon">Telegram</a> | <a href="https://www.linkedin.com/company/apillon/">LinkedIn</a> | <a href="https://www.reddit.com/r/apillon/">Reddit</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=995d0117a232" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apillon/beaten-but-not-broken-now-off-to-new-highs-995d0117a232">Beaten, but not broken. Now off to new highs!</a> was originally published in <a href="https://medium.com/apillon">Apillon</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bullish on the OpenGov referendum #81]]></title>
            <link>https://medium.com/apillon/bullish-on-the-opengov-referendum-81-de510307913f?source=rss-ef1d28b5a6d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/de510307913f</guid>
            <category><![CDATA[polkadot-network]]></category>
            <category><![CDATA[proposal]]></category>
            <category><![CDATA[apillon-thinking-web3]]></category>
            <category><![CDATA[polkadot]]></category>
            <category><![CDATA[web3]]></category>
            <dc:creator><![CDATA[Domen Ursic]]></dc:creator>
            <pubDate>Sat, 05 Aug 2023 14:50:13 GMT</pubDate>
            <atom:updated>2023-08-23T13:18:14.570Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Hcq3h4eqYSoqfI5Wu6NPiA.png" /></figure><h4>We firmly believe that open-sourced platform is precisely what our ecosystem requires to accelerate Web3 adoption. Below I explain why I believe Referendum #81 will pass.</h4><p>A week before the conclusion of Referendum #81 (<a href="https://polkadot.polkassembly.io/referenda/81"><em>Bounty to support Apillon Web3 development platform as a common good infrastructure</em></a>), which aims to transition Apillon to an open-source framework, we remain confident that the proposal will receive approval from the community.</p><p>Based on what we have seen in the proposal process, there is a widespread consensus regarding the necessity of an open-source solution that significantly enhances the Web3 development process through its user-friendliness, efficiency, and cost-effectiveness.</p><h4>First things first</h4><p>First and foremost — a big thanks to all those who already voted in favor (AYE) or actively participated in the extensive and immensely valuable discussion leading up to the referendum.</p><p>A special shout-out goes to some of the best and brightest minds of the Polkadot ecosystem, including Ingo Rübe from KILT Protocol, Marvin Tong from Phala Network, Hoon Kim from Astar and Team STEP, Nate Hamilton from Purestake (the company behind the Moonbeam Network), and the Substrate Builders Program review team for their public endorsements.</p><p>It’s not just the top-notch technology; these exceptional individuals and teams are the reason we remain as optimistic as ever about the future of the Polkadot ecosystem.</p><h4><strong>My two cents on the current state of the Referendum #81</strong></h4><p>Throughout the lead-up to the referendum, we engaged in numerous debates, making a concerted effort to involve the community, actively listen to their feedback, and make adjustments to the proposal where deemed necessary.</p><p>The transition from the <em>Treasury</em> to the <em>Bounty</em> proposal, which empowers the community with control, reflects our responsiveness to the concerns raised and our commitment to taking appropriate action.</p><blockquote>However, as much as we strive to accommodate different perspectives, we understand that it’s impossible to please everyone.</blockquote><p>I believe the majority of NAY votes were influenced solely by the requested amount, with many stating, “There’s too much money involved”, and voting against the proposal.</p><p>Yes. The amount is mind-boggling to some and we understand how it ranges compared to the average treasury proposal. However, as we have consistently explained, the vast majority of these funds will be disbursed based on the achievement of specific milestones. They will be managed by parachain teams, W3F, Parity, and/or ecosystem members from a bounty account.</p><p>I want to reiterate that the funds will only be released if we successfully reach the milestones which are co-defined with the help of the DOT community.</p><figure><img alt="Milestones and payout definitions from the Proposal." src="https://cdn-images-1.medium.com/max/1024/1*FQawMZwCffM40swhBPimCQ.png" /></figure><p>Apart from the USD figure at the top of the proposal, I believe there were only minor concerns expressed by those who truly engaged and deep-dived into the proposal. Although the <strong>vast majority </strong>of the funds will be directed toward paying developers’ wages, a portion will also be allocated to user acquisition and the operational aspects of the project.</p><p>Personally, I strongly believe that projects funded through curated bounty or treasury proposals should not focus only on delivering code and UI but also on actively participating and competing in the user onboarding process, contributing to ecosystem growth, and supporting the evolution of the space. Thus, this funding structure considers everything related to running the project and its growth.</p><h4>The final countdown</h4><p>I think the referendum should and will pass. It <strong>should</strong> pass because the ecosystem has embraced the vision of becoming the leading ecosystem for developers and projects of the future Web — and Apillon has the potential to play a crucial role in making this vision a reality. And it <strong>will</strong> because we worked our asses off to make AYE a reality.</p><p>But even more so, I believe a significant shift is about to happen soon. We were able to get in touch with the person responsible for a whopping 86% of NAY votes. During our conversations, we reiterated why we strongly believe Apillon is a viable common-good infrastructure and proposed an in-depth analysis and review of the product. They (he/she, does it matter?) mentioned that if there is a mutual understanding between everyone involved in the process, the vote could potentially turn. I am a firm believer that it will, given my faith in the value of our platform, the underlying technology of Apillon, and the capabilities of our team.</p><blockquote>Since day one, we have emphasized our genuine belief in the governance process, and I truly think our proposal has the potential to become synonymous with two-way, in-depth communication, mutual respect among all parties involved (excluding a few malevolent individuals), and content-based decision-making.</blockquote><h4><strong>Some final thoughts</strong></h4><p>We understand that a significant amount of trust is needed to support this proposal, but we think we have addressed those concerns through our work so far and I’m happy that just days ago we received another nod from the Substrate Builders Program review team as we delivered what was planned — and some extra features as well — to complete Milestone 2 of the Substrate Builders Program.</p><blockquote>“Apillon team delivers strongly on their vision, making good progress to become the go-to platform for future Web3 developers.”</blockquote><blockquote>— The Substrate Builders Program review team</blockquote><p>We delivered. And we will keep delivering on our promises.</p><h4><strong>But what if …</strong></h4><p>Apillon will thrive with or without treasury funding. As founders, we have invested our own resources in the project, received venture capital funding, and enjoyed community support as well. Through discussions with other founders and leaders in the DOT ecosystem, we have concluded that open-source is the right direction, and we still firmly believe in it.</p><p>However, if necessary, we are prepared to change course and adapt to the circumstances.</p><p>But I think that won’t be necessary.</p><figure><a href="https://polkadot.polkassembly.io/referenda/81"><img alt="" src="https://cdn-images-1.medium.com/max/285/1*Z8_sraly_u5oKhBnh-F2Sg.png" /></a></figure><h3>⧓ About Apillon</h3><p>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.</p><p><a href="https://apillon.io/">Website</a> | <a href="https://wiki.apillon.io/">Wiki</a> | <a href="https://github.com/Apillon-web3">GitHub</a> | <a href="https://twitter.com/apillon">Twitter</a> | <a href="https://t.me/Apillon">Telegram</a> | <a href="https://www.linkedin.com/company/apillon/">LinkedIn</a> | <a href="https://www.reddit.com/r/apillon/">Reddit</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de510307913f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apillon/bullish-on-the-opengov-referendum-81-de510307913f">Bullish on the OpenGov referendum #81</a> was originally published in <a href="https://medium.com/apillon">Apillon</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How ecosystem engagement helped steer the way of the Apillon Proposal]]></title>
            <link>https://medium.com/apillon/how-ecosystem-engagement-helped-steer-the-way-of-the-apillon-proposal-93af9f568fdb?source=rss-ef1d28b5a6d6------2</link>
            <guid isPermaLink="false">https://medium.com/p/93af9f568fdb</guid>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[polkadot-ecosystem]]></category>
            <category><![CDATA[polkadot]]></category>
            <category><![CDATA[apillon-news]]></category>
            <dc:creator><![CDATA[Domen Ursic]]></dc:creator>
            <pubDate>Wed, 12 Jul 2023 11:39:45 GMT</pubDate>
            <atom:updated>2023-07-12T11:43:05.356Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9s_U24IQPq0WfYfNmi1Mpg@2x.jpeg" /></figure><h4><em>We made a genuine effort to engage the Polkadot community in our proposal. We had open discussions, listened to the feedback, and made amendments to the proposal accordingly.</em></h4><blockquote>From Polkassembly and Polkadot Forum debates, in-person discussions, conference talks, and online presentations, to thousands of lines of discussion written in different ecosystem groups, we made a sincere effort to engage the community when drafting our proposal. The shift from Treasury to Bounty proposal, which grants more control to the community, demonstrates that we have taken into account the concerns raised and have taken appropriate action.</blockquote><p>A mere week has passed since the Parachain Summit and Polkadot Decoded events in Copenhagen, where we had the opportunity to discuss the future of our Web3 development platform and, of course, <a href="https://ipfs.apillon.io/ipfs/QmVNKr3LxZ8yEhPBk5scgiVVezKK6YwRsZdyjxSqYmNJSb">our proposal</a> with most of Polkadot’s ecosystem.</p><p>Not only did we receive an overwhelming amount of positive feedback regarding the content of our proposal, with influential thought leaders within the ecosystem such as <a href="https://phala.network/">Phala Networks</a>’ <a href="https://sg.linkedin.com/in/marvintong/en">Marvin Tong</a>, <a href="https://astar.network/">Astars</a>’ <a href="https://de.linkedin.com/in/hoonsubin">Hoon Kim</a>, <a href="https://www.linkedin.com/in/nathanieldhamilton">Nate Hamilton</a> of <a href="https://www.purestake.com/">Purestake</a> (the company behind the <a href="https://moonbeam.network/">Moonbeam Network</a>), and the <a href="https://wiki.polkadot.network/docs/builders-program%C5%BE">Substrate Builders Program</a> review team offering their endorsements through quotes that can be found in the proposal, but our inclusive approach to crafting, rewriting and re-designing resonated well with stakeholders.</p><p>By adopting the best practices from various projects outside the Web3 ecosystem (especially stakeholder consultation and engagement processes), we actively made efforts to engage as many members of the ecosystem as possible. This led to over 50 productive in-person meetings with our peers in the past 3 months alone. And that was only the tip of the iceberg.</p><h4><strong>Engage. Discuss. Co-Create.</strong></h4><p>Being strong believers in co-ownership of such a crucial proposal for the ecosystem, our approach involved <strong>engaging key stakeholders at the earliest stage possible, before even drafting the first version of the document, with the goal of gathering feedback and enhancing the quality of our proposal</strong>. We then proceeded to discuss it with the broader ecosystem, actively seeking feedback and suggestions for improvements from Apillon’s community. Last but not least, we acted on raised concerns, giving power to the community.</p><p>It took us 3 months, approximately 10 live events (from ETH Denver to ETH Belgrade, to other conferences, meetups, and events in Prague, Bled, Zagreb, and Ljubljana), numerous calls, a few presentations, a couple of outside reviews and over 50 in-person meetings to get the proposal to the point that <strong>we were confident enough to push the document to Polkassembly and Polkadot Forum</strong> to start a month-long public discussion, at the end of which we made changes to the proposal itself as well.</p><h4><strong>Apillon’s proposal in a nutshell</strong></h4><blockquote>Apillon, a Web3 development platform for Polkadot, is proposed as a common good infrastructure solution for the Polkadot network. At the current stage, it provides the functionality of dashboard-based deployment of Web3 services and API connectivity to Polkadot parachains, radically transforming the Web3 development process with ease of use, speed, and low cost. With Treasury funding and community support, the Apillon platform would transition to an open-source product with permanent freemium access, governed by the community, and thus become a common good project, further spurring Web3 adoption, Polkadot ecosystem growth, and DOT utility. Through DOT-based open governance by the Apillon community, the platform would undergo future upgrades, including integrations of voted parachain and other services, to best respond to users’ needs and deliver user-oriented opportunities for Web3 adoption.</blockquote><h4><strong>The road to the proposal: first stop</strong></h4><p>It all began at this year’s <a href="https://blog.apillon.io/whos-making-waves-and-rocking-the-stages-of-ethdenver-it-s-apillon-15e3b8f471ea?source=---------6-----------------------">ETH Denver</a> in March, where we had the opportunity to participate in the Polkadot ecosystem booth as one of the 16 invited projects. During the event, we received feedback from various individuals within the ecosystem, acknowledging <strong>Apillon as the missing link for the widespread adoption of Polkadot</strong>.</p><p><a href="https://blog.apillon.io/whos-making-waves-and-rocking-the-stages-of-ethdenver-it-s-apillon-15e3b8f471ea">Who’s making waves and rocking the stages of ETHDenver? It’s Apillon!</a></p><p>They emphasized that open-sourcing the platform would be the most beneficial direction for the entire ecosystem, enabling faster onboarding of developers and aligning Apillon with Polkadot’s vision. And it made us think.</p><p>Upon returning to our HQ in Ljubljana, we wasted no time and immediately started working on the first draft of our proposal. Right from the outset, we made a <strong>deliberate decision to include a wide range of stakeholders</strong> — a path that is longer and more challenging but at the same time ensures greater transparency and inclusion of the community, thus aligning perfectly with our proposal’s objective of becoming a common good.</p><p>We began by presenting the idea of the proposal to our peers from the parachain teams, and having received positive feedback was encouraging enough to proceed. Subsequently, we had the opportunity to present the draft version of the proposal to <strong>Parity</strong> employees at the <strong><em>Ecosystem 101</em></strong> hosted by Alex Bird aka Birdo.</p><p>As part of the <strong>Substrate Builders Program</strong> (we have successfully completed Milestone 1, currently undergoing the review process for Milestone 2) we attended the <em>SBP weekly Open Hours</em> to pitch our idea of the proposal. Our CPO, Nino, presented a compelling demo, while I had the opportunity to discuss the proposal with the SBP ecosystem teams.</p><p>We also went to <strong>PolkadotPrague</strong> and <strong>ETHBelgrade</strong> to engage in in-person meetings with our peers. To our delight, the feedback exceeded our expectations.</p><h4><strong>And so, we moved forward</strong></h4><p>On <strong>June 19th</strong> we started the discussion on both <strong>Polkassembly</strong> and <strong>Polkadot Forum</strong>. You can find both discussions still open <a href="https://polkadot.polkassembly.io/post/1823">HERE</a> and <a href="https://forum.polkadot.network/t/apillon-web3-development-platform-as-a-common-good-infrastructure-polkadot-treasury-proposal/3145">HERE</a>.</p><p>We were particularly thrilled to receive positive feedback from the ecosystem teams we collaborate with closely, such as <a href="https://www.kilt.io/">KILT Protocol</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/0*U28r6iwPJFwGrtjj" /></figure><p>The official poll at Polkassembly has turned out in favor of the proposal as well, with almost 80 % in favor (voting AYE) for Apillon’s vision of becoming a common good infrastructure.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/904/0*SHCl4lN6vpHhqurD" /></figure><p>As part of our community engagement efforts, we also participated in the <strong>AAG</strong> episode at the <strong>Kusamarian</strong>, where our CEO, <a href="https://www.linkedin.com/in/matjazsobocan/">Matjaž</a>, discussed the benefits of our proposal with the voice of the ecosystem. You can watch the video and discover <strong>why the Web3 sphere needs an open-source common good development platform</strong> in the video below.</p><p><a href="https://www.youtube.com/live/BIsaNokzJX0?feature=share">AAG 🥚 #42 - REPLAY! - The Great DOT Rush of &#39;23 ⛏️</a></p><p>Last, but not least, we were invited by Polkadotters to share the topic of our proposal in our ecosystem.</p><h3>Polkadotters | Validators and media house on Twitter: &quot;https://t.co/QubTRvDn7V / Twitter&quot;</h3><p>https://t.co/QubTRvDn7V</p><h4><strong>The ecosystem coming together — Presenting the proposal at the Parachain Summit &amp; Polkadot Decoded, Copenhagen</strong></h4><p>We participated in the Parachain Summit, an event focused on shaping the future of our ecosystem a few days before Polkadot Decoded, to discuss Polkadot’s brand, business development, and various initiatives, including our own proposal. But this was just the beginning of an amazing week in Copenhagen.</p><p>As part of our ongoing community-building endeavors, we collaborated with Astar Network, Crust Network, and Phala Network to organize a Polkadot Decoded Opening night side-event, an exciting, also over-booked, social gathering at H15 Food &amp; Culture. Apillon’s CPO, <a href="https://www.linkedin.com/in/nino-kutnjak/">Nino</a>, took the stage to present our product, our ongoing collaborations with the ecosystem teams, our new <a href="https://blog.apillon.io/the-web3approved-initiative-offers-free-decentralized-hosting-for-100-years-c350a06f33b8">Web3Approved initiative</a> (an initiative aimed at those who want to practice what they preach and host their websites in a decentralized manner), and of course, the proposal.</p><p>The feedback we received was incredibly positive, and we found ourselves engaged in captivating conversations with familiar faces from the Web3 community, as well as forging new friendships with some of the new and upcoming teams from the ecosystem.</p><p>We also addressed our proposal on stage at the Polkadot Decoded, where Apillon’s CEO Matjaž took the audience on a journey of the Apillon platform in his talk titled “Build Web3 like it’s 1993”.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uZO75k7fAy6HLrsFcVuu9A.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Qd0nFYvAGGLl-52o_2UrPg.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SlhFhjO9kAyrdmVX2rolog.jpeg" /></figure><p>Finishing the Decoded in style, Matjaž joined Ben Greenberg, DevRel at Parity, to discuss Apillon for the Parity’s DevRel stream.</p><p><a href="https://www.youtube.com/live/eAOoyb1wxRU?feature=share&amp;t=7110">Decoded Day 1</a></p><h4><strong>Concerns were raised as well — we acted on it</strong></h4><p>All comments were not positive, but all of them were constructive and showed a lot of premeditated thought. So we took it upon ourselves to proactively engage in in-person discussions with everyone who provided useful feedback on any item in the proposal. The beauty of the process was that we had the opportunity to make the proposal better by listening and acting on community comments, whether in different ecosystem cooperatives, such as <strong>ChaosDAO</strong> and <strong>Polka Häus</strong> (we really appreciate all the hard times you gave us, because this made us rethink the proposal and make fundamental changes to it), or through any other channel of discussion where we have been actively engaged with the Polkadot community.</p><h4>What will be changed in the proposal before we move forward with it?</h4><ul><li>Proposal format pivots from Treasury to Bounty to align with OpenGov funding schemes and give <strong>more control to the governance and treasury community</strong> as a direct answer to raised concerns in the public discussion phase.</li><li>The total funding amount changes slightly <strong>to compensate for the DOT price volatility</strong> and treasury track placement.</li></ul><p>Once we have finished making changes to the proposal (which we expect to be tomorrow morning CEST), we will publish a comment with all the changes on Polkassembly and Polkadot Forum. We will also present the changes in a blog post. After giving everyone a few days to read through the changes and provide feedback to our team, we will proceed to the voting phase (early next week).</p><p>Let me just say that it has been an amazing journey. I would like to thank everyone who participated in the ongoing discussion, whether by giving us useful feedback and constructive critics, taking the time to jump on a call with us, or sharing our proposal with your communities. Your contributions made the proposal better, and we truly appreciate it.</p><p>If you feel you want to address any kind of question and /or doubt regarding Apillon’s proposal, you can reach out to <a href="https://twitter.com/ursicdomen">me on Twitter</a>.</p><p>Stay tuned.</p><h3>⧓ About Apillon</h3><p>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.</p><p><a href="https://apillon.io/">Website</a> | <a href="https://wiki.apillon.io/">Wiki</a> | <a href="https://github.com/Apillon-web3">GitHub</a> | <a href="https://twitter.com/apillon">Twitter</a> | <a href="https://discord.gg/apillon">Discord</a>| <a href="https://www.linkedin.com/company/apillon/">LinkedIn</a> | <a href="https://www.reddit.com/r/apillon/">Reddit</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=93af9f568fdb" width="1" height="1" alt=""><hr><p><a href="https://medium.com/apillon/how-ecosystem-engagement-helped-steer-the-way-of-the-apillon-proposal-93af9f568fdb">How ecosystem engagement helped steer the way of the Apillon Proposal</a> was originally published in <a href="https://medium.com/apillon">Apillon</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>