Jimmy
Jimmy
@cschuchardt88 conflict
@dusmart @vang1ong7ang may you guys do a security check on this pr since its a large one. Functionality has being reviewed, and is good to move forward.
emmmmm, i definately love this, but many unrelated change right? that part i dont like~~~~
this is for a verified "noverify". first of all, its not 1 hour in c#, far from it, second, even if its 1 hour, why cant we make it 50...
checkingpoints as @shargon said is the solution.
> But you currently can import with noVerify, isn't it? yes, this issue is trying to have a solution to have the speed of "noverify", while make it verifiable.
@AnnaShaleva please check latest update to make it `SignerWithWitness`, @chenzhitong please update the document accordingly, @superboyiii may you please test this pr? expecially the InvokeFunction and InvokeScript that may contain...
@AnnaShaleva updated this pr to mock the complete http request process, now should be able to work without miss any detail.
@shargon @superboyiii
> However, maybe @superboyiii should do a more extensive tests, these changes affects various methods I have updated to make it use existing unit test, without updating the unit test...