Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

API inconsistency in netmap #257

Open
roman-khimov opened this issue May 18, 2023 · 1 comment
Open

API inconsistency in netmap #257

roman-khimov opened this issue May 18, 2023 · 1 comment
Labels
enhancement Improving existing functionality I2 Regular impact S4 Routine U4 Nothing urgent

Comments

@roman-khimov
Copy link
Member

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.

@roman-khimov roman-khimov added enhancement Improving existing functionality U4 Nothing urgent S4 Routine I2 Regular impact labels Dec 20, 2023
@cthulhu-rider
Copy link
Contributor

also

// Returns network map snapshot of the current NeoFS epoch.
//
// Statuses:
// - **OK** (0, SECTION_SUCCESS):
// information about the current network map has been successfully read;
// - Common failures (SECTION_FAILURE_COMMON).
rpc NetmapSnapshot (NetmapSnapshotRequest) returns (NetmapSnapshotResponse);
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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Improving existing functionality I2 Regular impact S4 Routine U4 Nothing urgent
Projects
None yet
Development

No branches or pull requests

2 participants