Would it be valuable to the ecosystem to have a Filecoin-like native storage offering on Polkadot? 
One that uses DOT as the native token and where anyone in the ecosystem through XCM would be able to store and retrieve data. This is mainly inspired by the vision Gavin presented at Decoded 23 about building the Ubiquitous Supercomputer. When thinking about the app-centricity design and the Space and Cores model it will be critical for us to have native storage and not depend on other networks. This basically extends the Polkadot value offering to include storage, similar to Filecoin, and brings us closer to the supercomputer vision.
&nbsp;
We believe it's very important that this work is done as a public good with DOT used as the fee token, otherwise, any dependence on other networks or other tokens would undermine the goals. <a href="https://docs.google.com/document/d/16SZXvXyBRd-oEMIbgAid_vaxTuKzDlxuNc9CwSq3Lq0/edit" target="_blank" rel="noopener">Read our full draft proposal here.</a>
&nbsp;
We are looking for feedback, how can we improve the proposal? More links: 
<ul>
<li dir="ltr" style="line-height: 1.38;"><a href="https://github.com/eigerco/polkadot-native-storage/blob/main/doc/report/polkadot-native-storage-v1.0.0.pdf" target="_blank" rel="noopener">Our 48 page extensive research on how to do this.</a> Read this as it complements this proposal </li>
<li dir="ltr" style="line-height: 1.38;">Polkadot <a href="https://forum.polkadot.network/t/polkadot-native-storage/4551" target="_blank" rel="noopener">forum discussion</a>.</li>
<li dir="ltr" style="line-height: 1.38;">Github <a href="https://github.com/eigerco/polkadot-native-storage" target="_blank" rel="noopener">repository</a>.</li>
<li dir="ltr" style="line-height: 1.38;">Eiger <a href="https://www.eiger.co/" target="_blank" rel="noopener">website</a>.</li>
</ul>

Implementing a public good Polkadot-native system parachain for data storage

&nbsp;
Hey everyone, I wanna start by saying thank you to the community for the overwhelming support of <a href="494" target="_blank" rel="noopener">OpenGov referendum 494</a>. Since then we have been heads down working on the storage network and have now completed phase 1 and some extra parts.
If you weren't aware we have been posting weekly updates on <a href="https://forum.polkadot.network/t/polkadot-native-storage-updates/7021" target="_blank" rel="noopener">the forum&nbsp;</a>
Check out the book <a href="https://eigerco.github.io/polka-storage-book/">https://eigerco.github.io/polka-storage-book/</a> It contains lots of technical details and some nice instructions on how to test it. Work continues uninterrupted on phase 2 tasks.
During this time, in addition to the work on the storage network, there's two more projects we have been working on that contribute to Polkadot:
<ol>
<li>
We integrated Move to Substrate. Allowing builders to integrate the Move VM and execute Move smart contracts. Anyone can now create a Move parachain on Polkadot. <a href="https://x.com/Polkadot/status/1816109501394637034">https://x.com/Polkadot/status/1816109501394637034</a>
</li>
<li>
We have a full team working on Strawberry our client implementation of JAM and are very close to the first milestone. More updates on that soon.
</li>
</ol>
&nbsp;
Links:
<ul>
<li>Full proposal <a href="https://docs.google.com/document/d/16SZXvXyBRd-oEMIbgAid_vaxTuKzDlxuNc9CwSq3Lq0/edit">https://docs.google.com/document/d/16SZXvXyBRd-oEMIbgAid_vaxTuKzDlxuNc9CwSq3Lq0/edit</a></li>
<li>JAM DA integration <a style="background-color: #0d0d0d;" href="https://docs.google.com/document/d/1L1jlMI9-KOfxMYUMQVeq0tPNtz1fitxTXlg6gKwjXnM/edit?usp=sharing">https://docs.google.com/document/d/1L1jlMI9-KOfxMYUMQVeq0tPNtz1fitxTXlg6gKwjXnM/edit?usp=sharing</a></li>
</ul>
<ul>
<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">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">https://forum.polkadot.network/t/polkadot-native-storage/4551</a></li>
<li>Forum development updates <a href="https://forum.polkadot.network/t/polkadot-native-storage-updates/7021">https://forum.polkadot.network/t/polkadot-native-storage-updates/7021</a></li>
<li>OpenGov Phase 1/3 <a href="494">https://polkadot.polkassembly.io/referenda/494</a></li>
</ul>
&nbsp;
Edit: Adding some notes on the value proposition and our integration with JAM as we had looked at this&nbsp;months ago but realized that we hadn't shared it here. 
Why PolkaStorage, adding native storage offering to Polkadot:
<ul>
<li>Uses DOT exclusively as the fee token where anyone in the eco thru XCM can store and retrieve data. No new tokens to take away utility from DOT.</li>
<li>Inspired by Gavins presentation about the Ubiquitous Supercomputer, storage offering is critical: cores for execution, storage for data. Now with JAM, the same storage offering is needed.</li>
<li>Reliance on other networks is a weakness. Other solutions use their own token and are just incentivization models on top of IPFS. This would be exclusive native storage for the DOT ecosystem. Bringing in storage providers to the ecosystem, service fees paid in DOT.</li>
<li>Although we use some Filecoin libraries to speed up development and not waste developer time reinventing the wheel, this custom implementation allows us to tailor the solution to what is needed in DOT, we are adapting it around JAM (We have a separate team working on Strawberry our client implementation) and bring in other use cases like data availability on top of this storage. (We built the Celestia rust stack, <a href="https://www.eiger.co/blog/lumina-release-start-celestia-light-node" target="_blank" rel="noopener">read about our work and experience in DA</a>).</li>
</ul>
&nbsp;
Integrating Eiger&rsquo;s Polka Storage with JAM's Preimage Lookup System and Data Availability
&nbsp;
Providing access to larger data capacity that doesn't fit in account state and being the underlying storage layer for resupply of unrequested data that needs to be provided to validators on request.
<ul>
<li>Fully synchronous execution: ETH L1. All app data is stored on-chain and easily accessible. Not scalable.</li>
<li>Incoherent system: App data in different rollups, scalable but not composable, rollup model.</li>
<li>Best of both worlds: JAM with DA. Where apps can access this data and only keep crucial parts on the JAM state. We are building the underlying storage layer for that data.</li>
</ul>
Read our notes on this topic at <a href="https://docs.google.com/document/d/1L1jlMI9-KOfxMYUMQVeq0tPNtz1fitxTXlg6gKwjXnM/edit?usp=sharing">https://docs.google.com/document/d/1L1jlMI9-KOfxMYUMQVeq0tPNtz1fitxTXlg6gKwjXnM/edit?usp=sharing</a>

