The signers of a N3 transaction can specify the scope of their signatures. By default, signatures are CalledByEntry meaning "The signature is only effective to the contract script called by Entry". For example, the signer of a contract invoking ContractManagement.Deploy would not be effective for the _deploy method in the contract being deployed.
The signers of a N3 transaction can specify the scope of their signatures. By default, signatures are CalledByEntry meaning "The signature is only effective to the contract script called by Entry". For example, the signer of a contract invoking ContractManagement.Deploy would not be effective for the _deploy method in the contract being deployed.
Same issue neo3 visual tracker has. https://github.com/ngdenterprise/neo3-visual-tracker/issues/89