Closed plainerman closed 6 years ago
@uldaman could you take a look at it? I am not really familiar with the internal workings of thor.
There is no way to directly meet this requirement in thor api. So here are two options:
For full support it would probably be better to implement it in web3-gear natively? What is your view on it?
In our original scenario, only the lowest level of api was provided, and the business was resolved by the client itself. But if it is to make it compatible with Ethereum, it is reasonable for web3-gear
to support this parameter. I will do this.
I have done this on feature-full-tx
branch, you can pull it down and test it, hope to receive your feedback..
87a31356a710450edb34025aadbb2d802a8d7b43
Works great with web3j! Thank you very much.
eth_getBlockByHash
andeth_getBlockByNumber
specify an additional parameter that allows to return the full transaction objects instead of only the hashes of the transactions. These parameters are already specified, but the actual request ignores this parameter and only returns the hashes.