cctp-bridge

KO | EN

gitlite — search

#javascript #python #hacktoberfest #react #ai #llm #rust #linux #docker #nodejs #awesome #kubernetes #vue #awesome-list

(★ 11)

An app to bridge USDC over Circle's CCTP interface.

cctp-bridge 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# CCTP Bridge

Cross-chain USDC bridge supporting **EVM ↔ EVM**, **EVM → Solana**, and **Solana → EVM** transfers using Circle's CCTP v2 protocol.

Built with Next.js App Router, Wagmi/RainbowKit (EVM), Solana Wallet Adapter, Zustand, and a custom CCTP library.

## Getting Started

```bash
bun install        # Install dependencies
bun run dev        # Start dev server (localhost:3000)
bun run lint       # Run TypeScript checks (auto-creates placeholder generated metadata if missing)
bun run build      # Build production bundle
bun run metadata:refresh # Regenerate CCTP metadata + validated RPC candidates
bun run test:fork:evm    # Optional anvil fork tests; requires EVM_FORK_*_RPC_URL
```

## Supported Bridge Routes

| Source | Destination | Implementation |
|--------|-------------|----------------|
| EVM | EVM | Direct CCTP v2 (custom library) |
| EVM | Solana | Direct CCTP v2 (custom library) |
| Solana | EVM | Direct CCTP v2 (custom library) |

## Environment Variables

```bash
NEXT_PUBLIC_BRIDGEKIT_ENV=testnet|mainnet        # Chain environment (default: testnet)
NEXT_PUBLIC_FAST_TX_FEE_BPS=4                    # Optional fast tx app fee paid by user
NEXT_PUBLIC_FEE_ADDRESS_EVM=0x...                # Required with FAST_TX_FEE_BPS for EVM fees
NEXT_PUBLIC_FEE_ADDRESS_SOL=...                  # Required with FAST_TX_FEE_BPS for Solana fees
NEXT_PUBLIC_DISABLE_BALANCE_CHECK=1              # Development only: skip client-side balance validation
NEXT_PUBLIC_DISABLE_META_ANALYTICS=1             # Optional: disable verified bridge analytics emission
CORS_ORIGIN=https://your-app-domain.example      # Required in CI for RPC validation; local fallback defaults to https://cctp.io
EVM_FORK_ETH_RPC_URL=https://...                 # Optional: Ethereum fork tests
EVM_FORK_ARB_RPC_URL=https://...                 # Optional: Arbitrum fork tests
TURSO_DATABASE_URL=libsql://your-database.turso.io # Server-only first-party statistics database
TURSO_AUTH_TOKEN=...                               # Server-only Turso token
```

Bridge volume records are submitted server-side through `/api/events/burn` after a burn transaction is submitted. The route returns immediately and schedules the first-party Turso insert after the response. Turso stores an idempotent append-only `bridge_burn_submissions` ledger with origin/destination chains and addresses, entered amount, transfer type, app fee, Circle fee, and timestamps. Run `bun run db:generate` after schema changes and `bun run db:migrate` with the server-only Turso variables loaded to apply migrations.

Detailed bridge-burn data is stored only in Turso; it is not exported as a Vercel custom event. Vercel receives only the `bridge_verified_view` counter after a submitted bridge is verified. That counter is operational telemetry and must not be used for bridge-volume reporting.

Query first-party statistics for a supported rolling window with `bun run db:bridge-report -- --days 7|30|90|120`. The report prints total/fast/standard volume, app-collected fast fees, optional standard support contributions, and bridge counts. Circle relay fees remain available separately in the ledger and are not included in the app-fee totals.
Fast tx fees are charged only for fast transfers and are included in the entered amount. Standard transfers of 100,000 USDC or more offer an optional 2 bps contribution after the user presses Bridge Standard; declining proceeds with no app fee. On EVM, Circle's bridge contract routes 90% to `NEXT_PUBLIC_FEE_ADDRESS_EVM`; on Solana, the app adds an atomic SPL transfer that routes 100% to `NEXT_PUBLIC_FEE_ADDRESS_SOL`. Deprecated variables `NEXT_PUBLIC_BRIDGEKIT_RPC_OVERRIDES` and `NEXT_PUBLIC_BRIDGEKIT_TRANSFER_SPEED` are ignored and now emit runtime warnings when present.

## Architecture

- **`lib/cctp/`** — Custom CCTP v2 library with unified interfaces for EVM and Solana
- **`lib/metadata/`** — metadata loaders/types (generated JSON lives under `.generated/metadata/`)
- **`lib/rpc/`** — app-owned wallet-first RPC routing and rotating fallback transports
- **`lib/bridgeConfig.ts`** — compatibility facade backed by local metadata + RPC modules
- **`components/bridging-state/`** — Modular bridge progress UI (decomposed into hooks + sub-components)

## Routes

- **`/`** — bridge setup form and pre-burn pending (query-driven)
- **`/bridge`** — add pending transaction form (history button destination, query-prefill via `id`, `hash`, `error`)
- **`/bridge/<source_chain_id>/<tx_hash_or_nonce>`** — shareable tracking route; invalid or unrecoverable IDs redirect to `/bridge` with prefilled query params

## Metadata & RPC Generation

- `scripts/generate-cctp-metadata.ts` builds `.generated/metadata/cctp.generated.json` from BridgeKit.
- `scripts/generate-rpc-candidates.ts` fetches Chainlist RPCs, runs CORS validation with `Origin: $CORS_ORIGIN`, and writes:
  - `.generated/metadata/rpc.generated.json`
  - `.generated/reports/rpc-validation-report.json`
- `bun run build` runs `metadata:refresh` automatically via `prebuild`.

See `CLAUDE.md` for detailed architecture documentation.

cctp-bridge

cctp-bridge 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

cctp-bridge

cctp-bridge 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README