genlayer 0.33.1 → 0.34.1

package/docker-compose.yml

@@ -1,154 +0,0 @@
-version: "3.8"
-
-services:
-  frontend:
-    image: yeagerai/simulator-frontend:${LOCALNETVERSION:-latest}
-    ports:
-      - "${FRONTEND_PORT:-8080}:8080"
-    environment:
-      - VITE_*
-    env_file:
-      - ./.env
-    depends_on:
-      jsonrpc:
-        condition: service_healthy
-    expose:
-      - "${FRONTEND_PORT:-8080}"
-    restart: always
-    security_opt:
-      - "no-new-privileges=true"
-    logging:
-      driver: "json-file"
-      options:
-        max-size: "10m"
-        max-file: "3"
-    profiles:
-      - frontend
-
-
-  jsonrpc:
-    image: yeagerai/simulator-jsonrpc:${LOCALNETVERSION:-latest}
-    environment:
-      - FLASK_SERVER_PORT=${RPCPORT:-5000}
-      - PYTHONUNBUFFERED=1
-      - RPCDEBUGPORT=${RPCDEBUGPORT:-5001}
-      - WEBDRIVERHOST=${WEBDRIVERHOST:-webdriver}
-      - WEBDRIVERPORT=${WEBDRIVERPORT:-4444}
-    ports:
-      - "${RPCPORT:-5000}:${RPCPORT:-5000}"
-      - "${RPCDEBUGPORT:-5001}:${RPCDEBUGPORT:-5001}"
-    env_file:
-      - ./.env
-    healthcheck:
-      test: [ "CMD", "python3", "backend/healthcheck.py", "--port", "${RPCPORT}" ]
-      interval: 30s
-      timeout: 10s
-      retries: 3
-      start_period: 30s
-    depends_on:
-      database-migration:
-        condition: service_completed_successfully
-      webdriver:
-        condition: service_healthy  
-    expose:
-      - "${RPCPORT:-5000}"
-    restart: always
-    security_opt:
-      - "no-new-privileges=true"
-    logging:
-      driver: "json-file"
-      options:
-        max-size: "10m"
-        max-file: "3"
-    deploy:
-      replicas: ${JSONRPC_REPLICAS:-1}
-    volumes:
-      - hardhat_artifacts:/app/hardhat/artifacts
-      - hardhat_deployments:/app/hardhat/deployments
-
-
-  webdriver:
-    image: yeagerai/genlayer-genvm-webdriver:0.0.3
-    shm_size: 2gb
-    environment:
-      - PORT=${WEBDRIVERPORT:-4444}
-    expose:
-      - "${WEBDRIVERPORT:-4444}"
-    restart: always
-    security_opt:
-      - "no-new-privileges=true"
-    logging:
-      driver: "json-file"
-      options:
-        max-size: "10m"
-        max-file: "3"
-  
-  ollama:
-    image: ollama/ollama:0.9.6
-    ports:
-      - 11434:11434
-    container_name: genlayer-ollama
-    tty: true
-    restart: always
-    security_opt:
-      - "no-new-privileges=true"
-    logging:
-      driver: "json-file"
-      options:
-        max-size: "10m"
-        max-file: "3"
-    profiles:
-      - ollama
-
-  postgres:
-    image: postgres:17-alpine
-    ports:
-      - "${DBPORT:-5432}:5432"
-    environment:
-      - POSTGRES_USER=${DBUSER:-postgres}
-      - POSTGRES_PASSWORD=${DBPASSWORD:-postgres}
-      - POSTGRES_DB=${DBNAME:-simulator_db}
-    healthcheck:
-      test: pg_isready -U ${DBUSER:-postgres} -d ${DBNAME:-simulator_db}
-      interval: 10s
-      timeout: 3s
-      retries: 3
-    restart: always
-    security_opt:
-      - "no-new-privileges=true"
-    logging:
-      driver: "json-file"
-      options:
-        max-size: "10m"
-        max-file: "3"
-
-    # Uncomment the following lines if you want your DB to persist
-    # volumes:
-    #   - "./data/postgres:/var/lib/postgresql/data"
-
-  database-migration:
-    image: yeagerai/simulator-database-migration:${LOCALNETVERSION:-latest}
-    environment:
-      - DB_URL=postgresql://${DBUSER:-postgres}:${DBPASSWORD:-postgres}@postgres/${DBNAME:-simulator_db}
-    depends_on:
-      postgres:
-        condition: service_healthy
-
-  hardhat:
-    image: yeagerai/simulator-hardhat:${LOCALNETVERSION:-latest}
-    ports:
-      - "${HARDHAT_PORT:-8545}:8545"
-    environment:
-      - HARDHAT_NETWORK=hardhat
-    volumes:
-      - hardhat_artifacts:/app/artifacts
-      - hardhat_deployments:/app/deployments
-      - hardhat_cache:/app/cache
-      - hardhat_snapshots:/app/snapshots
-
-volumes:
-  hardhat_artifacts:
-  hardhat_deployments:
-  hardhat_cache:
-  hardhat_snapshots:
-  

