Using Cadence/Default protection

Default protection

What happens when someone misses a round, and how deposits absorb it.

The default flow#

When a round's deadline passes, the Default Detection + Deposit Draw workflow checks every member who hasn't contributed. If their security deposit still covers the missed amount, it's drawn automatically (DefaultCovered) and the round continues on schedule. If the deposit can't cover it, the round stalls (DefaultUncovered) until another member voluntarily covers it, as described in Managing a circle.

Covering and replenishing#

Any member can call coverDeposit(member) to pay a stalled contribution out of their own funds, becoming that slot's depositOwner — the rescuer, not the original defaulter, is who can later withdraw it back out. The original member can restore their own standing at any time with replenishDeposit(), reclaiming ownership of their slot.

Why withdrawals are pull, not push#

When a circle is cancelled or completed, deposits aren't pushed back out in a loop over every member — that pattern lets one member's address (a contract that reverts on receive, for example) block the refund for everyone else. Instead, withdrawDeposit(member) is pull-based: each member's slot is claimed independently, so one bad actor can't hold up the rest of the circle.