Implementing a Polkadot-native system parachain for data storage: Phase 2/3

We would like to add native storage offering to Polkadot.
One that uses DOT exclusively as the native token and where anyone in the ecosystem through XCM would be able to store and retrieve data. This is mainly inspired by the vision Gavin presented at Decoded 23 about building the Ubiquitous Supercomputer. When thinking about the app-centricity design and the Space and Cores model it will be critical for us to have native storage and not depend on other networks.
This basically extends the Polkadot value offering to include storage, similar to Filecoin, and brings us closer to the supercomputer vision.
We believe it's very important that this work is done as a system parachain with DOT used as the fee token, otherwise, any dependence on other networks or other tokens would undermine the goals.
Compared to existing offerings like Crust:
<ol>
<li>
Crust uses IPFS as its underlying storage network, on the other hand this would be native storage provided by the Polkadot storage providers, not the same storage network, not a subset. Even if you have a great incentivization model, being dependent on the storage technology limits what you can offer and how far you can innovate. For one to be free from these constraints it needs to have control of the whole stack.
</li>
<li>
We are not proposing to create a new token on top of which our business model and investor returns would be built upon. This is a network owned solution, a system parachain, not a private endeavor like Crust. We want DOT to be the exclusive fee payment token. Someone said in another chat "than put all the eggs into the basket of one team which, if it disappears, takes the product with it (which is the case with every parachain right now)" and that is what we are trying to avoid and solve for. We just want to build the solution, not own it, system parachain, so avoiding "here's another token". Everything would be open source, open license, no ownership. Anyone can then make proposals to maintain and improve it. This whole industry, this is what its all about, open source and decentralization, making the system own itself.
</li>
</ol>
<a href="https://docs.google.com/document/d/16SZXvXyBRd-oEMIbgAid_vaxTuKzDlxuNc9CwSq3Lq0/edit">Read our full proposal here.</a>
Notes about our experience:
<ul>
<li>
<a href="https://github.com/eigerco/substrate-move" target="_blank" rel="noopener">We are bringing MoveVM to Substrate</a>
</li>
<li>
We worked on and <a href="https://github.com/rs-ipfs/rust-ipfs">maintained IPFS in Rust</a> for several years. Our engineers are the top contributors (Eiger is a child company of Equilibrum)
</li>
<li>
More about our experience in section 2.4 of the proposal document
</li>
</ul>
More links:
<ul>
<li>
<a href="https://github.com/eigerco/polkadot-native-storage/blob/main/doc/report/polkadot-native-storage-v1.0.0.pdf" target="_blank" rel="noopener">Our 48 page extensive research</a> on how to do this. Read this as it complements this proposal
</li>
<li>
Polkadot <a href="https://forum.polkadot.network/t/polkadot-native-storage/4551">forum discussion</a>.
</li>
<li>
Github <a href="https://github.com/eigerco/polkadot-native-storage">repository</a>
</li>
<li>
Eiger <a href="https://www.eiger.co/">website</a>
</li>
</ul>

Implementing a Polkadot-native system parachain for data storage: Phase 1/3

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>