Skip to content

fix(statics): correct FLRP transaction explorer URL - #10139

Merged
ArunBala-Bitgo merged 1 commit into
masterfrom
cecho-2694-flrp-explorer
Nov 6, 2026
Merged

ArunBala-Bitgo merged 1 commit into
masterfrom
cecho-2694-flrp-explorer

Conversation

@ralph-bitgo

@ralph-bitgo ralph-bitgo Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

Description

Update the mainnet FLRP transaction explorer prefix in @bitgo/statics, add a transaction-link regression, and document the correction. This sends customers to the P-Chain Explorer instead of the incorrect Flarescan route. Testnet and address links are unchanged; no new dependencies.

Issue Number

CECHO-2694

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • nix develop . --command yarn --cwd modules/statics build passed.
  • nix develop . --command ./node_modules/.bin/mocha --no-config --require tsx modules/statics/test/unit/networks.ts passed (3,285 tests).
  • Ran the built statics package against the ticket transaction ID and verified the resulting URL.
  • nix develop . --command yarn --cwd modules/statics unit-test passed after building workspace prerequisites (41,943 tests). The coverage wrapper reported expand is not a function and produced 0% coverage.
  • Direct access to the explorer was blocked by the sandbox proxy (HTTP 403); the destination matches the ticket's expected URL.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • My code compiles correctly for both Node and Browser environments (Node package build passed; browser build not run)
  • I have commented my code, particularly in hard-to-understand areas (no new explanatory comments needed)
  • My commits follow Conventional Commits and I have properly described any BREAKING CHANGES
  • The ticket or github issue was included in the commit message as a reference
  • I have made corresponding changes to the documentation and on any new/updated functions and/or methods
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

Point mainnet FLRP transaction links at the Flare P-Chain Explorer
so customers can open the correct transaction instead of Flarescan.
Add a transaction-link regression and document the correction.

Ticket: CECHO-2694
Session-Id: 8218b461-62c0-4e6d-b832-f7a0eff2f031
Task-Id: 6cf7a3c4-c07b-4627-aa5e-a145b83203ec
@linear-code

linear-code Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

CECHO-2694

@github-actions

github-actions Bot commented Nov 6, 2026

Copy link
Copy Markdown
Contributor

⚠️ Compatibility checks are failing on Node.js 27-nightly (experimental, non-blocking). This does not block merge, but it signals an incompatibility to fix before this release becomes supported.

View run

@ArunBala-Bitgo
ArunBala-Bitgo marked this pull request as ready for review November 6, 2026 10:28
@ArunBala-Bitgo
ArunBala-Bitgo requested a review from a team as a code owner November 6, 2026 10:28

@claude claude Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Claude Code Review

This repository is configured for manual code reviews. Comment @claude review for a one-time review, or @claude review always to subscribe this PR to a review on every future push.

Tip: disable this comment in your organization's Code Review settings.

@manojkumar138 manojkumar138 left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@ArunBala-Bitgo
ArunBala-Bitgo merged commit cd3efcd into master Nov 6, 2026
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants