neoneo-go/pkg/rpc/client
Roman Khimov 0da0bb21ee rpc: make getnextvalidators behavior compliant with C# node
Turns out, our getnextvalidators implementation already works the way
getcandidates is supposed to work, but original getnextvalidators works a bit
differently. It only returns validators, it doesn't return Active flag (all
of them are active) and it represents votes as a number. So for the maximum
compatibility:
 * drop non-validator keys from getnextvalidators server-side
 * drop Active flag client-side (sorry, it doesn't exist)
 * allow unmarshalling old answers along with the new one

This technically breaks `query candidates` CLI command, but it'll be fixed
when getcandidates are to be introduced.
2022-07-01 14:52:02 +03:00
..
nns [#2442] English Check 2022-05-04 19:48:27 +03:00
client.go rpc: improve RPC Client initialization 2022-05-06 14:15:59 +03:00
doc.go rpc: update docs of RPC client 2022-01-17 12:00:56 +03:00
doc_test.go rpc: adjust client documentation 2021-09-08 17:53:09 +03:00
helper.go [#2442] English Check 2022-05-04 19:48:27 +03:00
native.go [#2442] English Check 2022-05-04 19:48:27 +03:00
nep.go [#2442] English Check 2022-05-04 19:48:27 +03:00
nep11.go [#2442] English Check 2022-05-04 19:48:27 +03:00
nep17.go [#2442] English Check 2022-05-04 19:48:27 +03:00
policy.go rpc: carefully review places where Client.cache.initDone is used 2022-02-22 12:52:14 +03:00
rpc.go rpc: make getnextvalidators behavior compliant with C# node 2022-07-01 14:52:02 +03:00
rpc_test.go rpc: improve RPC Client initialization 2022-05-06 14:15:59 +03:00
wsclient.go rpc: improve WS connection closure error a bit 2022-06-06 12:58:42 +03:00
wsclient_test.go rpc: add ability to get WSClient connection closure error 2022-05-24 11:29:19 +03:00