package/docs/delegator-guide.md

@@ -1,203 +0,0 @@
-# Delegator Guide
-
-This guide walks you through delegating GEN tokens to a validator on the GenLayer testnet.
-
-## What is Delegation?
-
-Delegation allows you to stake your GEN tokens with an existing validator without running validator infrastructure yourself. You earn staking rewards proportional to your stake.
-
-## Prerequisites
-
-- Node.js installed
-- GenLayer CLI installed (`npm install -g genlayer`)
-- GEN tokens for staking
-
-## Step 1: Create an Account
-
-```bash
-genlayer account create
-```
-
-You'll be prompted to set a password. This creates an encrypted keystore file.
-
-## Step 2: Set Network to Testnet
-
-```bash
-genlayer network testnet-asimov
-```
-
-## Step 3: Fund Your Account
-
-Transfer GEN tokens to your address. Check your balance:
-
-```bash
-genlayer account
-```
-
-## Step 4: Check Minimum Delegation
-
-```bash
-genlayer staking epoch-info
-```
-
-Note the `delegatorMinStake` - you need at least this amount.
-
-## Step 5: Find a Validator
-
-List all active validators:
-
-```bash
-genlayer staking active-validators
-```
-
-Output:
-```json
-{
-  count: 6,
-  validators: [
-    '0xa8f1BF1e5e709593b4468d7ac5DC315Ea3CAe130',
-    '0xe9246A020cbb4fC6C46e60677981879c9219e8B9',
-    ...
-  ]
-}
-```
-
-Get details about a specific validator:
-
-```bash
-genlayer staking validator-info --validator 0xa8f1BF1e5e709593b4468d7ac5DC315Ea3CAe130
-```
-
-Look for:
-- `live: true` - Validator is active
-- `banned: 'Not banned'` - Validator is in good standing
-- `identity` - Validator's metadata (moniker, website, etc.)
-
-## Step 6: Unlock Your Account (Optional)
-
-For convenience:
-
-```bash
-genlayer account unlock
-```
-
-## Step 7: Delegate to a Validator
-
-```bash
-genlayer staking delegator-join --validator 0xa8f1...130 --amount 100gen
-```
-
-Options:
-- `--validator <address>` - Validator address to delegate to (required)
-- `--amount <amount>` - Amount to stake (e.g., `100gen`)
-
-## Step 8: Verify Your Delegation
-
-```bash
-genlayer staking delegation-info --validator 0xa8f1...130
-```
-
-Output:
-```json
-{
-  delegator: '0x86D0d159483CBf01E920ECfF8bB7F0Cd7E964E7E',
-  validator: '0xa8f1BF1e5e709593b4468d7ac5DC315Ea3CAe130',
-  shares: '100000000000000000000',
-  stake: '100 GEN',
-  projectedReward: '0.2 GEN per epoch',
-  pendingDeposits: 'None',
-  pendingWithdrawals: 'None'
-}
-```
-
-The `projectedReward` shows your estimated earnings per epoch based on current inflation and your stake weight.
-
-## Managing Your Delegation
-
-### Check Your Stake
-
-```bash
-genlayer staking delegation-info --validator 0xa8f1...130
-```
-
-### Withdraw (Exit) Delegation
-
-To withdraw your stake:
-
-```bash
-genlayer staking delegator-exit --validator 0xa8f1...130 --shares 50
-```
-
-Options:
-- `--validator <address>` - Validator you delegated to
-- `--shares <shares>` - Number of shares to withdraw
-
-This initiates a withdrawal. Your tokens enter an **unbonding period of 7 epochs** before they can be claimed.
-
-Check your pending withdrawals with `delegation-info`:
-```json
-pendingWithdrawals: [
-  {
-    epoch: '5',
-    shares: '50',
-    stake: '50 GEN',
-    claimableAtEpoch: '12',
-    status: 'Unbonding (4 epochs remaining)'
-  }
-]
-```
-
-### Claim Withdrawals
-
-After the 7-epoch unbonding period, claim your tokens:
-
-```bash
-genlayer staking delegator-claim --validator 0xa8f1...130
-```
-
-## Choosing a Validator
-
-Consider these factors when choosing a validator:
-
-1. **Uptime** - Validators with high uptime earn more rewards
-2. **Reputation** - Check their identity metadata and community presence
-3. **Stake** - Higher stake may indicate trust from the community
-4. **Not banned/quarantined** - Avoid validators with issues
-
-Check quarantined validators:
-```bash
-genlayer staking quarantined-validators
-```
-
-Check banned validators:
-```bash
-genlayer staking banned-validators
-```
-
-## Troubleshooting
-
-### "No account found"
-Run `genlayer account create` first.
-
-### "Insufficient balance"
-Ensure you have enough GEN. Check with `genlayer account`.
-
-### "Below minimum stake"
-Check minimum with `genlayer staking epoch-info` and increase your amount.
-
-### "Validator not found"
-Verify the validator address is correct and they are still active.
-
-### Transaction Stuck
-Check the transaction status:
-```bash
-genlayer receipt <tx-hash>
-```
-
-## Lock Your Account
-
-When done, lock your account:
-
-```bash
-genlayer account lock
-```

