The engine creates one attestation per verified output. The input oracle verifies the proof format required by the origin chain.

Fill description

The fill description concatenates these fields in order. Fixed-width integers use big-endian encoding. Callback data and context each have a maximum encoded length of 65,535 bytes. The payload hash is keccak256(fillDescription).

Proof tuple

For the EVM FrostInputOracle, the message digest is:
The tuple occupies 128 bytes before hashing: four fields of 32 bytes each. The EVM oracle verifies the FROST Schnorr signature against its immutable secp256k1 group public key. The signature arguments are rx, ry, and z. FROST means Flexible Round-Optimized Schnorr Threshold signatures. Other chain families use their own encodings and signature verification paths. Do not apply EVM signature serialization to Solana or Move transactions.

Origin-specific signatures

The origin chain selects the signature suite because its oracle verifies the proof. The destination chain does not select that suite. Solana and Move use the protocol record ContinuumAttestationV1. The digest is keccak256(preimage). The preimage uses the following fixed layout and big-endian integer encoding. The target discriminator distinguishes Move from Solana. The curve discriminator identifies Ed25519 for these origin families. The wire signer epoch is separate from the signing request’s Attester Network KeyGeneration. Changing the Attester Network key generation does not change this encoded epoch. The engine rejects a Solana oracle with a different signer epoch before signing. Protocol record names and discriminators must remain byte-exact. The EVM oracle does not sign or parse this 291-byte record.

Proof storage

After successful verification, the input oracle records the tuple as proven. The EVM oracle exposes that state through isProven and efficientRequireProven. The escrow requires the relevant proofs before finalisation. The attestation registry stores published signature bytes under the order and output index. Registry publication requires an authorized operator, but publication does not verify the signature bundle. The solver checks signatures before using them. The input oracle verifies the submitted proof on chain.