format
format copied to clipboard
ethdebug
Smart contract debugging data format – Standards development working group
[copied from matrix] How well should the format account for code deduplication? To do this properly, basically any bytecode based debugging information would really have to be a list (by...
Currently the spec is based only on existing Solidity and Vyper features: > In addition, this proposal is necessarily geared towards the state of the Solidity/Vyper languages as they exist...
How will work progress with this effort? How will we know if work is progressing? Standards groups operate in projects with processes. These processes get documented. Sometimes a meeting schedule...
How is a person to get involved? What do they need to know to participate or observe? (Likely, this follows from #3)
It might be good to compile everyone's wishlist for what this effort needs to succeed.
This project does not currently state any license for public consumption or to inform potential contributors of their rights, if there are any. It's unclear (to me) whether there's any...
It's not yet established, either informally or via any software toolchain, what exactly this group will produce. Presumably, we should produce human-readable documents (for potential future EIP track efforts), as...
This project has not yet established clear goals or desired outcomes at all. While these may broadly be self-evident from the project itself, this project must establish and document clear...