[DIS] CKB Anywhere Card — Tap to Pay via Apple & Google Wallet, Self-Custodial

TL;DR

What’s New in V2

Thank you to everyone who supported and provided feedback on the original proposal. The feedback was clear: while the core concept was well received, the solution needed native mobile wallet support and a simpler, mobile-first user experience.

Over the past few months, we evaluated several regulated card issuing platforms capable of supporting native Apple Wallet and Google Wallet provisioning. Following discussions with Rain, we identified its regulated Visa issuing platform as the right foundation for Version 2. Rain has since provided sandbox access and developer APIs, enabling us to validate the architecture and begin integration planning.

Based on community feedback, Version 2 introduces four key improvements:

Tap-to-pay with Apple Wallet and Google Wallet. Users can add a virtual Visa card for seamless contactless payments.

Mobile-first experience. The browser extension has been replaced with a streamlined payment flow.

Regulated infrastructure. Card issuance, compliance, and Visa connectivity are provided through Rain’s regulated platform.

Reduced funding request. The grant request has been reduced from $70,000 to $45,000 while preserving the project’s core deliverables.

The proposal maintains its original objective**: enabling CKB holders to spend directly from self-custody through existing global payment infrastructure.**


Executive Summary

CKB Anywhere Card V2 transforms CKB into a practical payment asset by allowing users to spend directly from self-custody anywhere Visa is accepted.

Users add a virtual Visa card to Apple Wallet or Google Wallet, enabling contactless payments at more than 175 million Visa-accepting merchants worldwide. Unlike traditional crypto card products, users retain full custody of their CKB until they explicitly authorize an individual purchase.

The payment architecture separates user authorization from card settlement. Before a purchase is completed, the user approves a one-time spending authorization by signing a smart contract transaction from their self-custody wallet. Anywhere Payment then settles the corresponding Visa transaction using a revolving liquidity facility, after which the authorization contract transfers the approved amount of CKB to replenish that settlement. By removing blockchain confirmation times from the checkout experience, the system delivers fast, familiar card payments while preserving user custody until each transaction is explicitly authorized.

Phase 1 integrates JoyID as the reference wallet implementation due to its mobile-first design, biometric passkey authentication, and seamless user experience. The underlying authorization framework is wallet-agnostic by design, allowing additional Nervos wallets to integrate without changes to the payment architecture.

Card issuance, Visa network connectivity, compliance, and native Apple Wallet and Google Wallet provisioning are provided through Rain’s regulated card infrastructure, enabling regulated card issuance across more than 150 jurisdictions and acceptance at over 175 million Visa merchant locations worldwide.

This proposal requests $45,000 USD (payable in CKB) to develop the authorization smart contract, complete platform integration, perform an independent security audit, and deliver a production-ready payment layer on Nervos mainnet within four months.

Rather than funding a standalone consumer application, this proposal delivers reusable payment infrastructure that any compatible Nervos wallet can integrate. By enabling direct spending of self-custodied CKB through existing global payment rails, it expands the real-world utility of the Nervos ecosystem while preserving decentralization, transparency, and user ownership.

The result is shared infrastructure that serves the broader ecosystem rather than a single application, allowing future wallets, developers, and payment experiences to build on the same open authorization framework without duplicating development effort.

1. The Problem

CKB is one of the most capable UTXO blockchains, yet spending it in everyday commerce remains difficult.

Today, CKB holders can acquire, store, and participate throughout the Nervos ecosystem, but spending those assets typically requires transferring funds to a custodial platform before making a purchase. This introduces unnecessary friction, reduces user control, and undermines one of cryptocurrency’s core principles: self-custody.

Most existing crypto card products rely on pre-funded custodial accounts or require users to convert assets before spending. While these approaches enable card payments, they require users to relinquish custody before a transaction occurs.

Other solutions attempt to settle blockchain transactions during payment authorization. Although technically feasible, introducing blockchain settlement into the payment path increases complexity and creates additional points of failure in a process users expect to complete within seconds.

At the same time, Apple Wallet and Google Wallet have become the standard interface for contactless payments across most major markets. Payment solutions that cannot integrate with these platforms introduce unnecessary friction and fall short of modern user expectations.

CKB Anywhere Card V2 addresses these challenges by combining:

  • Self-custody. Users retain control of their CKB until they explicitly authorize each purchase.

  • Familiar payments. Contactless payments anywhere Visa is accepted using Apple Wallet or Google Wallet.

  • Regulated infrastructure. Card issuance, compliance, and Visa connectivity are provided through Rain’s regulated platform.

  • Fast settlement. User authorization is separated from Visa settlement, eliminating blockchain confirmation times from the checkout experience.

