WebChain Documentation

Core Features

Blockchain Architecture

• WebRTC P2P Network: Custom blockchain built with WebRTC enabling direct validator communication
• Hybrid Consensus: PoC+ (Proof-of-Concept+) combining PoS and PoC elements
• On-chain Operations: Supports mining, staking, order broadcasting, and P2P validators/peers
• EVM Compatibility: Fully compatible with MetaMask, Ethereum wallets, and DApps
• Validator Mining: Validators can mine ETK every 60 minutes after staking 370 ETK and maintaining 0.0000001 ETK balance
• Instant Confirmations: Transactions deposited into off-chain wallet from the user mining on-chain wallet in milliseconds
• WooCommerce Integration: Broadcasts all WooCommerce completed orders to the blockchain

Technical Integration

• JSON-RPC Endpoint: Full Ethereum-compatible endpoint for MetaMask integration at https://rpc.webchain.e-talk.xyz/
• Custom REST API: Includes /rpc, /supply, /verify-validator, /process-order, /mining-events, and /validator endpoints
• Peer System: Complete validator registration and peer management system
• Transaction Viewer: Real-time transaction display with verification status indicators
• E-Talk Plugin: Allows vendors to broadcast trade history to WebChain

Recent Enhancements

• On-chain Mining: Validator mining functionality now fully operational
• Multi-chain Support: ETK Scan verifies transactions on Ethereum, BSC, Polygon, and WebChain
• Auto-broadcasting: WooCommerce sites using sync plugins automatically broadcast completed orders

Technical Specifications

{
    "from": "0x...",
    "to": "0x...",
    "amount": 1.23,
    "nonce": 5,
    "note": "Payment",
    "timestamp": 1234567890,
    "hash": "0x..."
}

const { ethers } = require("ethers");
const fetch = require("node-fetch");

const RPC_URL = "https://rpc.webchain.e-talk.xyz";
const privateKey = "0x...";
const toAddress = "0x...";
const amountToSend = "20";

async function sendRawTx() {
  const provider = new ethers.providers.JsonRpcProvider(RPC_URL);
  const wallet = new ethers.Wallet(privateKey, provider);
  const nonce = await provider.getTransactionCount(wallet.address);
  const tx = {
    nonce,
    to: toAddress,
    value: ethers.utils.parseEther(amountToSend),
    gasLimit: ethers.utils.hexlify(21000),
    gasPrice: ethers.utils.hexlify(0),
    chainId: 1000001
  };
  const signedTx = await wallet.signTransaction(tx);
  const payload = {
    jsonrpc: "2.0",
    id: 1,
    method: "eth_sendRawTransaction",
    params: [signedTx]
  };
  const response = await fetch(RPC_URL, {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify(payload)
  });
  const json = await response.json();
  console.log("Transaction Hash:", json.result);
}
sendRawTx();
    

{
  "index": 43,
  "timestamp": 1698863000,
  "transactions": [...],
  "previous_hash": "a4f...",
  "hash": "c8e...",
  "merkle_root": "e9c...",
  "nonce": 102,
  "validator": "0xABCD..."
}

WebChain Decentralized Exchange (DEX) API

WebChain DEX provides endpoints for real-time market data, trading, liquidity management, and analytics, enabling seamless integration with platforms and tools.

Method: GET
URL: https://rpc.webchain.e-talk.xyz/price/etk
Description: Returns the current price of ETK.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/pools
Description: Returns a list of all liquidity pools.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/pool/{token_a}/{token_b}
Description: Returns detailed info for a specific liquidity pool. Replace {token_a} and {token_b} with token symbols.
        

Method: POST
URL: https://rpc.webchain.e-talk.xyz/dex/add-liquidity
Body Parameters:
{
    "token_a": "string",
    "token_b": "string",
    "amount_a": "number",
    "amount_b": "number"
}
Description: Adds liquidity to a specified pool.
        

Method: POST
URL: https://rpc.webchain.e-talk.xyz/dex/remove-liquidity
Body Parameters:
{
    "pool_id": "string",
    "liquidity": "number"
}
Description: Removes a portion of liquidity from a pool.
        

Method: POST
URL: https://rpc.webchain.e-talk.xyz/dex/swap
Body Parameters:
{
    "input_token": "string",
    "output_token": "string",
    "input_amount": "number",
    "min_output": "number (optional)"
}
Description: Swaps tokens in the DEX pool.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/my-liquidity
Description: Returns the logged-in user's liquidity positions.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/history
Query Parameters (optional):
    wallet: string
    limit: number (default: 50)
