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>

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://forum.polkadot.network/t/bringing-movevm-to-substrate-and-the-polkadot-ecosystem/4572">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

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:

1. 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.

2. 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.



[Read our full draft proposal here.](<https://docs.google.com/document/d/16SZXvXyBRd-oEMIbgAid_vaxTuKzDlxuNc9CwSq3Lq0/edit>)

Notes about our experience:

- [We are bringing MoveVM to Substrate](<https://forum.polkadot.network/t/bringing-movevm-to-substrate-and-the-polkadot-ecosystem/4572>)

- We worked on and [maintained IPFS in Rust](<https://github.com/rs-ipfs/rust-ipfs>) for several years. Our engineers are the top contributors (Eiger is a child company of Equilibrum)

- More about our experience in section 2.4 of the proposal document



More links:

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

- Polkadot [forum discussion](<https://forum.polkadot.network/t/polkadot-native-storage/4551>).

- Github [repository](https://github.com/eigerco/polkadot-native-storage)

- Eiger [website](<https://www.eiger.co/>)

&nbsp;

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 style="margin-top: 0; margin-bottom: 0; padding-inline-start: 48px;">
<li dir="ltr" style="list-style-type: decimal; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
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 dir="ltr" style="list-style-type: decimal; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
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 style="text-decoration: none;" href="https://docs.google.com/document/d/16SZXvXyBRd-oEMIbgAid_vaxTuKzDlxuNc9CwSq3Lq0/edit"><span style="font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; -webkit-text-decoration-skip: none; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;">Read our full draft proposal here.</a>
Notes about our experience:
<ul style="margin-top: 0; margin-bottom: 0; padding-inline-start: 48px;">
<li dir="ltr" style="list-style-type: disc; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
<a style="text-decoration: none;" href="https://forum.polkadot.network/t/bringing-movevm-to-substrate-and-the-polkadot-ecosystem/4572"><span style="font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; -webkit-text-decoration-skip: none; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;">We are bringing MoveVM to Substrate</a>
</li>
<li dir="ltr" style="list-style-type: disc; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
We worked on and <a style="text-decoration: none;" href="https://github.com/rs-ipfs/rust-ipfs"><span style="font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; -webkit-text-decoration-skip: none; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;">maintained IPFS in Rust</a> for several years. Our engineers are the top contributors (Eiger is a child company of Equilibrum)
</li>
<li dir="ltr" style="list-style-type: disc; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
More about our experience in section 2.4 of the proposal document
</li>
</ul>
More links:
<ul style="margin-top: 0; margin-bottom: 0; padding-inline-start: 48px;">
<li dir="ltr" style="list-style-type: disc; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
<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 dir="ltr" style="list-style-type: disc; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
Polkadot <a style="text-decoration: none;" href="https://forum.polkadot.network/t/polkadot-native-storage/4551"><span style="font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; -webkit-text-decoration-skip: none; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;">forum discussion</a>.
</li>
<li dir="ltr" style="list-style-type: disc; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
Github <a style="text-decoration: none;" href="https://github.com/eigerco/polkadot-native-storage"><span style="font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; -webkit-text-decoration-skip: none; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;">repository</a>.
</li>
<li dir="ltr" style="list-style-type: disc; font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: none; vertical-align: baseline; white-space: pre;" aria-level="1">
Eiger <a style="text-decoration: none;" href="https://www.eiger.co/"><span style="font-size: 10.5pt; font-family: Arial,sans-serif; background-font-weight: 400; font-style: normal; font-variant: normal; text-decoration: underline; -webkit-text-decoration-skip: none; text-decoration-skip-ink: none; vertical-align: baseline; white-space: pre-wrap;">website</a>.
</li>
</ul>

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

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>

General

Problem Statement:
- The current Polkadot ecosystem lacks native storage offering, limiting its app-centric design and dependence on other networks.

Significance:
- Adding native storage to Polkadot would align with the vision of building the Ubiquitous Supercomputer and expand the value offering of Polkadot, similar to Filecoin.

Proposed Solution:
- Create a system parachain with DOT as the fee token to provide native storage, allowing anyone in the ecosystem to store and retrieve data through XCM.

Expected Outcomes:
- Avoid dependence on other networks or tokens, enabling greater control and innovation.
- Open-source and decentralized solution, allowing for community proposals to maintain and improve the system.

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

No Active Proposals