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

Test IR change with main chain role change #943

Open
roman-khimov opened this issue Jan 27, 2025 · 2 comments
Open

Test IR change with main chain role change #943

roman-khimov opened this issue Jan 27, 2025 · 2 comments
Labels
feature Completely new functionality I2 Regular impact S4 Routine U2 Seriously planned

Comments

@roman-khimov
Copy link
Member

Is your feature request related to a problem? Please describe.

I'm always frustrated when we don't have tests for some core NeoFS things.

Describe the solution you'd like

Test IR change in 4-node IR scenario with main chain. IR is controlled by the designation contract on main chain, it's the same as IR set initially, but main chain committee can set it to any other list of nodes and FS chain must follow this change. IR includes CNs, both change in this setting.

Additional context

neo-project/neo#2267

@roman-khimov roman-khimov added feature Completely new functionality I2 Regular impact S4 Routine U2 Seriously planned labels Jan 27, 2025
@evgeniiz321
Copy link
Contributor

@roman-khimov questions:

  1. how to get the hash of the designation contract?
  2. as far as I understand I need to invoke designateAsRole function, but with what arguments? (designateAsRole int:16 [ {keys_str} ] -- {script_hash} ? )
  3. from IR side - how can I check that fs chain reflected the state of the designation contract (and how soon this can happen? next epoch?)

@roman-khimov
Copy link
Member Author

roman-khimov commented Feb 3, 2025

  1. 0x49cf4e5378ffcd4dec034fd98a174c5491e395e2
  2. Yes, it's an ID of role and an array of keys. Signed by the committee (in your case it should 1/1 for the main chain since you only have one validator).
  3. Get the committee from FS chain, check for logs. Not sure IR exports any metrics for it. neo-exported technically can do it, but we don't use it currently. IIRC it can take an epoch, but let's check.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature Completely new functionality I2 Regular impact S4 Routine U2 Seriously planned
Projects
None yet
Development

No branches or pull requests

2 participants