This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0165 [2020/11/13 02:21] nick ↷ Links adapted because of a move operation |
dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0165 [2022/02/03 16:49] (current) 86.125.5.245 ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| === Simple Summary === | === Simple Summary === | ||
| - | : //Creates a standard method to publish and detect what interfaces a smart contract implements.// | + | : //Creates a standard method to publish and detect what interfaces a [[dido:public:ra:xapend:xapend.a_glossary:s:smart_contract|smart contract]] implements.// |
| === Abstract === | === Abstract === | ||
| Line 27: | Line 27: | ||
| === Motivation === | === Motivation === | ||
| - | : // For some “standard interfaces” like the [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0020| ERC-20]] token interface, it is sometimes useful to query whether a contract supports the interface and if yes, which version of the interface, in order to adapt the way in which the contract is to be interacted with. Specifically for ERC-20, a version identifier has already been proposed. This proposal standardizes the concept of interfaces and standardizes the identification (naming) of interfaces.// | + | : // For some “standard interfaces” like the [[dido:public:ra:xapend:xapend.b_stds:defact:ethereum:eip:erc_0020| ERC-20]] token interface, it is sometimes useful to query whether a contract supports the interface and if yes, which version of the interface, in order to adapt the way in which the contract is to be interacted with. Specifically for ERC-20, a version [[dido:public:ra:xapend:xapend.a_glossary:i:id|identifier]] has already been proposed. This proposal standardizes the concept of interfaces and standardizes the identification (naming) of interfaces.// |