Conversation
Adds a new /bridges/ page listing the cross-chain bridges and messaging layers that curated assets depend on, seeded from the risk reports: - LayerZero (12 direct + 2 indirect), Chainlink CCIP (4 direct), and Circle CCTP (3 direct + 1 indirect). Each row links to its report and reuses that report's DefiLlama icon. - Per-row Direct/Indirect type badge; indirect rows tinted amber. - Data lives in src/data/bridges.json; icons reuse getAllReports(). Keeps the page in sync with reports via scripts/check_bridges.mjs, wired into dev/build: it fails on dependency slugs with no report and warns on unlisted bridge mentions (resolve via the bridge's ignore list). Update flow documented in reports/skill.md and reports/reassessment/SKILL.md. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
spalen0
marked this pull request as ready for review
July 15, 2026 11:39
…tical order Sort bridges alphabetically by name and have check_bridges.mjs fail the build if they drift out of order, since the page renders in file order. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Their reports carry no DefiLlama link, so the rows fell back to a placeholder. Add optional per-dependency icon overrides in bridges.json: 'icon' (DefiLlama protocol slug) for Apyx (apyx-protocol) and 'iconToken' (token address) for USDG, served via DefiLlama's token-icon CDN. All 22 rows now render a real icon. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Replace the ad-hoc icon/iconToken/iconChain fields with a single reusable 'icon' reference resolved by defillamaIconUrl(): protocol:<slug> | stablecoin:<slug> | token:[<chainId>:]<address> USDG now uses its DefiLlama stablecoin listing (stablecoin:global-dollar) and Apyx uses protocol:apyx-protocol — readable, slug-based, no raw address, and extensible to future assets across DefiLlama categories. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Generalize the report icon pipeline to the same typed DefiLlama refs the Bridges page uses (defillamaIconUrl). Reports whose markdown has no /protocol/ link now resolve via DEFILLAMA_ICON_OVERRIDES: paxos-usdg -> stablecoin:global-dollar superstate-ustb -> protocol:superstate apyx-apxusd -> protocol:apyx-protocol Existing protocol-slug overrides migrated to protocol:<slug> form. USTB/USCC token-icon CDN entries are a shared placeholder (identical hash), so USTB uses the Superstate protocol logo; USCC already resolves via its report's /protocol/bitwise-uscc link. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
Adds a new /bridges/ page mapping the cross-chain bridges and messaging layers that curated assets depend on, seeded from the risk reports. Linked from the header nav (Reports · Tokens · Bridges · Monitoring).
Bridges (alphabetical) and their detected dependencies:
Display
getAllReports()).Data & keeping it in sync
src/data/bridges.json— add a bridge/dependency only when a report actually relies on it.scripts/check_bridges.mjsis wired intodev/build: fails if a dependency slug has no report; warns when a report mentions a bridge keyword but isn't listed (resolve by adding it, or adding the slug to that bridge'signorelist).npm run check-bridgesenforces zero unreviewed mentions in CI.reports/skill.md(Post-Assessment) andreports/reassessment/SKILL.md.Validation
npm run buildpasses — 3 bridges, 22 dependencies, 0 warnings;/bridges/renders with all report links resolving.0x85d4…8Ef3→ LayerZero V2 EndpointV20x1a44…728c), confirming the two indirect LayerZero entries; not CCIP.Notes
🤖 Generated with Claude Code