ixje

> if you were to emit the event in your _deploy function in your contract. Order would be the same. That's not what I'm suggesting. I'm suggesting to put https://github.com/neo-project/neo/blob/a7db45c5364453b828445a541e4ce1d2dcaf9aec/src/Neo/SmartContract/Native/ContractManagement.cs#L103...

> `_deploy` can `ABORT` and it can `THROW`, so we can say that the contract is not yet deployed until it's done. At the same time `ContractManagement` will fail the...

> On TestNet T5 i don't even get `Transfer` event. Is this normal? What node you accessing? That is not normal. http://seed1t5.neo.org:20332

> Me neither, but some lazily coded thing that expects its deployment event in `events[1]` for your case can theoretically exist. At the same time this behavior can be easily...

The problem is I can't `jsonSerialize` a pretty simple and valid StackItem. I first have to figure out what items I have to base64 encode. That to me breaks the...

Thanks @cschuchardt88 but this issue is something that needs to be resolved for all nodes, not just my use-case. The main problem is that there is data on the chain...

single format would be my vote

Can we re-open this? This is the perfect example of wrong type with no VM failure https://github.com/neo-project/neo-devpack-dotnet/issues/769 that could have been prevented

> i am not sure neo fundation still have the legacy chain data available According to the post linked they should > "A final snapshot of the Neo Legacy network...

> [@ixje](https://github.com/ixje), have you tried to analyze remaining address verification scripts? Do we have any irregular ones, not using CHECKSIG/CHECKMULTISIG? @roman-khimov I have not. I don't seem to recall this...