Skip to main content
Molpha is a pull-native oracle protocol. A network of independent nodes fetches data from an off-chain API, converges on a canonical result, and signs it once with a single aggregate Schnorr signature. That one signed payload verifies on Solana, on every supported EVM chain, and on Starknet — without re-signing, repackaging, or per-chain feeds.

​
Why it works everywhere

The signed message deliberately omits chainId. The node network signs (jobId, value, canonicalTimestamp, …) once, and every chain’s verifier checks that exact same message. Verification is a pure cryptographic check against the registered node set — no bridge, no relayer, no per-chain attestation.

​
What you get

  • Arbitrary data feeds — any accessible API, not just token prices. A job commits to a URL and parsing logic; the network keeps the result verified.
  • Cryptographically verified values — every value is backed by a threshold aggregate Schnorr signature from the registered node set, verified on-chain at read or write time.
  • Two consumption modes — read the latest cached value from a Solana Feed account, or verify a fresh signed payload statelessly in your own transaction.
  • USDC-denominated pricing — subscriptions are paid in USDC on Solana. No protocol token, no token-price exposure.

​
How responsibilities split across chains

Solana is the canonical chain. The node registry, job definitions, subscriptions, and feed values live in the Molpha Solana program. EVM chains and Starknet run stateless verifiers. Each deployment carries only a mirror of the node public-key set (versioned snapshots) plus a lightweight verify() entrypoint. No job state, no round state, no feed state — everything arrives in calldata and is checked cryptographically. A successful verify() on a stateless chain proves who signed what — that a threshold of the deterministically selected node set signed the exact payload. It does not, by itself, prove the value is fresh: historical registry versions stay verifiable forever, so consumers always enforce their own freshness and replay policy. See the Security Model for the full trust boundary.

​
Where to start

Quickstart

Subscribe, create a job, and submit a verified value on Solana Devnet in five minutes.

How Molpha works

The end-to-end flow from API call to verified on-chain value.

EVM verification

The stateless Solidity verifier: registry, selection, plain-sum Schnorr.

Starknet verification

The Cairo port — bit-for-bit parity with the EVM pipeline.