Account, node, and channel
These are separate pieces of state:
Logging in recovers the CKB identity and connects the persistent managed node by default. Optional browser mode requires its own node identity and channel database, which stays in local IndexedDB during use and can move to the next device through KeyWay’s encrypted explicit-logout handoff. The two modes do not share channel state.
Relays are not channels
When KeyWay starts, it connects to public testnet relays. Relay connections provide network reachability and gossip; they do not lock funds and do not give the user payment capacity.activateCkbChannel() separately negotiates and funds a channel with an available channel peer. That channel places capacity into the Fiber graph.
On-chain and Fiber balances
- On-chain balance is the sum of live CKB cells controlled by the account’s lock script.
- Fiber balance is the sum of
local_balanceacross ready channels. - Opening a channel moves capacity from ordinary CKB cells into a channel funding cell.
- Fiber payments update channel states off-chain rather than broadcasting one CKB transaction per payment.
Routed payments
A payment can cross several public channels:1 CKB and fail for 999 CKB because route existence and route capacity are different questions.