[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

No current votes

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.