Thank you everyone for supporting us in <a href="494" target="_blank" rel="noopener">Phase 1</a> and <a href="1150" target="_blank" rel="noopener">Phase 2</a>. Happy to share that we have completed the work for phase 2. Check out the <a href="https://eigerco.github.io/polka-storage-book/" target="_blank" rel="noopener">book</a>, the <a href="https://github.com/eigerco/polka-storage/" target="_blank" rel="noopener">repo</a> and our <a href="https://forum.polkadot.network/t/polkadot-native-storage-updates/7021" target="_blank" rel="noopener">weekly progress updates</a> on the Polkadot forum.
As a side note we are happy to share that we are the first team to submit a <a href="https://github.com/w3f/jam-milestone-delivery/pull/6" target="_blank" rel="noopener">PR for review</a> for reaching JAM Milestone 1 with our JAM client Strawberry 🍓. We are very excited to turn this vision into executable code.
For this phase 3 we are incorporating feedback gathered during phase 2 and requesting USDT instead of DOT. Given the current market conditions and the community optimism on the future of the DOT price, we believe asking for stables is now the optimal choice for the treasury.
One more thing: During phase 2 we looked at integrating JAM data availability with Polkadot Storage so that it would serve as the underlying storage layer for resupply of unrequested data that needs to be provided to validators on request. What if we used Polkadot Storage as the archival layer of all DA networks such as Celestia, EigenDA, Avail and more. As you know data availability networks give you publishing guarantees but not archival. As <a href="https://github.com/eigerco/lumina" target="_blank" rel="noopener">contributors </a>to Celestia <a href="https://crates.io/users/eiger-releases" target="_blank" rel="noopener">stack</a>, we are familiar with the codebase and are exploring adding support to take historical snapshots, import, export and archive into Polkadot Storage. Historical data is useful for looking past the retention window, explorers, rollup developers etc. So in short: Storing all DA blockchains archival data into Polkadot Storage, why not.
Links:
<ul>
<li>Code <a href="https://github.com/eigerco/polka-storage/" target="_blank" rel="noopener">https://github.com/eigerco/polka-storage/</a></li>
<li>Phase 1/3 <a href="494" target="_blank" rel="noopener">https://polkadot.polkassembly.io/referenda/494</a></li>
<li>Phase 2/3 <a href="1150" target="_blank" rel="noopener">https://polkadot.polkassembly.io/referenda/1150</a></li>
<li>Full proposal <a href="https://docs.google.com/document/d/16SZXvXyBRd-oEMIbgAid_vaxTuKzDlxuNc9CwSq3Lq0/edit" target="_blank" rel="noopener">https://docs.google.com/document/d/16SZXvXyBRd-oEMIbgAid_vaxTuKzDlxuNc9CwSq3Lq0/edit</a></li>
<li>Thinking about JAM DA integration <a href="https://docs.google.com/document/d/1L1jlMI9-KOfxMYUMQVeq0tPNtz1fitxTXlg6gKwjXnM/edit?usp=sharing" target="_blank" rel="noopener">https://docs.google.com/document/d/1L1jlMI9-KOfxMYUMQVeq0tPNtz1fitxTXlg6gKwjXnM/edit?usp=sharing</a></li>
<li>Weekly dev updates <a href="https://forum.polkadot.network/t/polkadot-native-storage-updates/7021" target="_blank" rel="noopener">https://forum.polkadot.network/t/polkadot-native-storage-updates/7021</a></li>
<li>Research on native storage we first <a href="https://github.com/common-good-storage/report/blob/master/src/first.md" target="_blank" rel="noopener">did in 2021</a> but there were limitations with collators back then. We returned to this topic in 2023 and got <a href="https://github.com/dtuzi/Grants-Program/blob/4d5e7ff1cc90ab0416604dc705bd02c29ba136e6/applications/Eiger_Storage_on_Polkadot_1.md" target="_blank" rel="noopener">a grant</a> from W3F to figure out how.</li>
<li>Initial research pre-implementation <a href="https://github.com/eigerco/polkadot-native-storage/blob/main/doc/report/polkadot-native-storage-v1.0.0.pdf" target="_blank" rel="noopener">https://github.com/eigerco/polkadot-native-storage/blob/main/doc/report/polkadot-native-storage-v1.0.0.pdf</a></li>
<li>Forum discussion <a href="https://forum.polkadot.network/t/polkadot-native-storage/4551" target="_blank" rel="noopener">https://forum.polkadot.network/t/polkadot-native-storage/4551</a></li>
</ul>

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:** Incorporating feedback from Phase 2, the team aims to request USDT instead of DOT due to market conditions and community optimism, optimizing the treasury for Phase 3.
- **Significance:** Enhancing data availability networks by utilizing Polkadot Storage as an archival layer for various DA networks like Celestia, EigenDA, and Avail, providing historical data for exploration and development.
- **Proposed Solution:** Storing all DA blockchains' archival data into Polkadot Storage to address the lack of archival support in data availability networks.
- **Expected Outcomes:** Improved data accessibility, historical data availability for research and development, and enhanced support for explorers and rollup developers.

#1313 Polkadot Storage: Phase 3/3

No Active Proposals