CROSS Bridge (CrossDefi)

Bridge tokens between BSC, CROSS Chain, and Klaytn with one sentence. Native / EIP-2612 permit / approve+bridge auto-dispatch.


Bridge tokens across chains with one sentence.

Drives the CrossDefi swap-bridge backend. Lists pairs, resolves tokens, quotes with fees + native-gas breakdown, polls status, and executes the bridge with the right path automatically.


1. Install

The block below is a natural-language prompt to paste into your AI agent — not a terminal command.

Clone https://github.com/to-nexus/skill-cross-crossd into a temporary directory and run the install.sh script inside it to install the cross-crossd skill into my environment. Tell me the result in one line when you're done.
🚧

Bash execution required.

bridge signs transactions; quote / pairs / status are pure read.

Install all CROSS skills at once

Clone https://github.com/to-nexus/cross-skills-suite into a temporary directory and run the bootstrap.sh script inside it to install every CROSS skill into my environment. Tell me which skills succeeded and which failed.

2. Where it runs

✅ Supported · CLI agents with Bash access

Claude Code (CLI) · OpenClaw · Cursor Composer · Codex CLI · Aider · Goose · Gemini CLI · OpenInterpreter · any other Bash-capable CLI.

❌ Not supported · Browser / hosted only

Claude.ai (web) · ChatGPT (web) · Gemini (web) · Copilot Chat (web). The bridge tx signing needs viem in a local Node runtime.


3. What you can do

Read · no auth

SubcommandWhat it does
🟢 pairsList supported bridge pairs.
🟢 tokensResolve token metadata for a chain.
🟢 quoteQuote with full fee + native-gas breakdown.
🟢 statusPoll a bridge progress by permitId or tx hash.

Auth & write

SubcommandWhat it does
🟡 historyYour bridge history (auth required).
🔴 bridgeExecute the bridge. Auto-dispatches the right path: native (msg.value), permit (EIP-2612, no source gas), or approve+bridge (ERC-20).

4. Try it

brídge pairs 보여줘
BSC chain 의 토큰 메타데이터
USDT BSC → CROSS 1.0 견적 (수수료/도착시간 포함)
내 브릿지 진행상황 0xabc...
permit-hash 12345 상태
USDT 1개 BSC → CROSS 로 브릿지 (확정)
1 native CROSS 를 BSC 로 보내
List bridge pairs
Show BSC token metadata
Quote 1 USDT BSC to CROSS with fees and ETA
Check status of bridge tx 0xabc...
Permit-hash 12345 status
Bridge 1 USDT from BSC to CROSS — confirmed
Send 1 native CROSS to BSC

5. Command reference

commandargsauthmutationdescription
pairsreadSupported pairs.
tokens--chain <id>readToken metadata.
quote<FROM-chainId-tokenAddr> <TO-chainId-tokenAddr> <amount>readQuote + ETA + swap-pool route.
status<permitId> or --tx <hash>readBridge progress.
historyPKreadYour bridge history.
bridge<FROM> <TO> <amount> [--path=native|permit|approve] [--max-approve] [--confirm]PKtx (or permit)Execute the bridge.
📘

Path auto-detection. bridge.mjs picks native if the from-token is the chain's native asset, permit if EIP-2612 is supported, else approve+bridge. Override with --path=... if you need to.


6. Safety & credentials

🛑

bridge signs on-chain transactions (or off-chain permits).

RailWhat it does
Required credentialPRIVATE_KEY (EOA) for bridge / history. Read ops need nothing.
Source-chain id checkEvery signed tx aborts unless eth_chainId matches the <FROM> chain id.
MAX_BRIDGE_NOTIONALEnv cap. Aborts above.
CONFIRM_THRESHOLDBridges above this (default 1) require explicit --confirm.
MIN_GAS_NATIVESource-chain native floor (default 0.001).
Pair existence guardRefuses to sign for any pair not in /bridge/pairs.
💡

Hosted-agent tip. Use a disposable wallet. The skill never echoes PRIVATE_KEY back to the transcript.


7. Troubleshooting

wrong_chain on the bridge call.

Your RPC for the source chain is pointing at the wrong network. Set BSC_RPC_URL / CROSS_RPC_URL / KLAYTN_RPC_URL accordingly, or remove the override to use wallet-server.crosstoken.io defaults.

Bridge sent but funds haven't arrived on the destination.

Poll status with the permit id or tx hash. Cross-chain finality is 1–5 min typical; some routes can be longer if the relayer is queued.

pair_not_supported

The from-chain/to-chain/token combination isn't in /bridge/pairs. Run "list bridge pairs" to see what's supported.

Permit path returned no tx hash.

That's expected. Permit path uses EIP-2612 — the back-end submits the on-chain call. You get a permitId back; track it with status <permitId>.

Approve tx succeeded but bridge tx failed.

The allowance is set; only the bridge call reverted (usually slippage / lock-busy / paused). Retry bridge — the second call skips the approve step automatically.


© 2025 NEXUS Co., Ltd. All Rights Reserved.