package/docs/validator-guide.md

@@ -1,329 +0,0 @@
-# Validator Guide
-
-This guide walks you through becoming a validator on the GenLayer testnet using the CLI.
-
-For a deeper understanding of how staking works in GenLayer, see the [Staking documentation](/understand-genlayer-protocol/core-concepts/optimistic-democracy/staking).
-
-## Prerequisites
-
-- Node.js installed
-- GenLayer CLI installed (`npm install -g genlayer`)
-- GEN tokens for staking (minimum stake required)
-
-## Quick Start: Validator Wizard
-
-The easiest way to become a validator is using the interactive wizard:
-
-```bash
-genlayer staking wizard
-```
-
-The wizard guides you through all steps:
-1. Account setup (create or select)
-2. Network selection
-3. Balance verification
-4. Operator setup (optional, recommended for security)
-5. Stake amount selection
-6. Validator creation
-7. Identity setup (moniker, website, etc.)
-
-If you prefer manual setup, follow the steps below.
-
----
-
-## Manual Setup
-
-## Step 1: Create an Owner Account
-
-```bash
-genlayer account create --name owner
-```
-
-You'll be prompted to set a password. This creates an encrypted keystore file in standard web3 format.
-
-The owner account holds your staked funds and controls the validator. Keep it secure.
-
-## Step 2: View Your Account
-
-```bash
-genlayer account show
-```
-
-Output:
-```
-{
-  name: 'owner',
-  address: '0x86D0d159483CBf01E920ECfF8bB7F0Cd7E964E7E',
-  balance: '0 GEN',
-  network: 'localnet',
-  status: 'locked',
-  active: true
-}
-```
-
-## Step 3: Set Network to Testnet
-
-```bash
-genlayer network testnet-asimov
-```
-
-Verify with:
-```bash
-genlayer account show
-```
-
-You should see `network: 'Asimov Testnet'`.
-
-## Step 4: Fund Your Account
-
-Transfer GEN tokens to your address:
-- Use the faucet (if available)
-- Transfer from another funded account using `genlayer account send`
-
-## Step 5: Check Staking Requirements
-
-```bash
-genlayer staking epoch-info
-```
-
-Output:
-```
-✔ Epoch info
-
-  Current Epoch: 5 (started 9h 30m ago)
-  Next Epoch:    in 14h 30m
-  Validators:    33
-  Weight:        6061746783417938774454
-  Slashed:       0 GEN
-
-  Previous Epoch: 4 (finalized)
-  Inflation:      1732904.66 GEN
-  Claimed:        0 GEN
-  Unclaimed:      1732904.66 GEN
-  Slashed:        0 GEN
-
-  Min Epoch Duration:   24h 0m
-  Validator Min Stake:  42000 GEN
-  Delegator Min Stake:  42 GEN
-```
-
-You can also query a specific epoch:
-```bash
-genlayer staking epoch-info --epoch 4
-```
-
-Note the `validatorMinStake` - you need at least this amount.
-
-## Step 6: Unlock Your Account (Optional)
-
-For convenience, unlock your account to avoid entering password repeatedly:
-
-```bash
-genlayer account unlock
-```
-
-This caches your private key in the OS keychain.
-
-## Step 7: Join as Validator
-
-```bash
-genlayer staking validator-join --amount 42000gen --operator 0xOperator...
-```
-
-Options:
-- `--amount <amount>` - Stake amount (e.g., `42000gen` or `42000`)
-- `--operator <address>` - Operator address (recommended, see below)
-
-### Why Use an Operator Address?
-
-**Recommended:** Use a separate operator address for security.
-
-- **Validator wallet** - Holds your staked funds (keep offline/cold)
-- **Operator wallet** - Signs blocks and performs validator duties (hot wallet on server)
-
-This way, if your operator server is compromised, your staked funds remain safe.
-
-If you already have an operator wallet (e.g., from geth, foundry, or another tool), you can use its address directly. Otherwise, create one:
-
-```bash
-# Create operator account (skip if you already have one)
-genlayer account create --name operator
-
-# View operator address
-genlayer account show --account operator
-# Address: 0xOperator123...
-
-# Export keystore for validator node software (standard web3 format)
-genlayer account export --account operator --output ./operator-keystore.json
-
-# Join as validator with separate operator
-genlayer staking validator-join --amount 42000gen --operator 0xOperator123...
-```
-
-Transfer `operator-keystore.json` to your validator server and import it into your validator node software. The keystore is in standard web3 format, compatible with geth, foundry, and other Ethereum tools.
-
-You can change the operator later:
-
-```bash
-genlayer staking set-operator --validator 0xYourValidator... --operator 0xNewOperator...
-```
-
-## Step 8: Verify Your Validator Status
-
-```bash
-genlayer staking validator-info
-```
-
-Output:
-```
-{
-  validator: '0x86D0d159483CBf01E920ECfF8bB7F0Cd7E964E7E',
-  vStake: '42000 GEN',
-  vShares: '42000000000000000000000',
-  live: true,
-  banned: 'Not banned',
-  ...
-}
-```
-
-## Step 9: Set Validator Identity (Metadata)
-
-Set your validator's public identity so delegators can find you:
-
-```bash
-genlayer staking set-identity \
-  --validator 0x86D0...7E \
-  --moniker "My Validator" \
-  --website "https://myvalidator.com" \
-  --description "Reliable validator with 99.9% uptime" \
-  --twitter "myvalidator" \
-  --github "myvalidator"
-```
-
-**Required:**
-- `--validator <address>` - Your validator address
-- `--moniker <name>` - Display name for your validator
-
-**Optional:**
-- `--logo-uri <uri>` - Logo image URL
-- `--website <url>` - Website URL
-- `--description <text>` - Description of your validator
-- `--email <email>` - Contact email
-- `--twitter <handle>` - Twitter handle
-- `--telegram <handle>` - Telegram handle
-- `--github <handle>` - GitHub handle
-- `--extra-cid <cid>` - Additional data as IPFS CID
-
-Your identity will show in `validator-info`:
-
-```bash
-genlayer staking validator-info
-```
-
-Output will include:
-```
-{
-  ...
-  identity: {
-    moniker: 'My Validator',
-    website: 'https://myvalidator.com',
-    twitter: 'myvalidator',
-    github: 'myvalidator'
-  }
-}
-```
-
-## Managing Your Validator
-
-### Priming Your Validator
-
-Validators must be "primed" each epoch to participate in consensus. Priming updates the validator's stake record for the upcoming epoch.
-
-```bash
-# Prime your validator
-genlayer staking validator-prime 0xYourValidator...
-
-# Or prime all validators at once (anyone can do this)
-genlayer staking prime-all
-```
-
-The `validators` command shows priming status:
-- **Green** `e11` - Primed for current epoch
-- **Yellow** `e10` - Needs priming before next epoch
-- **Red** `e9!` - Urgently needs priming (behind)
-
-### Add More Stake
-
-```bash
-genlayer staking validator-deposit --validator 0xYourValidatorWallet... --amount 1000gen
-```
-
-### Check Active Validators
-
-```bash
-genlayer staking active-validators
-```
-
-### View Validator Set
-
-```bash
-# Show all validators with stake, primed status, and weight
-genlayer staking validators
-
-# Include banned validators
-genlayer staking validators --all
-```
-
-### Exit as Validator
-
-```bash
-genlayer staking validator-exit --validator 0xYourValidatorWallet... --shares 100
-```
-
-This initiates a withdrawal. Your tokens enter an **unbonding period of 7 epochs** before they can be claimed.
-
-Check your pending withdrawals with `validator-info`:
-```
-selfStakePendingWithdrawals: [
-  {
-    epoch: '5',
-    shares: '100',
-    stake: '100 GEN',
-    claimableAtEpoch: '12',
-    status: 'Unbonding (4 epochs remaining)'
-  }
-]
-```
-
-### Claim Withdrawals
-
-After the 7-epoch unbonding period:
-
-```bash
-genlayer staking validator-claim --validator 0xYourValidatorWallet...
-```
-
-## Troubleshooting
-
-### "No account found"
-Run `genlayer account create` first.
-
-### "Insufficient balance"
-Ensure you have enough GEN. Check with `genlayer account show`.
-
-### "Below minimum stake"
-Check minimum with `genlayer staking epoch-info` and increase your stake amount.
-
-### Transaction Stuck
-Check the transaction status:
-```bash
-genlayer receipt <tx-hash>
-```
-
-## Lock Your Account
-
-When done, lock your account to remove the cached private key:
-
-```bash
-genlayer account lock
-```

