2019-01-25 17:41:43 +00:00
|
|
|
# Roadmap for neo-go
|
|
|
|
|
|
2019-09-18 09:06:10 +00:00
|
|
|
This defines approximate plan of neo-go releases and key features planned for
|
2022-04-20 18:30:09 +00:00
|
|
|
them. Things can change if there is a need to push a bugfix or some critical
|
2019-10-25 15:30:17 +00:00
|
|
|
functionality.
|
2019-09-18 09:06:10 +00:00
|
|
|
|
2020-02-06 18:35:43 +00:00
|
|
|
## Versions 0.7X.Y (as needed)
|
|
|
|
|
* Neo 2.0 support (bug fixes, minor functionality additions)
|
|
|
|
|
|
2024-05-21 09:51:33 +00:00
|
|
|
## Version 0.107.0 (~Jun-Jul 2024)
|
2023-12-29 13:19:48 +00:00
|
|
|
* protocol updates
|
2024-05-21 09:51:33 +00:00
|
|
|
* bug fixes
|
|
|
|
|
* node resynchronisation from local DB
|
|
|
|
|
* CLI library upgrade
|
2022-11-10 13:18:59 +00:00
|
|
|
|
2023-12-29 13:19:48 +00:00
|
|
|
## Version 1.0 (2024, TBD)
|
2022-11-10 13:18:59 +00:00
|
|
|
* stable version
|
|
|
|
|
|
|
|
|
|
# Deprecated functionality
|
|
|
|
|
|
|
|
|
|
As the node and the protocol evolve some external APIs can change. Usually we
|
|
|
|
|
try keeping backwards compatibility for some time (like half a year) unless
|
|
|
|
|
it's impossible to do for some reason. But eventually old
|
|
|
|
|
APIs/commands/configurations will be removed and here is a list of scheduled
|
|
|
|
|
breaking changes. Consider changing your code/scripts/configurations if you're
|
|
|
|
|
using anything mentioned here.
|
|
|
|
|
|
2023-04-06 16:33:09 +00:00
|
|
|
## GetPeers RPC server response type changes and RPC client support
|
|
|
|
|
|
|
|
|
|
GetPeers RPC command returns a list of Peers where the port type has changed from
|
|
|
|
|
string to uint16 to match C#. The RPC client currently supports unmarshalling both
|
|
|
|
|
formats.
|
|
|
|
|
|
2024-05-21 09:51:33 +00:00
|
|
|
Removal of Peer unmarshalling with string based ports is scheduled for Jun-Jul 2024
|
|
|
|
|
(~0.107.0 release).
|
2023-04-20 02:46:19 +00:00
|
|
|
|
|
|
|
|
## `NEOBalance` from stack item
|
|
|
|
|
|
|
|
|
|
We check struct items count before convert LastGasPerVote to let RPC client be compatible with
|
|
|
|
|
old versions.
|
|
|
|
|
|
2024-05-21 09:51:33 +00:00
|
|
|
Removal of this compatiblility code is scheduled for Jun-Jul 2024.
|
2023-05-10 14:10:56 +00:00
|
|
|
|
|
|
|
|
## `serv_node_version` Prometheus gauge metric
|
|
|
|
|
|
|
|
|
|
This metric is replaced by the new `neogo_version` and `server_id` Prometheus gauge
|
|
|
|
|
metrics with proper version formatting. `neogo_version` contains NeoGo version
|
|
|
|
|
hidden under `version` label and `server_id` contains network server ID hidden
|
|
|
|
|
under `server_id` label.
|
|
|
|
|
|
2024-05-21 09:51:33 +00:00
|
|
|
Removal of `serv_node_version` is scheduled for Jun-Jul 2024 (~0.107.0 release).
|
2023-08-15 20:53:29 +00:00
|
|
|
|
|
|
|
|
## RPC error codes returned by old versions and C#-nodes
|
|
|
|
|
|
|
|
|
|
NeoGo retains certain deprecated error codes: `neorpc.ErrCompatGeneric`,
|
|
|
|
|
`neorpc.ErrCompatNoOpenedWallet`. They returned by nodes not compliant with the
|
|
|
|
|
neo-project/proposals#156 (NeoGo pre-0.102.0 and all known C# versions).
|
|
|
|
|
|
2024-05-21 09:51:33 +00:00
|
|
|
Removal of the deprecated RPC error codes is planned for Jun-Jul 2024 (~0.107.0
|
|
|
|
|
release).
|
2023-12-29 11:33:46 +00:00
|
|
|
|
|
|
|
|
## Block based web-socket waiter transaction awaiting
|
|
|
|
|
|
|
|
|
|
Web-socket RPC based `waiter.EventWaiter` uses `header_of_added_block` notifications
|
|
|
|
|
subscription to manage transaction awaiting. To support old NeoGo RPC servers
|
|
|
|
|
(older than 0.105.0) that do not have block headers subscription ability,
|
|
|
|
|
event-based waiter fallbacks to the old way of block monitoring with
|
|
|
|
|
`block_added` notifications subscription.
|
|
|
|
|
|
|
|
|
|
Removal of stale RPC server compatibility code from `waiter.EventWaiter` is
|
2024-05-21 09:51:33 +00:00
|
|
|
scheduled for Jun-Jul 2024 (~0.107.0 release).
|
