Skip to content

Solana balance routed to helius which lacks getBalance #17

Description

@oritwoen

explorers_balance on chain: solana failed with "Operation getBalance not supported by helius". Same address through nodes_balance on publicnode answered instantly (6fpgynJPg7bSi922YTWHG964eV3UGU2k7chmPgJgdhY1, ~0.0999 SOL).

If a provider can't serve an operation, the router should skip it instead of surfacing its limitation as the call result. Either filter providers by supported operations per chain, or fall through to the next one that can. Right now picking helius for solana makes the tool strictly worse than having no default at all, since I have to know in advance which provider actually works.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions