-
Notifications
You must be signed in to change notification settings - Fork 51
Build a Resilient IPFS Pinning Service with Multi-Provider Failover #171
Copy link
Copy link
Closed
Labels
GrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26Campaign: Official Campaign | FWC26backenddifficulty: hardHard difficulty issueHard difficulty issueenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededpriority: highHigh priority issueHigh priority issuereliabilityweb3
Description
Activity
Metadata
Metadata
Assignees
Labels
GrantFox OSSIssue tracked in GrantFox OSSIssue tracked in GrantFox OSSMaybe RewardedIssue may be eligible for a GrantFox rewardIssue may be eligible for a GrantFox rewardOfficial Campaign | FWC26Campaign: Official Campaign | FWC26Campaign: Official Campaign | FWC26backenddifficulty: hardHard difficulty issueHard difficulty issueenhancementNew feature or requestNew feature or requesthelp wantedExtra attention is neededExtra attention is neededpriority: highHigh priority issueHigh priority issuereliabilityweb3
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
backend/npm run lintAcceptance Criteria
Estimated Time
1-3 days