Why Ethereum

Security and neutrality [2] enable credible settlement.

  • Liquidity: Operators can borrow against future income

  • Composability: Easy integration with insurance and lending

Deployment model:

  • Ethereum L1 → canonical home for identity, governance, and final settlement checkpoints

  • Ethereum L2s → handle day-to-day interactions with low fees while inheriting L1 security

Gas constraints addressed via:

  • Compact, aggregated attestations with event packing and short code-hash identifiers

  • Artifact storage off-chain with CID-only commitments

  • L2 deployment with blob DA and calldata compression [7]

  • Batched oracle attestations and job resolution to amortize overhead

  • Optional account abstraction for sponsorless robot submissions

Typical attestation payload (quorum aggregate): ~160–220 bytes

  • State changes dominate gas

  • On rollups, calldata costs are much lower while preserving verifiability

  • With blob-based DA (e.g., 4844-style), oracle aggregates can be posted even more cheaply

Ordering risk and MEV effects [11]:

  • Minimized because Morph uses short, single-shot transactions

  • Commit-then-reveal avoids acceptance sniping

Gas and Cost Model

Assuming optimized L2 with calldata compression + blob DA (where applicable), and fees at 1–5% of L1, the following applies:

Table 4: Estimated costs with optimized L2 design

Function

Gas (exec)

Bytes

L2 cost (USD)

postJobLite

45,000

48

≈ $0.03

acceptJob

30,000

24

≈ $0.02

revealAcceptance

20,000

48

≈ $0.02

submitProof (commit)

30,000

64

≈ $0.03

attestAggregate

55,000

48

≈ $0.04

resolve

60,000

48

≈ $0.04