Getting Started

New to blockchains? This is your UX wall walkthrough — from zero to first transaction in 3 steps.

Step 1: Get Your Wallet

A blockchain wallet is like a bank account, but you hold the keys. WayChain uses Ed25519 signatures — different from Bitcoin/Ethereum.

Use the web wallet at /wallet for key generation. All operations happen client-side, but the wallet stores keys in browser storage on this device, so treat it as a convenience wallet rather than a hardened vault.

Or use any Ed25519-compatible library in your preferred language to generate keys locally.

• Your seed phrase (12 words) — write this down. Never share it.
• Your public address (0x...) — this is like your account number.
• Your private key — never share this either. Keep it secret.

Step 2: Get Test Tokens

Two ways to get WAY tokens:

Option A: CashApp Bitcoin Bridge

Precompile live (BitcoinRegistry 0x16). Consumer UX in development.

1. Send $1 BTC to the WayChain treasury address (shown on Dox_Dev Badge page)
2. Your TXID proves the send (6+ confirmations on Bitcoin)
3. ~100 WAY will credit to your WayChain address

Treasury holds the BTC. Protocol credits your address.

Option B: Request from Faucet

Go to /faucet. Paste your address. Click "Request 10 WAY". Get tokens in 1 second.

1. Go to Faucet
2. Paste your WayChain address (starts with 0x)
3. Click "Request 10 WAY"
4. Check your balance in 1 second (links to explorer)

Option C: Send Bitcoin, Receive 1WAY Stablecoin

Precompile live (WayStablecoin 1WAY 0x22). Consumer UX in development.

Send real BTC and receive 1WAY — the Bitcoin-backed stablecoin — at 1:1 peg. 1WAY is minted by the 1WAY precompile (0x22) itself when BTC is deposited and attested (BTC locked → 1WAY minted). It is not minted by the BitcoinRegistry (0x16, which only maps BTC addresses to WayChain addresses) and not by the Vault. The Vault (TwoWayVault 0x18) is a separate CDP engine that mints 2WAY against deposited stablecoins. The oracle

1. Send BTC to the 1WAY bridge address (details on badge page)
2. Wait for 6+ confirmations (~1 hour on Bitcoin)
3. 1WAY credits to your WayChain address via the 1WAY precompile (0x22)
4. Use 1WAY anywhere on WayChain — swap, send, hold

1WAY = Bitcoin on WayChain. Fully backed 1:1 (BTC locked → 1WAY minted at 0x22). Vault (0x18) mints 2WAY, not 1WAY.

Step 3: Send Your First Transaction

Transfer tokens to another address. Watch it get confirmed in 1 second.

WayChain uses Ed25519-signed binary transactions submitted via eth_sendRawTransaction — there is no eth_sendTransaction (account-unlocking) RPC. Build and sign the tx client-side (see web wallet / mobile wallet), then broadcast the raw bytes.

What happened:

• Your transaction entered the pool
• A validator picked it up within 1 second
• The block was finalized
• The recipient got the tokens

What Is a Blockchain?

A blockchain is a digital ledger that everyone can read but no one can secretly edit. Instead of one company holding all records, copies exist on thousands of computers worldwide.

Developer Walkthrough

Build on the lighthouse. Native Go precompiles. 1-second finality.

Quick Start (Code)

Example: Using the WayChain Client

# Install the WayChain client
curl -sSL https://raw.githubusercontent.com/ThinkIbrokeIt/waychain-client/main/scripts/install.sh | bash

# Check Dox_Dev badge level for an address
waychain rpc call way_getDoxLevel 0xYourAddress

# Check balance
waychain rpc call eth_getBalance 0xYourAddress latest

Key Differences from Standard EVM

RPC API

# Current block
curl -X POST https://api.waychain.org \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"eth_blockNumber","params":[],"id":1}'

# Check Dox_Dev level
curl -X POST https://api.waychain.org \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","method":"way_getDoxLevel","params":["0xYourAddress"],"id":1}'

# WebSocket stream
wss://api.waychain.org/ws

Native Precompiles (0x0C-0x27)

Web Connection Layer (Live)

The frontend talks to mainnet through a single shared precompile registry — one source of truth for all 28 precompiles (0x0C–0x27) and all 128 methods (54 read / 74 write), verified against the Go source on the node. Both the web and mobile wallets use it.

• Real Ed25519 auth — the web wallet derives a 20-byte address (hex(pubkey)[0:40]) matching the chain's canonical format. No fake/placeholder addresses.
• Live reads — precompileCall dispatches eth_call to the correct precompile + selector + ABI-encoded args. Proven working against mainnet (e.g. Dox_Dev returns 3 badges on-chain).
• Write path — web writes are currently gated (the web transaction signer is still being ported). Mobile already signs and broadcasts; web shows clear “not implemented” rather than a broken send.

Prebuilt UI sections (all reading live chain state): /tokens (BIJO · 1WAY · SWAY · SwapRoute), /identity (Dox_Dev · Governance · TaskRegistry), /defi (TwoWayVault · StabilityPool · TrustlessLock · AccountRecovery), /realworld (MineralRights · BitcoinRegistry · DeadMansSwitch), /protocol (oracles · privacy · cross-chain · template registry).

Dox_Dev Identity Requirements

• Level 1 (Lantern) — Verified human. Can hold tokens, receive/from transfers.
• Level 2 (Compass) — Can deploy contracts. SHA256 selector validation.
• Level 3 (Lighthouse) — Can verify others. Curator privileges.

Deploy Gate (3 Layers)

1. RPC Layer — HTTP check before transaction enters pool.
2. Block Production — Proposer verifies all transactions.
3. EVM Opcode — Runtime enforcement in every contract call.