Skip to content

Gnosis block-explorer links point to dead gnosischa.in (should be beaconchain.gnosischain.com) #63

Description

@NandyBa

Summary

The Gnosis block-explorer URL used by the web3signer "brain" points to https://gnosischa.in, which has been offline for months. Every explorer link in the Gnosis brain UI (per-validator links, the multi-validator "Dashboard" button, etc.) therefore leads to a dead site.

Verification

$ curl -s -o /dev/null -w '%{http_code}\n' https://gnosischa.in
000            # dead (connection fails)

$ curl -s -o /dev/null -w '%{http_code}\n' https://beaconchain.gnosischain.com
200            # working, maintained Gnosis beacon-chain explorer (beaconcha.in instance)

Where

The dead URL is hardcoded as the Gnosis blockExplorerUrl in the brain — both the backend network config (packages/brain/dist/modules/config/networks/gnosis.js) and the built UI bundle (uiBuild/assets/index-*.js). Links are constructed as <blockExplorerUrl>/validator/<index>, <blockExplorerUrl>/dashboard?validators=<indices>, etc.

Suggested fix

Replace the Gnosis blockExplorerUrl https://gnosischa.in with https://beaconchain.gnosischain.com — the maintained beaconcha.in instance for Gnosis, which uses the same URL/API paths.

Secondary issue with the same fix: the multi-validator "Dashboard" button builds <explorer>/dashboard?validators=<indices>. On beaconchain.gnosischain.com that ?validators= form 302-redirects to a bare /dashboard, dropping the validators (empty page). The path form <explorer>/dashboard/<indices> returns 200 and shows the validators, so it's worth switching the link construction to the path form as well.

Environment

  • Package: DAppNodePackage-web3signer-generic (web3signer-gnosis brain)
  • Network: Gnosis

🐛 Bug flagged by NandyBa, reported by Claude.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions