Nexwave Gateway

Unified crosschain USDC balance via Circle Gateway + Circle Programmable Wallets. Deposit USDC on any supported chain, check your unified balance, and instantly mint USDC on any destination chain in <500ms — no bridging, no raw private keys.

MIT-0 · Free to use, modify, and redistribute. No attribution required.
0 · 1.1k · 0 current installs · 0 all-time installs
MIT-0
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Suspicious
medium confidence
Purpose & Capability
The skill claims to provide unified USDC access via Circle Gateway and Circle Programmable Wallets and the code, SKILL.md, and README all implement that flow (Gateway API client, EIP-712 typed data, Circle MPC wallet SDK). Requesting CIRCLE_API_KEY, CIRCLE_ENTITY_SECRET, and CIRCLE_WALLET_SET_ID is expected for this purpose. However, the registry metadata at the top of the package lists "Required env vars: none" while the SKILL.md and code clearly require those env vars — an inconsistency in the manifest/metadata.
Instruction Scope
Runtime instructions are scoped to the Gateway use-case: run setup.sh, install Node deps, run check-balance.js / deposit.js / transfer.js. The SKILL.md and scripts only reference Circle credentials, Gateway API, and RPC endpoints needed for supported testnets. There are no instructions to read unrelated local files, the shell history, or arbitrary system configuration.
Install Mechanism
There is no remote download of arbitrary archives; setup.sh runs npm install for known packages (viem, dotenv, @circle-fin/developer-controlled-wallets) and copies the included JS files into a gateway-app directory. This is a typical local project setup. Risk is moderate because running setup.sh will write files and install Node packages — but the packages are standard and the script does not fetch code from unknown URLs.
!
Credentials
The skill requires developer-level Circle credentials (CIRCLE_API_KEY, CIRCLE_ENTITY_SECRET, CIRCLE_WALLET_SET_ID) which legitimately enable the described behavior but are highly sensitive: they allow creating wallets, signing transactions via Circle's API, and moving funds. The requirement is proportionate to the functionality, but because the author/source is unverified and the package metadata omitted these env vars, users should treat the credentials as high-risk and avoid using production/mainnet funds without full trust and review. setup.sh also creates a local .env template — ensure it is stored securely.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and won't be force-included. It copies files into a local gateway-app directory and creates a .env template when you run setup.sh — expected for a local demo app. There is no evidence it alters global agent settings or other skills' configurations.
What to consider before installing
This package implements exactly what it says: a testnet demo of Circle Gateway + Circle Programmable (MPC) wallets. However: 1) The skill requires sensitive Circle developer credentials (API key, entity secret, wallet set ID) — these grant the ability to create/sign transactions and should never be uploaded to untrusted systems or used with real/mainnet funds until you fully trust the code and author. 2) The registry metadata omitted the required env vars; that mismatch suggests sloppy packaging — review the SKILL.md and code before running. 3) Confirm the author (nexwave) and owner, and prefer running the setup and scripts in an isolated environment (container or VM) and on testnets first. 4) Inspect the included JS files yourself (they are present) and verify endpoints (Circle Gateway testnet URL, Circle SDK, Arc RPC) are correct. If you are not comfortable with handling API secrets or signing transactions via a third-party service, do not install or supply credentials.

Like a lobster shell, security has layers — review code before you run it.

Current versionv1.0.2
Download zip
latestvk973j74bfq353gf77axven5mnh80sg7g

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

SKILL.md

Nexwave Gateway — Unified Crosschain USDC for OpenClaw Agents

What This Skill Does

Circle Gateway gives you a single unified USDC balance that is instantly accessible on any supported chain in under 500 milliseconds. Instead of holding separate USDC balances on Ethereum, Base, Avalanche, etc., you deposit USDC into Gateway on any chain and can mint it out on any other chain — instantly.

This is fundamentally different from bridging. There are no liquidity pools, no bridge operators, no 15-minute waits. Gateway uses a deposit → sign burn intent → receive attestation → mint flow that executes in <500ms.

Supported Chains (Testnet)

ChainDomain IDUSDC Address
Ethereum Sepolia00x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238
Base Sepolia60x036CbD53842c5426634e7929541eC2318f3dCF7e
Arc Testnet260x3600000000000000000000000000000000000000

Note: Arc is Circle's purpose-built L1 blockchain where USDC is the native gas token. No separate gas token needed — USDC covers everything. Arc has the fastest Gateway finality at ~0.5 seconds.

Gateway Contracts (same address on all EVM chains):

  • Gateway Wallet: 0x0077777d7EBA4688BDeF3E311b846F25870A19B9
  • Gateway Minter: 0x0022222ABE238Cc2C7Bb1f21003F0a260052475B

Gateway API (testnet): https://gateway-api-testnet.circle.com/v1

Prerequisites

  1. Circle Developer Account with API key and entity secret (https://console.circle.com)
  2. The circle-wallet skill installed (clawhub install eltontay/circle-wallet) with a wallet set containing wallets on ETH-SEPOLIA, BASE-SEPOLIA, and ARC-TESTNET
  3. Testnet USDC from https://faucet.circle.com (20 USDC per address per chain, every 2 hours)
  4. Testnet ETH for gas on Sepolia/Base Sepolia (use Google's Sepolia faucet). On Arc, USDC is the native gas token — same faucet covers everything.
  5. Node.js installed with the viem, dotenv, and @circle-fin/developer-controlled-wallets packages

How To Use This Skill

Step 1: Setup the Project

Run the setup script to initialize the project with all dependencies:

cd /path/to/nexwave-gateway && bash setup.sh

This creates a gateway-app/ directory with all necessary files pre-configured.

Step 2: Check Gateway Info and Your Balance

cd gateway-app && node check-balance.js

This queries the Gateway API for supported chains and shows your unified USDC balance across all chains.

Step 3: Deposit USDC into Gateway

node deposit.js

This deposits USDC into the Gateway Wallet contract on Ethereum Sepolia and Arc Testnet. After deposit and chain finality, your unified balance is credited. Arc finalizes in ~0.5 seconds; Ethereum may take up to 20 minutes.

Step 4: Transfer USDC Crosschain Instantly

node transfer.js

This creates burn intents, signs them via Circle Programmable Wallets (MPC — no raw private keys), submits them to the Gateway API for attestation, and mints USDC on Base Sepolia. The attestation response typically arrives in <500ms.

Key Concepts

Unified Balance: After depositing USDC into Gateway on any chain, the Gateway system credits your address with a unified balance. This balance is not locked to any specific chain — it can be accessed on any supported chain.

Burn Intent: To withdraw from your unified balance to a specific chain, you sign a "burn intent" — an EIP-712 typed data structure specifying the source chain, destination chain, amount, and recipient. Signing is done securely via Circle's MPC Programmable Wallets (no raw private keys). Gateway verifies your balance is sufficient and returns a signed attestation.

Circle Programmable Wallets: Instead of raw private keys in .env files, this skill uses Circle's developer-controlled wallets backed by multi-party computation (MPC). The private key is never exposed — signing happens server-side via Circle's API. This makes the skill safe for agent use without risk of key exfiltration.

Attestation: The Gateway API's signed proof that authorizes minting on the destination chain. You submit this attestation to the Gateway Minter contract on the destination chain to receive USDC.

Fees: 0.5 basis points (0.005%) during the early access period (through June 30, 2026). Plus base gas fees for on-chain transactions.

Flow Diagram

Agent deposits USDC on Chain A
        │
        ▼
Gateway Wallet Contract (approve + deposit)
        │
        ▼
Wait for chain finality → Unified balance credited
        │
        ▼
Agent signs burn intent (EIP-712 via Circle MPC Wallets)
        │
        ▼
Submit to Gateway API ──► Attestation returned (<500ms)
        │
        ▼
Submit attestation to Gateway Minter on Chain B
        │
        ▼
USDC minted on Chain B for recipient

Agent Use Cases

  • Multi-chain arbitrage: Access USDC on any chain instantly to capture price differences
  • Cross-chain payments: Pay for services on any chain from a single balance
  • Treasury management: Consolidate USDC from multiple chains into one balance
  • Agent-to-agent commerce: Accept payment on one chain, spend on another without delays
  • Capital efficiency: No need to pre-position USDC across chains

Troubleshooting

  • "Insufficient balance": Wait for chain finality after depositing. Ethereum takes ~20 min, Arc is ~0.5 seconds.
  • "Gateway deposit not yet picked up": The Gateway API waits for block confirmations. Be patient on Ethereum.
  • Gas errors: On Ethereum/Base you need testnet ETH for gas. On Arc, USDC is the gas token — same faucet covers everything.
  • Faucet limits: You can get 20 USDC per address per chain every 2 hours from faucet.circle.com.

References

Files

11 total
Select a file
Select a file to preview.

Comments

Loading comments…