Automata Docs
  • Understanding Automata
    • What is Automata?
      • TEE Coprocessor
      • Proof of Machinehood
        • Optimistic Attestation
        • Zero Knowledge Proof
        • Modular Trust
    • Key terms
  • TEE Overview
    • TEE Prover
    • Multi-Prover AVS (EigenLayer)
      • Operator guide
        • Installation
        • Deposit strategies
        • Opt in to run AVS
        • FAQ
    • TEE Compile
      • Getting Started
      • Vendorizing
      • Attestation Report
    • TEE Builder
      • Block Builder Architecture
      • Stateless Executor
    • Verifiable Random Function
      • Why Automata VRF
      • How does Automata VRF work
      • Attestation
  • Build with PoM
    • Introduction
      • Smart contract libraries
      • Attestations on Verax
      • Frequently asked questions
    • Attestation module
      • Machine Attestation
        • Intel SGX
        • AWS Nitro Enclaves
        • Miscellaneous
      • Device Attestation
        • Yubikey
        • Andriod
        • Apple
        • Windows
        • FIDO U2F Authenticator
      • WebAuthn Attestation
        • WebAuthn Attestation Types
        • Attestation Statements & Privacy Impacts
  • Backed by PoM
    • 1RPC
    • L2Faucet
      • Frequently asked questions
  • Protocol
    • App-Specific Rollup
    • Mainnet
    • Testnet
    • Bridge
      • Bridging Native Tokens from L1 to L2
      • Bridging Native Tokens from L2 to L1
    • Explorer
    • Specification
      • Attestation
      • Attestor
      • Smart Contract
  • Research
    • Account Abstraction
    • Decentralized Randomness
    • Maximal Extractable Value
    • Reproducible Build
    • Lightpaper
Powered by GitBook
On this page
  • Native on-chain verification
  • Optimistic Execution: From Creation to Publication
  • Optimistic Attestation: From Publication to Verification

Was this helpful?

  1. Understanding Automata
  2. What is Automata?
  3. Proof of Machinehood

Optimistic Attestation

Attest first, verify later

On-chain attestation is pivotal in achieving Proof of Machinehood. It comprises a public display of evidence that convinces others of the system's integrity, including elements such as hardware, firmware, software, applications, services, and more.

However, verifying individual components grows increasingly challenging with the rising complexity and diversity of system components. Each element presents a unique method of attestation through various cryptographic algorithms, leading to potential incompatibilities and substantial costs when executed and stored on blockchain systems like Ethereum.

The goal of optimistic attestation is to provide a swift lane for delivering attestation on-chain from the moment of creation by the attestor.

This is achieved by presuming honesty: in the execution by the rollup operator; and honest attestations from the attestor. All data is readily available on-chain so any discrepancies can be disputed using fraud proof systems. This serves as a deterrent to discourage any potential malicious actions.

Native on-chain verification

Storing and verifying attestation on-chain is a twofold process. Attestors who have vested interests and stand to gain economically bear the storage costs. However, verification costs are preposterously high due to the need to reproduce existing verification logic not designed for restricted environments like blockchains.

Major challenges in verification include the lack of on-chain trust anchors and the need to traverse the chain of trust, where verifying each individual step demands hefty computation. This is prohibitive, even with apparent benefits in a Layer-1 environment.

Executing this on a rollup presents an economically viable approach that makes attestations affordable for many applications. Attestation rollup’s additional benefit lies in providing a trust-minimized approach making the L2 state accessible at L1.

Optimistic Execution: From Creation to Publication

By using optimistic rollup with fraud proof, you can expedite the process from creation to publication of attestations. This is advantageous in scenarios demanding real-time performance where the delay in attestations could potentially bottleneck the process. For instance, on a per-transaction basis, any delay in attestation would consequently delay the transaction, disrupting subsequent executions.

Optimistic Attestation: From Publication to Verification

The key concept for optimistic attestation centers around the assumption of an honest attestor, which further reduces the gap between the time when an attestation is available and when it can be safely consumed by other parties. The credibility of an attestor depends on various factors, including the security deposit and the duration and reputation of the attestation service, etc.

The whole workflow is as follows:

  1. Attestors can publish attestations that can be challenged by anyone on-chain through a verification process.

  2. A successfully verified attestation becomes a permanent part of the attestation layer.

  3. Depending on the attestation’s importance, a security deposit may be required upon creation of a new attestation, even without initiating the verification process.

  4. Challengers need not provide a security deposit. They do bear the cost of the verification, but if the challenge is legitimate, they can recoup these expenses.

  5. The security deposit of the attestor forms a significant part of this reimbursement. Additional incentives can be provided during the initial stages to promote protocol adoption.

PreviousProof of MachinehoodNextZero Knowledge Proof

Last updated 1 year ago

Was this helpful?

Page cover image