Add /stale-bridges, /bridge-search, and /netflows/compare endpoints#489
Merged
Merged
Conversation
vrtnd
approved these changes
Jun 3, 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
2 participants
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.
Three new read-only endpoints to improve observability and discoverability of bridge data.
GET /stale-bridges
Exposes the stale bridge detection logic (previously only sent to Discord) as an API response. Returns bridges and chains that have had no activity for 3 or more days, grouped by bridge name with the number of stale days per chain.
GET /bridge-search?q=&chain=
Search and filter bridges by name or chain. At least one of q (name substring) or chain is required. Eliminates the need for clients to fetch all bridges and filter client-side.
GET /netflows/compare?period=day|week|month&chains=ethereum,arbitrum
Compare netflows for specific chains side by side. Reuses the existing getNetflows query and filters to the requested chains, returning deposited, withdrawn, and net flow per chain. Supports up to 10 chains per request.