Skip to content

1.14: Two upstreams share the same priority #242

@PDVJAM

Description

@PDVJAM

Upgraded to 1.14 and see the following in logs:

2023-06-06 15:23:52.964 | WARN  |   PriorityForkChoice | Two upstreams share the same priority. It can cause an unpredicted behaviour of the Dshackle. Check config for alchemy and infura, both have 10 priority

But the config is actually has different priorities for alchemy and infura upstreams:

    - id: alchemy
      chain: ethereum
      role: secondary
      priority: 20
      options:
        disable-validation: true
        validation-interval: 60
      connection:
        ethereum:
          rpc:
            url: "https://eth-mainnet.g.alchemy.com/v2/${ALCHEMY_KEY}"
    - id: infura
      chain: ethereum
      role: primary
      priority: 10
      options:
        disable-validation: true
        validation-interval: 60
      connection:
        ethereum:
          rpc:
            url: "https://mainnet.infura.io/v3/${INFURA_DA_USER}"
          ws:
            url: "wss://mainnet.infura.io/ws/v3/${INFURA_DA_USER}"

Seems like a small bug.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions