<h1 id="treasuryproposalretroactivefundingfordotmemoproofofattendanceprotocolonpolkadot">Treasury Proposal: Retroactive Funding for Dotmemo - Proof of Attendance Protocol on Polkadot</h1>
<p><a href="https://docs.google.com/document/d/1UY8veod8yXqKqVILi1274XlKyGX1n0C9tWYsylzmF_E">&gt;&gt;&gt;&gt; Full proposal &lt;&lt;&lt;&lt;</a></p>
<h2 id="context">Context</h2>
<p><a href="https://dotmemo.xyz/">Dotmemo</a> is a decentralized, permissionless, and free-to-use application built natively on Polkadot Asset Hub for creating and preserving digital memories of online &amp; offline events. It leverages Polkadot's infrastructure to offer a next-generation system for minting, distributing, and verifying on-chain proofs of attendance (POAPs) as NFTs.</p>
<p><strong>Claim a test memo here :)&nbsp;</strong></p>
<p><a href="https://dotmemo.xyz/claim/dotdark">https://dotmemo.xyz/claim/dotdark</a></p>
<h2 id="problemstatement">Problem Statement</h2>
<p>Before dotmemo, the Polkadot ecosystem lacked a native, decentralized solution for creating and managing digital event memories. This absence made it challenging for event organizers, communities, and projects within the Polkadot ecosystem to easily mint, distribute, and verify attendance NFTs without relying on centralized services.</p>
<h2 id="objectives">Objectives</h2>
<ol>
<li>Secure retroactive funding for the development and deployment of dotmemo.</li>
<li>Enhance community engagement through blockchain-based proof of attendance.</li>
<li>Provide a robust, Polkadot-native dApp for creating and collecting digital memories of events.</li>
</ol>
<h2 id="solution">Solution</h2>
<p>Dotmemo's implemented solution involves four core components:</p>
<ol>
<li>Indexer: A high-performance indexer to track POAP-related activities across Polkadot.</li>
<li>Backend: A scalable server infrastructure to manage POAP logistics.</li>
<li>Frontend - Landing Page: An informative and engaging introduction to dotmemo.</li>
<li>Frontend - Claim and Create Pages: Intuitive interfaces for users to claim POAPs and for organizers to create them.</li>
<li>Maintenance &mdash; maintain uptime of the app, develop new features, support the ecosystem teams</li>
</ol>
<h2 id="budget">Budget</h2>
<p>Total requested: $42,000 in USDT</p>
<p>Breakdown:</p>
<ul>
<li>Indexer Development: $6,930</li>
<li>Backend Development: $8,460</li>
<li>Frontend - Landing Page: $6,120</li>
<li>Frontend - Claim and Create Pages: $7,650</li>
<li>Maintenance (6 months): $12,840</li>
</ul>
<h2 id="report">Report</h2>
<p>Quantitative Metrics:</p>
<ul>
<li>Total memories (POAPs) minted: 3,000+</li>
<li>Unique events supported: 10+</li>
<li>Unique users: 3,000+</li>
<li>Networks deployed on: 2 (Polkadot and Kusama)</li>
<li>Largest single event supported: 1,500 attendees (Polkadot Decoded 2023)</li>
</ul>
<p>Qualitative Achievements:</p>
<ul>
<li>Enhanced community engagement and event participation in the Polkadot ecosystem</li>
<li>Successful collaborations with universities and major ecosystem events</li>
<li>Developed innovative features specific to Polkadot's infrastructure</li>
<li>Demonstrated adaptability to various event types and scales</li>
</ul>
<p>We invite the community to review this proposal and provide feedback. The full proposal details, including milestones, timelines, and team information, are available <a href="https://docs.google.com/document/d/1UY8veod8yXqKqVILi1274XlKyGX1n0C9tWYsylzmF_E">here.</a></p>
<p>Proposer: Damsky, Founder of dotmemo.xyz<br />Polkadot account: 15VmrRmgPhKMfBanjS5ei4dCcVL54GMLCfnVRryynSYzvyys</p>

Retroactive Funding for Dotmemo - Proof of Attendance Protocol on Polkadot

Treasury

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:** Lack of a decentralized solution for creating and managing digital event memories in the Polkadot ecosystem.
- **Significance:** Difficulty for event organizers to mint, distribute, and verify attendance NFTs without centralized services.
- **Proposed Solution:** Retroactive funding for dotmemo to develop a Polkadot-native dApp for creating digital event memories.
- **Expected Outcomes:** Enhanced community engagement, improved event participation, and support for Polkadot ecosystem teams.

#1230 Retroactive Funding for Dotmemo - Proof of Attendance Protocol on Polkadot

No Active Proposals