Web3.js: getTransactionReceipt should include status if it's present in the rpc response.

Created on 24 Oct 2017 · 9Comments · Source: ChainSafe/web3.js

After Byzantium rolled out the getTransactionReceipt rpc call returns also status field which indicates if the transaction passed or not: https://github.com/ethereum/wiki/wiki/JavaScript-API#web3ethgettransactionreceipt. I think it should be added to the existing output of the function inside web3.

Source

michalwarda

👍5

Most helpful comment

```json
"config": {
"chainId": 15,
"homesteadBlock": 0,
"eip150Block": 0,
"eip155Block": 0,
"eip158Block": 0,
"byzantiumBlock": 0,
"daoForkSupport": true
}

Mobelis on 10 Feb 2018

👍9

All 9 comments

Indeed, that would be great to have.

kot-begemot on 26 Oct 2017

Good news, you can have it already. Make sure your geth client version is at least 1.7.3 or above.

kot-begemot on 28 Oct 2017

@kot-begemot @michalwarda
no status
geth client version 1.7.3

ShengkunZhang on 25 Jan 2018

no status in mac os
geth-darwin-amd64-1.7.3-4bb3c89d

this is a test in private net

> eth.getTransactionReceipt("0xb8314bbdd1394e65abe5f5f011fd6b668e31156ac2b901752384c1c74f16db89")
{
  blockHash: "0xb701d5b83f4bed349912144ce9f8116fd43192f27d5ecc11f12d12e0972ff6d1",
  blockNumber: 15343,
  contractAddress: null,
  cumulativeGasUsed: 21000,
  from: "0xddd24f735ebb48421577c3f538ba421168649862",
  gasUsed: 21000,
  logs: [],
  logsBloom: "0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
  root: "0xd79aa239640d0d497f319579ef328c5d8d63604539acb10896ffb2512bc7b284",
  to: "0x51533a6e1de29c8e69ac063a659054b337a5ce49",
  transactionHash: "0xb8314bbdd1394e65abe5f5f011fd6b668e31156ac2b901752384c1c74f16db89",
  transactionIndex: 0
}

sbwdlihao on 25 Jan 2018

👍1

on the main network, I can get this field when txhash
is '0x23ec45f5530ca118ebcc1189706b46092d81147c0972434c4fd08967200764c6' ,
but not get 'status' when txhash is '0xeacb0daa203bddfcb515b2ee0982b58ca296b6100760824cc2b2d06f5f5fa6c4'
why is that? i can't understand

ShengkunZhang on 26 Jan 2018

Someguy in stackoverflow once said that to get the status property, you need to set, in the genesis file, what is the byzantin block. Not sure if it's true though.

floriancastelain on 26 Jan 2018

👍1

```json
"config": {
"chainId": 15,
"homesteadBlock": 0,
"eip150Block": 0,
"eip155Block": 0,
"eip158Block": 0,
"byzantiumBlock": 0,
"daoForkSupport": true
}

Mobelis on 10 Feb 2018

👍9

With byzantiumBlock record in genesis file, geth (1.8.3 in my case) returns expected status field.