libotony
libotony
> But output and error are already returned as part of `callTracer`. If efficiency is a concern one option I can think of is to allow `callTracer` an option to...
I also have a second option upon decoding the revert reason. It's better decoding outside of `geth`.
> So, I have a patch which adds the revert reason to the call tracer: https://github.com/s1na/go-ethereum/tree/calltracer/revert. It builds on #25430 which adds a `onlyTopCall` option to call tracer. When this...
BTW, feel free to close this once #25430 is merged
https://vechainaddress.abyteahead.com/
You can try [connex-repl](https://github.com/vechain/connex-repl)
There are some scenarios will make high disk load(read operation in this case): 1. re-synchronization 2. on-going pruning 3. intensive requests of query blocks/txs/state by RESTful API
Usually there the node does not perform that high disk load, can you check if there is another program performing requests to the RESTful API and whether the high io...
https://docs.vechain.org/thor/learn/transaction-calculation.html#total-gas-price
> 这个合约开源了么 https://github.com/vechain/ThorNode-contracts