Erik Zhang

We need to explain what the contract is supposed to do and give the best practices for doing it in one step using `CheckWitness`.

Maybe you can transfer neo to multiply addresses?

I think this can solve the problem. https://www.eecs.harvard.edu/~michaelm/postscripts/aller2006.pdf > This paper describes dynamic bit reassignment, an approach that allows the size of the fingerprint to flexibly change with the load...

Needs to translate into English.

@lightszero Can you provide an English version?

@lightszero Is this PR still updated?

In this case, I think you should use `WitnessScope.CustomContracts`.

https://github.com/neo-project/neo/issues/2772#issuecomment-1162616415

The sender of a deployed contract is not necessarily the owner of the contract. A contract may have logic to modify its owner. Maybe `CheckWitness(contract.Hash)` directly?

> The hash and the possible owner? Just need `hash`. If `hash` is equal to `AppalicationEngine.CallingScriptHash`, `CheckWitness` returns `true`; otherwise, the contract's `verify` method will be called.