Ambiguous submission recovery
A timeout is treated as uncertainty. CellFlow reconciles by deterministic transaction hash before any retry decision.
CKB transaction operations infrastructure
Make transaction uncertainty operationally manageable.
CellFlow is a non-custodial control plane for CKB applications. Persist transaction identity before broadcast, recover through RPC ambiguity, observe canonical state, and verify the live Cell your application actually depends on.
Non-custodialApplication-neutralPostgreSQL-backedSigned webhooksCKB-native verification
Durable lifecycle
01
Persist intentbusiness operation exists before network side effects
02
Persist tx identitydeterministic hash is known before broadcast
03
Reconcile CKBtimeouts and restarts resume from durable state
04
Verify live Cellsettlement requires the expected chain state
What it solvesBuilt for the part after
Built for the part after send_transaction.
CellFlow does not replace wallets, RPC providers or your domain database. It owns the operational lifecycle between a signed CKB transaction and the final state your application is willing to trust.
Canonical chain observation
Track pending, committed, confirmed, rejected and reorged states without collapsing chain state into one application flag.
Expected Cell verification
Verify the output you expected is live and matches the lock, type and data assertions your application depends on.
Auditable operations
Persist lifecycle events, operator notes, delivery history and portable evidence for incident review or external verification.
Clear product boundary
Operational truth, not another application database.
Intent lifecycle, transaction identity, observations, confirmation state, expected-Cell assertions, audit events and webhook delivery.
Users, orders, entitlements, balances, business permissions and signing keys. CellFlow references those operations without taking custody of them.
Production candidate
Separate operator console and safe demo surface.
The real console accepts project credentials and exposes operational controls. The demo is isolated, local-only and cannot be mistaken for live CKB activity.