package/esbuild.config.dev.js

@@ -1,17 +0,0 @@
-export default {
-  context: {
-    tsconfig: "./tsconfig.json",
-    entryPoints: ["src/index.ts"],
-    bundle: true,
-    outfile: "dist/index.js",
-    platform: "node",
-    target: "es2020",
-    format: "esm",
-    define: { "import.meta.url": "import.meta.url" },
-    banner: {
-      js: `const _importMetaUrl = new URL(import.meta.url).pathname;`,
-    },
-    external: ["commander", "dockerode", "dotenv", "ethers", "inquirer", "update-check", "ssh2", "fs-extra", "esbuild", "keytar"]
-  },
-  watch: true,
-};

package/esbuild.config.js

@@ -1,22 +0,0 @@
-/* eslint-disable no-undef -- Allow process and console in ignored file */
-
-import esbuild from "esbuild";
-
-const isProduction = process.env.NODE_ENV === "production";
-const config = isProduction
-  ? await import("./esbuild.config.prod.js")
-  : await import("./esbuild.config.dev.js");
-
-const run = async () => {
-  if (config.default.watch) {
-    const context = await esbuild.context(config.default.context);
-    await context.watch();
-  } else {
-    await esbuild.build(config.default.context);
-  }
-};
-
-run().catch(e => {
-  console.error(e);
-  process.exit(1);
-});