Skip to content

valoper: unify duplicate per-valoper profile fetch (signing address + server type) #106

Description

@louis14448

Context

Code review of branch fix/valoper-signing-address-moniker (moniker resolution by signing address). Non-blocking follow-up.

Problem

Two code paths independently fan out one RPC call per valoper to fetch the same valoper profile render on every moniker refresh:

Each profile is therefore fetched twice per refresh cycle, doubling RPC round-trips for the same data.

Suggested fix

Unify into a single per-valoper fetch that parses both Signing Address and Server Type from one render, shared by both consumers.

Aside

The parse-format doc comment at health.go:~415 is now stale: the render uses - Operator Address: / - Signing Address:, not - Address: / - PubKey:.

Severity: medium (RPC efficiency / duplication).

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions