> ## Documentation Index
> Fetch the complete documentation index at: https://docs.molpha.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Payloads

> The signed data artifact that moves from Molpha nodes to applications.

A Molpha payload is the portable proof object produced by one signing round. It is the thing applications verify.

## Payload components

| Component          | Purpose                                                                      |
| ------------------ | ---------------------------------------------------------------------------- |
| `DataUpdate`       | The data being attested: feed ID, registry version, quorum, value, timestamp |
| `SchnorrSignature` | The aggregate signature, commitment, and signer bitmap                       |
| Verifier args      | Chain-specific encoding generated by the SDK                                 |

## Why it is portable

The signed message intentionally omits `chainId`. Solana, EVM, and Starknet verifiers check the same domain-separated message, signer selection, registry snapshot, and aggregate Schnorr signature.

## What verification proves

Verification proves that enough eligible registered nodes signed the exact payload. It does not prove that your application should accept the value forever.

Consumers must still check:

* Feed identity (`feedId`)
* Freshness (`canonicalTimestamp`)
* Replay protection where needed
* Value bounds and decoding
* Expected quorum (`signaturesRequired`)

## Field-level reference

See [Payload Schema](/reference/payload-schema).