There was this other article here where the author made an interactive NFT. When you looked at it in the market it actually nice. But once you bought it, the web server knew that you were in your wallet and it was just the poop emoji…
nice, wondering how that conditional logic works. I've played with getImageUri() methods for some time. Maybe they actually setImageUri() within the transfer() method and it checks the owner address for certain ABI characteristic of a smart contract versus an EOA (individual's address). or actually never needing to setImageUri() and just have that last check in getImageUri to serve different metadata based on the type of owner address.
It's incredibly simple. The NFT points to a URL controlled by the author. The author configured the web server so that it would respond with different images "based on the IP or User Agent of the requester." There's nothing web3 or blockchain going on here, it's just a normal image URL where the web server responds differently for different requests. Kinda like image hosting services that would return a placeholder image if you tried to hotlink directly to the image URL.
author here - folks... just look into this stuff for 5 mins, it's amazing. Beeple (famous NFT artist) actually threatened to do this to one his NFTs if Trump one the 2020 election
Comments
There was this other article here where the author made an interactive NFT. When you looked at it in the market it actually nice. But once you bought it, the web server knew that you were in your wallet and it was just the poop emoji…
nice, wondering how that conditional logic works. I've played with getImageUri() methods for some time. Maybe they actually setImageUri() within the transfer() method and it checks the owner address for certain ABI characteristic of a smart contract versus an EOA (individual's address). or actually never needing to setImageUri() and just have that last check in getImageUri to serve different metadata based on the type of owner address.
thats hilarious.
The story is from this blog post: https://moxie.org/2022/01/07/web3-first-impressions.html
It's incredibly simple. The NFT points to a URL controlled by the author. The author configured the web server so that it would respond with different images "based on the IP or User Agent of the requester." There's nothing web3 or blockchain going on here, it's just a normal image URL where the web server responds differently for different requests. Kinda like image hosting services that would return a placeholder image if you tried to hotlink directly to the image URL.
author here - folks... just look into this stuff for 5 mins, it's amazing. Beeple (famous NFT artist) actually threatened to do this to one his NFTs if Trump one the 2020 election
https://api.niftygateway.com/beeple/100010001/
More info: https://cryptobriefing.com/rare-beeple-donald-trump-nft-sell...
Me again - lom this is the experiment you’re talking about: https://moxie.org/2022/01/07/web3-first-impressions.html