@evvm/testnet-contracts 2.2.1 → 2.2.2

package/README.md

@@ -1,861 +1,86 @@
 # EVVM Testnet Contracts
 
-EVVM is an innovative blockchain virtualization system that allows you to create and deploy your own virtual blockchains on top of existing Ethereum networks where you can:
+[![npm version](https://img.shields.io/npm/v/@evvm/testnet-contracts.svg)](https://www.npmjs.com/package/@evvm/testnet-contracts) [![license](https://img.shields.io/badge/license-EVVM--NONCOMMERCIAL--1.0-blue.svg)](LICENSE) [![docs](https://img.shields.io/badge/docs-evvm.info-blue.svg)](https://www.evvm.info/)[![npm downloads](https://img.shields.io/npm/dw/@evvm/testnet-contracts.svg)](https://www.npmjs.com/package/@evvm/testnet-contracts) 
 
-- **Create your own virtual blockchain** with custom tokens and governance
-- **Deploy on testnets** like Ethereum Sepolia or Arbitrum Sepolia for testing
-- **Use proven, audited contracts** for staking, treasury management, and domain services
-- **Scale to mainnet** when ready for production
+A compact toolkit for creating virtual EVM chains on testnets.
 
-## What's included?
+Quick overview
+- Use the Solidity packages in `src/` as a library (install via NPM or Forge).
+- Use the `evvm` CLI to deploy and manage EVVM instances.
 
-EVVM provides a complete ecosystem of smart contracts:
-- **Core EVVM**: Your virtual blockchain's main engine
-- **NameService**: Domain name system for your blockchain (like ENS)
-- **Staking**: Token staking and rewards system
-- **Treasury**: Secure fund management inside the host chain or across chains
-- **Estimator**: Reward calculation and optimization
-- **P2PSwap**: Peer-to-peer token exchange service with automated market making
+Docs & hosted library: https://www.evvm.info/
 
-## Latest Features
 
-**Enhanced Deployment Experience:**
-- **CLI Executable**: Global `evvm` command for seamless deployment and management
-- **Interactive Wizard**: User-friendly deployment wizard with comprehensive guidance
-- **Automatic RPC Fallback**: 99%+ deployment success rate with multiple fallback endpoints
-- **Deployment Summary**: Instant access to all deployed contract addresses with explorer links
-- **Auto Registry Integration**: Automatic EVVM registration and ID configuration
-- **Smart Prerequisites Check**: Automatic dependency initialization and validation
-- **Multi-Wallet Support**: Easy selection from your Foundry keystores
+Install the library (1 min)
 
-**CLI Commands Available:**
-- `evvm deploy` - Deploy new EVVM instance with interactive setup
-- `evvm register` - Register existing EVVM in the registry
-- `evvm fulltest` - Run complete test suite
-- `evvm help` - Display comprehensive help
-- `evvm version` - Show CLI version
-
-**Reliability Improvements:**
-- Intelligent retry mechanism for network failures
-- Comprehensive error handling and troubleshooting guides
-- Verified high-performance RPC endpoints
-- Zero-configuration setup for most users
-
-## Use Cases
-
-This repository serves two main purposes:
-
-### Deploy Your Own EVVM Instance
-Create and deploy a complete virtual blockchain with all EVVM contracts on testnets for experimentation and testing.
-
-### Build Services Using Existing EVVM
-Use EVVM contracts as a library to build services that interact with already deployed EVVM instances.
-
----
-
-## Quick Start Options
-
-Choose your path based on what you want to achieve:
-
-### Option A: Building Services on Existing EVVM 
-
-**Perfect if you want to create smart contracts that interact with already deployed EVVM instances.**
-
-Simply install the library and start building:
-
-```bash
-# Install via NPM
-npm install @evvm/testnet-contracts
-
-# OR install via Forge  
-forge install EVVM-org/Testnet-Contracts
-```
-
-**What you get**: Access to all EVVM interfaces and contracts to build services that interact with live EVVM instances on testnets.
-
-**Next steps**: Jump to [Library Usage](#library-usage) section below.
-
-### Option B: Deploy Your Own Complete EVVM Instance
-
-**Perfect if you want to create your own virtual blockchain with custom tokens and governance.**
-
-Follow the complete deployment process:
-
-**What you get**: Your own virtual blockchain with custom tokens, domain system, staking rewards, and treasury management - all deployed and verified on public testnets.
-
-**Next steps**: Jump to [Deploy Your Own EVVM](#deploy-your-own-evvm) section below.
-
----
-
-## Library Usage
-
-> **For Building Services**: This section is for developers who want to build smart contracts that interact with existing EVVM instances. If you want to deploy your own complete EVVM instance, skip to [Deploy Your Own EVVM](#deploy-your-own-evvm).
-
-This repository can be used as a library in your Solidity projects through multiple installation methods:
-
-### Installation Options
-
-#### Option 1: NPM
 ```bash
+# NPM (recommended for dApp developers)
 npm install @evvm/testnet-contracts
-```
 
-#### Option 2: Forge
-```bash
+# Or with Forge
 forge install EVVM-org/Testnet-Contracts
 ```
 
-### Configuration
-
-#### If using NPM installation
-Add to your `foundry.toml`:
-```toml
-remappings = [
-    "@evvm/testnet-contracts/=node_modules/@evvm/testnet-contracts/src/",
-]
-```
-
-#### If using Forge installation
-Add to your `foundry.toml`:
-```toml
-remappings = [
-    "@evvm/testnet-contracts/=lib/Testnet-Contracts/src/",
-]
-```
-
-### Package Structure
-
-```
-@evvm/testnet-contracts/
-├── src/
-│   ├── contracts/
-│   │   ├── evvm/Evvm.sol           # Core EVVM implementation
-│   │   ├── nameService/NameService.sol  # Domain name resolution
-│   │   ├── staking/Staking.sol     # Staking mechanism
-│   │   ├── staking/Estimator.sol   # Rewards estimation
-│   │   ├── treasury/Treasury.sol   # Treasury management
-│   │   ├── treasuryTwoChains/      # Cross-chain treasury contracts
-│   │   └── p2pSwap/P2PSwap.sol     # Peer-to-peer token exchange
-│   ├── interfaces/                 # All contract interfaces
-│   └── lib/                       # Utility libraries
-```
-
-### Quick Integration Example
-
-```solidity
-// SPDX-License-Identifier: MIT
-pragma solidity ^0.8.19;
-
-import "@evvm/testnet-contracts/interfaces/IEvvm.sol";
-import "@evvm/testnet-contracts/interfaces/ITreasury.sol";
-
-contract MyDApp {
-    IEvvm public immutable evvm;
-    ITreasury public immutable treasury;
-    
-    constructor(address _evvm, address _treasury) {
-        evvm = IEvvm(_evvm);
-        treasury = ITreasury(_treasury);
-    }
-    
-    function getEvvmInfo() external view returns (string memory name, uint256 id) {
-        name = evvm.getEvvmName();
-        id = evvm.getEvvmID();
-    }
-}
-```
-
-### Available Contracts
-
-#### Core Contracts
-- `contracts/evvm/Evvm.sol` - Main EVVM virtual machine implementation
-- `contracts/nameService/NameService.sol` - Domain name resolution system
-- `contracts/staking/Staking.sol` - Token staking and rewards mechanism
-- `contracts/staking/Estimator.sol` - Staking rewards estimation and calculation
-- `contracts/treasury/Treasury.sol` - Manages deposits and withdrawals
-- `contracts/p2pSwap/P2PSwap.sol` - Peer-to-peer decentralized token exchange service
-
-#### Cross-chain Treasury
-- `contracts/treasuryTwoChains/TreasuryHostChainStation.sol` - Host chain treasury management
-- `contracts/treasuryTwoChains/TreasuryExternalChainStation.sol` - External chain treasury management
-
-#### Interfaces
-All contracts have corresponding interfaces in the `interfaces/` directory:
-- `interfaces/IEvvm.sol`
-- `interfaces/INameService.sol`
-- `interfaces/IStaking.sol`
-- `interfaces/IEstimator.sol`
-- `interfaces/ITreasury.sol`
-- `interfaces/ITreasuryHostChainStation.sol`
-- `interfaces/ITreasuryExternalChainStation.sol`
-- `interfaces/IP2PSwap.sol`
-
-#### Utility Libraries
-- `lib/AdvancedStrings.sol` - Advanced string manipulation utilities
-- `lib/SignatureRecover.sol` - Signature recovery utilities
-- `lib/Erc191TestBuilder.sol` - ERC-191 signature testing utilities
-- `lib/StakingServiceHooks.sol` - Simplified staking integration for service contracts
-
-### Import Patterns
-
-#### Individual Contract Imports
-```solidity
-import "@evvm/testnet-contracts/contracts/evvm/Evvm.sol";
-import "@evvm/testnet-contracts/interfaces/IEvvm.sol";
-import "@evvm/testnet-contracts/lib/AdvancedStrings.sol";
-```
-
-#### Interface-Only Imports (Recommended for DApps)
-```solidity
-import "@evvm/testnet-contracts/interfaces/IEvvm.sol";
-import "@evvm/testnet-contracts/interfaces/IStaking.sol";
-```
-
-### Dependencies
-
-#### If using NPM installation
-Dependencies are automatically handled when you install the package. However, you need to ensure you have the peer dependencies:
-
-```bash
-npm install @openzeppelin/contracts
-```
-
-For cross-chain functionality, you might also need:
-```bash
-npm install @hyperlane-xyz/core
-```
-
-#### If using Forge installation
-You need to manually install all dependencies:
+Guide: How to build on top of EVVM (library): https://www.evvm.info/docs/HowToMakeAEVVMService
 
-```bash
-forge install OpenZeppelin/openzeppelin-contracts
-forge install hyperlane-xyz/hyperlane-monorepo  # For cross-chain functionality
-```
-
-## Repository Structure
-- `evvm` — CLI executable - Main entry point for all EVVM commands
-- `cli/` — CLI source code (TypeScript)
-  - `index.ts` — Main entry point and CLI initialization
-  - `commands/` — Command implementations
-    - `deploy/` — Deployment command modules
-      - `deploySingle.ts` — Single-chain deployment
-      - `deployCross.ts` — Cross-chain deployment
-    - `register/` — Registration command modules
-      - `registerSingle.ts` — Single-chain registration
-      - `registerCross.ts` — Cross-chain registration
-    - `developer.ts` — Developer utilities
-    - `help.ts` — Help documentation
-    - `version.ts` — Version information
-    - `registerEvvm.ts` — EVVM registration logic
-    - `setUpCrossChainTreasuries.ts` — Cross-chain treasury setup
-  - `utils/` — Utility functions
-    - `configurationInputs.ts` — Configuration input handling
-    - `crossChain.ts` — Cross-chain utilities
-    - `explorerVerification.ts` — Block explorer contract verification
-    - `foundry.ts` — Foundry integration and scripts
-    - `prompts.ts` — Interactive CLI prompts
-    - `rpc.ts` — RPC endpoint management and fallback
-    - `validators.ts` — Input validation functions
-  - `constants/` — CLI constants and configuration
-    - `ChainData.json` — Network and chain configuration data
-    - `index.ts` — Constants exports
-  - `types/` — TypeScript type definitions
-    - `index.ts` — Type definitions
-- `src/contracts/evvm/` — Core EVVM contracts and storage
-- `src/contracts/nameService/` — NameService contracts for domain management
-- `src/contracts/staking/` — Staking and Estimator contracts
-- `src/contracts/treasury/` — Treasury contract for managing deposits and withdrawals
-- `src/contracts/p2pSwap/` — P2P token exchange service contracts
-- `src/lib/` — Shared Solidity libraries (AdvancedStrings, SignatureRecover, etc.)
-- `script/` — Foundry deployment scripts (e.g., `Deploy.s.sol`)
-- `lib/` — External dependencies (OpenZeppelin, Uniswap v3, forge-std)
-- `broadcast/` — Foundry deployment artifacts and transaction history
-- `cache/` — Foundry compilation cache
-- `input/` — Configuration files for deployment (generated by CLI)
-
-## Prerequisites
-- [Foundry](https://getfoundry.sh/) (Solidity development toolkit)
-- [Bun](https://bun.sh/) v1.0 or higher (JavaScript runtime for CLI - faster than Node.js)
-- Git (for cloning and managing the repository)
-- Environment variables set up (`.env` file with API keys and RPC URLs)
-
-> **Note**: The CLI uses Bun for superior performance. If you don't have Bun installed, you can install it with:
-> ```bash
-> curl -fsSL https://bun.sh/install | bash
-> ```
-
-### Environment Setup
-Create a `.env` file with your configuration:
-```bash
-# Ethereum Sepolia RPC (primary endpoint)
-RPC_URL_ETH_SEPOLIA=https://0xrpc.io/sep
-
-# Arbitrum Sepolia RPC (primary endpoint)
-RPC_URL_ARB_SEPOLIA=https://sepolia-rollup.arbitrum.io/rpc
-
-# Etherscan API key for contract verification
-ETHERSCAN_API=<YOUR_ETHERSCAN_API_KEY>
-```
-
-**Note**: The deployment wizard includes automatic RPC fallback mechanisms. If your primary RPC endpoint fails, it will automatically try alternative endpoints to ensure deployment success. See the [RPC Reliability](#rpc-reliability) section for details.
-
-### Security Setup - Import Private Key
-Before deploying to testnets, securely import your private key using Foundry:
-```bash
-cast wallet import defaultKey --interactive
-```
-This command will prompt you to enter your private key securely. The key will be encrypted and stored locally by Foundry.
-
-> **Note**: `defaultKey` is the default alias used in the makefile and deployment scripts. If you prefer to use a different alias, simply replace `defaultKey` with your chosen name in both the import command and update the corresponding references in the makefile and scripts.
-
-> **Security Note**: Never commit real private keys to version control. Always use the secure wallet import method above for testnet and mainnet deployments.
-
-## Key Dependencies
-- [OpenZeppelin Contracts](https://github.com/OpenZeppelin/openzeppelin-contracts)
-
-## Deploy Your Own EVVM
-
-Want to create your own virtual blockchain? Follow these steps to deploy a complete EVVM instance on testnets:
-
-> **What you'll get**: Your own virtual blockchain with custom tokens, domain system, staking rewards, and treasury management - all deployed and verified on public testnets.
-
-### 1. Clone and Install
+Quick start (2 min)
+1) Clone & install
 ```bash
 git clone --recursive https://github.com/EVVM-org/Testnet-Contracts
 cd Testnet-Contracts
 make install
 ```
 
-### 2. Make CLI Globally Available (Optional but Recommended)
-```bash
-# Make the CLI executable
-chmod +x evvm
-
-# Add to your PATH (choose one method):
-# Method 1: Create symlink in local bin
-mkdir -p ~/.local/bin
-ln -s $(pwd)/evvm ~/.local/bin/evvm
-
-# Method 2: Add to PATH in your shell profile
-echo 'export PATH="'$(pwd)':$PATH"' >> ~/.bashrc  # or ~/.zshrc
-source ~/.bashrc  # or source ~/.zshrc
-
-# Verify installation
-evvm version
-```
-
-Once installed, you can use `evvm` commands from anywhere in your terminal.
-
-### 3. Environment Setup
-Create `.env` file with your configuration:
+2) Prepare environment
 ```bash
 cp .env.example .env
-# Add your RPC URLs and API keys
+# Edit RPC_URL, ETHERSCAN_API, etc.
 ```
 
-### 4. Secure Key Import
+3) Import wallet (secure)
 ```bash
 cast wallet import defaultKey --interactive
 ```
 
-### 5. Deploy Using the CLI
-
-The **recommended way** to deploy is using the EVVM CLI. You have two options:
-
-**Option A: Using Global CLI (Recommended - if you completed step 2)**
-```bash
-evvm deploy
-```
-
-**Option B: Using NPM from the repository directory**
-```bash
-npm run wizard
-```
-
-**Option C: Using CLI with custom options**
-```bash
-# Skip interactive setup and use existing configuration
-evvm deploy --skipInputConfig
-
-# Deploy with a specific wallet
-evvm deploy --walletName myWallet
-
-# Combine options for quick deployment
-evvm deploy -s -w myWallet
-```
-
-The interactive deployment wizard will guide you through:
-- **Prerequisites check** (Foundry, Git, Node.js)
-- **Dependency initialization** (git submodules - automatic)
-- **Administrator addresses** (admin, golden fisher, activator)
-- **EVVM metadata** (name, principal token details)
-- **Advanced parameters** (supply, rewards) - optional
-- **Network selection** (Ethereum Sepolia, Arbitrum Sepolia, or custom RPC)
-- **Wallet selection** (from your Foundry keystores)
-- **Automatic deployment** with contract verification
-- **Deployment summary** with all contract addresses and explorer links
-- **Registry EVVM registration** (cross-chain registration on Ethereum Sepolia)
-- **EVVM ID configuration** (automatic setup on your deployment chain)
-
-**What happens after deployment:**
-- All 6 core contracts deployed and verified on your chosen network
-- Complete deployment summary displayed with:
-  - EVVM Core contract address
-  - Treasury contract address
-  - Staking, Estimator, NameService, and P2PSwap addresses
-  - Direct links to block explorer for each contract
-- **Cross-chain registration flow:**
-  1. Registry registration happens on Ethereum Sepolia (where the Registry EVVM lives)
-  2. You receive a unique EVVM ID (e.g., ID: 1090)
-  3. The EVVM ID is then set on your deployed contract (on your deployment chain)
-  4. Both transactions show explorer links for verification
-
-That's it! Your EVVM virtual blockchain is now deployed, verified, and ready to use.
-
-## CLI Commands Reference
-
-The EVVM CLI provides powerful commands for managing your EVVM deployments:
-
-### Deploy Command
-
-Deploy a new EVVM instance with interactive configuration:
-
-```bash
-evvm deploy [options]
-```
-
-**Options:**
-- `--skipInputConfig`, `-s` - Skip interactive setup, use existing `./input/Inputs.sol`
-- `--walletName <name>`, `-w <name>` - Specify Foundry wallet (default: `defaultKey`)
-
-**Examples:**
+4) Deploy (interactive)
 ```bash
-# Interactive deployment with configuration wizard
+# If installed globally:
 evvm deploy
-
-# Deploy using existing configuration
-evvm deploy --skipInputConfig
-
-# Deploy with specific wallet
-evvm deploy --walletName myWallet
-
-# Quick deploy with existing config and custom wallet
-evvm deploy -s -w production
-```
-
-### Register Command
-
-Register an existing EVVM instance in the registry:
-
-```bash
-evvm register [options]
+# Or from repo:
+bun run evvm deploy
 ```
+Quick Start (CLI): https://www.evvm.info/docs/QuickStart
 
-**Options:**
-- `--evvmAddress <address>` - EVVM contract address to register
-- `--walletName <name>`, `-w <name>` - Foundry wallet name (default: `defaultKey`)
-- `--useCustomEthRpc` - Use custom Ethereum Sepolia RPC for registry calls
-
-**Examples:**
-```bash
-# Register with prompts for missing information
-evvm register
+CLI - common commands
+- evvm deploy       # deploy EVVM (single or cross-chain)
+- evvm register     # register EVVM in registry
+- evvm fulltest     # run full test suite
+- evvm help         # show CLI help
+- evvm version      # CLI version
 
-# Register with specific EVVM address
-evvm register --evvmAddress 0x123...
+Library usage (quick)
+- NPM: `npm install @evvm/testnet-contracts`
+- Forge: `forge install EVVM-org/Testnet-Contracts`
+- Import interfaces: `import "@evvm/testnet-contracts/interfaces/IEvvm.sol";`
 
-# Register with custom wallet and RPC
-evvm register --evvmAddress 0x123... --walletName myWallet --useCustomEthRpc
-```
-
-**Note**: The RPC URL for your deployment chain is read from the `RPC_URL` environment variable in your `.env` file.
-
-### Test Command
-
-Run the complete EVVM test suite:
-
-```bash
-evvm fulltest
-```
-
-Executes all unit tests with:
-- Test results summary
-- Detailed execution logs
-- Gas usage reports
-- Progress indicators
-
-### Help Command
-
-Display comprehensive CLI documentation:
-
-```bash
-evvm help
-# or
-evvm --help
-evvm -h
-```
-
-### Version Command
-
-Show current CLI version:
-
-```bash
-evvm version
-# or
-evvm --version
-evvm -v
-```
-
-### Global Options
-
-These options work with any command:
-
-- `-h`, `--help` - Show help for the command
-- `-v`, `--version` - Show CLI version
-
-### Environment Variables
-
-The CLI reads configuration from your `.env` file:
-
-```bash
-# Required for deployment
-RPC_URL=https://sepolia-rollup.arbitrum.io/rpc
-
-# Optional: Custom Ethereum Sepolia RPC (for registry operations)
-ETH_SEPOLIA_RPC=https://eth-sepolia.public.blastapi.io
-
-# Optional: Block explorer API key for contract verification
-ETHERSCAN_API=your_api_key_here
-
-# Optional: For Blockscout verification
-BLOCKSCOUT_HOMEPAGE=https://sepolia.explorer.com
-```
-
-### CLI Features
-
-Automatic RPC Fallback:
-- Automatically tries 5 fallback endpoints if primary RPC fails
-- 99%+ deployment success rate
-- No manual intervention required
-
-Smart Prerequisites Check:
-- Validates Foundry installation
-- Verifies wallet configuration
-- Checks network connectivity
-- Initializes git submodules automatically
-
-Interactive Prompts:
-- Address validation with format checking
-- Secure password input for sensitive data
-- Arrow-key selection menus
-- Confirmation dialogs with defaults
-
-Comprehensive Error Handling:
-- Clear error messages with troubleshooting tips
-- Automatic retry on transient failures
-- Helpful suggestions for common issues
-- Direct links to documentation
-
-## Manual Configuration (Alternative)
-
-If you prefer manual control over configuration, create these files in `input/`:
-
-**input/address.json**:
-```json
-{
-  "admin": "0x...",
-  "goldenFisher": "0x...",
-  "activator": "0x..."
-}
-```
-
-**input/evvmBasicMetadata.json**:
-```json
-{
-  "EvvmName": "EVVM",
-  "EvvmID": 1,
-  "principalTokenName": "Mate token",
-  "principalTokenSymbol": "MATE"
-}
-```
-
-**input/evvmAdvancedMetadata.json**:
-```json
-{
-  "eraTokens": 1016666666500000000000000000,
-  "reward": 5000000000000000000,
-  "totalSupply": 2033333333000000000000000000
-}
-```
-
-> **Important**: The field order in `evvmAdvancedMetadata.json` **must be alphabetical** (`eraTokens`, `reward`, `totalSupply`). Foundry's `vm.parseJson` decodes fields alphabetically, not by matching field names. Do not use code formatters (like Prettier) on these files as they may reorder fields incorrectly.
-
-## Local Development & Manual Deployment
-
-### Start Local Development
-```bash
-make anvil                # Start local blockchain
-make deployLocalTestnet   # Deploy to local chain
-```
-
-### Manual Deployment to Testnets
-
-If you prefer to deploy manually after configuration:
-
-```bash
-# Ethereum Sepolia
-make deployTestnet NETWORK=eth
-
-# Arbitrum Sepolia  
-make deployTestnet NETWORK=arb
-
-# Custom RPC
-forge script script/DeployTestnet.s.sol:DeployTestnet \
-    --rpc-url <YOUR_RPC_URL> \
-    --account defaultKey \
-    --broadcast \
-    --verify \
-    --etherscan-api-key $ETHERSCAN_API
-```
-
-## Development Commands
-```bash
-make install     # Install dependencies and compile
-make compile     # Recompile contracts
-make seeSizes    # Check contract sizes
-make help        # Show all available commands
-```
-
-### NPM Scripts
-```bash
-npm run wizard           # Run interactive deployment wizard (uses CLI internally)
-npm run build           # Copy src/ files to root (for NPM publishing)
-npm run clean           # Remove copied files from root
-npm run compile         # forge build
-npm run test            # forge test
-npm run deploy:anvil    # Deploy to local Anvil
-npm run deploy:sepolia  # Deploy to Ethereum Sepolia
-npm run deploy:arbitrum # Deploy to Arbitrum Sepolia
-```
-
-### Direct CLI Usage
-
-Once you've set up the CLI executable, use it directly:
-
-```bash
-evvm deploy              # Deploy new EVVM instance
-evvm register            # Register existing EVVM
-evvm fulltest            # Run test suite
-evvm help                # Show all commands
-evvm version             # Show CLI version
-```
-
-Advantages of direct CLI usage:
-- Faster execution with Bun runtime
-- Available globally from any directory
-- Cleaner syntax
-- Better error messages
-- Tab completion support in compatible shells
-
-## RPC Reliability
-
-The deployment wizard includes an intelligent RPC fallback mechanism to ensure maximum deployment success rates, even when individual RPC providers experience downtime.
-
-### How It Works
-
-**Automatic Failover**: If your primary RPC endpoint fails, the wizard automatically tries alternative endpoints without user intervention.
-
-**Multi-Provider Support**: Each network has 5 verified RPC endpoints:
-
-**Ethereum Sepolia Fallback Chain:**
-1. `https://1rpc.io/sepolia` (1RPC - fastest)
-2. `https://ethereum-sepolia.rpc.subquery.network/public` (SubQuery)
-3. `https://ethereum-sepolia-rpc.publicnode.com` (PublicNode - stable)
-4. `https://sepolia.drpc.org` (dRPC)
-5. `https://gateway.tenderly.co/public/sepolia` (Tenderly)
-
-**Arbitrum Sepolia Fallback Chain:**
-1. `https://sepolia-rollup.arbitrum.io/rpc` (Official Arbitrum)
-2. `https://arbitrum-sepolia.gateway.tenderly.co` (Tenderly)
-3. `https://endpoints.omniatech.io/v1/arbitrum/sepolia/public` (Omnia)
-4. `https://arbitrum-sepolia-rpc.publicnode.com` (PublicNode)
-5. `https://arbitrum-sepolia.drpc.org` (dRPC)
-
-**Smart Retry Logic**: The wizard displays clear progress messages during fallback attempts and provides troubleshooting tips if all endpoints fail.
-
-### Benefits
-- **99%+ success rate** through endpoint redundancy
-- **Zero configuration** required for most users
-- **Automatic recovery** from individual RPC failures
-- **Clear visibility** into which RPC is being used
-- **Future-proof** against provider outages
-
-## Deployment Summary
-
-After successful deployment, the wizard displays a comprehensive summary of all deployed contracts:
-
-```
-DEPLOYED CONTRACTS SUMMARY
-==========================
-
-Network: Arbitrum Sepolia (Chain ID: 421614)
-
-Core Contracts:
-  EVVM:        0x3e562a2e932afd6c1630d5f3b8eb3d88a4b058c2
-               https://sepolia.arbiscan.io/address/0x3e56...
-  Treasury:    0x5c3a673dcf38e08b1f4e361ed7ed7be76df7b188
-               https://sepolia.arbiscan.io/address/0x5c3a...
-
-Supporting Contracts:
-  Staking:     0xcdef28d767f0029f0e75563c8e7ed44a2aab6cf2
-  Estimator:   0xcfff3e950c3b1f7b850394d4cf3d60b31041f139
-  NameService: 0xdfa5e2529b06683dcec37f67f0607f294809a512
-  P2PSwap:     0xef2efb60d353731287696d74d360c635844f0ae2
-
-REGISTRY EVVM REGISTRATION
-==========================
-
-  EVVM Address: 0x3e562a2e932afd6c1630d5f3b8eb3d88a4b058c2
-  Deployed on: Arbitrum Sepolia (Chain ID: 421614)
-  Registry: Ethereum Sepolia (cross-chain registration)
-
-EVVM registered with ID: 1090
-EVVM ID 1090 set on Arbitrum Sepolia
-```
-
-This summary includes:
-- Network name and chain ID
-- All 6 deployed contract addresses
-- Direct links to block explorer for verification (Etherscan for ETH Sepolia, Arbiscan for Arbitrum Sepolia)
-- Organized by contract importance (Core vs Supporting)
-- Cross-chain registration status and assigned EVVM ID
-
-## Troubleshooting
-
-### RPC Connection Issues
-
-Problem: Deployment fails with "Connection timed out" or "HTTP error 522"
-
-Solution: The wizard automatically tries fallback RPCs. If all fail:
-1. Check your internet connection
-2. Verify firewall/VPN settings aren't blocking RPC endpoints
-3. Try again later (temporary provider downtime)
-4. Update your `.env` file with a custom RPC from [chainlist.org](https://chainlist.org/)
-
-### Wallet Not Found
-
-Problem: "No wallets found" error during deployment
-
-Solution:
-```bash
-cast wallet import <WALLET_NAME> --interactive
-```
-Then run the wizard again and select your imported wallet.
-
-### Insufficient Funds
-
-Problem: Deployment fails with "insufficient funds for gas"
-
-Solution:
-1. Get testnet ETH from faucets:
-   - Ethereum Sepolia: [sepoliafaucet.com](https://sepoliafaucet.com/)
-   - Arbitrum Sepolia: [faucet.quicknode.com/arbitrum/sepolia](https://faucet.quicknode.com/arbitrum/sepolia)
-2. Verify your wallet address has received funds
-3. Run the wizard again
-
-### Git Submodules Not Initialized
-
-Problem: Compilation fails with missing dependencies
-
-Solution: The wizard automatically initializes submodules, but you can also do it manually:
-```bash
-git submodule update --init --recursive
-```
-
-### Contract Size Too Large
-
-Problem: "Contract code size exceeds 24576 bytes"
-
-Solution: The project uses `via-ir` optimization to stay under limits. If you modified contracts:
-```bash
-make seeSizes  # Check contract sizes
-```
-Consider refactoring large contracts or using libraries.
-
-### CLI Command Not Found
-
-Problem: `evvm: command not found` when trying to run CLI commands
-
-Solution: The CLI executable is not in your PATH. You have three options:
-
-1. **Run from the repository directory:**
-   ```bash
-   ./evvm deploy
-   ```
-
-2. **Add to PATH temporarily (current session only):**
-   ```bash
-   export PATH="$(pwd):$PATH"
-   evvm deploy
-   ```
-
-3. **Add to PATH permanently (recommended):**
-   ```bash
-   # For bash
-   echo 'export PATH="'$(pwd)':$PATH"' >> ~/.bashrc
-   source ~/.bashrc
-   
-   # For zsh
-   echo 'export PATH="'$(pwd)':$PATH"' >> ~/.zshrc
-   source ~/.zshrc
-   ```
-
-### Bun Not Installed
-
-Problem: CLI fails with "bun: command not found"
-
-Solution: Install Bun runtime:
-```bash
-curl -fsSL https://bun.sh/install | bash
-
-# Restart your terminal or run:
-source ~/.bashrc  # or source ~/.zshrc
-
-# Verify installation
-bun --version
-```
-
-### TypeScript/TSX Not Found
-
-Problem: `npm run wizard` fails with "tsx: command not found"
-
-Solution:
-```bash
-npm install  # Reinstall dependencies
-```
+Troubleshooting (short)
+- RPC timeouts: CLI automatically tries fallback RPCs; set `RPC_URL` in `.env` to a reliable endpoint.
+- Wallet not found: import with `cast wallet import <name> --interactive`.
+- Bun missing: install Bun (`curl -fsSL https://bun.sh/install | bash`).
+- Tests: run `evvm fulltest` or `forge test`.
 
-## Contract Architecture
-The EVVM ecosystem consists of six main contracts:
-- **Evvm.sol**: Core virtual machine implementation
-- **NameService.sol**: Domain name resolution system  
-- **Staking.sol**: Token staking and rewards mechanism
-- **Estimator.sol**: Staking rewards estimation and calculation
-- **Treasury.sol**: Manages deposits and withdrawals of ETH and ERC20 tokens
-- **P2PSwap.sol**: Peer-to-peer decentralized exchange for token trading
+Files & structure (short)
+- `src/contracts/` — core contracts (Evvm, NameService, Staking, Treasury, P2PSwap)
+- `cli/` — TypeScript CLI source
+- `script/` — Foundry deployment scripts
+- `input/` — optional JSON/Sol files generated by CLI
 
+Security & contributing (short)
+- Never commit private keys. Use `cast wallet import`.
+- Add tests for new features and open a PR.
 
-## Configuration Files
-Key files for EVVM deployment:
-- `evvm` — CLI executable entry point (run with `./evvm` or just `evvm` if in PATH)
-- `cli/` — CLI implementation (TypeScript with Bun runtime)
-- `input/Inputs.sol` — Generated deployment configuration (created by CLI wizard)
-- `.env` — Environment variables (RPC URLs, API keys)
-- `foundry.toml` — Foundry project configuration
-- `makefile` — Build and deployment automation
-- `package.json` — NPM scripts and dependencies
+If you want, I can further shorten a specific section (CLI, Library, or Troubleshooting).
 
-## Contributing
 
 **Development Flow Context**: This repository is the next step after successful playground testing. It is dedicated to advanced integration, deployment, and validation on public testnets, before mainnet implementation.
 

package/interfaces/IEvvm.sol

@@ -58,9 +58,6 @@ interface IEvvm {
     function acceptImplementation() external;
     function addAmountToUser(address user, address token, uint256 amount) external;
     function addBalance(address user, address token, uint256 quantity) external;
-    function payMultiple(EvvmStructs.PayData[] memory payData)
-        external
-        returns (uint256 successfulTransactions, bool[] memory results);
     function caPay(address to, address token, uint256 amount) external;
     function disperseCaPay(EvvmStructs.DisperseCaPayMetadata[] memory toData, address token, uint256 amount) external;
     function dispersePay(
@@ -108,6 +105,9 @@ interface IEvvm {
         address executor,
         bytes memory signature
     ) external;
+    function payMultiple(EvvmStructs.PayData[] memory payData)
+        external
+        returns (uint256 successfulTransactions, bool[] memory results);
     function pointStaker(address user, bytes1 answer) external;
     function proposeAdmin(address _newOwner) external;
     function proposeImplementation(address _newImpl) external;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@evvm/testnet-contracts",
-  "version": "2.2.1",
+  "version": "2.2.2",
   "type": "module",
   "description": "EVVM Testnet Contracts - Smart contracts and tools for scalable, modular, and cross-chain EVM virtualization",
   "files": [