Rather than introducing another custodial crypto card, CKB Anywhere Card V2 delivers reusable payment infrastructure that enables CKB to participate in everyday commerce while preserving the ownership principles of the Nervos ecosystem.


2. The Solution — Smart Contract Authorization & Revolving Settlement

CKB Anywhere Card V2 separates two functions that conventional crypto card products typically combine:

  • User authorization

  • Visa settlement

Rather than requiring users to preload funds into a custodial account or depending on real-time blockchain settlement during payment authorization, V2 introduces a Nervos-native authorization model supported by a revolving liquidity facility.

Before making a purchase, the user signs a one-time authorization through a compatible Nervos wallet. This authorizes a single transfer of the approved CKB amount within a short validity window while the assets remain under their control.

The user then completes payment by tapping their phone using Apple Wallet or Google Wallet. Rain processes the Visa authorization while Anywhere Payment settles the transaction using the revolving liquidity facility, allowing merchants to receive a standard Visa authorization without interacting with blockchain infrastructure.

Following payment authorization, the smart contract validates the signed approval and transfers the authorized amount of CKB from the user’s wallet to the replenishment account. Each authorization is single-use, time-limited, and limited to the exact amount approved by the user.

The temporary gap between Visa authorization and on-chain settlement is covered by the revolving liquidity facility. Settlement is continuously monitored, failed transfers are automatically retried, and new payment authorizations are paused if settlement cannot be completed within predefined operating thresholds.

To mitigate short-term market volatility, an exchange-rate snapshot is taken before the user authorizes the transaction. The smart contract calculates a maximum transferable CKB amount using this reference rate together with a predefined volatility buffer. If market movement exceeds the permitted tolerance before settlement is completed, the authorization automatically expires and the payment must be approved again.

By separating blockchain authorization from Visa settlement, CKB Anywhere Card V2 preserves self-custody while delivering the fast, familiar payment experience users expect from modern payment cards.


3. Architecture

Rain — Card Issuance & Visa Network Access

Anywhere Payment operates as the program manager on Rain’s regulated card infrastructure.

Rain provides:

  • Visa network connectivity

  • Virtual Visa card issuance

  • Regulatory compliance

  • End-user KYC

  • Native Apple Wallet provisioning

  • Native Google Wallet provisioning

This integration enables regulated Visa card issuance across more than 150 jurisdictions without requiring the Nervos ecosystem to build or operate traditional card issuing infrastructure.


Wallet Authorization Layer — JoyID (Phase 1)

Phase 1 integrates JoyID as the reference wallet implementation due to its mobile-first design, biometric passkey authentication, and seamless payment experience.

Before payment, the user signs a one-time smart contract authorization through JoyID. The signed authorization is valid only within a short authorization window and authorizes a single transfer of the approved CKB amount for the user’s next purchase.

The authorization framework is wallet-agnostic by design. Any Nervos wallet that implements the required authorization interface can integrate without changes to the underlying payment architecture.

Neither Anywhere Payment, Rain, nor any third party can initiate a transfer without the user’s explicit authorization.


Nervos Smart Contract

The authorization smart contract serves as the trust layer between the user’s wallet and Anywhere Payment’s settlement infrastructure.

For every payment, the smart contract:

  • Validates the user’s signed authorization

  • Verifies that the authorization has not expired

  • Enforces single-use execution

  • Calculates the approved CKB transfer amount

  • Transfers only the amount authorized by the user to the replenishment account

Replay protection, expiry validation, and single-use execution ensure that every authorization can only be executed once.

Before mainnet deployment, the smart contract will undergo an independent third-party security audit, and the completed audit report will be published publicly.


4. Comparison

Feature Legacy Crypto Cards CKB Anywhere Card V2
Custody Custodial / Pre-funded Self-custodial — CKB remains in the user’s wallet until settlement is authorized
Funding Model Manual deposits or top-ups One-time wallet authorization
Payment Authorization Assets transferred before spending User authorizes each purchase through their wallet
Visa Settlement Pre-funded by the user Immediately settled through the revolving liquidity facility
Form Factor Physical and virtual cards Virtual Visa card in Apple Wallet and Google Wallet
Asset Location Held by the card provider Remains in the user’s wallet until settlement is authorized
User Experience Deposit → Wait → Spend Authorize → Tap → Done

5. Transaction Flow

Step 1 — Authorize

The user opens a compatible Nervos wallet and authenticates using the wallet’s supported authorization method. In Phase 1, this is provided through JoyID using biometric passkey authentication.

The wallet generates a one-time authorization permitting a single smart contract execution within a short authorization window. No assets move during this step.

Step 2 — Tap to Pay

