Skip to main content
Smart contracts consume Molpha by verifying a self-contained signed payload. You do not need to run a node, trust a relayer, or maintain a per-chain feed contract.

What your contract receives

Every chain receives the same logical artifact:
  • DataUpdatefeedId, registryVersion, signaturesRequired, value, canonicalTimestamp
  • SchnorrSignature — aggregate scalar, commitment, and signersBitmap
The payload proves that the selected Molpha node quorum signed exactly that data. Your contract still enforces freshness, replay policy, and feed identity.

EVM

Full guide: Verify on EVM.

Solana

Use one of two patterns:
  1. Read the latest maintained Feed account for low-latency consumption.
  2. Verify a fresh payload directly with the molpha-verifier Rust crate when the decision needs point-in-time proof.
Full guide: Read and Verify on Solana.

Starknet

Use the Cairo verifier with the same signed payload. The SDK can build Starknet-ready arguments from a gateway result. Full guide: Verify on Starknet.

Consumer checklist

  • Verify the payload before using the value.
  • Check feedId against the feed you intended to consume.
  • Enforce canonicalTimestamp freshness.
  • Track consumed payloads if replay matters.
  • Decode value according to the feed schema.

Next steps

EVM verifier

Solidity structs, registry layout, and gas notes.

Solana verifier

Feed PDA layout, submit_data_update, and direct Rust verification.

Payload schema

Field-level reference for the signed artifact.