Skip to main content

Coordination Transaction

A Coordination Transaction is the core execution process in Silvana’s Coordination Layer - a high-throughput, low-latency blockchain responsible for orchestrating and sequencing user-defined logic across the stack. After a proof is generated, this layer ensures the pipelined transaction is ordered, executed, and recorded as part of the rollup’s state progression and runs in the following flow:

  • Transaction sequencing: determines execution order for smart contracts tied to user-defined logic.
  • Execution coordination: triggers contract calls on the Execution Layer according to the sequence.
  • Proof handling: accepts cryptographic proofs and metadata from Agents; optionally performs recursive proof aggregation (Merge Execution) to reduce settlement payloads.
  • Event emission: emits transaction-level events for downstream processing and traceability.
  • State progression: computes the intermediate rollup state commitment and tracks proof-to-coordination references.

Each Coordination Transaction Includes:

  • a unique transaction hash;
  • a coordination-specific block number;
  • a reference list of proof CIDs';
  • an intermediate coordination hash representing the rollup’s current state.

Example of a Coordination Transaction.

Note

Coordination Layer is Silvana’s key innovation underpinning the Silvana Rollup, known for showing the ultra-fast transaction execution of optimistic rollups and the security of zk rollups. Coordination Layer ensures near-instant transactions by running execution on fast blockchains.

Get insights into Coordination Transactions by exploring them on Silvascan.

Metadata​

As a user transaction runs with a provable record, its metadata is logged to establish links between all transaction types. Each settlement transaction is associated with:

  • A unique L1 hash;
  • A block number and nonce;
  • The associated proof digest (e.g., proof_data_availability_digest);
  • Any referenced coordination hash or data availability fields.

Custom transaction metadata includes:

  • blockNumber: Coordination-layer block index (28)
  • number_of_transactions: How many settlement transactions this proof supports (3)
  • sequences: The range of coordination transaction sequence numbers covered ([49, 51])
  • settlement_hash: The L1 state commitment (Mina devnet) updated by this proof
  • nonce: A unique job identifier (626)
  • proof_data_availability: CID for the proof payload used for DA
  • proof_data_availability_digest: Coordination-layer event reference for DA
  • au_proof_data_availability: Additional proof DA CID (for aggregated proofs)
  • coordination_hash: The new rollup state commitment on the coordination layer
  • linkId: A reference tying this metadata record back to the agent job (ID "28").

Through this process, Silvana guarantees state anchoring, verifiability, and data retrievability. Even if internal Silvana infrastructure were to fail, any third party could reconstruct and verify the rollup’s state using public data and L1 commitments.