The user taps their phone using Apple Wallet or Google Wallet.

Rain processes the Visa authorization request while Anywhere Payment immediately settles the transaction using the revolving liquidity facility, allowing the merchant to receive a standard Visa authorization without interacting with blockchain infrastructure.

Step 3 — On-Chain Settlement

Immediately after payment authorization, the Nervos smart contract validates the signed authorization and transfers the approved CKB amount from the user’s wallet to the replenishment account.

Replay protection, expiry validation, and single-use execution ensure each authorization can only be executed once.

To protect against short-term market volatility, the authorization uses an exchange-rate snapshot taken before wallet approval together with a predefined volatility buffer. If market movement exceeds the permitted tolerance before settlement completes, the authorization automatically expires and the payment must be approved again.

Step 4 — Liquidity Replenishment

Accumulated CKB is periodically converted into USDC once predefined operating thresholds have been reached. The resulting USDC replenishes the revolving liquidity facility for future payments. Because this conversion occurs outside the payment authorization path, exchange execution has no impact on the user’s payment experience.


6. DAO-Owned Revolving Liquidity Facility

The proposal includes a $10,000 DAO-owned revolving liquidity facility that bridges the brief interval between Visa authorization and on-chain settlement.

Rather than being consumed as an operational expense, the facility continuously recycles as payments settle and liquidity is replenished, allowing the same capital to support future transaction volume.

Custody

The DAO-owned liquidity facility is held within Rain’s regulated payment infrastructure.

User CKB is never held by Anywhere Payment or Rain before settlement. Users retain full self-custody until they explicitly authorize each payment.

Replenishment

Following on-chain settlement, accumulated CKB is periodically converted into USDC through automated exchange execution once predefined operating thresholds have been reached. USDC serves solely as the operational settlement asset used to replenish the revolving liquidity facility, as Visa settlement requires a stable-value asset.

Transparency

All smart contract settlement transactions remain publicly verifiable on Nervos Layer 1.

Monthly operational reports will include:

  • Liquidity balances

  • Facility utilization

  • Replenishment activity

  • Transaction volume

These reports will be published to DAO stewards and the wider community.

Operational Controls

Settlement transactions are continuously monitored.

Temporary infrastructure failures are automatically retried. If settlement cannot be completed within defined operating parameters, new payment authorizations are paused until normal operation is restored.

DAO-appointed multi-signature stewards retain an emergency kill switch capable of disabling middleware access to the liquidity facility if activity falls outside approved operating parameters.

Settlement Failure & Liquidity Protection

Visa authorization and CKB settlement are separated by design. If a Visa payment is authorized but on-chain settlement cannot complete, the middleware automatically retries settlement and temporarily pauses new authorizations if failures exceed predefined operating thresholds.

The revolving settlement facility is protected through:

  • Per-transaction spending limits

  • Velocity controls

  • Merchant risk controls

  • One-time wallet authorizations

  • Settlement monitoring

  • DAO-controlled emergency pause mechanism

These controls limit exposure during settlement failures, prevent continued processing when settlement issues occur, and allow operations to be paused while issues are investigated and resolved.

Chargebacks & Risk Management

Chargebacks are handled through Visa’s standard dispute process.

Risk is managed through:

  • Per-transaction spending limits

  • User velocity controls

  • Merchant risk controls

  • One-time wallet authorizations

  • Immediate on-chain settlement

This governance model ensures community capital remains transparent, recoverable, and protected by clearly defined operational controls while enabling practical real-world payments on Nervos.


7. Funding Request

Component Amount Purpose
Revolving Liquidity Facility $10,000 DAO-owned revolving liquidity facility released following successful completion and community approval of Milestone 2.
Smart Contract Development & Independent Security Audit $15,000 Development of the authorization smart contract, wallet authorization logic, independent security audit, and security remediation.
Middleware & Platform Integration $20,000 Rain integration, wallet integration, Apple Wallet and Google Wallet provisioning, replenishment automation, compliance onboarding, testing, and production deployment.
Total Requested $45,000 Payable in CKB.

The funding request has been reduced from the original proposal while preserving the project’s core deliverables.

Of the total request, $10,000 is allocated to a DAO-owned revolving liquidity facility that remains a community asset rather than a development expense. Excluding this facility, the development budget is $35,000.

The development funding will deliver a production-ready, audited payment layer, including the authorization smart contract, integration with regulated Visa infrastructure, and deployment on Nervos mainnet.


8. Delivery Milestones

Milestone 1 (Months 1–2) — Smart Contract & Platform Integration

