&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>

- **Problem Statement:** 
  - Lack of native storage offering in the Polkadot ecosystem.

- **Significance:** 
  - Integrating Move to Substrate and developing Strawberry client implementation of JAM to enhance Polkadot's functionality.

- **Proposed Solution:** 
  - Implementing PolkaStorage to use DOT exclusively as the fee token for data storage and retrieval within the Polkadot ecosystem.

- **Expected Outcomes:** 
  - Enhanced data storage capabilities, increased utility for DOT, and reduced reliance on external networks for storage needs.

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