Backend: index/mirror/cache NFT data
See original GitHub issueThis issue is to generally handle the case of the frontend asset loading being slow.
The first part is that the preview images are slow (https://github.com/webaverse/app/issues/937).
The larger issue is that hitting the backend will currently read the blockchain. This is far too slow, because it usually requires multiple web3 requests to resolve to find NFT data.
Instead we should mirror all of the NFTs in a local dynamodb.
Table:
sidechain-cache
Primary Key
id: String
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
How to build NFT marketplaces part 2: Backend | by Evan Vischi
How to build NFT marketplaces part 2: Backend. Create wallets, NFTs, store metadata, and sell NFTs using fixed-price or auction listings.
Read more >NFT Project Series Part 3: Build The Backend Server
Learn how to create a backend server in Supabase, Firebase, Mongo, and MySQL using Node.js and Express.
Read more >How to Store and Analyze NFT Data in a Relational Database
Find out how we sourced NFT data and created a schema to store NFT transactions in the open-source relational time-series database, ...
Read more >NFT Marketplace with Lazy Minting #5 IPFS and Database Layer
In this episode we explain why we create Backend APIs to interact with ... how to store NFTs along with offchain data in...
Read more >Create a Complete NFT App - YouTube
Create a Complete NFT App - Smart contract, Backend, Frontend. Watch later. Share. Copy link. Info. Shopping. Tap to unmute.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Ok. Found the right combination of contracts. I think it’s all working.
You can listen to the sidechain ethereum nodes with Web3, and then mint something. If you get the event, you know it’s working.