The trader who delegated BABY cannot consider the unstake click as they are actually accessing that inventory as a trader in the market. However, the other assumption is false as well. This isn't a 21-day "cool down" period that many PoS networks have.

Babylon first places the undelegation in the queue until the current epoch's end. This epoch is tied to the Bitcoin and the token release waits for 300 Bitcoin confirmations, which is approximately 50 hours under normal timing. Depending on network conditions, it may take longer.

So, I'd not be adding another category to either “liquid balance” or long-lock “capital”. It acts more like stock that is based on Bitcoin timing.

That is the difference in the way that a trader will make plans for him or her. The clock is useful, and begins with the epoch boundary and will end only when the BABY is again transferable. Failure to follow this sequence may result in a trader being positioned to make a trade at a time when the funds are not ready.

The stake is held by the Babylon Genesis, but Bitcoin decides when the exit can be used. That means that the confirmation clock is not positioned in the fine print, but right next to the entry price.

@BabylonLabs_io $BABY #baby