[BS] DOT #1313 - Polkadot Storage: Phase 3/3
Terminated 6d 11hrs ago
terminated
Description

https://polkadot.subsquare.io/referenda/1313

  • The team completed Phase 2 of their project and shared updates on their book, GitHub repository, and weekly progress on the Polkadot forum.
  • They became the first team to submit a PR for review for reaching JAM Milestone 1 with their JAM client, Strawberry.
  • For Phase 3, they plan to incorporate feedback from Phase 2 and request USDT instead of DOT due to current market conditions.
  • They explored integrating JAM data availability with Polkadot Storage, considering it as an archival layer for DA networks like Celestia, EigenDA, and Avail.
  • The team, contributors to Celestia, is exploring adding support for historical snapshots and archival into Polkadot Storage.
  • Links to their code, phases, full proposal, JAM DA integration, weekly updates, and research are provided.
Optionssingle

Votes·6

12Hi...E9N3
12Hi...E9N3
12His7t3EJ38tjdBbivUzWQeaNCLKfMqtKp1Ed3xHMyCE9N3
Nay
# 2
The offer is too expensive.
14Gn...YLEh
14Gn...YLEh
14Gn7SEmCgMX7Ukuppnw5TRjA7pao2HFpuJo39frB42tYLEh
Nay
# 2
I share the view that the proposal poses quite a high cost. I am not unaware of all the effort they have made previously, in fact, I find it very commendable that they have already worked with JAM, but I still can't really justify spending almost 2 million dollars for all this.
14gM...deVb
14gM...deVb
14gMJV95zwxUsFEZDSC8mtBVifS6SypKJkfBKANkMsLZdeVb
Nay
# 2
Have same feelings with most proposal nay comments.
1xzc...1bX6
1xzc...1bX6
1xzcLSwo7xBFkJYZiL4EHaqFpuPTkH641E3V43W4cuk1bX6
Abstain
# 3
We think that multiple decentralized storage solutions will be needed in the future. However, we think that this proposal is perhaps coming a bit to early since JAM isa not even ready yet. We also have some concerns about what the future maintenance costs might be for this infrastructure product.
15fT...yBzL
15fT...yBzL
15fTH34bbKGMUjF1bLmTqxPYgpg481imThwhWcQfCyktyBzL
Aye
# 1
I objected to the Milestone 1 proposal of this effort. But since both Milestone 1 and 2 have passed community vote, to reject this proposal would be to break a contract. I aye it reluctantly, mainly to keep the promise.
1ZSP...vx6w
1ZSP...vx6w
1ZSPR3zNg5Po3obkhXTPR95DepNBzBZ3CyomHXGHK9Uvx6w
Aye
# 1
One important question is how this will be productized after completion. However, I believe the team has done good work so far and the project is de-risked by components being ported from another protocol, and the previous work done. This is an investment in a future more fully featured global shared computer running on Polkadot (and then jam)

Discussions·1

6d 10hrs ago

Hey everyone, thanks for engaging with us and having such an open and transparent process, I respect that a lot. We replied to your comment on the referenda but pasting it here also in case someone doesn't see it.

About the pricing:

  • Our ask has remained unchanged since the initial proposal back in February. All the plans, breakdowns, timelines, work allocation have been transparently available in the full proposal from the beginning.
  • Its a large amount but its also proportional to the work that goes into creating a whole storage network comparable to Arweave, Filecoin etc the difference is that we are not creating a new L1, not launching a new token and not owning the network. Just adding to DOT utility.
  • People typically pay for such projects, not because they are cheap/expensive but because the value created in return is bigger than the cost.
  • As a business, on top of paying salaries for blockchain devs we have to cover other supporting personnel, health and social security, sick times, vacations, national holidays, training, replacements, taxes, which add to the difference between individual expectations and real costs.
  • While the cost might seem high, we aim to deliver high quality work and avoid delivering a rushed, low quality product that would cost more to the network due to its failures, user experience, downtime or damaged reputation.

About the timing, I don't agree with that, these things take time and the bulk of the work must be done in parallel, if things are done sequentially then timelines are extended and we as an ecosystem miss the timing. As the first team to send our Jam client implementation for review and open sourced the code, we have the finger on the pulse with the latest developments and graypaper updates and believe the timing is right.

Information
Snapshot
Timestamp
Created
Dec 16 2024 19:54
Start date
Dec 16 2024 00:00
End date
Jan 15 2025 00:00
Results
Voters
6
one-person-one-vote
Aye
2 VOTE
 
Nay
3 VOTE
 
Abstain
1 VOTE
 
© 2024 OpenSquare. All Rights Reserved.