btw, just for reference, I tested my proxy idea in the current updated version of the boilerplate, and overall it ends up performing faster with all the images showing.
src/components/NFTBalance.jsx
const handleChange = (e) => {
setAmount(e.target.value);
};
// Start Change
if (NFTBalances?.result) {
NFTBalances.result.forEach(element => {
if (element.token_uri.indexOf('workaround-proxy') < 0) {
element.token_uri = `https://workaround-proxy.herokuapp.com/${element.token_uri}`
}
});
}
// End Change
console.log("NFTBalances", NFTBalances);
return (
<>
<div style={styles.NFTs}>
So, some sort of proxy / caching layer may well be a good intermediate solution.
Iām also thinking of routing the NFT images received through a CDN so theyāre more stable and donāt run into request limitations on origin server.