Skip to main content
Compose.Market supports multiple EVM chains with a unified Smart Account experience. Users get the same Smart Account address across all supported chains through deterministic CREATE2 deployment.

​
Cross-Chain Identity

The key innovation is universal Smart Account addresses. A user who creates a Smart Account on Avalanche Fuji will have the exact same address on Cronos Testnet.

​
How It Works

The Smart Account address is derived from:
Since we deploy the same AccountFactory at the same address on all chains, users automatically get identical Smart Account addresses.

​
Cronos Testnet Deployment

Cronos Testnet lacks a native ERC-4337 bundler, so we deployed the full AA infrastructure ourselves using CREATE2 to match ThirdWeb’s universal addresses.

​
Deployment Method

We extracted the deployment parameters from the original Ethereum mainnet transaction and replayed them on Cronos:
  1. Find original deployment tx on Etherscan/Blockscout
  2. Extract CREATE2 salt (first 32 bytes of input data)
  3. Extract init code (remaining bytes)
  4. Call Arachnid’s CREATE2 deployer (0x4e59b44847b379578588920cA78FbF26c0B4956C)
This produces identical addresses on any EVM chain where Arachnid’s deployer exists.

​
Deployed Contracts

​
Supported Chains

​
Account Registration Flow

When a user connects on Cronos Testnet:

​
API Endpoints

​
POST /api/aa/prepare

Prepare a UserOperation for signing.

​
POST /api/aa/submit

Submit a signed UserOperation for execution.

​
POST /api/aa/register-cronos

Deploy a Smart Account on Cronos (if not already deployed).

​
Key Files

​
Value for Cronos Ecosystem

This work provides production-ready ERC-4337 v0.7 infrastructure for Cronos Testnet:
  • Universal AccountFactory: Same address as Ethereum, Fuji, and other chains
  • EntryPoint v0.7: Latest standard with PackedUserOperation support
  • Gasless transactions: SimplePaymaster for gas sponsorship
  • Cross-chain identity: Users keep the same Smart Account address
Developers building on Cronos can reuse these contracts or follow the same CREATE2 deployment pattern.