Deliverables

  • Authorization smart contract deployed to the Nervos testnet

  • End-to-end payment authorization successfully demonstrated

  • JoyID integrated as the Phase 1 reference wallet

  • Rain API integration completed

  • Apple Wallet and Google Wallet provisioning operational within the test environment

  • Independent smart contract security audit commissioned

  • Replenishment automation implemented and tested

Milestone 2 (Month 3) — Mainnet Launch

Deliverables

  • Authorization smart contract deployed to Nervos mainnet

  • Apple Wallet and Google Wallet provisioning available through Rain

  • Independent security audit completed and published

  • End-to-end payment flow publicly demonstrated

  • Settlement transactions publicly verifiable on Nervos Layer 1

  • Community verification of milestone completion

  • Release of the DAO-owned revolving liquidity facility following milestone approval

  • Monthly operational reporting begins

Milestone 3 (Month 4) — Operational Validation

Deliverables

  • Early community onboarding

  • Production monitoring and performance optimization

  • Monthly operational reporting

  • Technical documentation published

  • Wallet-agnostic authorization framework prepared for future Nervos wallet integrations

  • Architecture roadmap published outlining future evolution toward channel-based settlement through technologies such as the Fiber Network while preserving the existing wallet authorization framework


9. Why This Matters for Nervos

CKB Anywhere Card V2 extends the practical utility of CKB beyond storing and transferring value by enabling everyday payments without requiring users to surrender custody of their assets.

Rather than introducing another custodial crypto card, the project establishes reusable payment infrastructure built around Nervos’ native smart contract capabilities. It demonstrates how regulated payment infrastructure and decentralized asset ownership can work together while preserving the principles that define the Nervos ecosystem.

The architecture is designed for the ecosystem rather than a single wallet implementation. The platform is designed to evolve alongside the Nervos ecosystem. While payments initially settle directly on Nervos Layer 1, the architecture can incorporate future settlement technologies such as the Fiber Network without changing the wallet authorization model or user experience.

Benefits to the Nervos Ecosystem

  • Real-world utility. CKB becomes spendable at more than 175 million Visa merchants through Apple Wallet and Google Wallet.

  • Self-custody preserved. Users retain control of their assets until they explicitly authorize each payment.

  • Fast payments. Payment authorization is separated from blockchain settlement, eliminating confirmation times from the checkout experience.

  • Reusable infrastructure. The authorization framework can be adopted by future Nervos wallets and payment applications.

  • Transparent governance. Settlement transactions remain publicly verifiable on Nervos Layer 1 and are supported by monthly operational reporting.

  • Security-first architecture. The authorization smart contract will undergo an independent third-party security audit before mainnet deployment.

  • Permanent community asset. The DAO-owned revolving liquidity facility continues supporting payment volume long after the grant has been completed.

  • Future-ready design. The architecture can evolve alongside the Nervos ecosystem as additional settlement technologies mature.

Funding this proposal delivers foundational payment infrastructure that expands the practical utility of CKB, strengthens the Nervos ecosystem, and provides reusable infrastructure for future wallets and payment applications.


10. About Build Union & Anywhere Payment

Build Union is a multichain product development collective focused on building practical infrastructure that connects blockchain networks with real-world financial systems.

Anywhere Payment is Build Union’s payments platform, designed to enable self-custodial digital asset spending through regulated card infrastructure.

Website: https://anywherepayment.xyz/

Build Union has executed a mutual NDA with Rain and has been granted access to Rain’s developer sandbox and APIs for integration, testing, and technical validation throughout development.

Build Union Ltd is a registered company in the United Kingdom (Company No. 16676071).

Team:

The engineering team has experience developing payment card infrastructure, directly relevant to the card issuing, settlement, and authorization components required for this system. Build Union has also previously built within the Nervos ecosystem.

Emmanuel (Nervos Talk: BuildUnion) https://www.linkedin.com/in/emmanuelstreetcredit/

Has led business development and product initiatives across multiple blockchain ecosystems, including Nervos, with a focus on connecting decentralized infrastructure to practical financial applications.

A seasoned blockchain architect specializing in smart contracts, DeFi, and NFT solutions. Successfully led the development of UTXO and ERC-20 token ecosystems and consulted on blockchain infrastructure projects requiring advanced cryptocurrency and distributed systems expertise. His experience includes designing custom smart contracts, deploying DeFi architectures, and delivering fintech products at scale.

Sergey Chekriy https://github.com/sergey-chekriy

A full-stack and blockchain developer with more than 15 years of experience building end-to-end products. He has architected and launched complex Web3 applications, including Thrust.com, and contributed to the architecture of major DeFi platforms such as Seedify.fund. His expertise spans secure smart contract development, scalable Web3 infrastructure, and AI-powered applications.

Laxman https://www.linkedin.com/in/trylaxman/

