Describe the bug
#2849 brings back the strict contract script checking during contract deploy and update. This patch was checked for the mainnet against hardforks creation (see #2849 (comment)), and it's confirmed that #2849 doesn't cause any states differences in mainnet.

However, in NeoGo we've had this strict script check before the #2849 and it's currently enabled in NeoGo 0.101.2 running in T5. A couple of days ago we've faced with the issue nspcc-dev/neo-go#3049: our T5 node stopped accepting blocks since 2272533 height.

We've checked the roots of this problem, it's caused by the fact that strict contract script check is enabled in our node. Since #2849 is included into 3.6 release, it will break the current T5. We either need a hardfork for T5 that enables contract script checking code starting from some height or we need to deploy a new testnet after 3.6 release. Otherwise current T5 will be broken by 3.6 release and won't be able to accept new blocks after 2272533.

To Reproduce
Please, see the checking results in nspcc-dev/neo-go#3049 (comment).

Expected behavior
Testnet should function normally after 3.6 release.

Platform:

• Version: 3.5.0