[DIS] CKB × NEAR Intents: Building a Cross-Chain Bridge and Multichain Swap Gateway

[DIS] CKB × NEAR Intents: Building a Cross-Chain Bridge and Multichain Swap Gateway

Funding Requested: 7,000 USDT equivalent
Estimated Duration: 8 weeks
Applicant / Team: FoundationLab
GitHub: ckbswap

1. Executive Summary

This project proposes building a bridge between CKB and NEAR and integrating with NEAR Intents to create a gateway for exchanging CKB across blockchain ecosystems.

Users will be able to bridge CKB to NEAR, receive its bridged representation, nCKB, and exchange it for a target asset through an intent-based swap flow. In the reverse direction, users will be able to exchange supported assets for nCKB and redeem it for native CKB.

The project will cover architecture, bridge contracts, MPC signing, relayer services, Intents integration, a reference quoting service, a user interface, and testing documentation. The deliverable will be a reproducible testnet prototype demonstrating the complete bridge-and-swap lifecycle.

We request 7,000 USDT equivalent from the CKB Community Fund DAO to complete this work over 8 weeks, establishing the technical foundation for future mainnet integration and liquidity partnerships.

2. Background and Motivation

Expanding CKB’s adoption requires making it easier for users from other ecosystems to acquire and use CKB, while giving CKB holders access to a broader range of assets and applications.

A bridge enables asset transfers between networks. An exchange integration addresses the next question: what can users do with those assets after bridging?

This project combines both capabilities:

Native CKB → nCKB on NEAR → NEAR Intents settlement → Target asset

The reverse path will be:

Source asset → NEAR Intents settlement → nCKB → Native CKB redemption

NEAR Intents provides infrastructure for expressing desired outcomes, obtaining quotes, and settling exchanges. Its documentation describes cross-chain swap interfaces and custom contract integrations. NEAR Intents documentation

By connecting CKB to this infrastructure, the project aims to reduce the friction of entering and leaving the CKB ecosystem and make CKB more accessible to multichain users and applications.

3. Project Objectives

Build a bidirectional CKB–NEAR bridge

Implement CKB deposits, nCKB issuance on NEAR, nCKB burning, and withdrawals back to CKB.

nCKB will follow the NEP-141 token standard and use a reserve accounting model designed around 1 nCKB representing 1 CKB. Deposit, issuance, withdrawal, and reserve reconciliation rules will be documented publicly.

Enable intent-based nCKB swaps

Implement the integration needed to deposit nCKB into an Intents settlement contract, query balances, obtain quotes, sign swap intents, execute settlement, and withdraw assets.

This phase will include a reference quoting and execution service that demonstrates bidirectional swaps between nCKB and at least one test asset in a controlled environment.

Provide a unified user interface

Users will be able to view deposit addresses, select a swap direction, review quotes and fees, and track bridge and swap progress through one interface.

Establish a foundation for broader CKB distribution

Publish reusable interfaces and documentation for future integrations with wallets, aggregators, and cross-chain applications.

The initial scope focuses on native CKB. Support for additional CKB ecosystem assets will be evaluated separately based on demand, security requirements, and liquidity availability.

4. Product and Technical Design

CKB-to-NEAR deposits

Users deposit CKB into designated addresses. After the configured number of confirmations, an authorized relayer submits the deposit record to the NEAR bridge contract, which processes nCKB issuance.

Deposits will be identified by transaction hash and output index to prevent duplicate processing and associate each deposit with its recipient and amount.

NEAR-to-CKB withdrawals

Users submit withdrawal requests, and the bridge contract handles nCKB burning and withdrawal state.

The system will use NEAR Chain Signatures to request MPC signatures for CKB withdrawal transactions. The contract will validate recipient amounts and change destinations, while the relayer handles broadcasting, confirmation tracking, and status updates.

NEAR Intents integration

After bridging, nCKB can enter an intent-based exchange flow. A reference execution service will provide quotes and submit compatible execution intents alongside the user’s signed intent.

The testing environment will use the open-source NEAR Intents Verifier contract and test assets to validate actual contract settlement. Project-operated test deployments will be clearly distinguished from production services. NEAR Intents contracts

The project will also prepare asset integration information, quoting interfaces, and liquidity requirements for future production integration.

Public nCKB swaps will require execution providers willing to quote and supply liquidity. Issuing a bridged token does not automatically make it available across the public swap network. NEAR Intents’ asset onboarding guidance identifies liquidity and solver coordination as part of this process. Token onboarding guidance

User interface

A lightweight web application will support:

  • Wallet connection, CKB deposit addresses, and balance viewing.
  • Deposits, swaps, and CKB redemption.
  • Quotes, minimum received amounts, fees, and quote expiry.
  • Deposit confirmation, settlement, and withdrawal tracking.
  • Transaction history and block explorer links.
  • Clear handling of unavailable quotes, expired quotes, and service errors.