A full-stack and blockchain developer with over 15 years of experience in end-to-end product development. Has architected and launched complex Web3 applications like Thrust.com and contributed to the architecture of prominent DeFi platforms like Seedify.fund. Specializes in secure Web3 systems, smart contract development, and AI integrations, focusing on scalability and maintainability.

Closing

CKB Anywhere Card V2 transforms CKB from an asset that can be stored and transferred into one that can be spent through the world’s existing payment infrastructure while preserving self-custody. Rather than funding a wallet-specific application, the Nervos DAO is investing in reusable payment infrastructure that any compatible wallet can integrate. This creates lasting ecosystem value by expanding the utility of CKB, lowering the barrier for future wallet integrations, and establishing an open foundation for real-world payments on Nervos.

28 Likes

Will the total cost be lower than paying directly with a Visa card? If so, how can that advantage be maintained over time? If not, what value proposition would encourage users to choose this solution over a lower-cost alternative?

3 Likes

That’s a good question and thank you for asking. The goal is not necessarily to be cheaper than paying directly with a traditional Visa debit card. If a user already has fiat in a bank account, paying with that card will often be the lowest-cost option.

The value proposition is different: enabling users to spend self-custodied CKB directly, without first transferring funds to a centralized exchange, selling their assets, withdrawing to a bank account, and spending time waiting for settlement.

Most CKB holders who want to use their assets in everyday life will eventually need to off-ramp to fiat before they can spend them. CKB Anywhere Card removes those additional steps by allowing users to spend directly from self-custody through the existing Visa network. This saves time, reduces friction, reduces custodial risk, and can often avoid the cumulative costs of exchange trading fees, withdrawal fees, and banking transfers.

Beyond convenience, the solution lets users remain in the CKB ecosystem until the point of sale, reducing the need to off-ramp into fiat prematurely while still providing access to the global Visa payment network.

Regarding costs, Anywhere Payment is designed to minimize fees by using a revolving settlement model rather than requiring users to preload custodial balances. As transaction volume grows, exchange execution can be batched, liquidity can be recycled efficiently, and operating costs will be reduced. Any improvements in liquidity, FX execution, or partner pricing are passed on to users over time.

In short, the primary value proposition is convenience, self-custody, keeping value longer on CKB and making CKB genuinely spendable in everyday commerce, not simply competing with traditional bank cards on transaction cost.

4 Likes

Thank you for your detailed response. There is no doubt that the goal and the value proposition of the project are clear.
However, as you know, there are already many exchanges and ways to convert cryptocurrencies. For example, a user can sell CKB on almost any exchange, transfer the funds to their bank card, and spend them that way.
I believe most users would choose that option if it results in lower overall costs, especially since the process only takes a few minutes and may become even faster and more cost-effective in the future.
I understand that increasing the use of CKB is beneficial, even if it means continuous selling of CKB to provide the liquidity needed for payments.
Based on what you’ve shared, you’ve already had discussions with the Rain team. I assume those discussions included conversion fees, exchange rates, and the long-term continuity of the service. However, we still don’t know what the actual conversion cost will be. If it turns out to be relatively high, it could discourage users from adopting the service.
I’m only asking these questions because I want to better understand the design and economics behind the solution. I’m genuinely excited about this project and would love to see more real-world use cases for CKB

2 Likes

Thank you for the thoughtful questions.

One clarification on the “continuous selling” point: the conversion isn’t selling CKB ahead of demand. The revolving settlement facility covers the payment first, and only afterwards is the equivalent amount of CKB converted to replenish that facility. CKB therefore remains in self-custody until it is actually spent.

On costs, you’re absolutely right that they matter for adoption. As Phrio previously suggested, one option today is converting CKB into a prepaid crypto card through aggregators such as Trocador. While this works, it requires users to move funds into a custodial prepaid balance before spending. Prepaid crypto cards available through Trocador charge approximately 5.9% for a €100 card, increasing to around 8.5% for a €10 card.

By comparison, the CKB Anywhere Card allows users to spend directly from a self-custodial CKB wallet. Based on our current settlement model, estimate the total transaction cost is approximately 2.5%, including swap execution, card FX and settlement.

This is substantially lower than the fee structure of many existing crypto prepaid card solutions while also removing the extra steps of moving funds to an exchange or prepaid balance before spending, making CKB genuinely usable for everyday payments.

4 Likes

Thank you. I appreciate the clarification. That is a convincing answer for me, and I wish you success with the project

3 Likes

Thanks @BuildUnion for this proposal

It would be good to see more information about the team’s background in delivering products and experience with scripting on CKB. This would help to supplement the proposal’s framing of the concept with the ability to execute. This seems like a scenario where it’s beneficial to share a small proof of concept to demonstrate a strong understanding from an engineering perspective, prior to a more significant grant.

