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
  • What is attestation?
  • How does attestation work?
  • How often can I attest my device to receive tokens?
  • Why didn't I receive tokens after attesting my device?

Was this helpful?

  1. Backed by PoM
  2. L2Faucet

Frequently asked questions

What is attestation?

Attestation checks that the device is what it claims to be. Users attest devices (machines) to receive testnet tokens from the faucet.

How does attestation work?

When you request tokens from our faucet, we'll perform a check to verify the machine, which may include details such as its operating system, hardware configuration, and security status. The attestation report confirms the authenticity and integrity of your device, and can be verified on-chain.

Device attestation does not access or store any personal information.

How often can I attest my device to receive tokens?

User receive testnet tokens with each successful device attestation. The amount varies across faucets:

  • 1 Holesky ETH on the Holesky Faucet

  • 0.1 Sepolia ETH on the Sepolia Faucet

  • Depends on user selection on the L2Faucet

We have a daily limit on the total number of tokens you can receive every 24 hours to prevent abuse and ensure fair distribution.

Why didn't I receive tokens after attesting my device?

If you didn't receive tokens, it might be because your device was not attested successfully, you've already hit the limit within the last 24 hours, or there may be a temporary issue with the faucet. The best solution is to try again - either later, or with a different device.

PreviousL2FaucetNextApp-Specific Rollup

Last updated 1 year ago

Was this helpful?