Harry Pierson

This will be addressed as part of the overall Storage Schema Preview work

The [debug info format](https://github.com/ngdseattle/design-notes/blob/master/NDX-DN11%20-%20NEO%20Debug%20Info%20Specification.md) is specified in ngdseattle/design-notes. any changes to the format should have bugs opened up over there. This bug can stay open to track implementing this change...

I am 100% on board with supporting multiple, strongly typed return values in the debug format. However, I want to make sure we have a consistent way of implementing that...

> I'm not sure this approach would work for NEO 2. We can rework something in master branch, of course. I looked at the master-2.x branch neovm code, it appears...

Thanks for reporting this. This is primarily a problem in the generated debug info, rather than the debugger, but neither has been designed to handle variable name reuse like this....

The debugger will deploy the contract to the proto chaim used during debugging, if it isnt already present in the xheckpoint specified in the launch config. The launch configs listed...

I *think* this is a per-language feature. Not sure how debugger can support this generally across languages (yet)

Agree. We still have this issue but it is moot when we remove the user db from core in favor of data sources

A few nitpicks: * I think we should use the term `struct` instead of `namedtype` * Why is `value` a JSON object with a `type` property? Seems needlessly complex. Can...

> I only see `ContractType` extensions there like `Struct` or `Address`, but these can't be backwards compatible with NEP-14 and I'd like to keep that given that the additional type...