Regarding the flow, I have some queries:

  1. How does the merchant/seller convey exactly the amount needed for payment to the wallet?
  2. What happens in a scenario where the Visa transaction goes through but the on-chain transaction fails? How does this protect against a sophisticated attacker draining the revolving liquidity pool? There are some mitigations mentioned, but it seems it isn’t prevented completely
  3. The Visa-side refund process is mentioned, but it doesn’t clarify how the CKB refund would be managed.

Not sure if this is intended to be left in the proposal text.

My personal overall feeling is I would like to see a lightweight POC delivered that demonstrates the contract/authorisation aspects on the CKB side.

2 Likes

Thanks for taking the time to review the proposal and for the thoughtful feedback.

On team background: That’s a fair point. We’ included our company information, LinkedIn profiles, GitHub repositories, and previous work in Section 10. Our backend engineer’s pinned GitHub project is a payment card program, which is directly relevant to this architecture, and Build Union has previously built within the Nervos ecosystem. If there are additional technical details the community would find helpful, we’re happy to include them.

On the POC: We understand the request. Rather than adding an additional milestone outside the proposal scope, we’ve structured the grant so that funding is released incrementally. The $10,000 liquidity facility is only unlocked after the core payment infrastructure has been delivered, independently audited, and verified by the community in Milestone 2. That structure allows the community to validate execution before any liquidity is deployed.

On the payment flow: The merchant doesn’t communicate directly with the wallet. The purchase amount comes through the standard Visa authorization flow. Anywhere Payment converts that amount into CKB using a current exchange-rate snapshot, and the wallet presents the user with a request to authorize that specific amount. The smart contract enforces the approved amount, authorization, expiry, and one-time execution.

On settlement failure risk: If a Visa authorization succeeds but on-chain settlement can’t complete, the middleware automatically retries. If settlement can’t complete within defined operating parameters, new authorizations are paused, preventing the revolving liquidity facility from funding additional transactions until the issue is resolved. Exposure is further limited by per-transaction spending limits, velocity controls, merchant risk controls, one-time authorizations, and the DAO-controlled kill switch. You’re right that these controls reduce rather than completely eliminate risk, so we’ll add the proposed circuit-breaker thresholds (for example, how many failed settlements trigger a pause and the recovery conditions) to the proposal before Milestone 1 sign-off.

On refunds: Visa refunds follow the standard Visa dispute process. Once a refund is confirmed, the equivalent amount of CKB is returned to the user’s wallet by referencing the original transaction ID, ensuring the refund is tied to the original purchase rather than handled manually. We’ll add a dedicated section documenting this flow.

Thanks again for the detailed review. These are valuable questions.

Thank you, I appreciate you taking the time to ask thoughtful questions. The discussion has been very valuable. Thanks again for the support!

I see, so the merchant needs to initiate a Visa transaction.

  1. How is that communicated by the merchant to Rain/Anywhere Payment? Presumably by tap?
  2. At what point is the visa authorisation approved?

Let’s say a sophisticated attack uses multiple different cards or devices to bypass limits or velocity controls to drain the liquidity facility. Would a pause affect the entire pool? I’m guessing some kind of KYC may be needed.

I looked at the history of the engineers mentioned. I saw evidence of Ethereum / ERC20 / Solidity development on the github and CV provided. CKB programming requires a substantially different approach, which is why I’m asking specifically about CKB scripting experience and previous work.

Providing detailed information helps the community undertake the necessary due diligence. My opinion in recent times is that a small proof of concept helps the community to see more substance behind the proposal where the requested grant is higher. I see it as an important part of the groundwork and inspiring confidence in the community.

2 Likes

Thanks again for the detailed feedback.

On the payment flow: The merchant doesn’t communicate directly with the Nervos wallet. The transaction begins through the standard Visa contactless flow. During the tap, the merchant terminal sends the transaction amount through the Visa network to Rain. Anywhere Payment receives the authorization request, converts the amount into CKB using a current exchange-rate snapshot, and prompts the user to authorize that specific amount through their wallet. Once the user signs the authorization, Rain completes the Visa authorization and the payment proceeds.

On settlement failure risk: If on-chain settlement can’t be completed, the middleware automatically retries. If settlement falls outside defined operating parameters, new payment authorizations are paused until the issue is resolved. The pause applies to the payment system as a whole, prioritizing protection of the DAO-owned liquidity facility over continued payment processing. The facility is further protected through Rain’s KYC requirements, per-transaction spending limits, velocity controls, merchant risk controls, one-time authorizations, continuous monitoring, and the DAO-controlled emergency kill switch. We’ll document the specific circuit-breaker thresholds, including how many failed settlements trigger a pause and the recovery conditions, before Milestone 1 sign-off.

