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.

Sign up for GitHub

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

Jump to bottom

Track last update epoch of v2 node #159

Open
roman-khimov opened this issue Feb 13, 2025 · 0 comments
Open

Track last update epoch of v2 node #159

roman-khimov opened this issue Feb 13, 2025 · 0 comments
Labels
blocked Can't be done because of something enhancement Improving existing functionality I3 Minimal impact S3 Minimally significant U2 Seriously planned
Milestone
v0.13.0

Comments

@roman-khimov
Copy link
Member

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

nspcc-dev/neofs-contract#462
nspcc-dev/neofs-contract#445
@roman-khimov roman-khimov added blocked Can't be done because of something enhancement Improving existing functionality I3 Minimal impact S3 Minimally significant U2 Seriously planned labels Feb 13, 2025
@roman-khimov roman-khimov added this to the v0.13.0 milestone Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
blocked Can't be done because of something enhancement Improving existing functionality I3 Minimal impact S3 Minimally significant U2 Seriously planned
Projects
None yet
Milestone
v0.13.0
Development

No branches or pull requests
1 participant
@roman-khimov