Turns out fragments from the misc category don't get their contents displayed, they just get the numbers listed in a "Miscellaneous internal changes" section.
Yeah, as far as I know, someone did this intentionally. I added an "internal" section to trinity that shows towncrier content here: https://github.com/ethereum/trinity/blob/62a85b1d3c89908c37fd62d9c4370dc8e3b139e2/pyproject.toml#L34-L37 -- the idea is that it's only of interest to contributors rather than users. Then misc would be for trivial changes, like maybe changing flake8 rules and updating the repo. @veox
18 days later, ACD is noisy because of the difficulty bomb. :/
TL;DR: There might be an out-of-schedule call on Friday.
py-evm... I want to do essentially what is done in this exercise: https://easythereentropy.wordpress.com/2014/06/04/understanding-the-ethereum-trie/ -- but using
pythereum, and using the nice boilerplate project template that you have in the cookbooks. My question is where in the
py-evmAPI or source would I find the logic that does the same thing
pyethereum? Or, perhaps I'm totally going about this the wrong way, in which case my question is even more general: What's a good starting place for simple DB/State/Trie understanding of the evm?
Istanbul(and a couple other things) is released:
I have a feeling someone'll have to take over PR #1885 from me, or provide a lot of guidance.
lint failures are all for improper definitions/returns in low-level API classes:
VirtualMachineAPI; and some related abstract classes.
Take a look at this CI job most errors are an either-or choice, and I don't know which one is "correct".
eth/chains/base.py:250: error: Unexpected keyword argument "chain_context" for "VirtualMachineAPI" eth/abc.py:2270: note: "VirtualMachineAPI" defined here
which means something unexpected may be happening.
@/all Muir Glacier support is here:
<Christoph> @Pet3ris I'm afraid I can not answer this without diving into the code myself. One thing I suggest is to run py-evm with log level
0 to get full tracing output. Then you'll see output such as: https://gist.github.com/cburgdorf/41ce3a9c9502d2f194c9e54454e6a689
You can search for the output in Py-EVM and sprinkle the code paths with
breakpoint() statements and then use the debugger to examine from there. That's how I'd approach it.
vm.state.coinbaseetc., but I'd like to find something like
vm.current_transaction.computation.memoryto get other elements