Ingestion
Source Registry And Signals
Public sources become evidence candidates. Human review is required before partner-facing or Salesforce-synced claims.
Registry
MetaMask docsmedium
developer_docs · weekly · chain metadata, gas display
QuickNode statusmedium
status · hourly · incidents, degraded endpoints
Arc bridge docshigh
official_docs · daily · routes, networks, troubleshooting
Aave governance/GitHubmedium
github_forum · daily · oracle issues, integration blockers
Arcscanhigh
explorer · daily · contract verification, tx evidence
Signals
StargateP0 · High
Route support and transfer troubleshooting need launch gate evidence.
All partnersP1 · High
Arcscan evidence should be required for testnet transactions and verified contracts.
AaveP0 · Medium
Oracle/feed readiness remains the main lending launch gate until real protocol source evidence is attached.
Ramp NetworkP1 · Medium
Ramp and corridor signals should become growth opportunities after real RSS/changelog source is attached.
Adapter Simulation
| Source | Adapter | Field update | Priority | Review |
|---|---|---|---|---|
| MetaMask developer docs | website/docs | chain metadata + gas UX fields | P1 | needs review |
| QuickNode status page | status | endpoint health + incidents | P1 | needs review |
| Stargate route docs | bridge/docs | route readiness + transfer support | P0 | needs review |
| Aave GitHub/governance | github/forum | oracle + risk blockers | P0 | needs review |
| Ramp Network docs | developer_docs | ramp/API/KYC requirements | P1 | needs review |
| Fireblocks developer docs | developer_docs | custody asset support + policy controls | P1 | needs review |