Jimmy
Jimmy
> Wait, wait, wait a minute! As much as I love this change you can't just roll it out with the nearest hardfork. Remember all the pain of #2810. We...
> Will this affect calls between contracts? Yes, it will. That is why this pr may only take effect to contracts that are depolyed or updated after the next hardfork,,,,,,...
> Is not rebased? I see changes from other PRs I am tring to fix, but still have no clue, changed that are already merged into the base branch still...
> I prefer an exception instead of a denial of service, but this will be solved using memory instead of reference counter https://github.com/neo-project/neo-vm/issues/202 @shargon is a good point, should we...
> > > I prefer an exception instead of a denial of service, but this will be solved using memory instead of reference counter [neo-project/neo-vm#202](https://github.com/neo-project/neo-vm/issues/202) > > > > >...
> `Integer` & `FastInteger`. It's confused. > > I have another optimization, and maybe more clearer. sure, just go ahead work on your pr. that one can keep as draft...
no longer needed, close to clean up the pr list, such that we can focus on active prs.
@roman-khimov I know, I have being evaluating it in the past few days. First of all, yes, verifywitness is part of the cause (removing it can improve the speed by...
in the meanwhile, it is actually an issue of how does a light node verify the authenticity of a given block without syncing the whole blockchain.
should be able to be fixed easily if we add the.execution result to the storage.