On team background: You’re right that CKB scripting is fundamentally different from Solidity, and we don’t consider EVM experience alone to demonstrate CKB scripting capability. Combined, the team has 20+ years in UTXO-model development. With this project involves ramping up on CKB-native tooling. Our backend engineer’s experience is specifically in card issuance infrastructure, which is directly relevant to this project’s architecture.

On the POC: Regarding the suggestion of a lightweight POC, we understand the reasoning and appreciate the perspective. Our approach was to mitigate execution risk through milestone-based funding rather than introducing a separate pre-grant milestone. The proposal includes incremental funding, an independent smart contract security audit, community verification, and only releases the DAO-owned liquidity facility after the core payment infrastructure has been successfully delivered and verified. We believe that provides an appropriate balance between reducing risk for the DAO and funding the work required to build a production-ready implementation.However as a compromise We’ll publish a lightweight testnet POC, the authorization contract signing and validating a single transfer via JoyID, before the DAO vote closes.

1 Like

This is where my confusion arises. Your replies make clear that the flow is:

Tap → Authorise → Done

But the proposal clearly states that the flow is:

Authorise → Tap → Done

Which is correct?

Ok, this was missing from the proposal. Can you share some links that substantiate this and work done? Also, a reminder of any CKB-related scripting previously done by yourself or the team would be helpful.

That’s good to hear, although more time may be needed for the community to assess it. Ultimately, sharing work with the community in advance helps strengthen a proposal’s credentials.

1 Like

1.如果我将CKB在交易所卖掉,然后再把USDT提到U卡进行消费,并不麻烦,也几乎不会产生磨损,我不知道2.5%磨损的优势在哪里;

2.对于BTC ETH这些市值更高、使用范围更广的加密货币,也并没有产生以自托管的方式进行消费的需求。大家很习惯卖成USDX再消费。请问为什么它们不做,是忽视了1.7亿的巨大市场吗?请问在这种情况下CKB要做这件事的市场必要性在哪里?

3.只是追求自托管能支撑多大的商业价值?或者说,在换成法币消费这件事上,自托管为什么有不言自明的价值?

4 Likes

Thanks for pointing this out. The proposal reflects the intended flow, and I’ll edit the comment in my reply. will respond to the remaining points tomorrow.

Thanks for raising this, it’s a fair question to the core premise. I want to give it a proper answer rather than a quick one late tonight. I’ll respond to you tomorrow too.

I’ve read your proposal, and in the basis I’m getting very excited reading about a “cbk credit card”. I do have a few questions tho.

Question 1:

The proposal clearly improves usability, which I think is a major step forward. However, could the team explain how they expect this product to create sustained demand for CKB itself? Since spent CKB will eventually be converted to replenish liquidity, what mechanisms ensure that long-term demand outweighs the resulting sell pressure?

Question 2:

Is the long-term vision that users will primarily spend CKB, or is this intended as a payment infrastructure that will eventually support assets issued on Nervos (such as stablecoins or RGB++ assets)? Understanding this vision would help the community evaluate the long-term value proposition.

Question 3:

One of the biggest challenges for mainstream adoption is onboarding. Today, a new user would still need to create a wallet, buy CKB on an exchange, transfer it, and then start spending. Are there plans to simplify this onboarding process so that using the card becomes almost as easy as getting a traditional debit card?

Question 4:

What would success look like in three years? Are there measurable targets (active users, transaction volume, cards issued, etc.) that the community can use to evaluate whether the project has delivered the expected value?

Then, not really a question, but a creative thought.

I’ve increasingly come to think that the card might not actually be the product at all. The card is likely the distribution channel.

The real product is this:

Nervos is becoming a blockchain you can use without even realizing you’re using a blockchain.

And I believe that is exactly where the entire industry is ultimately heading.

Apple Pay is successful because no one thinks about NFC, EMV, or payment protocols; you simply tap your phone against the terminal.

If Nervos ever achieves that same thing where people simply make payments while the blockchain runs in the background that might well be far more valuable than having a technically superior Layer 1.

Like to hear from you, again, I feel excited when I read the proposal.

1 Like

On the team’s background: Our team’s core experience is in blockchain engineering, payment infrastructure, smart contracts, and backend Web3 systems. I should clarify my earlier wording around UTXO-related experience. Sergey has worked on Bitcoin bridge architecture involving deposits and withdrawals between a custom blockchain and the Bitcoin network. The implementation is client-owned and cannot be shared publicly, but an architecture demonstration and explanation video is available here: https://youtu.be/1-UT06Pm6ZY (in Russian, but the architecture is understandable visually).

