Issues

• Provider accepts uploads and commits on a bucket where it is only a replica

  paritytech/web3-storage#580 · Filter by author bkontur opened on Nov 6, 2026
  

• provider: GET /read has no length limit, so one request makes the node build a whole blob in memory

  paritytech/web3-storage#577 · Filter by author ilchu opened on Nov 6, 2026

• A slashed provider's agreement can be kept alive with repeated challenges

  paritytech/web3-storage#575 · Filter by author ilchu opened on Nov 6, 2026

• No e2e test runs the challenge responder against a live chain

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

• A replica that never synced blocks bucket deletion

  paritytech/web3-storage#559 · Filter by author ilchu opened on Oct 28, 2026
  2

• provider-node: tests depend on packages/papi metadata

  paritytech/web3-storage#547 · Filter by author bkontur opened on Oct 21, 2026
  

• Challenge response proof vectors are unbounded Vec<H256>

  paritytech/web3-storage#536 · Filter by author ilchu opened on Oct 20, 2026
  2

• Snapshot signer bitfield is hand-rolled bytes and drops late signers

  paritytech/web3-storage#529 · Filter by author ilchu opened on Oct 19, 2026
  1

• Provider UI answers challenges with a current-state proof

  paritytech/web3-storage#523 · Filter by author ilchu opened on Oct 15, 2026
  2

• No defense for a pre-prune commitment after delete_before

  paritytech/web3-storage#522 · Filter by author ilchu opened on Oct 15, 2026

• Signed leaf_count is provider-chosen and bounds the challengeable range

  paritytech/web3-storage#521 · Filter by author ilchu opened on Oct 15, 2026

• provider-storage: commit and chunk proofs read every chunk's bytes to walk the content tree

  paritytech/web3-storage#518 · Filter by author ilchu opened on Oct 13, 2026

• Rename npm packages @web3-storage

  paritytech/web3-storage#516 · Filter by author rosarp opened on Oct 11, 2026

• Virtual providers are designed but not implemented

  paritytech/web3-storage#508 · Filter by author ilchu opened on Oct 9, 2026

• Runtime API in code diverges from design: on-chain discovery, bounded MemberBuckets, no ProviderBuckets, unpaged provider_agreements

  paritytech/web3-storage#507 · Filter by author ilchu opened on Oct 9, 2026

• Primary cap is a provider count, not checkpoint slots; no cancel_challenge

  paritytech/web3-storage#506 · Filter by author ilchu opened on Oct 9, 2026

• Agreement end of life in code diverges from design: permissionless extension, partial burn, admin termination, no replacement or refund

  paritytech/web3-storage#505 · Filter by author ilchu opened on Oct 9, 2026

• Provider lifecycle in code diverges from design: two-step deregistration, stake-per-byte rule, 24h settlement

  paritytech/web3-storage#504 · Filter by author ilchu opened on Oct 9, 2026
  3

• Agreement terms in code diverge from design: quote prices, max_payment, grow-only stake, no agreement_id

  paritytech/web3-storage#503 · Filter by author ilchu opened on Oct 9, 2026

• Provider hardware requirements are undefined

  paritytech/web3-storage#500 · Filter by author dr333ws opened on Oct 8, 2026
  

• Attaching a replica to a private bucket publishes the bucket's contents without warning

  paritytech/web3-storage#498 · Filter by author ilchu opened on Oct 7, 2026
  3

• Replica sync never bootstraps a bucket the node does not already store

  paritytech/web3-storage#497 · Filter by author ilchu opened on Oct 7, 2026

• Frozen buckets don't seem to be append only in code

  paritytech/web3-storage#487 · Filter by author eskimor opened on Oct 5, 2026
  2

• Prune redundant events

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

• 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