NethermindEth
feat: SRC5 Interface detection
@julio4 can you give more context to this
Show an example of how a contract can implement the ISRC5 trait to comply with SRC-5 for interfaces detection.
from the above docs shared, we are implementing a trait function that check this interface_id == 0x3f918d17e5ee77373b56385708f855659a07f75997f365cf87748628532a055
from the above docs shared, we are implementing a trait function that check this
interface_id == 0x3f918d17e5ee77373b56385708f855659a07f75997f365cf87748628532a055
Not exactly, this specific interface_id is only an example. SRC5 is a standard that define how to generate interface ids and how a contract can publish what interfaces it implements in order to allow anyone to query if the contract implement it.
You can take a look at the OZ implementation for an example here
this OpenZeppelin implementation is somewhat same thing we are going to do here
this OpenZeppelin implementation is somewhat same thing we are going to do here
Yes but not as a component (atleast for now), we only want to demonstrate how one contract can implement the trait to return true for a specific interface id. So developers can quickly understand without having to read all the SNIP!
