Skip to content

Build a Resilient IPFS Pinning Service with Multi-Provider Failover #171

Description

@meshackyaro

Description

This issue aims to address the implementation of Build a Resilient IPFS Pinning Service with Multi-Provider Failover.

The core objective is to: Pin deliverables across multiple IPFS providers with content-hash verification, automatic failover, and a re-pin worker that guarantees durability of stored CIDs.

By completing this feature, we will ensure that the TrustFlow protocol maintains its high standards for security, usability, and decentralized logic. This issue requires careful attention to the Backend architecture and adherence to the existing project conventions.

When picking up this issue, please ensure you document any new dependencies or architectural decisions made during development.

Component

Backend

Difficulty

🔴 Hard

Tasks

  • Review Node.js API architecture in backend/
  • Implement logic for: Build a Resilient IPFS Pinning Service with Multi-Provider Failover
  • Write unit tests for the new endpoints using Supertest
  • Update Swagger terminology / OpenAPI specs
  • Verify PostgreSQL queries are optimized
  • Run npm run lint

Acceptance Criteria

  • Feature accurately implements the objective: Pin deliverables across multiple IPFS providers with content-hash verification, automatic failover, and a re-pin worker that guarantees durability of stored CIDs.
  • Any PR that introduces TypeScript errors is automatically blocked
  • CI pipeline runs in under 3 minutes per PR
  • Code is properly reviewed and approved by codeowners

Estimated Time

1-3 days

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions