Welcome to Cell Sandbox

Start with one simple idea.

You do not need to understand CKB yet. We will open one Cell together, see what it holds, and follow what happens when it moves through a transaction.

  • No wallet needed
  • Nothing will be sent
  • Raw details can wait
Cell lifecycleLive Cell
State exists as one complete Cell

Guided journey

The four layers of a CKB CellAn exploded view showing capacity, lock script, optional type script, and data.CAPACITYvalue + storage boundaryLOCK SCRIPTrequired ownership ruleTYPE SCRIPToptional application ruleDATA
Value and byte budget

The Cell model

State lives in Cells

A live Cell is an immutable piece of state. It holds capacity and defines how that state may be used. Open its layers before touching the raw structure.

Capacity is both value and the byte budget for everything inside the Cell.

Guided journey

The four layers of a CKB CellAn exploded view showing capacity, lock script, optional type script, and data.CAPACITYvalue + storage boundaryLOCK SCRIPTrequired ownership ruleTYPE SCRIPToptional application ruleDATA
Who may consume it

Ownership and rules

Scripts guard the state

The lock script controls who may consume a Cell. An optional type script enforces application rules across matching inputs and outputs.

Lock answers “who can spend?” Type answers “what transition is valid?”

Guided journey

Consumed input100 CKBLive before the transaction
Created output61 CKBRecipient
Created change38.999 CKBReturned to the wallet

State transition

Cells are consumed, not edited

A transaction references existing live Cells as inputs and creates new Cells as outputs. Change and fees become visible only after funding is completed.

The 100 CKB input disappears. Two entirely new output Cells take its place.

Guided journey

1Transaction.from(outputs)propose the new Cells
2completeInputsByCapacity(signer)select live funding Cells
3completeFeeBy(signer, 1000)add fee and wallet change

Visual to code

The model maps directly to CCC

The visual workflow proposes outputs. CCC asks the signer for spendable inputs, completes the fee and change, then the wallet signs the result.

The interface should make these three operations easier to see, not hide them.