Issues

• Sketch user-flows and their latency/viability in a cross-chain setup

  paritytech/web3-storage#482 · Filter by author eskimor opened on Oct 1, 2026

• A dishonest provider can defend a chunk challenge without storing the chunk

  bug
  Bug

  paritytech/web3-storage#480 · Filter by author danielbui12 opened on Oct 1, 2026
  3

  

• Commitment verification conflict between provider-node and storage_primitives::verify_merkle_proof

  bug
  Bug

  paritytech/web3-storage#479 · Filter by author danielbui12 opened on Sep 30, 2026
  

• Runtime API responses erase the chain's account and balance types

  paritytech/web3-storage#477 · Filter by author eskimor opened on Sep 30, 2026

• Providers, bucket members and agreements carry no storage deposit

  paritytech/web3-storage#476 · Filter by author eskimor opened on Sep 30, 2026

• s3-registry and drive-registry keep Layer 1 metadata on chain

  paritytech/web3-storage#475 · Filter by author eskimor opened on Sep 30, 2026
  2

  

• Timeout must be the only slash reason

  paritytech/web3-storage#473 · Filter by author eskimor opened on Sep 30, 2026
  2

  

• Lazy challenge resolution: replace the on_initialize slash sweep with an extrinsic

  paritytech/web3-storage#464 · Filter by author bkontur opened on Sep 29, 2026
  

• Provider is slashed when a challenge targets an older signed commitment

  bug
  Bug

  paritytech/web3-storage#463 · Filter by author danielbui12 opened on Sep 28, 2026
  

• Buckets can be created for a transaction fee and never removed

  paritytech/web3-storage#451 · Filter by author ilchu opened on Sep 23, 2026

• Primary provider is challengeable for a snapshot it did not sign

  paritytech/web3-storage#450 · Filter by author ilchu opened on Sep 23, 2026
  

• Clients wait for finality before calling the provider; they should wait one slot and retry

  paritytech/web3-storage#445 · Filter by author ilchu opened on Sep 22, 2026
  1

• Provider checks membership at the finalized block; it should use its best block

  paritytech/web3-storage#444 · Filter by author ilchu opened on Sep 22, 2026

• Replace the per-provider replay window with a per-owner agreement nonce

  paritytech/web3-storage#422 · Filter by author eskimor opened on Sep 15, 2026
  2

  

• Add end-to-end test for the replica flow

  paritytech/web3-storage#420 · Filter by author bkontur opened on Sep 14, 2026
  

• Concept: web3-storage replica as a backing/durability tier for Bulletin

  paritytech/web3-storage#391 · Filter by author bkontur opened on Sep 5, 2026
  

• Investigate: Bitswap support in the provider for Bulletin interoperability

  paritytech/web3-storage#390 · Filter by author bkontur opened on Sep 5, 2026
  1

  

• checkpoint counts signature entries, not distinct providers

  paritytech/web3-storage#388 · Filter by author bkontur opened on Sep 4, 2026
  

• RFC: Forced re-stake deadline + auto-eviction after a slash

  paritytech/web3-storage#387 · Filter by author kelwinshen opened on Sep 4, 2026
  1

• RFC: Size provider stake to economic exposure, not just physical bytes

  paritytech/web3-storage#386 · Filter by author kelwinshen opened on Sep 4, 2026
  3

• [Provider] Layer-0 read endpoints are unauthenticated, so bucket visibility is unenforced

  paritytech/web3-storage#383 · Filter by author bkontur opened on Sep 4, 2026
  

• [Provider] Bucket quota (max_bytes) is never enforced — every bucket is initialised as unlimited

  bug
  paritytech/web3-storage#382 · Filter by author bkontur opened on Sep 4, 2026
  1

  

• Add max_buckets and min_price to ProviderInfo

  paritytech/web3-storage#379 · Filter by author franciscoaguirre opened on Sep 3, 2026
  3

  

• provider-storage: turn StoredNode into a leaf/internal enum, validate children

  paritytech/web3-storage#378 · Filter by author bkontur opened on Sep 3, 2026
  

• [Provider] Storage data-format versioning & migration (fail loudly on incompatible on-disk data)

  paritytech/web3-storage#375 · Filter by author bkontur opened on Sep 1, 2026