antazoey

`TransactionAPI might be over-specified ` : Care to elaborate on this one?

Thank you for adding this info! I agree, those fields only matter during serialization and can be handled at the implementation level.

i dont want to have to specify the python-version, so CI is blocked by https://github.com/ApeWorX/github-action/pull/33/files ill release the gh action after that and itll advance us here

frontend is unable to use the ABIs because of a bug in core Ape, fixed here: https://github.com/ApeWorX/ape/pull/2190

> cc @antazoey, maybe we can add a config item to `node` in core called like `has_websocket: true` What about something like this: https://github.com/ApeWorX/ape/pull/2194?

> I was trying/expecting something like that. I would suggest having the three parameters, uri and http_url could be use indistinctly: I was considering this as well, and either deprecating...

> Option 1 would need all event definitions exposed in `ContractContainer` objects (signifying an event with no contract address), which would require some changes in ape (cc @antazoey for your...

I am not sure what you mean! This package is not node software; it merely transforms data received from Ethereum nodes and creates pydantic models from them. As far as...

> If I want to use API `trace-replaytransaction`, should I use Geth? If I run a light node, can I replay any of the transactions in previous blocks? Honestly, I...

Closing as it not related to `evm-trace`, the package