Binance users’ emergency fund is now down by half — and its replenishment rules don’t require it to be topped up promptly.
The facts: The wallet Binance identifies as the Secure Asset Fund for Users (SAFU) now holds just over 7,500 BTC, worth around $580 million at a price of approximately $77,000 (CoinDesk, Nov. 3, based on on-chain data from mempool.space). That’s half of the 15,000 BTC it held last February, when the roughly $1 billion fund finished converting from stablecoins to BTC. The reduction came from four transactions on Oct. 31 — a transfer of 7,499 BTC that Binance confirmed was a partial SAFU payout to cover the $6.34 billion hack, alongside company funds and some futures insurance funds. Binance has pledged to restore SAFU to around $1 billion, but has set no deadline.
My take: What caught my attention here wasn’t the transfer — that had already been announced — but the gap in the rules. Binance’s SAFU FAQ requires the fund to be topped back up to $1 billion if its value falls below $800 million “due to BTC price fluctuations.” A payout following a hack isn’t covered by that wording. So the fund that’s actually used in a crisis is the one with no replenishment deadline. Binance says users won’t bear the cost of the hack, and that matters — but the gap between a promise with no date and the written rules is exactly what the public should be pressing them on.
What I’m watching: a concrete date for replenishing SAFU, whether there are any further payouts from the fund, and whether Binance updates its FAQ to close this gap.
What do you think: should an emergency fund of this size have a binding replenishment deadline, or is a promise with no date enough?
This is my analysis, not financial advice — always DYOR.
#Binance #SAFU $BTC
The facts: The wallet Binance identifies as the Secure Asset Fund for Users (SAFU) now holds just over 7,500 BTC, worth around $580 million at a price of approximately $77,000 (CoinDesk, Nov. 3, based on on-chain data from mempool.space). That’s half of the 15,000 BTC it held last February, when the roughly $1 billion fund finished converting from stablecoins to BTC. The reduction came from four transactions on Oct. 31 — a transfer of 7,499 BTC that Binance confirmed was a partial SAFU payout to cover the $6.34 billion hack, alongside company funds and some futures insurance funds. Binance has pledged to restore SAFU to around $1 billion, but has set no deadline.
My take: What caught my attention here wasn’t the transfer — that had already been announced — but the gap in the rules. Binance’s SAFU FAQ requires the fund to be topped back up to $1 billion if its value falls below $800 million “due to BTC price fluctuations.” A payout following a hack isn’t covered by that wording. So the fund that’s actually used in a crisis is the one with no replenishment deadline. Binance says users won’t bear the cost of the hack, and that matters — but the gap between a promise with no date and the written rules is exactly what the public should be pressing them on.
What I’m watching: a concrete date for replenishing SAFU, whether there are any further payouts from the fund, and whether Binance updates its FAQ to close this gap.
What do you think: should an emergency fund of this size have a binding replenishment deadline, or is a promise with no date enough?
This is my analysis, not financial advice — always DYOR.
#Binance #SAFU $BTC