VeeFriends rating of Poor is innaccurate. Please fix asap.

[kwigbelle]

Guessing you see the cdn fronting and the onchain bridge service as centralized. It’s backed by on chain and arweave data but there are wrappers now for performance and compatibility. You can look at the GetMetadata call on the VeeFriends contract itself, it returns all the metadata. The only thing the tokenURI does is read this direct from chain and format it as an ERC721 metadata json. This is because services expect a URI for that value and there is no standard URI that would point them at the chain itself.

The erc 721 standard didn’t expect true onchain data would be a thing so it left no provision for it.
The CDN is just a performance wrapper if you take the first part of the path of that URI and put it against any arweave gateway it will resolve to a blockchain hosted json array. Within this array the individual bits of content are listed.
The second part of the path is the index on this list.
Take the hash from that on chain list and it is also hosted on arweave.
All the cdn does is read on chain data to find and cache on chain data, so that it serves faster for a good web experience.