ERC 165: Detect what interfaces are supported by a smart contract
ฝัง
- เผยแพร่เมื่อ 19 ก.ย. 2024
- ERC 165 allows you to detect what interfaces a smart contract implements.
This can help prevent users or smart contracts from sending tokens to contracts that don't support the token interface, as this would cause the tokens to become stuck in the receiving contract.
The smart contract in the video is deployed on the Rinkeby testnet here:
rinkeby.ethers...
You can also call the methods to generate the interface ids. (don't worry, this consumes zero gas because the methods are not modifying the state of the blockchain)
Github for the smart contract used in the video:
github.com/rob...
en.wikipedia.o...
eips.ethereum....
Thank you for this!
Awesome Video, you explained the topic so well! :) Thank you!
Excellent video tutorial. Thank you for your work.
Def very helpful for what I was looking for. Thanks!
Thank you. This was excellent.
Super useful stuff. Thanks
Great video.
Glad you enjoyed it =)
Yes Great Video - I will have to watch it several more times to grasp this fully. I only want to encourage you to continue with your videos sir.
@@chrissgchriss thank you Chriss!
Amazing !
subbed. great work dude ty. curious, why use the big endian to assign the ID? seems like a lot of 0's just hanging around waiting for another y2k to bite someone in the ass for not adding room for a long hash ID. also, in theory couldn't you trick the XOR statement into thinking your shit token is exactly what it needs to work with so long as you minted a shit token with a matching hash? i mean it's improbable not impossible... today ... but... immutable means if shit pops off and another hash is created with that same big endian hash ID... then... game over.... haven't seen anyone talk about this anywhere.... did i make up an imaginary enemy? sorry it's been about since the year 2000 since i was passionate about a project i'm working on and i was just curious! thanks!