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

[dependabot]

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

Release notes

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

Liquidation

This is a hotfix release to fix t4 testnet incompatibility at block 1589202. The actual problem was found and fixed during 0.99.0 development cycle, but 0.99.0 is expected to be incompatible with t4 testnet. This release allows to continue working with it as well as mainnet (and contains some other fixes for known problems). It does not require resynchronizing a node.

Improvements:

• double call to WSClient.Close() method won't cause a panic (#2420)

Bugs fixed:

• Rules scope considered as invalid in binary representation (#2452)
• incorrect compressed P2P message could lead to panic (#2409)
• notary-assisted transaction could be in inconsistent state on the Notary node (#2424)
• WSClient panics if request is made after connection breakage (#2450)
• Rules scope JSON representation wasn't compatible with C# implementation (#2466)
• JSONized Rules scope could only contain 15 conditions instead of 16 (#2466)

Karstification

We've decided to release one more 3.1.0-compatible version bringing all of the new features and bug fixes made (along with complete support for Windows platform) before going into full 3.2.0 compatibility. It's important for us to give you more stable and flexible environment for the ongoing hackathon. Contract bindings generator might be very useful for anyone operating with already deployed contracts written in other languages, while the node itself can now be configured for lightweight operation, keeping only the data relevant for the past MaxTraceableBlocks, no more and no less. Current public networks don't benefit from it yet with their large MaxTraceableBlocks setting, but they're growing every day and it's just a matter of time when this feature will start making a difference. And sorry, but this release is again faster than the previous one.

We recommend updating, but if your node is not public and you don't specifically want to play with new things brought by it you might as well wait for the next one. It requires resynchronization and 0.99.0 will do too because of planned protocol changes.

New features:

• protocol extension allowing to change the number of validators in existing network (#2334)
• MPT garbage collection mechanism allowing to store a set of latest MPTs, RemoveUntraceableBlocks setting now activates it by default unless KeepOnlyLatestState is used (#2354, #2360)
• NEP-11/NEP-17 transfer data garbage collection (#2363)
• Go bindings generator based on contract manifests (#2349, #2359)

Behavior changes:

• some RPC client functions for divisible NEP-11 changed signatures using slice of bytes now instead of strings for IDs (#2351)
• heavily refactored storage and dao package interfaces (#2364, #2366)
• support for Go 1.18 added, 1.15 dropped (#2369)

Improvements:

• additional CLI tests (#2341)
• defer statement is now compiled more effectively (#2345)
• defer statement can be used in conditional branches now (#2348)
• new tests for divisible NEP-11 contract (#2351)
• all tests failing on Windows platform are fixed (#2353)
• RPC functions now accept integers larger than 2^64 from strings (#2356)
• 10-35%% improvement in bulk block processing speed (node synchronization) depending on machine and configuration (#2364)
• reworked VM CLI fixing Windows incompatibility and UTF-8 bugs (#2365)
• incompletely signed transaction JSONs now also contain hash (#2368)
• RPC clients can now safely be used from multiple threads (#2367)
• additional tests for node startup sequences (#2370)
• customizable notary service fee for Notary extension (#2378)
• signers passed into RPC methods can now contain rules (#2384)
• compiler tests now take less time (#2382)
• some fuzzing tests added (#2399)

Bugs fixed:

• test execution result wasn't checked for CLI invocations that saved transaction into file (#2341)

... (truncated)

Changelog

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

0.98.3 "Liquidation" (07 May 2022)

This is a hotfix release to fix t4 testnet incompatibility at block 1589202. The actual problem was found and fixed during 0.99.0 development cycle, but 0.99.0 is expected to be incompatible with t4 testnet. This release allows to continue working with it as well as mainnet (and contains some other fixes for known problems). It does not require resynchronizing a node.

Improvements:

• double call to WSClient.Close() method won't cause a panic (#2420)

Bugs fixed:

• Rules scope considered as invalid in binary representation (#2452)
• incorrect compressed P2P message could lead to panic (#2409)
• notary-assisted transaction could be in inconsistent state on the Notary node (#2424)
• WSClient panics if request is made after connection breakage (#2450)
• Rules scope JSON representation wasn't compatible with C# implementation (#2466)
• JSONized Rules scope could only contain 15 conditions instead of 16 (#2466)

0.98.2 "Karstification" (21 Mar 2022)

We've decided to release one more 3.1.0-compatible version bringing all of the new features and bug fixes (along with complete support for Windows platform) made before going into full 3.2.0 compatibility. It's important for us to give you more stable and flexible environment for the ongoing hackathon. Contract bindings generator might be very useful for anyone operating with already deployed contracts written in other languages, while the node itself can now be configured for lightweight operation, keeping only the data relevant for the past MaxTraceableBlocks, no more and no less. Current public networks don't benefit from it yet with their large MaxTraceableBlocks setting, but they're growing every day and it's just a matter of time when this feature will start making a difference. And sorry, but this release is again faster than the previous one.

We recommend updating, but if your node is not public and you don't specifically want to play with new things brought by it you might as well wait for the next one. It requires resynchronization and 0.99.0 will do too because of planned protocol changes.

New features:

• protocol extension allowing to change the number of validators in existing network (#2334)
• MPT garbage collection mechanism allowing to store a set of latest MPTs, RemoveUntraceableBlocks setting now activates it by default unless KeepOnlyLatestState is used (#2354, #2360)
• NEP-11/NEP-17 transfer data garbage collection (#2363)
• Go bindings generator based on contract manifests (#2349, #2359)

... (truncated)

Commits

• 0b05007 CHANGELOG: release 0.98.3
• 7dc0404 transaction: fix maxSubitems handling in JSON scope unmarshaller
• c410219 transaction: fix Rules stringer, it's WitnessRules in C#
• b1f74b5 rpc: avoid panic during request after WS connection is closed
• a7fe85a services: fix changing of main tx size of Notary request
• d68f57b rpc: avoid panic on double-call to *WSClient.Close()
• 92a2ec5 network: check compressed payload size in decompress
• 5a6cda3 github: add ability to manually trigger publishing workflow with latest tag
• af7e4ce github: adjust Docker image publishing workflows
• 11bfb55 core: consider Rules witness scope as valid
• 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)

[dependabot]

Superseded by #209.