Public Timeline Modular Component for IP Assets #29
Conversation
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
|
@gelluisaac is attempting to deploy a commit to the mipdapp-6438's projects Team on Vercel. A member of the Team first needs to authorize it. |
Contributor
|
gm gm @gelluisaac any progress? still getting errors |
Author
|
gm gm @salvadorcamino you can check it now |
Contributor
gm can you check your implementation? here it shows no assets |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
This PR introduces a new PublicTimeline component that showcases tokenized IP assets registered via the Mediolano Protocol. The implementation includes:
Infinite scroll functionality for browsing assets chronologically
Card-based display of IP assets with key metadata:
Creator information (name/address)
Asset title, description, and media preview
Licensing terms and provenance data
Robust IPFS integration with:
Multiple gateway fallback support
Error handling for failed metadata fetches
Responsive grid layout with loading skeletons
Filtering by asset type (art, music, documents, etc.)
Technical Details:
Built with Next.js and React
Integrates with Starknet contracts for asset data
Uses intersection observer for scroll detection
Implements proper TypeScript typing throughout
Includes comprehensive error states and loading UI
close #5