Calculating sha3 of address in solidity vs web3 [duplicate]

Question

This question already has an answer here:

• keccak3 in SOLIDITY and in WEB3 different hashes for an address type field 3 answers

sha3 of address-type argument calculated in solidity

function get_sha() constant returns (address, bytes32) {
    return (msg.sender, sha3(msg.sender));
}

is different from that calculated in web3js using buffer constructed from hex representation of the argument:

• returned from contract:
  address: 0xca35b7d915458ef540ade6068dfe2f44e8fa733c
  bytes32: 0xb1591967aed668a4b27645ff40c444892d91bf5951b382995d4d4f6ee3a2ce03

• returned by web3js:
  > web3.sha3(Buffer.from('ca35b7d915458ef540ade6068dfe2f44e8fa733c', 'hex').toString())
'0xd53a2663473d029b80bddef493a064cc91bad113e4a61353b243b769c6909222'

They match if I compare sha3s of string-type arguments like "a", but don't match in case of address-type argument. I also tried to pad string inside Buffer.from(...) with 24 zeros on the left and on the right, so that it would represent 32 bytes, but the result is still incorrect.

How can I make web3's value match that of solidity's?

Answer 1

Try web3.sha3('0xca35b7d915458ef540ade6068dfe2f44e8fa733c') or web3.sha3('0xca35b7d915458ef540ade6068dfe2f44e8fa733c', { encoding: 'hex' })

Answer 2

One of my friend fixed this issue by making some changes in original solidity-sha3 package which was created to match the behavior of sha3 in Solidity and web3.sha3 but still there were some issues.

Now, this Nodejs package and solidity's sha3 behaves same.

In order to use it, you will have to include it inside package.json as shown below -

"solidity-sha3": "https://github.com/nalinranjan/solidity-sha3/tarball/master"

and then run

npm install

After that if you want to use solidity-sha3 package in your test cases, you can import it like this -

const sha3 = require('solidity-sha3').default;

Hope this helps.