Gifty’s Chain-Fusion Bet: Make Bitcoin Gifting a Trust Exercise

A new ICP project is treating Bitcoin onboarding as a trust and education problem rather than a wallet-installation problem.

In a July forum proposal, Gifty Labs described a planned platform for sending Bitcoin or crypto to people who have never owned a wallet. The recipient would complete short lessons selected by the sender—covering topics such as what Bitcoin is, how to hold a gift and how to stay safe—before the gift becomes claimable. The team calls this “Learn and Unlock.”

The design uses ICP’s chain-fusion stack as its core settlement layer. The team says it plans to use ckBTC for a 1:1 BTC-backed asset native to ICP, while Internet Identity would provide an initial account experience without requiring a seed phrase. ICP’s documentation confirms that ckBTC is minted and burned through canisters connected to Bitcoin, and that it supports fast ICP-side transfers through standard ICRC interfaces. The platform’s proposal also relies on reverse gas so a recipient would not need to acquire tokens merely to claim a gift.

The most consequential promise is the escrow model. Gifty says gift funds would be governed by canister code rather than by an administrator, with a longer-term plan to remove controllers after testing and public verification. That could reduce dependence on the project team, but it would also turn deployment and upgrade safety into part of the product’s trust model. Community feedback in the thread specifically raised reproducible builds, testing with testnet Bitcoin and the risk that permanently disabling controllers could make serious bugs impossible to fix.

The proposal is not yet a launch announcement. Gifty states that its MVP remains in design and technical planning, and the site and video represent an intended direction rather than a product available for public use. The team later said it planned to begin with testnet Bitcoin and was still considering how to protect funds without relying on an irreversible deployment.

Email-bound claiming is another area where the security details matter. Internet Identity’s current developer guidance distinguishes a raw email attribute from verified_email: the latter is only present when the linked provider has marked the address as verified. A production claim flow would therefore need to verify the signed attribute bundle, its issuer, origin, nonce and freshness—not merely accept an email string. It would also need a clear fallback for passkey users who do not have a verified email attribute.

There is already an ICP example in this direction. A 2025 forum project, Bitcoin Gift Cards, described a deployed ckBTC gifting flow that used Google sign-in, while also disclosing that its canisters remained under developer control and had not received an external security audit. Gifty’s proposed education gate is the newer angle: the gift is intended to teach the recipient before transferring responsibility.

That makes the project’s next test unusually concrete. Can a first-time user distinguish a legitimate claim from a phishing link, understand what they are accepting, and recover safely if authentication fails? If Gifty can answer those questions with a testnet flow, reproducible code and plainly stated trust assumptions, chain fusion becomes invisible infrastructure for a human onboarding experience. Until then, its strongest contribution is a useful design question: how much security education should accompany a first Bitcoin gift?