feat: add BridgeNode facilitator (Solana self-facilitation) - #1098
Open
BridgeNode-cc wants to merge 1 commit into
Open
feat: add BridgeNode facilitator (Solana self-facilitation)#1098BridgeNode-cc wants to merge 1 commit into
BridgeNode-cc wants to merge 1 commit into
Conversation
Contributor
|
@BridgeNode-cc is attempting to deploy a commit to the Merit Systems Team on Vercel. A member of the Team first needs to authorize it. |
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.
Summary
Add BridgeNode (https://bridgenode.cc) as an x402 facilitator.
BridgeNode is an AI inference bridge for AI agents — pay-per-request LLM inference via x402 on Solana USDC, with self-facilitation (in-process facilitator, fee sponsorship). This is a resubmission of #1078 with on-chain settlement evidence.
Changes
packages/external/facilitators/src/facilitators/bridgenode.ts— new facilitator config:BHMDv3ri3LBEZjEzJgDZeUiguVX7LmsCstTXbM3dL8rN(USDC)dateOfFirstTransaction: 2026-08-07 (first self-facilitated settlement)/.well-known/x402, facilitator block withkind: both)packages/external/facilitators/src/facilitators/index.ts— export registrationpackages/external/facilitators/src/lists/all.ts— added to the validated listapps/scan/public/bridgenode.jpg— facilitator logo (same asset served at https://bridgenode.cc/logos/bridgenode.jpg)Evidence: real, on-chain-verified settlement volume
The x402-list.com indexer (independent, on-chain verification) reports for this address:
Public source:
https://x402-list.com/api/v1/facilitators/bridgenode—verification: "on-chain",settler_count: 1.Why x402scan shows 0 transactions for this origin
The BridgeNode origin is already registered here (
7f221b2b-f7a3-4f69-a737-f6c55ea9d24d, verified), but its self-facilitated settlements are invisible to the sync indexer because the Solana transfer sync only scans known facilitator addresses (signer_pubkeys = [facilitatorConfig.address]insync/transfers/trigger/chains/solana/bigquery/query.ts). Since BridgeNode's settler address is not yet in the facilitator list, its 768 tx/30d are never indexed — a chicken-and-egg: the volume bar cannot be observed until the facilitator is registered.Adding this entry makes the existing on-chain volume visible immediately; the address uniqueness is enforced by the existing
validateUniqueFacilitatorscompile-time check.Notes
extra.feePayer).solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp, USDC mintEPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v.