[eddiemessiah]

The hole, and the fix

Three bridge routes on the docs sent readers somewhere unsafe, nowhere, or to a product that is shutting down, and several links only worked through redirects.

• Satellite (Axelar) is retired. Axelar's docs say "Satellite has been retired" and point to app.axelar.network. The satellite.money domain now forwards to forsale.godaddy.com/forsale/satellite.money, a domain Axelar no longer controls. This PR removes the Satellite section from build/tools/bridges/bridges.mdx and the Satellite entry from learn/bridged-tokens/bridges.mdx, and drops "Axelar" from the bridge page's description because the page no longer lists an Axelar app. Squid (which routes over Axelar) stays, and Axelar Network stays in the cross-chain messaging list on the overview page.
• Galaxy is offline. galaxy.exchange and galaxy.exchange/swap both return HTTP 402 with X-Vercel-Error: DEPLOYMENT_DISABLED. The section is removed because the deployment is disabled.
• Allbridge is removed. The entry pointed at Allbridge Classic (app.allbridge.io), which Allbridge's docs say "is deprecated and will be stopped in November 2026". Allbridge Core does not list Celo (https://api.core.allbridge.io/token-info returns ETH,POL,ARB,AVA,OPT,BAS,UNI,BSC,TRX,SOL,SRB,SUI,STX), so there is no current Allbridge route to link. The ## AllBridge section, the "Allbridge" mention in the page description, and the bullet on learn/bridged-tokens/bridges.mdx are gone.
• Portal was described as "formerly known as Wormhole". Portal is the bridge app; Wormhole is the protocol it runs on (portalbridge.com: "Powered by Wormhole"). The link text now reads [Portal](https://portalbridge.com/) (built on Wormhole), matching the Transporter entry's pattern.
• Redirected links now point at their final destination, host-only edits with query strings preserved:
  • build/tools/bridges/bridges.mdx: v2.app.squidrouter.com -> app.squidrouter.com (307), jumper.exchange -> jumper.xyz (301), www.usenexus.org -> nexus.hyperlane.xyz (301, then 308)
  • learn/bridged-tokens/bridges.mdx:19, :21 and learn/gas-fees.mdx:27: the same Squid and Jumper host changes

What this does NOT do / residual risk

• No other descriptive copy is rewritten. Some remaining entries still carry wording that AGENTS.md discourages ("seamless"-style adjectives); a style pass on the page is out of scope.
• Portal's Celo support was not re-verified; only its relationship to Wormhole was checked.
• Satellite is not replaced with app.axelar.network: Axelar's docs name it as the current interface but do not say it supports Celo. A maintainer who confirms Celo transfers there can add it back as one section.
• No redirects are needed: no page moved or was deleted. No internal link points at the removed #satellite-axelar, #galaxy or #allbridge anchors.

Issues

Refs: none. No open issue in celo-org/docs covers these bridge links.

Stacking / conflicts

Based on current main (7b8f97c2, after #2368 and the home/ to learn/ move), so the paths above are the post-restructure paths. Independent of the other open PRs: #2375 touches only operate/specification/* and learn/protocol/transactions/overview.mdx; no shared files.

Verification evidence

Diff against main: 3 files changed, 14 insertions, 52 deletions (build/tools/bridges/bridges.mdx, learn/bridged-tokens/bridges.mdx, learn/gas-fees.mdx). Files keep their CRLF line endings.

Outbound links, re-checked 2026-10-08 with curl -sL and a browser user agent:

https://app.squidrouter.com/?chains=10%2C42220     200
https://jumper.xyz/?fromChain=10&toChain=42220     200   (a bare user agent gets 403)
https://nexus.hyperlane.xyz/                       200
https://portalbridge.com/                          200
https://galaxy.exchange/swap                       402   X-Vercel-Error: DEPLOYMENT_DISABLED
https://satellite.money/lander                     -> forsale.godaddy.com/forsale/satellite.money

Leftovers: a case-insensitive search of every .mdx, .md and .json file (excluding node_modules and submodules) for satellite, galaxy, allbridge, usenexus, v2.app.squid and jumper.exchange returns nothing, including docs.json.

mint broken-links --check-redirects on this head (abc13cc4): success, no broken links found, per the round-two review run. The head is unchanged since that run; this update edits only the title and description.

Sources:

Claim	Source
Satellite retired; current Axelar app	https://docs.axelar.dev/resources/satellite/
Allbridge Classic deprecated, stops November 2026	https://docs.allbridge.io/
Allbridge Core live chain list has no Celo	https://api.core.allbridge.io/token-info
Portal is powered by Wormhole	https://portalbridge.com/

Remaining ops steps

None.

Checklist

• Title is the commit message I want on main
• Ships the test that fails on pre-fix code (n/a: docs content change)
• Covers the seam (n/a)
• Error responses audited (n/a)
• Judgement calls flagged above
• mint broken-links --check-redirects passes on the current head (review run on abc13cc4)
• Re-read acceptance criteria of every Closes issue (no Closes)
• Development sidebar links match Closes/Refs above
• README / runbook / examples updated (n/a)
• Lockfile touched (n/a)
• Wallet/provider tree touched (n/a)
• UI touched (n/a)
• Money/security path (n/a)
• No secrets in the diff
• Questions for the maintainer: none

🤖 Generated with Claude Code

[GigaHierz]

head 340cf0d · local ref and API headRefOid match; merged into origin/main a12466b in a scratch checkout: clean, mint broken-links --check-redirects success, check-orphans.sh clean; both changed pages render on :3441 at 1280 and 412x915 with 0 console errors and no Satellite/Galaxy text

Verdict: REQUEST-CHANGES

Thanks for this, and for the unusually careful evidence in the description. The removals are correct and I could reproduce them. There is one entry I'd like handled before merge and one inconsistency the PR creates, both small.

Findings

1. Medium · tooling/bridges/bridges.mdx:90-100 (Allbridge section), tooling/bridges/bridges.mdx:3 (description), home/bridged-tokens/bridges.mdx:23 (learn/bridged-tokens/bridges.mdx:23 on main)

   • Defect: the PR keeps an entry it has itself shown is about to stop working. docs.allbridge.io says "Allbridge Classic is deprecated and will be stopped in November 2026", the link targets Classic (app.allbridge.io), and the live Core chain list has no Celo (I re-ran https://api.core.allbridge.io/token-info: ETH, POL, ARB, AVA, OPT, BAS, UNI, BSC, TRX, SOL, SRB, SUI, STX).
   • Failure scenario: within weeks a reader, or an agent reading llms.txt where the description still advertises "Allbridge", is sent to a bridge that no longer works, which is the same class of problem this PR fixes for Satellite.
   • Fix shape: remove the Allbridge section, the word "Allbridge" in the description, and the Learn-page bullet in this PR. If you would rather leave the decision to the maintainers, a filed issue linked from the PR body is the only other acceptable resolution; a checkbox in the body is not enough. Restoring it later is cheap if Core adds Celo.

2. Medium · learn/bridged-tokens/bridges.mdx:19 and :21 (home/bridged-tokens/bridges.mdx on the PR head), learn/gas-fees.mdx:27 (home/gas-fees.mdx:27 on the PR head)

   • Defect: the title says "fix redirected links", but the same providers are still linked at their redirecting URLs on two other pages. After this PR the Bridge Providers page says https://app.squidrouter.com/ and https://jumper.xyz/ while the Learn bridging page says https://v2.app.squidrouter.com/?... and https://jumper.exchange/?....
   • Failure scenario: one provider, two URLs across pages meant to agree; the next link audit flags the leftover redirects again and the PR title over-promises.
   • Fix shape: change the host on those three lines. I checked that query strings survive both redirects (v2.app.squidrouter.com/?chains=10%2C42220 goes 307 to app.squidrouter.com/?chains=10%2C42220; jumper.exchange/?fromChain=10&toChain=42220 goes 301 to jumper.xyz/?fromChain=10&toChain=42220), so it is a host-only edit. Make it on the path as it exists on main (learn/), see merge notes.

Verified good

• Satellite: https://docs.axelar.dev/resources/satellite/ is titled "Satellite (Retired)" and says "Satellite has been retired. Use Axelar's current interface at app.axelar.network for supported transfers. Do not use satellite.money - that domain is no long[er ...]". curl of satellite.money/lander returns 307 to forsale.godaddy.com/forsale/satellite.money. Removal is right, and not substituting app.axelar.network (HTTP 200, Celo support unconfirmed) is the right call.
• Galaxy: galaxy.exchange/ and /swap both return HTTP 402 with x-vercel-error: DEPLOYMENT_DISABLED. I found no vendor announcement; the evidence is the disabled deployment only. That is enough to remove a link, but I would soften "is not a bridge" in the description: public listings describe Galaxy as a cross-chain swap aggregator. Offline is the reason, not the category.
• Redirected links, old and new with curl -sIL: v2.app.squidrouter.com 307 to app.squidrouter.com 200; jumper.exchange 301 to jumper.xyz 200 (403 with a short user agent, 200 with a full Chrome one, so a bot challenge and not a dead link); www.usenexus.org 301 to usenexus.org 308 to nexus.hyperlane.xyz 200. All three new targets are the canonical hosts.
• Portal wording: portalbridge.com meta description "Powered by Wormhole", author "Wormhole Labs". "(built on Wormhole)" is accurate. Portal's Celo support I could not confirm (page is client-rendered); the PR says the same.
• Leftovers: git grep -i satellite and galaxy over the repo (including docs.json) return nothing. Remaining axelar hits are Squid's description, learn/bridged-tokens/bridges.mdx:56 and tooling/bridges/cross-chain-messaging.mdx (Axelar Network as a messaging protocol); none link to Satellite.
• No page moved or deleted, so no redirect is owed (AGENTS section 2); no orphan produced. No #satellite-axelar or #galaxy anchor is linked anywhere.
• Remaining providers still answer: transporter.io, mach.exchange, smolrefuel.com, layerzero.network, app.allbridge.io all 200.
• Not reproducible, harmless: the body says both files keep CRLF endings; at the base commit file reports plain UTF-8 for tooling/bridges/bridges.mdx. Probably a local autocrlf artefact; the diff is clean.

What the PR got right

• Removal of two dead entries with a rationale for each, and the explicit refusal to guess a replacement URL for Satellite.
• Correcting "formerly known as Wormhole", which was a real factual error.
• An honest residual-risk section (Allbridge, leftover links), which is what made findings 1 and 2 quick to confirm.
• Trimming "Axelar" from the description so llms.txt stays accurate, and keeping the diff to the bridge pages.

Merge-order hazards

• Behind main by 1 commit (the Home to Learn rename, #2367). git merge-tree --write-tree origin/main refs/remotes/pr/2374 is clean: git follows the rename and applies the one-line deletion to learn/bridged-tokens/bridges.mdx (confirmed with a real merge in a scratch checkout). A git rebase origin/main does the same; the only manual step is that the finding-2 edits go in learn/..., not home/....
• #2368 (Build tab) has not landed: tooling/bridges/bridges.mdx is still at that path on main. When it does, it renames this file to build/tools/bridges/bridges.mdx; the PR's edits sit inside a file that stays well over 50% similar, so rename detection should carry them, but whoever merges second should re-run git merge-tree first.
• #2375 touches different files (operate/specification/*); no conflict between the two PRs.

Checks run

mint broken-links --check-redirects: success on the merge with main (the Windows false positives described in the PR body do not reproduce). bash scripts/check-orphans.sh: no orphans. gh pr checks 2374: only GitGuardian and StepSecurity listed, both pass; the repo's mint broken-links workflow does not appear, most likely waiting for maintainer approval for an outside contributor.

[eddiemessiah]

Rebased onto main after #2367. The change that touched home/ now applies to learn/bridged-tokens/bridges.mdx; the rest of the diff is unchanged.

[eddiemessiah]

Previewed in a local live deployment (mint dev, this branch merged with the other open docs fixes, no overlapping files) at desktop 1280px and phone 412px:

• /tooling/bridges/bridges
• /learn/bridged-tokens/bridges

Each page returns 200 and renders the new text, with no horizontal overflow on phone, no broken images and 0 console errors.

[eddiemessiah]

Head abc13cc4. Thanks for the review, Lena. Both findings are fixed, and the description is softened as you suggested.

#	Finding	Status	Where / what changed
1	Allbridge entry kept despite deprecation	FIXED	Removed the ## AllBridge section from build/tools/bridges/bridges.mdx (was lines 90-100), dropped "Allbridge" from its description (line 3), and removed the bullet from learn/bridged-tokens/bridges.mdx:23.
2	Redirecting Squid and Jumper URLs on Learn pages	FIXED	Host-only edits, query strings unchanged: learn/bridged-tokens/bridges.mdx:19 v2.app.squidrouter.com -> app.squidrouter.com; :21 jumper.exchange -> jumper.xyz; learn/gas-fees.mdx:27 v2.app.squidrouter.com -> app.squidrouter.com.
-	"Galaxy is not a bridge" wording in the PR description	FIXED	Now reads "Galaxy is offline and is not a bridge" with a correction that the reason for removal is the disabled deployment, not the category. Nothing else in the body changed.

Re-checked today (2026-10-06, 17:48-17:52 UTC) before removing Allbridge:

• https://docs.allbridge.io/ (HTTP 200): "Allbridge Classic is deprecated and will be stopped in November 2026."
• https://api.core.allbridge.io/token-info (HTTP 200): chains ETH,POL,ARB,AVA,OPT,BAS,UNI,BSC,TRX,SOL,SRB,SUI,STX; no CEL, and the strings "celo" and "42220" appear nowhere in the response.
• The removed link targeted Classic (app.allbridge.io/bridge?...).
• New targets with their query strings, curl -sIL -A "Mozilla/5.0 ... Chrome/130.0": app.squidrouter.com/?chains=10%2C42220&tokens=... 200, jumper.xyz/?fromChain=10&...&toChain=42220&... 200, no further redirects.

Checks on abc13cc4:

• git merge-tree --write-tree origin/main HEAD: clean.
• mint broken-links --check-redirects (Windows, npx -y mint@latest): reports found 575 broken links in 122 files, byte-for-byte the same flagged-entry set as an unmodified checkout of origin/main (7b8f97c2); every flagged entry is an internal path to a page that exists, and no external URL is flagged. This is the Windows false-positive behaviour from the PR body; I could not get a Linux run working locally, so your run on the merge and CI are the authoritative pass.
• scripts/check-orphans.sh: no orphans (run as a line-for-line Node port since jq is not installed here; 225 nav pages, 224 page files).
• git grep -ni "allbridge\|v2\.app\.squidrouter\|jumper\.exchange": no matches. The only remaining "Jumper Exchange" strings are the product name, linked to jumper.xyz.
• mint dev --port 3475: /build/tools/bridges/bridges, /learn/bridged-tokens/bridges and /learn/gas-fees each return 200 at 1280x900 and 412x915 and the served HTML contains app.squidrouter.com and jumper.xyz (where linked) and no "Allbridge"; no horizontal overflow, 0 console errors. Screenshots of all six views are saved locally and I can attach them if useful.

Push was a rebase: #2368 merged at 17:44 UTC, so the branch is now on 7b8f97c2 and the bridge-page edits follow the rename to build/tools/bridges/bridges.mdx (git carried the earlier commit across cleanly; tooling/bridges/bridges.mdx no longer exists on the branch). Pushed with --force-with-lease. Net diff vs main: 3 files, +14/-52.

[GigaHierz]

head abc13cc · local ref and API headRefOid match; PR merge-base is origin/main 7b8f97c (no merge needed), git merge-tree --write-tree clean; mint broken-links --check-redirects success, check-orphans.sh clean; both bridge pages served from the PR on :3611 (no Satellite/Galaxy/Allbridge text, new Squid/Jumper hosts in the rendered hrefs)

Verdict: REQUEST-CHANGES

Thank you for the quick turnaround, and for rebasing onto the new learn/ and build/ layout. Both substantive findings from the last round are fixed and I could reproduce your evidence for each. One small item is left: the PR description now describes the code as it was before the follow-up commit.

Status of earlier findings

1. Allbridge kept although Classic stops in November 2026 and Core has no Celo: FIXED. build/tools/bridges/bridges.mdx no longer has the ## AllBridge section, the description no longer says "Allbridge" (line 3), and the bullet is gone from learn/bridged-tokens/bridges.mdx. Re-checked: docs.allbridge.io still reads "Allbridge Classic is deprecated and will be stopped in November 2026", and https://api.core.allbridge.io/token-info still returns ETH, POL, ARB, AVA, OPT, BAS, UNI, BSC, TRX, SOL, SRB, SUI, STX with no Celo. Removal is the right call.
2. Redirecting Squid and Jumper hosts on the Learn pages: FIXED. learn/bridged-tokens/bridges.mdx:19 and :21 and learn/gas-fees.mdx:27 now use app.squidrouter.com and jumper.xyz, host-only edits with the query strings untouched. curl -sIL with a browser user agent: the three new URLs (with their full query strings) return 200 with no further redirect. Old to new, for the record: v2.app.squidrouter.com/?chains=10%2C42220 307 to app.squidrouter.com/?chains=10%2C42220; jumper.exchange/?fromChain=10&toChain=42220 301 to jumper.xyz/?fromChain=10&toChain=42220. The rendered Learn pages carry the new hrefs.
3. Galaxy "is not a bridge" wording: FIXED where it matters. The PR body now strikes the claim and says the reason is the disabled deployment. The original commit message (689865e) still says "it is a DEX, not a bridge", but the repository squash-merges with the PR title as the commit and a blank message body, so that sentence does not reach main. Nothing to change.

New findings

1. Low · PR description and title (not a file)
   • Defect: the description was not updated after the follow-up commit, so several statements are now untrue of the head: "Allbridge is unchanged" and the first "Remaining ops steps" box (decide on Allbridge); "The same redirected Squid and Jumper URLs remain ... left for a follow-up" and the second box; file paths tooling/bridges/bridges.mdx, home/bridged-tokens/bridges.mdx, home/gas-fees.mdx (they are build/tools/bridges/bridges.mdx, learn/bridged-tokens/bridges.mdx, learn/gas-fees.mdx); "Branched off main (50ed71d)" and the #2368 / #2258 stacking notes (both landed); "Questions for the maintainer: should the Allbridge entry go now". The diff stat quoted in the body (2 files, 11 insertions, 36 deletions) is now 3 files, 14 insertions, 52 deletions. The title also omits the Allbridge removal, and the title becomes the squash commit on main.
   • Failure scenario: a maintainer deciding on the merge reads that Allbridge is still listed and that a decision is pending, or a later reader of git log sees a commit message that does not mention one of the three removals.
   • Fix shape: edit the body to match the head (paths, the Allbridge and Squid/Jumper sections moved from "does NOT do" to "fix", tick or delete the two ops boxes, drop the maintainer question) and retitle to something like docs(bridges): remove retired Satellite, offline Galaxy and deprecated Allbridge, fix redirected links. Re-paste the mint broken-links result for the head.

Verified good

• Satellite: https://docs.axelar.dev/resources/satellite/ is titled "Satellite (Retired)" and says "Satellite has been retired. Use Axelar's current interface at app.axelar.network for supported transfers. Do not use satellite.money - that domain is no longer controlled by Axelar." curl -sIL https://satellite.money/lander returns 307 to forsale.godaddy.com/forsale/satellite.money. Not substituting app.axelar.network (Celo support not confirmed) is correct.
• Galaxy: galaxy.exchange/ and /swap both return HTTP 402 with x-vercel-error: DEPLOYMENT_DISABLED.
• Leftovers: a case-insensitive search of every .mdx, .md and .json file (excluding node_modules and submodules) for satellite, galaxy, allbridge, usenexus, v2.app.squid and jumper.exchange returns nothing, including docs.json.
• Learn and Build pages agree: both give Squid as app.squidrouter.com, Jumper as jumper.xyz, Portal as Wormhole-based, and Transporter as Chainlink CCIP; neither lists Satellite, Galaxy or Allbridge. The lists differ in membership (Learn has LayerZero, Mach, USDT0; Build has Layerswap and Hyperlane Nexus), which was already the case and is not a contradiction.
• Remaining outbound links all return 200: nexus.hyperlane.xyz, portalbridge.com, layerzero.network, www.transporter.io, www.mach.exchange, smolrefuel.com/?outboundChain=42220, app.squidrouter.com, jumper.xyz.
• Portal wording "(built on Wormhole)" fixes the earlier "formerly known as Wormhole" error.
• No page moved or deleted, so no redirect is owed (AGENTS section 2); no orphan; no #satellite-axelar, #galaxy or #allbridge anchor is linked anywhere. Rendered section ids on the Build page are superbridge, layerswap, squid-router, jumper-exchange, hyperlane-nexus, portal-wormhole, transporter-chainlink-ccip, smolrefuel.
• CI: gh pr checks 2374 lists GitGuardian and the three StepSecurity checks, all passing. The repository's mint broken-links workflow does not appear; it is most likely waiting for maintainer approval of the first-time-contributor run. Locally it passes on the head.

What the PR got right

• Three dead or misleading entries removed with a stated rationale each, and no guessed replacement URL for Satellite.
• The "formerly known as Wormhole" correction was a real factual error.
• The follow-up did exactly the narrow edits asked for: host-only changes, query strings preserved, no wording churn.
• The earlier honest residual-risk list is what made the verification quick.

Merge-order hazards

• None. The PR is based directly on current main (7b8f97c) and git merge-tree --write-tree origin/main refs/remotes/pr/2374 is clean. GitHub reports it mergeable, with the merge state BLOCKED pending required checks and review.
• #2375 touches only operate/specification/*; no shared files with this PR.

[eddiemessiah]

Thanks for the second pass, Lena.

Low · PR description and title: fixed. The title now names all three removals (docs(bridges): remove retired Satellite, offline Galaxy and deprecated Allbridge, fix redirected links), since it becomes the squash commit. The description matches the head:

• Allbridge and the Learn-page Squid/Jumper hosts have moved from "does NOT do" into the fix list.
• Paths are now build/tools/... and learn/....
• The base is current main (7b8f97c2), and the docs: merge Build on Celo and Tooling into one Build tab #2368/story: Learn tab — move home/* (plus kept L1 content) to learn/* #2258 stacking notes are gone.
• Both ops boxes and the maintainer question are removed.
• The diff stat reads 3 files, 14 insertions, 52 deletions.

I re-checked the outbound links today: Squid, Jumper (with a browser user agent), Hyperlane Nexus and Portal return 200; Galaxy still returns 402 DEPLOYMENT_DISABLED.

No file changes in this round, so the head is still abc13cc4.

[GigaHierz]

Re-reviewed the current head: the findings from the earlier review are resolved, the diff merges cleanly into current main, and the changed claims still check out.