Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add transactions' input to getBlock RPC response #210

Open
thomasvds opened this issue Jan 31, 2019 · 0 comments
Open

Add transactions' input to getBlock RPC response #210

thomasvds opened this issue Jan 31, 2019 · 0 comments
Labels
enhancement New feature or request

Comments

@thomasvds
Copy link

thomasvds commented Jan 31, 2019

Currently when calling the web3.eth.getBlock() function, the array of transactions that is returned contains only partially correct information about the transactions.

Here is an example transaction retrieved with getBlock(58459):

{ 
    hash: '0xd11822009862abad1279da71eb1a869898a856df6c3325c7c2f6f3ac3a42c982',
    nonce: 20,
    blockHash: '0x0329ae704bb212b6b0de6c2cdac9251a012d70c06d86288554bb2d01e6b33458',
    blockNumber: 58459,
    transactionIndex: 0,
    from: '0xfd972bdA362588C1EDB81Bc22eF3E14E41e9aA60',
    to: '0x7A9C3d6373f11FC50969d7DA5A506623678C79d2',
    value: '0',
    gas: 0,
    gasPrice: '0',
    input: '0x' 
}

However I would have expected that the input field contains the actual transaction inputs (that is, the arguments passed when calling in this case a smart contract method).

This would prove very helpful to get much more details about transactions occurring in a given block, so as to be able to create rich block explorer functionalities.

@eduardonunesp eduardonunesp added the enhancement New feature or request label Feb 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants