AI agents
Connect an agent to Molpha over MCP in minutes.
Backends
Request and publish signed data with the TypeScript SDK.
Smart contracts
Verify an attestation on EVM, Solana or Starknet.
Molpha currently runs on Solana devnet with verifiers on EVM and Starknet testnets, and the contracts are pre-audit. Don’t secure real value with it yet. See Deployments.
How it works
1
Define a source
Describe the API call and the value to extract. Its
sourceId is the hash of that config, so there is nothing to register. See Sources and feeds.2
Request a round
Pay with a subscription or per request over x402. The gateway stamps the round and dispatches it.
3
Nodes sign once
A deterministically selected group of registered nodes fetches the API independently, agrees on one value, and produces one aggregate signature. See Rounds and attestations.
4
Verify anywhere
Submit the attestation to a Solana
Feed account, or call verify() on EVM or Starknet. Verifiers re-derive the signer selection and check one signature against the node set they mirror.Why it verifies everywhere
- No
chainIdin the signed message. Every verifier checks the same bytes, so the same attestation is valid on every supported chain, with no bridge and no per-chain feed. - The signer set is signed. The bitmap of signers is part of the message and must fall inside the selection that verifiers re-derive themselves.
- Stateless verification. EVM and Starknet verifiers hold only a mirror of the node keys. Everything else arrives in calldata.
- Solana is the canonical chain. The node registry, deposits, subscriptions, rewards and
Feedaccounts live in the Molpha Solana program.
What you get
Verification proves who signed what. Freshness, replay protection and which sources you accept stay your application’s policy: see the consumer checklist.