Skip to content

docs(helia): add the content node to the architecture and target diagrams #75

Open

Description

@Winter-Soren

Summary

Update the Helia integration overview once the node decision is made.

Estimated size: S

Proposal

  • Update the architecture diagram, limitations (Section 12) and target architecture (Section 14) to include the Kubo node, and record the Boxo decision.

Acceptance criteria

  • Diagrams render and describe the node as built.

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
    boxoBoxo (Go IPFS library) custom services
    tier-1Start here: builds on existing code or config (e.g. reuses the EVM code)
    documentationImprovements or additions to documentation
    kuboKubo (Go IPFS daemon) as the always-on platform node
    and removed
    enhancementNew feature or request
    boxoBoxo (Go IPFS library) custom services
    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

    documentationImprovements or additions to documentationgood first issueGood for newcomerskuboKubo (Go IPFS daemon) as the always-on platform nodestorageDecentralized storage and provenancetier-1Start here: builds on existing code or config (e.g. reuses the EVM code)

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions