Track last update epoch of v2 node #64

New issue

Closed

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

sami commented

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

Owner

Originally created by @roman-khimov on GitHub (Feb 13, 2025).

Originally assigned to: @smallhive on GitHub.

I'm always frustrated when we don't export some useful data about nodes. We also need to update to v0.21.0 contracts.

Describe the solution you'd like

contracts 0.21.0 have a last update epoch for v2 nodes. We need to track both versions for now and export additional field for v2 candidates.

Additional context

https://github.com/nspcc-dev/neofs-contract/pull/462
https://github.com/nspcc-dev/neofs-contract/pull/445

Originally created by @roman-khimov on GitHub (Feb 13, 2025). Originally assigned to: @smallhive on GitHub. ## Is your feature request related to a problem? Please describe. I'm always frustrated when we don't export some useful data about nodes. We also need to update to v0.21.0 contracts. ## Describe the solution you'd like contracts 0.21.0 have a last update epoch for v2 nodes. We need to track both versions for now and export additional field for v2 candidates. ## Additional context https://github.com/nspcc-dev/neofs-contract/pull/462 https://github.com/nspcc-dev/neofs-contract/pull/445

sami

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

closed this issue
added the
enhancement

S3

I3

U2
labels

sami commented

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

Author

Owner

@roman-khimov commented on GitHub (Mar 19, 2025):

There is a UseNodeV2 network configuration flag that should be used, if it's not on we're using v1 map, if it's on --- v2 with additional data.

@roman-khimov commented on GitHub (Mar 19, 2025): There is a `UseNodeV2` network configuration flag that should be used, if it's not on we're using v1 map, if it's on --- v2 with additional data.