Introducing Muon - General-Purpose Validation Layer for Web3

Ecosystem
1

Hey everyone,

I’m Ross, working on Muon—a general-purpose validation layer for Web3. We’ve been building on Avalanche but are exploring Polkadot as a potential home, and wanted to introduce the project and get community feedback.

The problem we’re solving

Smart contracts can’t access external data or verify cross-chain state without trusted intermediaries. Current oracle solutions are inflexible—they push predetermined data feeds rather than letting developers define custom validation logic. This limits what dApps can actually build.

How Muon works

Instead of fixed data feeds, Muon lets developers deploy programmable micro-validators (we call them MuonApps) that can fetch, process, and cryptographically sign any data from any source. These run on a decentralized network using FROST threshold signatures and rotating subnets.

The flow is straightforward: dApp requests data → micro-validators process and sign it → proof gets verified on-chain. No waiting for oracle callbacks, no predetermined feeds.

“We’re live on Avalanche mainnet, following a 2,000+ node testnet.”

Why Polkadot

A few things caught our attention:

  • Substrate has native Schnorr signature support, which aligns directly with our FROST-based cryptography

  • The parachain model means validation infrastructure could serve the entire ecosystem, not just one chain

  • There’s a clear gap in flexible validation tooling here

We’re looking at building a Substrate pallet for native proof verification, plus MuonApps tailored to Polkadot use cases (cross-chain verification, price feeds, VRF).

Links

Curious to hear thoughts from the community. What validation or oracle gaps are parachains running into? Are there specific use cases where this kind of programmable validation would help?

1 Like