@chenzhitong please take a look to this solution, I think that verification it's quite important to replicate the logic around modules.

We've played a little with neo-project/neo-modules#378 and I think this is really needed to do it right.

@chenzhitong please take a look to this solution, I think that verification it's quite important to replicate the logic around modules.

Brother, have a cold Coke.

Can it be solved by creating mocked IVerifiable?

Can it be solved by creating mocked IVerifiable?

Take a look at neo-project/neo-modules#378 (comment), I don't think we can make anything useful without real Transaction. Signature check is something expected to be used in verification context and it needs real data.

Can you provide some code on how you plan to call it? I want to see if there are other ways.

Can you provide some code on how you plan to call it? I want to see if there are other ways.

https://github.com/neo-project/neo-modules/pull/378/files#diff-b7c84ee5f6c8ef2d64f5942c80e7cf30024bc0ebfe006f02cc2a2b9c0842ba65R88

I didn't find where it calls TryCreateVerifyEngine. @Tommo-L

We want to add a InvokeContractVerify method in rpc server.

var tx = new Transaction{ Witnesses =[new Witness ]}
var witnessIndex = 0
if (Helper.TryCreateVerifyEngine(tx, snapshot.clone(), scriptHash, witnessIndex, MaxVerificationGas), out ApplicationEngine engine)
{
      JObject json = new JObject();
      json["script"] = Convert.ToBase64String(contract.Script);
      json["state"] = engine.Execute();
      json["gasconsumed"] = new BigDecimal(engine.GasConsumed, NativeContract.GAS.Decimals).ToString();
      json["exception"] = GetExceptionMessage(engine.FaultException);
}

Maybe add a method LoadContractMethod() in ApplicationEngine? And it automatically load _initialize if it exists.

LoadContractMethod() can be used in both Verification and Application triggers.

Maybe add a method LoadContractMethod() in ApplicationEngine? And it automatically load _initialize if it exists.

LoadContractMethod() can be used in both Verification and Application triggers.

@shargon what do you think?

@shargon what do you think?

I will do it

@erikzhang @Tommo-L please take a look

Maybe we should modify CallContractInternal() to use LoadContract() too.

Maybe we should modify CallContractInternal() to use LoadContract() too.

I think that it's ok like this because CallContractInternal is more complex.

@superboyiii tested?

@superboyiii tested?

Tested on my local within Native contract's methods. It works well.