Description: Returns trade history. Can filter by wallet.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/quote
Query Parameters:
{
    "input_token": "string",
    "output_token": "string",
    "input_amount": "number"
}
Description: Returns estimated output amount for a swap.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/wallet/{wallet}/all-balances
Description: Returns balances for the specified wallet address.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/tokens/all-with-etk
Description: Returns a list of all tokens paired with ETK.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/debug-liquidity
Description: Returns detailed info of user's liquidity for debugging.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/supply
Description: Returns ETK supply info.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/volume-pair/{token_a}/{token_b}
Description: Returns 24h volume for a token pair.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/volume/{token}
Query Parameters (optional):
    days: number (default 7, max 30)
Description: Returns volume for a token over a period of days.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/market/summary
Description: Provides market summary for all trading pairs.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/market/pair/{pair_id}
Description: Returns market data for a specific trading pair.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/market/history/{pair_id}?interval=1
Description: Returns historical data for charts. Interval in hours/days.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/pairs
Description: Returns all available trading pairs.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/cmc/metadata
Description: Returns CoinMarketCap metadata for ETK.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/cmc/listings
Description: Returns CoinMarketCap token listings.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/coingecko/market
Description: Returns market data from CoinGecko for ETK and pairs.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/wusd-reserve
Description: Returns current WUSD reserve in DEX pools.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/dex/fee-earnings
Description: Returns total fees earned from DEX liquidity pools.
        

Method: GET
URL: https://rpc.webchain.e-talk.xyz/fear-greed
Description: Returns a sentiment index (0–100) reflecting market emotions based on DEX data.

Exchange Integration Guide

🌐 WebChain Is a Layer-1 Blockchain

WebChain is a full Layer-1 blockchain (PoC+) with its native coin ETK. It supports standard Ethereum-style JSON-RPC methods, enabling exchanges to integrate using familiar tools. For faster and safer operations, WebChain also provides a REST-based RPC Gateway that adds extra security features such as OTP verification and validator approval.

🔧 Standard JSON-RPC Integration (Recommended for Exchanges)

Connect to our RPC endpoint exactly like Ethereum:

POST https://rpc.webchain.e-talk.xyz
{
  "jsonrpc": "2.0",
  "method": "eth_getBalance",
  "params": ["0xYourHotWallet", "latest"],
  "id": 1
}
    

Supported JSON-RPC Methods

• eth_chainId – Returns chain ID [Recommended]
• net_version – Returns network version [Recommended]
• eth_getBalance – Returns account balance [Recommended]
• eth_sendTransaction – Processes signed transactions [Legacy/Optional]
• eth_sendRawTransaction – Processes raw signed transactions [Recommended]
• eth_getTransactionReceipt – Returns transaction details [Recommended]
• eth_blockNumber – Returns latest block number [Recommended]
• eth_getBlockByNumber – Returns block information [Legacy/Optional]
• eth_getTransactionCount – Returns account nonce [Recommended]

ETK-Specific JSON-RPC Methods

• etk_sendRawTransaction – Broadcast ETK transaction with OTP support [Recommended]
• etk_getBalance – Get ETK balance (on-chain) [Recommended]
• etk_getTransactionCount – Get nonce for a wallet [Recommended]
• etk_getBlockByNumber – Fetch block info by number [Recommended]
• etk_getBlockByHash – Fetch block info by hash [Recommended]
• etk_getTransactionByHash – Get transaction details by hash [Recommended]
• etk_blockNumber – Latest block number [Recommended]
• etk_syncing – Node syncing status [Recommended]
• etk_chainId – WebChain chain ID [Recommended]
• etk_gasPrice – Returns 0 ETK [Recommended]
• etk_getValidators – List of validators with balances [Recommended]
• etk_getSupply – Total ETK supply [Recommended]

Example Use Cases

• Deposit Processing: Track incoming transactions using etk_getTransactionByHash or eth_getLogs
• Withdrawal Processing: Broadcast validator-approved signed withdrawals using etk_sendRawTransaction
• Bulk Withdrawals: Submit multiple validator-approved transactions in one call via etk_sendRawTransaction
• OTP Verification: When sending via etk_sendRawTransaction, OTP verification ensures security for off-chain to on-chain transfers

🔐 WebChain RPC Gateway (Enhanced Integration)

Exchanges may use the REST-based RPC Gateway for simpler integration. This adds OTP/email verification, validator approval, and automatic wallet safety checks.

1. Get User Balance [Recommended]

GET /balance?user_id=99999&check_validator=true
Accept: application/json
    

2. Off-chain to On-chain Transfer (OTP) [Recommended]

POST /transfer
Content-Type: application/json

