Seems the docs doesn’t contain the answer. Looks like that part was moved elsewhere with latest transaction.
The aim is to access encodeFunctionSignature() for knowing to which function name the selector 82661dc4 belongs to in theᴅᴀᴏ contract.

  • Why the downvote ? This is an ᴀᴘɪ question. – user2284570 Aug 15 '19 at 11:52
  • Since Metamask is a plugin it is problematic for them to provide an web3 version. If it is too new it might contains bugs, if it is too old it might not work with some apps. So they decided that you do not have to rely on the web3 version included with Metamask but to use your own. – Ismael Aug 16 '19 at 3:26

You can lookup 82661dc4 via the 4byte.directory:
See here: https://www.4byte.directory/signatures/?bytes4_signature=0x82661dc4

web3.eth.abi is part of web3.js 1.2.x, while Metamask uses web3.js 0.2.x
See this link on how to use web3.js 1.2.1 with metamask:
problem connecting web3 v 1.2.1 with metamask : 'currentProvider' of undefined

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.