Decentralized Snippet Storage Using IPFS#116
Open
veemakama wants to merge 1 commit into
Open
Conversation
Updated file
|
@veemakama is attempting to deploy a commit to the Sudipta 's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@veemakama Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
✅ Store snippet content on IPFS while keeping ownership metadata on Stellar
We use Helia, a modern IPFS implementation, to store snippet code off-chain
Ownership metadata ( owner_wallet_address ) remains in the database and is still linked to your existing Stellar blockchain integration
Added ipfs_cid column to database to map snippets to their IPFS content
✅ Generate and store IPFS CIDs in database
The storeOnIPFS() function generates a CID for snippet content
This CID is stored in the ipfs_cid column of the snippets table
Each snippet can have its own unique IPFS CID
✅ Link CIDs to snippet ownership records
CIDs are stored directly on snippet records, maintaining a 1:1 mapping
Snippet ownership is still verified using your existing Stellar-based authentication/authorization system
✅ APIs for storing and fetching snippets
Store : POST /api/snippets with storeOnIpfs: true parameter will store content on IPFS and save the CID
Fetch by CID : GET /api/snippets/ipfs?cid=QmXYZ... retrieves content from IPFS
Fetch by ID : GET /api/snippets/[id] still works, and now returns the ipfs_cid field if present
Standalone IPFS storage : POST /api/snippets/ipfs can store arbitrary content on IPFS
✅ Validation and error handling
Fallback mechanism: If IPFS storage fails, the snippet is still stored reliably in the database
Proper error responses from all API endpoints
Zod validation remains active for snippet data
Graceful error handling in both service and API layers
Backward compatibility: All existing API endpoints continue to work exactly as before
Closes Decentralized Snippet Storage Using IPFS #83