Skip to content

feat(content-node): reprovide only pinned content #65

Open

Description

@Winter-Soren

Summary

Limit what the node announces to what the platform pinned.

Estimated size: S

Proposal

  • Set the reprovide strategy to pinned or roots (verify option names for the pinned release).
  • Document the trade-off: cached blocks are not announced.

Acceptance criteria

  • Only pinned CIDs are announced; documented with the command used to check.

Dependencies


Part of #43. Ground rules for the content layer: no secrets in the repo, content-layer failures must never block or discard quantum execution, and tests and docs ship with every PR.

Activity

  1. added
    enhancementNew feature or request
    storageDecentralized storage and provenance
    kuboKubo (Go IPFS daemon) as the always-on platform node
    tier-2Needs a new SDK, service or account model
    on Oct 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requestkuboKubo (Go IPFS daemon) as the always-on platform nodestorageDecentralized storage and provenancetier-2Needs a new SDK, service or account model

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions