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

Monitor uses a hardcoded operator with a non-zero realm #10413

Open
steven-sheehy opened this issue Feb 18, 2025 · 0 comments
Open

Monitor uses a hardcoded operator with a non-zero realm #10413

steven-sheehy opened this issue Feb 18, 2025 · 0 comments
Labels
enhancement Type: New feature monitor Area: Monitoring and dashboard

Comments

@steven-sheehy
Copy link
Contributor

steven-sheehy commented Feb 18, 2025

Problem

Monitor uses a hardcoded genesis account 0.0.2 as its operator and should be adjusted to work with non-zero realms.

Solution

  • On startup, retrieve the actual shard and realm from /api/v1/networks?limit=1 response field node_account_id. If the operator ID is the default of 0.0.2, adjust it to the retrieved shard.realm.2. If the operator ID is not the default value, verify the shard and realm match.
  • Change obtainer id in transaction suppliers similarly

Alternatives

No response

@steven-sheehy steven-sheehy added enhancement Type: New feature monitor Area: Monitoring and dashboard labels Feb 18, 2025
@steven-sheehy steven-sheehy moved this from 📋 Backlog to 🏃‍♀ Sprint backlog in Mirror Node (Archived) Feb 18, 2025
@steven-sheehy steven-sheehy changed the title Monitoruse hardcoded 0.0.2 Monitor uses a hardcoded operator with a non-zero realm Feb 18, 2025
@rbarker-dev rbarker-dev moved this to 🏃‍♀ Sprint backlog in Mirror Node Feb 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Type: New feature monitor Area: Monitoring and dashboard
Projects
Status: 🏃‍♀ Sprint backlog
Development

No branches or pull requests

1 participant