Remove obsolete "Core Tools"#338
Open
EndymionJkb wants to merge 6 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
mendesfabio
reviewed
May 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Removed the three core-tool widgets (Batch Swap, Pools, Smart Order Router) under docs/tools/core, along with their VuePress components, providers, and ABIs.
They were V2-era and unfixable without a full rebuild: pinned to @balancer/sdk 0.0.3 (V2-only), fetching pools from The Graph's decommissioned hosted service (the mainnet endpoint now returns 301, which is exactly why no pool could be selected and no route was found), and encoding calldata against the V2 Vault (batchSwap / joinPool / poolId).
The Pools widget's join/exit forms also still used the legacy @balancer-labs/sdk. A V3 version would be a new build rather than an edit, so per the "broken content goes" stance we removed them.
The same workflows are documented for V3 in the SDK guides (Swapping with the SOR and SDK, Swapping custom paths with the Router, and the add/remove-liquidity SDK tutorials), which pull pinned code via and don't depend on live infrastructure. The /tools hub and its external tool links remain.
To rebuild this for V3, we'd need:
BalancerApi+Swap/Router). This is application work, not a docs edit.api-v3.balancer.fi(plus an RPC) that someone has to monitor and fix when the API or SDK changes. This live dependency is what broke the widgets in the first place.Probably not happening at this point.
Resolves #253