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
  • Introduction of Device Attestation
  • On-chain Device Attestation

Was this helpful?

  1. Build with PoM
  2. Attestation module

Device Attestation

Introduction of Device Attestation

Device attestation is a crucial security process that allows a relying party, such as a server or service, to verify the authenticity of a specific device. In the context of cybersecurity, attestation serves as a means to ensure that a device is genuine, has not been tampered with, and is operating as expected. This process is particularly important for devices that play a critical role in user authentication and data protection, such as hardware security keys.

The attestation process typically involves the generation of an attestation statement by the device, which includes a cryptographic signature and other metadata. The relying party then verifies the attestation statement by checking the cryptographic signature and metadata, confirming that the statement came from a genuine device. This verification process provides an added layer of security, ensuring that only trusted devices can access sensitive information and services.

On-chain Device Attestation

In the traditional device attestation process, a relying party, such as a server or service, is responsible for verifying the authenticity of a device. However, this approach has limitations in terms of transparency and accessibility. To address these issues, we have implemented a novel approach by replacing the relying party with an on-chain contract. In this new model, the attestation statement generated by the device is verified and stored on a blockchain. This approach offers several advantages:

  • It provides a transparent and tamper-proof record of the attestation, as the attestation statement is immutably stored on the blockchain.

  • It allows anyone to publicly access and verify the attestation statement, enhancing the trustworthiness of the attestation process.

  • By leveraging the decentralized and secure nature of blockchain technology, we can ensure that the device attestation process is more robust, transparent, and accessible to all.

PreviousMiscellaneousNextYubikey

Last updated 1 year ago

Was this helpful?