Tranfr — Programmable Recovery for CKB

DAOs & Funding Spark Program
16

Tranfr — Progress Update

I’ve made solid progress on the core Tranfr implementation and have now completed several of the key technical foundations.

Completed so far

  • Finalized the Tranfr data layout and state representation.

  • Implemented and tested the deadline-check logic in both Rust and TypeScript.

  • Measured real CKB network timing to validate the deadline assumptions against actual chain behavior.

  • Set up the CKB contract project and established the initial contract structure.

  • Added input validation and checks around the expected transaction/state structure.

  • Implemented and tested the owner unlock flow, including signature verification.

This gives me the core pieces needed to move from the initial protocol work into the recovery path and more comprehensive security testing.

Next steps

Next week I’ll focus on the remaining core contract functionality and security validation:

  • Implement recipient claims after the deadline.

  • Add additional safety and invariant checks.

  • Run comprehensive attack-scenario and expiry-boundary tests.

  • Deploy the contract to CKB testnet.

  • Work toward a reproducible/verifiable deployment so the deployed contract can be independently verified.

Once the contract side is stable, I’ll start the TypeScript SDK, including:

  • Encoders and decoders

  • Deadline and recovery-status checks

  • Status lookup

  • createTransfer transaction construction

After that, I’ll move on to the remaining functionality:

  • Renew / heartbeat flow

  • Reclaim / recovery flow

  • Minimal demo UI

  • Technical documentation and integration examples

The goal for this phase is to have the core Tranfr primitive working end-to-end on testnet, with the contract behavior independently testable and the SDK providing the interface needed for applications to integrate it.

1 Like
CKB Ecosystem Biweekly Update