build(deps): bump github.com/nspcc-dev/neo-go from 0.78.3 to 0.101.0

[dependabot]

Bumps github.com/nspcc-dev/neo-go from 0.78.3 to 0.101.0.

Release notes

Sourced from github.com/nspcc-dev/neo-go's releases.

Shortness

This release delivers an important fix for block execution application logs and requires a resynchronization, therefore it's 0.101.0 (even though it's also 3.5.0-compatible). It fixes some other minor problems as well (the other most notable change probably is in the compiler), so we recommend upgrading.

Improvements:

• updated golang.org/x/* dependencies (#2854)
• CLI help and required flags handling fixes (#2852)
• transfer data storage optimization (#2865)
• network's magic number is stored (and checked against the config on startup) in the DB now, reducing potential for node operator errors (#2867)

Bugs fixed:

• in rare cases nodes could request an invalid number of blocks from peers leading to disconnect (#2846)
• outdated documentation fixes (#2860, #2876)
• application logs for blocks that contained GAS spends for transaction fees contained (and returned from getapplicationlog RPC) incorrect (off by one) values for amount in Transfer events; transaction application logs were not affected by this, but data returned to RPC event subscribers could potentially be (#2865)
• findstates RPC returned an error instead of an empty data set for valid contracts that have no data (unlike C# node, #2866)
• miscompiled shadowed range loop variable definition (#2871)
• missing (compared to C# node) explicit (even though null) 'exception' field in the getapplicationlog RPC output from server (#2872)

Chaptalization

This is a tiny update that 99.99% of users can easily skip. The reason for this release is the need to fix compatibility with the NeoFS mainnet sidechain and have some stable version to be used there. In any other case it can be ignored, but if you still decide to upgrade you don't need to resynchronize.

Behaviour changes:

• Aspidochelone fork is made to include ContractManagement native contract deploy/update methods call flags change, initially it was an unconditional part of 0.99.0 NeoGo release (or 3.2.0 C# version), but this behavior is incompatible with the NeoFS mainnet sidechain; the change to the fork logic does not affect any other public networks (mainnet/testnet) and any new networks that have Aspidochelone enabled since block 0 (#2848)

Improvements:

• more robust NEP-11 divisibility check in the RPC server code (#2841)
• microoptimization for some debug log messages (#2842)
• additional fuzz tests for integer serialization and script parsing code (#2851)

Centuplication

A 3.5.0-compatible version of NeoGo with all the appropriate protocol updates and a number of other changes. The most notable ones are configuration updates. New features and some long-standing inconsistencies required for some changes and this release brings them with it. Old configurations are still supported and will work the same way (except for one minor exception in VerifyBlocks that is only supposed to be used for tests/development), but we'd like to highlight that all of the old settings will be removed in ~6 months, so please review these updates and update your configurations. For public networks the best way to go is to take the new versions from the "config" directory and then adjust for particular scenario if needed.

This release requires a complete resynchronization due to native contract changes, so please schedule your updates appropriately.

New features:

• System.Runtime.LoadScript syscall (and appropriate smart contract interops) allowing to load/run dynamic code (#2719)
• PUSHT/PUSHF VM instructions allowing for simpler/cheaper booleans (#2770)
• ContractManagement native contract was extended with ID->hash mappings and getContractById and getContractHashes methods (#2702, #2837)
• LogLevel application configuration option that can be changed on SIGHUP (#2831)
• additional type data generated by the compiler that then can be used by the RPC bindings (SDK/contract wrapper) generator, this allows for complex types (structures/arrays/maps) to be easily represented/handled in contract-specific RPC code (#2828)
• multiaddress listeners for all services and P2P, this changes the old Address/Port (and AnnouncedPort for P2P) configuration scheme to more generic Addresses list, the old configuration is still supported, but is deprecated and will be removed in future node versions (#2827, #2839)

Behaviour changes:

• Aspidochelone fork block for NeoFS sidechain mainnet configuration is rescheduled again (#2823, #2830)
• Blockchain's GetHeaderHash() method now accepts uint32 for parameter (#2814)
• pre-0.97.3 and pre-0.99.0 deprecated compatibility fields and logic were dropped from the result.Version (getversion RPC result) structure (#2786)
• SecondsPerBlock protocol configuration variable was replaced with TimePerBlock allowing for sub-second precision, SecondsPerBlock is still supported, but will eventually be removed (#2829)
• AttemptConnPeers, BroadcastFactor, DialTimeout, ExtensiblePoolSize, MaxPeers, MinPeers, PingInterval, PingTimeout, ProtoTickInterval settings were moved into the new P2P section, timing parameters now use Duration type allowing for more human-friendly values in many cases, old parameters are still supported, but will eventually be removed (#2827)
• consensus (dBFT) is configured as a separate service now that can be enabled/disabled (and can work in "watch only" mode without a wallet), the old direct "UnlockWallet" specification in "ApplicationConfiguration" is still supported, but is deprecated and will be removed in future versions (#2832)
• GarbageCollectionPeriod, KeepOnlyLatestState, RemoveUntraceableBlocks, SaveStorageBatch and VerifyBlocks settings were moved from ProtocolConfiguration to ApplicationConfiguration; old configurations are still supported, except for VerifyBlocks which is replaced by SkipBlockVerification with inverted meaning (and hence an inverted default) for security reasons; this also affects NewBlockchain and neotest APIs (#2833)

... (truncated)

Changelog

Sourced from github.com/nspcc-dev/neo-go's changelog.

0.101.0 "Shortness" (13 Jan 2022)

This release delivers an important fix for block execution application logs and requires a resynchronization, therefore it's 0.101.0 (even though it's also 3.5.0-compatible). It fixes some other minor problems as well (the other most notable change probably is in the compiler), so we recommend upgrading.

Improvements:

• updated golang.org/x/* dependencies (#2854)
• CLI help and required flags handling fixes (#2852)
• transfer data storage optimization (#2865)
• network's magic number is stored (and checked against the config on startup) in the DB now, reducing potential for node operator errors (#2867)

Bugs fixed:

• in rare cases nodes could request an invalid number of blocks from peers leading to disconnect (#2846)
• outdated documentation fixes (#2860, #2876)
• application logs for blocks that contained GAS spends for transaction fees contained (and returned from getapplicationlog RPC) incorrect (off by one) values for amount in Transfer events; transaction application logs were not affected by this, but data returned to RPC event subscribers could potentially be (#2865)
• findstates RPC returned an error instead of an empty data set for valid contracts that have no data (unlike C# node, #2866)
• miscompiled shadowed range loop variable definition (#2871)
• missing (compared to C# node) explicit (even though null) 'exception' field in the getapplicationlog RPC output from server (#2872)

0.100.1 "Chaptalization" (28 Dec 2022)

This is a tiny update that 99.99% of users can easily skip. The reason for this release is the need to fix compatibility with the NeoFS mainnet sidechain and have some stable version to be used there. In any other case it can be ignored, but if you still decide to upgrade you don't need to resynchronize.

Behaviour changes:

• Aspidochelone fork is made to include ContractManagement native contract deploy/update methods call flags change, initially it was an unconditional part of 0.99.0 NeoGo release (or 3.2.0 C# version), but this behavior is incompatible with the NeoFS mainnet sidechain; the change to the fork logic does not affect any other public networks (mainnet/testnet) and any new networks that have Aspidochelone enabled since block 0 (#2848)

Improvements:

• more robust NEP-11 divisibility check in the RPC server code (#2841)
• microoptimization for some debug log messages (#2842)
• additional fuzz tests for integer serialization and script parsing code (#2851)

... (truncated)

Commits

• 22fc8d1 Merge pull request #2877 from nspcc-dev/chlog-101
• ee3257d CHANGELOG: release 0.101.0
• c46b7a9 Merge pull request #2876 from nspcc-dev/improve-consensus-doc
• e2bd767 config: improve 4 CN docker configs, three nodes are enough
• 1e35387 docs: fix the MinPeers consensus requirements
• efbef42 Merge pull request #2873 from nspcc-dev/drop-circleci
• 40ef567 Merge pull request #2872 from nspcc-dev/fix-missing-exception-in-applog
• babc44b Merge pull request #2871 from nspcc-dev/fix-shadowed-infinite-loop
• 4862bb9 drop CircleCI support
• 9a6fa84 Merge pull request #2867 from nspcc-dev/store-magic-in-db
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)