Avalanche has price oracles. It has identity solutions. It has tokenization infrastructure from Securitize and Ondo. What it doesn't have is a compliance and evidence layer — the infrastructure that tells institutions whether they can actually use what's on the chain.
Today, we're changing that with five focused plugins built specifically for Avalanche's institutional and tokenization narrative.
Institutional Risk Oracle
Returns PASS/WARN/BLOCK for any token. MiCA compliance score, reserve quality, sanctions screening.
On-Chain Evidence Anchor
SHA-256 evidence hashes anchored on C-Chain. Batch anchoring via Merkle roots. Independently verifiable.
Cross-Subnet Compliance Passport
Compliance passports for Avalanche Subnets. Enables institutional subnets to verify counterparty compliance.
These aren't empty contracts. We've seeded them with real compliance assessments:
Any smart contract on Avalanche can now call AvaRisk.isCompliant(tokenAddress) and get a verifiable answer.
Beyond smart contracts, we've deployed five MCP (Model Context Protocol) servers that make compliance data accessible to AI agents and automated systems:
| Plugin | Tools | What It Does |
|---|---|---|
| AvaRisk | 3 | Institutional risk assessment — PASS/WARN/BLOCK per token |
| AvaEvidence | 3 | Anchor & verify evidence hashes on Avalanche |
| SubnetGuard | 3 | Cross-subnet compliance passports & interaction checks |
| AvaRWA | 3 | Due diligence for tokenized assets (BUIDL, USDY, OUSG) |
| AvaAmpel | 3 | MiCA/DORA regulatory readiness for Avalanche protocols |
All servers are live at feedoracle.io/mcp/{plugin}/ and use FeedOracle's 402 billing protocol.
Avalanche's institutional strategy is built on Subnets — Spruce, Evergreen, Intain. But here's the gap: when an institutional subnet wants to interact with another subnet, there's no standardized way to verify the counterparty's compliance status.
SubnetGuard solves this. It provides a compliance passport for each assessed subnet — validator decentralization, contract audit status, stablecoin exposure, governance structure, regulatory readiness. All scored, all verifiable on-chain.
All contracts are written in Solidity 0.8.24, compiled with Foundry (via-IR + optimizer), and verified on Snowtrace. The oracle address can be updated by the contract owner, allowing FeedOracle to push continuous compliance updates on-chain.
Evidence anchoring uses SHA-256 hashes with optional Merkle batch anchoring for cost efficiency. Every hash is independently verifiable — you don't need FeedOracle to confirm the evidence exists.
MCP servers use StreamableHTTP transport with FeedOracle's standard 402 billing protocol and ECDSA evidence signatures.
Call AvaRisk from any Avalanche smart contract, or connect via MCP.
Live Ampel Dashboard →