5. Value to the CKB Ecosystem

Broader access to CKB. The project will establish a technical route for users from other ecosystems to acquire CKB with fewer manual steps.

More opportunities to use CKB. CKB holders will gain a foundation for accessing other assets and applications through a unified flow, supporting future payment and cross-chain use cases.

New liquidity connections. Intents-based quoting and execution can create opportunities to connect CKB with external market makers and asset networks. Actual depth and pricing will depend on liquidity participation.

Greater ecosystem visibility. Open-source integrations, demonstrations, and developer documentation will introduce CKB to more NEAR and multichain developers and reduce future integration work.

Reusable public infrastructure. The funded work will include bridge contracts, signing adapters, relayers, Intents integration, and a reference interface that other teams can inspect and reuse.

Success will be measured through verifiable software deliverables rather than speculative promises about users, trading volume, or total value locked.

6. Development Plan and Acceptance Criteria

Milestone Timeline Deliverables Acceptance Criteria Amount
M1: Architecture and integration design Weeks 1–2 Bridge architecture, asset flows, permission model, Intents interfaces, and liquidity plan Publish the design, including quoting, settlement, fees, and failure handling 1,000 USDT
M2: Bidirectional bridge Weeks 3–4 nCKB contract, MPC signing adapter, deposit and withdrawal relayers Demonstrate CKB deposits, nCKB issuance, and native CKB redemption on testnet 2,500 USDT
M3: Intents swaps and interface Weeks 5–6 Settlement integration, reference quoting service, and user interface Demonstrate bidirectional swaps between nCKB and at least one test asset, with settlement records 2,000 USDT
M4: Verification and public delivery Weeks 7–8 Failure testing, fixes, documentation, demonstration, and final report At least two accounts complete a combined 10 bridge-and-swap test cycles; publish code, records, and reproduction instructions 1,500 USDT
Total 8 weeks 7,000 USDT

Testing will cover duplicate deposits, unauthorized calls, invalid withdrawal outputs, quote expiry, slippage limits, replay protection, signing failures, and relayer restarts.

A public mainnet swap service requires additional security review, asset onboarding, and production liquidity. Third-party listing or launch commitments are outside this phase’s acceptance criteria.

7. Budget and Disbursement

Budget Item Amount
Bidirectional bridge contracts and deposit/withdrawal relayers 2,500 USDT
NEAR MPC and CKB signing adapter 1,500 USDT
Intents integration and reference quoting service 1,500 USDT
User interface 800 USDT
Testing, documentation, and demonstration 500 USDT
Deployment and operating costs during delivery 200 USDT
Total 7,000 USDT

Disbursement is proposed upon acceptance of each milestone. The budget and milestone tables describe the same funding allocation and are not additive.

The request is denominated in USDT equivalent. The payment asset and conversion method will follow the DAO’s approved arrangement.

This budget covers development and test delivery. It does not include mainnet liquidity capital, trading incentives, a formal third-party security audit, or ongoing production operations.

8. Security and Operational Boundaries

This phase will use authorized relayers to report CKB deposits. The trust assumptions will be disclosed, with permission controls, pause functionality, and processing limits.

MPC provides distributed signing. It does not replace deposit verification, bridge contract security, or administrative controls.

Withdrawal transactions will be checked for recipient, amount, and change destination. Complete on-chain enforcement of miner fees requires trustworthy input information.

Bridging and swapping involve multiple execution steps. Atomic settlement within the Intents contract does not make the entire cross-chain journey atomic. Each stage will have separate tracking and documented recovery procedures.

Swaps will require valid quotes, minimum received amounts, expiry conditions, and replay protection. Unavailable quotes will prevent execution.

A withdrawal that has already received a valid signature cannot be refunded solely because it timed out: the signed transaction might still be broadcast. Recovery procedures must prevent duplicate payouts.

The funded release is a testnet prototype. Mainnet deployment, formal external auditing, light-client or SPV deposit verification, and a complete multi-relayer consensus system are outside this phase.

9. Open Source, Maintenance, and Community Updates

Source code, tests, deployment scripts, and documentation will be published under a clearly specified open-source license, respecting dependency licenses.

Progress updates will be published every two weeks. Final delivery will include:

  • Deployable bridge and Intents integration code.
  • A testnet interface and demonstration video.
  • Deposit, swap, and withdrawal records.
  • A test report, deployment guide, and security documentation.
  • Asset integration materials and production liquidity requirements.

Long-term operations and mainnet maintenance will require a separate ownership and funding arrangement.

10. Funding Request

We request 7,000 USDT equivalent to build a bidirectional CKB–NEAR bridge and demonstrate asset exchange through NEAR Intents.

The goal is to establish a multichain gateway for CKB: making it easier for external users to acquire CKB, enabling CKB holders to access more assets and applications, and expanding CKB’s reach through open, reusable integrations.

1 Like