<img src="https://bafybeidq4oje33op4nh76je66npvnvz3lellauywj327lhhrdphwdfmw4m.ipfs.web3approved.com/?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJjaWQiOiJiYWZ5YmVpZHE0b2plMzNvcDRuaDc2amU2Nm5wdm52ejNsZWxsYXV5d2ozMjdsaGhyZHBod2RmbXc0bSIsInByb2plY3RfdXVpZCI6IjRiZDI1NDZiLTY3MTQtNDU3Ni1hZTAxLWY4NmUxZWE5NjVlNiIsImlhdCI6MTczMDM5Mzg2Miwic3ViIjoiSVBGUy10b2tlbiJ9.d2lnDS8goceout52mI-0dz0j-OG7xLZpnJdoZvJStg4" alt="" width="800" height="536" />
Project Details
⧓ Apillon, the leading Web3 development platform for Polkadot &mdash; <a href="https://www.apillon.io">Apillon.io</a>
Proposer: Matjaž Sobočan, CEO
Execution estimate: 8 months 
Requested allocation: 809,600 USDT 
Proposal Overview
<ul>
<li>POP Network: Pre-made, verified generic ink! contracts</li>
<li>KWIL: Decentralized database infrastructure</li>
<li>CESS: Streamlined storage process for sensitive data</li>
<li>Prosopo: Web3 Captcha</li>
<li>Improvements of existing features:
<ul>
<li>Embedded wallets UX and customizability</li>
<li>IPNS enhanced, transformed into a standalone service</li>
<li>NFT Wizard for mobile and general revamp of the feature</li>
<li>Unique Network&rsquo;s expansion of the token-creation functionalities</li>
<li>Vercel Templates for increased visibility of Polkadot&rsquo;s projects</li>
<li>Security Audit request after Milestone 2</li>
</ul>
</li>
</ul>
<a href="https://bafybeiaeeikiyb2fvj64haobws4k5l37qhtdbzwc6ofnldrv74xyjlyheu.ipfs.web3approved.com/?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJjaWQiOiJiYWZ5YmVpYWVlaWtpeWIyZnZqNjRoYW9id3M0azVsMzdxaHRkYnp3YzZvZm5sZHJ2NzR4eWpseWhldSIsInByb2plY3RfdXVpZCI6IjRiZDI1NDZiLTY3MTQtNDU3Ni1hZTAxLWY4NmUxZWE5NjVlNiIsImlhdCI6MTczMDM5Mjg3OSwic3ViIjoiSVBGUy10b2tlbiJ9.5SGDzt8z6K2EGcS7dHbTGe8TpQRzjR9bwb7HkabYFso">⧓ The full Apillon Milestone 3 Proposal</a>
Revised Apillon Proposal for Polkadot Treasury - Milestone 3
Following extensive community feedback on our previous discussion post (<a href="../post/2520">#2520</a>), which highlighted Apillon&rsquo;s enterprise ambitions, we&rsquo;re introducing an updated approach for Milestone 3 of the Apillon platform. Conversations with ecosystem stakeholders (Permanence DAO, ChaosDao, Opengov.watch, and others) provided critical insights that shaped this revision. While our Salesforce Web3 Cloud integration remains an exciting future possibility, it became clear that this element took focus away from the foundational goals of Milestone 3. To address this, we have removed Salesforce-related components and dependencies from this proposal, refocusing on the core infrastructure and service improvements that Apillon is uniquely positioned to deliver.
Before jumping to M3, check out our Embedded Wallet Ad: <iframe src="https://www.youtube.com/embed/ktvYBSN5IDM" width="560" height="314" allowfullscreen="allowfullscreen"></iframe>
Our Core Objectives for Milestone 3
Milestone 3 focuses on two fundamental achievement areas:
<ul>
<li>New Service Integrations</li>
<li>Enhancements to Existing Services</li>
</ul>
This structured approach centers on supporting developers and enterprises with robust, user-friendly tools, which reduce Web3 adoption barriers and enable no-code/low-code solutions. Through new integrations and streamlined, enterprise-oriented templates, we are committed to expanding the accessibility and utility of Polkadot parachains and Apillon&rsquo;s capabilities.
Why Vote Aye? 
With this refined proposal, we believe Apillon is set to drive meaningful growth and innovation within the Polkadot ecosystem:
⧓ Strengthening Core Integrations &ndash; Our expanded partnerships with Kwil, CESS, and POP provide developers access to decentralized databases, encrypted storage, and INK! smart contracts, enhancing versatility and usability for the entire community.
⧓ Enterprise-ready Templates &ndash; Refining Simplets into targeted, use-case-focused products to streamline deployment and customization for large-scale clients.
⧓ Enhanced User Experience &ndash; With continuous UX and Developer Experience improvements, Milestone 3 addresses user feedback to deliver a seamless experience.
⧓ Supporting Open-source Growth &ndash; Ready-made open-source tools, such as GitHub auto-pull integrations and Vercel templates, incentivize community adoption, making Web3 more accessible.
⧓ Commitment to Security &ndash; Ongoing third-party audits strengthen Apillon&rsquo;s security, reinforcing developer and enterprise trust within the Polkadot ecosystem.
Moving Forward 
This proposal aims to provide a clear path to achieving the ambitious goals of Milestone 3, with a transparent focus on building strong foundations within the Polkadot ecosystem. By concentrating on core improvements and integrations, Apillon is positioned to drive sustainable growth and facilitate future enterprise partnerships. We will bring the Salesforce integration forward in a separate proposal, ensuring that it undergoes community review independently and doesn&rsquo;t jeopardize the primary goals of Milestone 3.
We want to make the reasoning behind the new Apillon&rsquo;s Polkadot Treasury Proposal as comprehensive and transparent as possible. We will do our best to provide additional explanation and information you might require.
Previous treasury reports: <a href="https://blog.apillon.io/apillon-milestone-1-proposal-recap-done-and-done-%EF%B8%8F-afe9ac238ac4">Apillon Milestone 1 Proposal Recap</a>, <a href="https://docs.google.com/document/d/1crcB6QDziJyqe15hBcoUN4h44nJFFuxgt2sjrDqmZM0/edit#heading=h.xw709a247j9n">Apillon Milestone 2: Deliverables and Outcomes</a>

Propose and approve a spend of treasury funds.

## Dispatch Origin

Must be [`Config::SpendOrigin`] with the `Success` value being at least
`amount` of `asset_kind` in the native asset. The amount of `asset_kind` is converted
for assertion using the [`Config::BalanceConverter`].

## Details

Create an approved spend for transferring a specific `amount` of `asset_kind` to a
designated beneficiary. The spend must be claimed using the `payout` dispatchable within
the [`Config::PayoutPeriod`].

### Parameters
- `asset_kind`: An indicator of the specific asset class to be spent.
- `amount`: The amount to be transferred from the treasury to the `beneficiary`.
- `beneficiary`: The beneficiary of the spend.
- `valid_from`: The block number from which the spend can be claimed. It can refer to
  the past if the resulting spend has not yet expired according to the
  [`Config::PayoutPeriod`]. If `None`, the spend can be claimed immediately after
  approval.

## Events

Emits [`Event::AssetSpendApproved`] if successful.

- Problem Statement: Updating the Apillon platform for Milestone 3 to focus on core infrastructure and service improvements, removing distractions from enterprise ambitions.
- Significance: Enhancing Polkadot's ecosystem by providing decentralized databases, encrypted storage, smart contracts, and user-friendly tools to reduce adoption barriers.
- Proposed Solution: Refining existing services, introducing new integrations, and enhancing user experience to drive growth and innovation within the Polkadot ecosystem.
- Expected Outcomes: Strengthened core integrations, enterprise-ready templates, improved user experience, support for open-source growth, and a commitment to security through ongoing audits.

#1266 Apillon Milestone 3 Proposal: Core Integrations and Service Enhancements for Polkadot Ecosystem Growth

No Active Proposals