LogoLogo
  • Imua
    • About
  • Manifesto
    • The Problems
    • The Principles
  • Architecture
    • Imua Design Principles
    • Imua Network
    • Imua Modules
    • Client Chain Bridges
      • Trustless Verification of Client Chain State
      • Handling Race Conditions between Imua and Client Chains
    • Client Chain Contracts
  • Concepts
    • Ecosystem
      • Re/stakers
      • Operators
      • Services (AVS)
        • Service Integration with Imua
        • Service Committee
        • Service Integration Details
    • restaked Proof-of-Stake (rPOS)
    • Multi-Token Restaking
    • Multi-Chain Restaking with Trustless Bridging
    • Voting Power
    • Price Oracle
    • Flexible Integration with AVS
    • Tribe Staking
  • Governance
  • Risk Management
    • Risk Analysis
      • Risk Modeling
      • Risk Parameters
      • Crypto-Economic Risk
      • Unintended Slashing
      • Black Swan Events
    • Risk Mitigation
      • Smart Contract Simplicity
      • Audits
      • Slashing Prevention
      • Slashing Vetos
      • Insurance Pools
      • Circuit Breakers
  • Components
    • Testnet
    • Oracle Module
      • Reaching Consensus on Asset Prices
      • Penalty
      • Implementation Detail
    • Smart Contracts
    • Explorer
    • Registry
  • Validator Setup
    • Prerequisites
    • Node Install
    • Compiling Binary from Source
    • Oracle Price Feeder
    • Running the Node
    • Snapshot
    • Register Option 1 (Bootstrap)
    • Register Option 2 (Post Network Launch)
    • Deposit Tokens
    • Delegating Tokens
    • Confirm Election Status
    • Faucets
    • Managing The Validator
    • Security Best Practices
    • Risks & Mitigation
    • Participation in Governance
    • FAQs & Resources
  • Testnet Upgrade to v1.1.1
  • AVS Setup
    • AVS Overview
    • Prerequisites
    • Building the AVS in Imua
    • Hello-World-AVS Example
    • Becoming AVS Operator
    • AVS Register and Deploy
    • AVS Task Example
    • Enhanced and Automated Edition of hello-avs integration guide&example
  • Whitepaper (2023)
    • .pdf
  • FAQ
    • What problems is Imua solving?
    • What are the main design trade-offs that had to be made with an omnichain design?
    • Does the omnichain design imply added trust assumptions (relative to a single-chain design)?
    • What concurrency-related challenges would you face with a different design?
    • How does Imua integrate with new chains?
    • Do specific chains prove unique challenges w.r.t. integration?
    • How is the cross-chain communication is achieved?
    • What are the known attack / censorship vectors here, if any?
    • Are the restaked tokens being pooled in a centralized account?
    • Who will run the validators in the Imua network?
    • Is Imua an AVS?
    • How does Imua address the risks of overloading L1 social consensus?
    • Does the Imua queuing system raise concerns around latency?
    • What are the main benefits of an omnichain design?
Powered by GitBook
On this page
  1. Validator Setup

Faucets

This page describes how to receive imETH and imua tokens via the faucet.

exoETH

exoETH is a testnet token used for staking. It has no real value. The way to obtainexoETH via our faucet is listed below. You will need some Sepolia ETH to pay for gas, and your Ethereum private key.

This faucet gives out 1 exoETH every 24 hours per requesting address.

# script constants
EXO_ETH_FAUCET_ADDR=0x.... # join the validator chat to obtain this

# user input
ETH_PRIVATE_KEY=0xabcde....
ETHEREUM_RPC_URL=https://rpc.ankr.com/eth_sepolia

cast send --rpc-url $ETHEREUM_RPC_URL \
    $EXO_ETH_FAUCET_ADDR \
    "requestTokens()" \
    --private-key $ETH_PRIVATE_KEY

The expected output looks similar to that of any other transaction.

blockHash               0x496b22768c38687dedeaf1f6b3823b0973b25ae90ea961e702f6dd4ba82a980a
blockNumber             6679149

<! -- truncated -->

transactionHash         0x24426c2acf0e6a411961f478bca68a36c12ed0bff3d7206cd1cd7662908d40cf
transactionIndex        84
type                    2
blobGasPrice            
blobGasUsed             
authorizationList       
to                      0x8fc4E764C2C3B0646ba572AEa958fB5724706412

imua

imua is the native token for Imua, used to pay for gas. It can only be obtained once the network is live (post the bootstrap phase). Use our faucet to obtain this token. The token on testnet has no real value.

FAUCET_URL=https://..... # join the validator chat to obtain this
IM_ADDRESS=$(imuad --home $HOMEDIR keys show -a $ACCOUNT_KEY_NAME)

curl -X POST $FAUCET_URL -H "Content-Type: application/json" \
    -d "{\"address\": \"$IM_ADDRESS\"}"
{"txHash":"0x3977c552862fc4c24f6f44792182b61524af3118cf6bad4e1e2aeacdcbe32e74"}
PreviousConfirm Election StatusNextManaging The Validator

Last updated 2 months ago

The response is a json containing the transaction hash, which can be tracked on our

explorer