{
  "user_id": 1,
  "amount": 50.0,
  "validator_address": "0x"
}
    

3. On-chain Withdrawal (OTP) [Recommended]

POST /withdraw
Content-Type: application/json

{
  "user_id": 1,
  "amount": 1.0,
  "to": "0xExternalWalletAddressHere",
  "is_offchain": false,
  "validator_address": "0x"
}
    

4. On-chain Withdrawal to Off-chain (OTP) [Recommended]

POST /withdraw
Content-Type: application/json

{
  "user_id": 1,
  "amount": 6.0,
  "to": "",
  "is_offchain": true,
  "validator_address": "0x"
}
    

5. Confirm Transaction with OTP [Recommended]

POST /confirm_tx
Content-Type: application/json

{
  "user_id": 1,
  "otp": "dgXq8a"
}
    

📋 Prerequisites

• Validator address (cold wallet recommended)
• Static IP addresses for servers
• RPC endpoint: https://rpc.webchain.e-talk.xyz

📝 Onboarding

Submit validator address, company info, IP addresses, and transaction volume to WebChain admin for approval.

🔒 Security Requirements

⚠️ Troubleshooting

WebChain Validator Layer (WVM-20 Tokens)

Core Features

Database Structure (Protocol Level)

The Validator Layer maintains internal structures to manage tokens and validator activity:

webchain_tokens - Stores token information and status
webchain_token_approvals - Tracks validator votes on tokens
webchain_token_balances - Maintains token balances per wallet
webchain_token_transfers - Records all token transfer transactions
webchain_governance_proposals - Governance proposal management
webchain_governance_votes - Tracks votes on governance proposals

REST API Endpoints

The Validator Layer exposes a comprehensive REST API for token operations:

Token Creation Lifecycle

1. User sets their wallet address
2. User submits token creation request with parameters
3. Token enters “pending” status awaiting validator approval
4. Validators vote to approve or reject the token
5. When sufficient approvals are reached, the token is finalized
6. Finalized tokens are broadcast to the blockchain and become active
7. Initial token supply is minted to the creator’s wallet

Developer Hooks

Developers can extend functionality via hooks:

// Filter to modify token data
add_filter('webchain_token_data', function($token_data, $token_id) {
  return $token_data;
}, 10, 2);

// Action when token is approved
add_action('webchain_token_approved', function($token_id, $token_row) {
  // Custom logic
}, 10, 2);

// Action when token is rejected
add_action('webchain_token_rejected', function($token_id, $token_row) {
  // Custom logic
}, 10, 2);

Reference Implementation: WordPress Plugin

To make WVM-20 tokens accessible to non-technical users, WebChain provides a reference WordPress plugin. This plugin offers a full UI and shortcode interface for interacting with the Validator Layer.

Shortcode Interface

<!-- Example usage -->
[webchain_token_platform]

• Network configuration for EVM wallets
• Wallet address management
• Token creation form
• Token approval status chart
• Token transfer functionality
• Token minting capability
• Validator approval interface (for validators)
• Token balance display

Installation (WordPress Plugin)

1. Install the WebChain Validator Plugin in WordPress
2. On activation, required database tables are created automatically
3. Add the shortcode [webchain_token_platform] on any page to display the interface
4. Users must set their wallet address before creating tokens
5. Validators can approve or reject token creation requests

MetaMask Integration

Add WebChain to MetaMask with:

WooCommerce Integration

Process WooCommerce orders on WebChain via:

Order Data Structure

{
    "order_id": 123,
    "amount": 10.50,
    "currency": "USD",
    "customer": {
        "id": 456,
        "email": "user@example.com"
    },
    "items": [{
        "product_id": 789,
        "name": "Product Name",
        "quantity": 1,
        "price": 10.50
    }],
    "user_email": "validator@example.com",
    "wallet": "0x..."
}

Non-CMS Platform Integration

If your platform does not use WordPress, you can broadcast orders to WebChain using the HTTP request below. This works on any language or stack that can make HTTP requests.

### 1. Test WebChain Order Broadcast
POST https://rpc.webchain.e-talk.xyz/process-order
Content-Type: application/json

{
  "user_email": "validator@e-talk.xyz",
  "wallet": "0x1234567890abcdef1234567890abcdef12345678",
  "order_data": {
    "order_id": 9999,
    "amount": 10.50,
    "currency": "USD",
    "customer": {
      "id": 1204,
      "email": "test@e-talk.xyz"
    },
    "items": [
      {
        "product_id": 111,
        "name": "Test Product",
        "quantity": 1,
        "price": 10.50
      }
    ]
  }
}