API inconsistency in netmap #91

New issue

Open

opened 2025-12-28 18:12:30 +00:00 by sami · 1 comment

sami commented

2025-12-28 18:12:30 +00:00

Owner

Originally created by @roman-khimov on GitHub (May 18, 2023).

One can get network settings or node info via the netmap service, but there is no way to change any of them. API tries to hide blockchain details, but fails to do that because changes require good old Neo transactions via JSON-RPC connections.

Originally created by @roman-khimov on GitHub (May 18, 2023). One can get network settings or node info via the netmap service, but there is no way to change any of them. API tries to hide blockchain details, but fails to do that because changes require good old Neo transactions via JSON-RPC connections.

sami added the

enhancement

labels

2025-12-28 18:12:30 +00:00

sami commented

2025-12-28 18:12:31 +00:00

Author

Owner

@cthulhu-rider commented on GitHub (Feb 22, 2024):

also nspcc-dev/neofs-api@dcead71f81/netmap/service.proto (L37-L43) allows to request only the current network map, while https://pkg.go.dev/github.com/nspcc-dev/neofs-contract@v0.19.1/netmap#SnapshotByEpoch is time-based

@cthulhu-rider commented on GitHub (Feb 22, 2024): also https://github.com/nspcc-dev/neofs-api/blob/dcead71f810afa7043e48476fdf3b70025fce751/netmap/service.proto#L37-L43 allows to request only the current network map, while https://pkg.go.dev/github.com/nspcc-dev/neofs-contract@v0.19.1/netmap#SnapshotByEpoch is time-based