His broader technical background is available through his LinkedIn profile: https://www.linkedin.com/in/sergeychekriy/

Thanks for raising this — it is a fair question about the core value proposition.

You’re right that for experienced users, the existing flow of selling CKB on an exchange and withdrawing stablecoins to a card can work. The proposal is not trying to replace that workflow for everyone.

The gap we are addressing is the lack of a direct path between holding native CKB and using it in everyday payments without requiring users to first move through a custodial exchange environment. For CKB specifically, the challenge is less about saving a percentage of fees and more about creating practical utility and reducing the steps required to use the asset outside the ecosystem.

Regarding BTC and ETH, I agree that self-custody alone is not sufficient to drive mass adoption of crypto spending cards. The value comes from combining self-custody with practical payment infrastructure and everyday usability. The broader opportunity here is not ‘self-custody is the product’ as another commenter put it well, the card may be the distribution channel more than the product itself, connecting blockchain assets to existing payment infrastructure.

CKB holders will ultimately need a way to convert value into real-world payments. The goal of this infrastructure is to allow users to remain within the ecosystem longer, with conversion occurring closer to the actual point of spending rather than requiring users to exit into another asset before they have a payment need.

A payment layer for Nervos helps close this gap and ensures that CKB holders have access to the same type of real-world utility that other major blockchain ecosystems are increasingly building toward.

The long-term vision is to make Nervos assets usable in everyday contexts without users needing to think about the underlying blockchain rails. CKB is the starting point because it is the native asset of the ecosystem, but the infrastructure can support broader Nervos-native assets over time.

Thanks. I really appreciate this, and the questions go right to the heart of the long-term goal.

On sustained demand vs. sell pressure (Q1):: Fair question. First, this keeps users in the CKB ecosystem longer, since they off-ramp only at the point of use rather than converting days or hours ahead of when they actually need to spend.

There is an operational sell flow created by payment activity.The goal is that increased utility creates additional demand for CKB by making it useful beyond holding and speculation. Users still need to acquire and hold CKB to access the payment layer, and the long-term objective is to expand the ecosystem of CKB holders and real-world users. This is ultimately something that will be measured through adoption and usage after launch.

On CKB vs. broader Nervos assets (Q2): The architecture is intentionally wallet-agnostic and designed as payment infrastructure for the wider Nervos ecosystem. Phase 1 focuses on CKB, but the authorization framework can support additional Nervos-native assets, including stablecoins and RGB++ assets, without redesigning the core payment architecture.

On onboarding (Q3): This is an important area for future improvement. V2 focuses on removing one of the largest barriers — requiring users to transfer assets into a custodial card provider before spending. A complete mainstream experience will also require simpler wallet creation, asset acquisition, and onboarding flows.

On 3-year success metrics (Q4): Key metrics would include active card users, transaction volume, retention, number of integrated wallets, and ecosystem usage. We want to establish realistic targets based on early production data rather than selecting arbitrary numbers before launch.

On your point that the card may be the distribution channel rather than the product, I agree. The long-term vision is for blockchain infrastructure to become invisible to the user experience, with Nervos powering real-world applications without users needing to think about the underlying rails.

Really appreciate the thoughtful questions and the way you framed this. This is exactly the type of discussion we hope the proposal creates, not just about building a card, but about how Nervos infrastructure can become more useful in everyday applications.

First of all, thank you for taking the time to provide such detailed and thoughtful answers. I genuinely appreciate that you addressed each question directly instead of avoiding the more difficult topics. This is exactly the kind of open discussion that strengthens both the proposal and the community.

I especially appreciate the honesty regarding Questions 1 and 3. Acknowledging that there will be operational sell pressure and that onboarding is still a challenge gives confidence that the team is approaching this realistically rather than overpromising. Those are important considerations, and I think it’s better to discuss them openly from the start.

Regarding the success metrics, I understand the reasoning behind not wanting to set arbitrary numbers before launch. At the same time, I would have liked to see at least some preliminary targets or milestones. They don’t have to be strict commitments, but having an initial vision of what success could look like (for example in terms of wallet integrations, active users, or transaction volume) would make it easier for the community to evaluate progress over time.

One final question came to mind after reading your responses:

What is the primary use case you envision for the first few years? Do you see this mainly as a spending solution for existing (CKB) crypto holders, or do you believe it can realistically attract users who currently only use traditional banking?

Thanks again for taking the time to engage with these questions. I think discussions like this are valuable because they move beyond the technical implementation and focus on the long-term economics and adoption of the ecosystem.

3 Likes