Replay Lab

Failure replay, route comparison, and smallest-fix evidence.

Selected trace

trace_da028861-8c31-48cb-861f-9ef27e624851

Open Trace Detail

Original failed payment

trace_da028861-8c31-48cb-861f-9ef27e624851

replayed
Amount
160,000,000,000 CKB
Failure time
45ms
Sender
fiber-rpc-node
Receiver
0360779e54f1b2f380fe6889223ccf240c857bfebacd3c197a8d0124e9ab5d0484

ROUTE_CAPACITY_INSUFFICIENT

Route capacity insufficient

A route was discovered, but the available forwarding capacity was lower than the requested payment amount.

Failed at fiber_rpc_error after 45ms

Failure Timeline

Lifecycle events captured in milliseconds.

5 events
  1. 0ms
    request_receivedinfo

    Live Fiber payment dry-run requested

  2. 35ms
    node_infosuccess

    Connected to Fiber Network Node RPC

  3. 35ms
    channel_snapshotsuccess

    Captured 1 live Fiber channels

  4. 35ms
    graph_snapshotsuccess

    Captured live Fiber graph snapshot

  5. 45ms
    fiber_rpc_errorerror

    Send payment error: Failed to build route, Insufficient balance: max outbound liquidity 0 is insufficient, required amount: 160000000000

Generated Replay Scenarios

Selected from the failure fingerprint, not manually scripted in the UI.

same_conditionsauto
reduced_amount_80auto
reduced_amount_64auto
increased_outbound_capacityauto
alternate_routeauto
split_paymentauto

Recommended fix

Smallest route-capacity fix

Replay showed the original 160000000000 CKB payment fails, 80% still fails, and 102400000000 CKB succeeds. Split payment and exact outbound capacity repair also succeeded.

Split the payment into two 80000000000 CKB parts, or reduce amount to 102400000000 CKB.

If the operator controls liquidity, add at least 57600000000 CKB outbound route capacity.

Confidence: highsplit_payment

Original vs Replay

Original

Failed
Amount
160,000,000,000 CKB
Latency
45ms
Failed at
fiber_rpc_error

Replay

success
What changed
Split payment into 80000000000 CKB + 80000000000 CKB
Latency
54ms

Replay Evidence

same_conditions

Original amount, route, peer state, fee limit, timeout, and asset unchanged

failed

The original failure reproduces under the same conditions, confirming the fingerprint is stable.

52ms

reduced_amount_80

Reduced amount to 80%: 128000000000 CKB

failed

128000000000 CKB still exceeds the constrained route capacity, so the payment fails again.

44ms

reduced_amount_64

Reduced amount to 64%: 102400000000 CKB

success

102400000000 CKB matches the observed maximum forwardable capacity and settles.

38ms

increased_outbound_capacity

Added exact outbound route capacity deficit: 57600000000 CKB

success

Adding 57600000000 CKB raises route capacity to the original payment amount and removes the constrained hop.

42ms

alternate_route

Selected alternate route excluding the failing condition

success

A route with different hops avoids the original failure point with slightly higher latency.

73ms

split_payment

Split payment into 80000000000 CKB + 80000000000 CKB

success

Splitting widens eligible paths and lowers per-route capacity pressure while preserving the original total amount.

54msSmallest-fix recommendation

Report Export

Export the failure timeline, replay evidence, recommendation, and mode disclosure.

Original
Failed
Replay
Success
Confidence
high