Local simulation · no API key · no chain writes

Transaction recovery walkthrough

Explore the lifecycle without connecting a project. This page uses local UI state only and never presents simulated activity as production data.

Go to real console →

Interactive example · local only

See how CellFlow protects a SkillPass transfer

This walkthrough does not submit anything to CKB. It demonstrates the recovery model using Alice → Bob service-right transfer.

Business intentSkillPass Service BundleAlice → Bob · transferable entitlement

Created

Create durable intent

CellFlow stores the business intent before any CKB submission begins.

# 1) Create a durable business intent
curl -X POST "$CELLFLOW_URL/api/v1/intents" \
  -H "Authorization: Bearer $CELLFLOW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "intentId": "skillpass-transfer-1042",
    "metadata": {"useCase":"SkillPass transfer","from":"Alice","to":"Bob"},
    "expectedCells": [{
      "outputIndex": 0,
      "mode": "live",
      "lock": {"args":"0xBOB_LOCK_ARGS"}
    }]
  }'

# 2) After signing, persist the deterministic transaction hash before broadcast
curl -X POST "$CELLFLOW_URL/api/v1/intents/skillpass-transfer-1042/prepare" \
  -H "Authorization: Bearer $CELLFLOW_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"txHash":"0xYOUR_64_HEX_TX_HASH"}'

# 3) Reconcile / inspect at any time
curl "$CELLFLOW_URL/api/v1/intents/skillpass-transfer-1042" \
  -H "Authorization: Bearer $CELLFLOW_API_KEY"

Key invariant: persist transaction identity before broadcast; after a timeout, reconcile by hash before deciding whether any retry is safe.

Why this matters

A broadcast timeout is not a failed transaction.

Blindly retrying can duplicate business effects. CellFlow records deterministic identity first, then reconciles chain truth by hash.

What the demo proves

The state machine and operator model.

It demonstrates CREATED → PREPARED → SUBMISSION_UNKNOWN → PENDING → COMMITTED → CONFIRMED and the expected-Cell verification boundary.

What it does not prove

No fake production claims.

This walkthrough does not submit to CKB, generate real confirmations or create durable evidence. Use the console with a configured project for live operations.