Allow uploading via URL/IPFS/Arweave on Dashboard (also show CID on details page)
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
From Victor: today assets can be in 4 states:
1. not uploaded from IPFS and not pinned in our gateway's IPFS (noop)
2. uploaded from IPFS but not pinned to our gateway (that case)
3. not uploaded from IPFS but pinned to our gateway
4. uploaded from IPFS and pinned to our gateway (most likely ending up with a different CID)
For state 2., we should show the IPFS CID in the dashboard as the IPFS CID from the gateway we imported from.
https://discord.com/channels/423160867534929930/611650333243867170/1038163981078110239
Contributor guide
Research direction
Start by tracing the Dashboard upload and asset-details entry points, then review how imported IPFS assets are represented across the four states described here. Define the expected behavior for URL, IPFS, and Arweave uploads, including showing the imported gateway CID; completion should cover each state and the details-page display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100