Crypto News and Tradfi News - COINOTAG

• OpenAI cut its fundraising target to $20 billion from $30 billion, per the Financial Times on Friday.
• OpenAI's target valuation fell to $1.25 trillion from $1.4 trillion in the revised round.
• The Nasdaq 100 has slumped about 10% in three weeks since its October 6 record high.
From $30 billion to $20 billion
OpenAI has cut the scale of the private funding round it had been preparing, trimming the amount it seeks to raise to roughly $20 billion at a $1.25 trillion valuation, according to a Financial Times report published late Friday. The revised terms step down from the $30 billion raise at a $1.4 trillion valuation the company had previously pursued. In practice, both sides of the plan have moved: the raise is about a third smaller, and the valuation target sits roughly 11% below the earlier figure.
The market backdrop explains the timing. The Nasdaq 100 has lost about 10% in the three weeks since it set a record high on October 6, and it dropped another 4.5% on Friday as selling in technology shares accelerated. The report surfaced hours after that session closed, late on Friday. Valuation pressure has concentrated on AI-linked companies, and a private firm hoping to raise tens of billions cannot price a round without reference to where comparable public valuations now trade. OpenAI had already pushed its initial public offering back to 2027, which leaves private markets as its main financing channel for now. Nothing in the revision indicates the company lacks operational momentum; what has changed is the price investors will pay for a business of this scale. The report did not name the investors behind the revised round or give a closing date, so the final size of the raise remains unconfirmed.
Racing Anthropic for capital
The revised ask lands while OpenAI's closest rival prepares a much larger public debut. Anthropic plans to go public in November and is reportedly aiming to raise as much as $100 billion at a $1.5 trillion valuation, a target several times the size of OpenAI's reduced round. The two companies draw on the same institutional investor base, and Anthropic's November window now sits directly across the capital OpenAI wants to secure. With its own listing deferred to 2027, OpenAI's near-term financing runs through private markets, where a competing mega-round shapes both pricing and allocation.
The November timing matters for another reason. A listing that succeeds at a $1.5 trillion valuation would set a public reference point above the $1.25 trillion price OpenAI is now considering for its private round, and it would hand investors a direct alternative for AI exposure. Two years of steep growth expectations carried AI valuations rapidly higher, and private rounds priced off that optimism. The recent selloff has changed how investors set those prices. Appetite for very large rounds now tracks public market valuations more closely, and terms have tightened even where financing remains available. OpenAI's downward revision shows the repricing has reached the private side of the market rather than stopping at listed stocks. Future large AI financings will now be measured against the terms OpenAI has just accepted.
OPENAI slips 4.4% in 24 hours
The pre-IPO instrument tracking the company, OpenAI, last changed hands at $1,347.46, down 4.43% over the past 24 hours and near the lower end of a $1,339.12 to $1,424.50 range, COINOTAG data shows. The daily composite reads a downtrend, with a bearish MACD signal and a 14-day RSI of 33.5. COINOTAG's scoring puts the strongest support at $1,333.57, rated 92 out of 100, while the nearest resistance overhead sits at $1,444.63 with a score of 88/100. Perpetual open interest stands at $13,003,243, with funding at 0.0025% per interval, a level that leaves positioning largely neutral rather than crowded to one side. Until the market works back through that resistance band, the $1,333.57 support, at 92/100, is the nearest and strongest line below the price.

• Developer nicolashw filed a draft on October 30 to block EIP-7702 delegation permanently.
• Draft installs a 3-byte marker, candidate value 0xef0200, via a self-send transaction.
• Marker installation carries a proposed gas fee of 33,500, called a conservative estimate.
The 0xef0200 Marker and Its Limits
Exchange hot wallets and institutional custody desks are the parties a new Ethereum (ETH) draft would bind first, and it would bind them permanently. A developer posting under the account nicolashw filed the draft in the Ethereum EIP repository on Friday, October 30. It has not been merged into the repository's main listing and carries no EIP number yet.
The draft targets EIP-7702, the standard that lets an externally owned account, the ordinary wallet type signed with a private key, delegate smart contract code to run at its existing address. Delegation keeps the account address intact while widening what the wallet can do: batching several operations into one transaction, letting another account cover the fees, or splitting out specific spending authority. The current specification allows a signed message to clear code already recorded on an account, but nothing stops that account from delegating again afterward, which is exactly the gap the new draft addresses.
The account would send a special transaction to its own address with the EIP-7702 authorization list left empty, writing a 3-byte non-executable marker into its code. The candidate marker value is 0xef0200, which the draft itself flags as neither settled nor formally assigned. Once installed, signatures that try to set a new delegation, or to clear the existing one, are not processed, and the same rule covers the signature that would erase the marker, so the block cannot be lifted. The installation transaction carries a proposed gas fee of 33,500, a figure the draft describes as conservative without presenting any measurements. Nothing else about the account changes: it keeps its address, can still send Ether, call a smart contract and sign ordinary transactions, and the marker is not treated as executable code. The proposal targets account control, not the Ethereum price: no monetary parameter moves.
The draft's text names exchange hot wallets and institutional fund management accounts as the intended apply targets. Withdrawal approvals, transaction limits, monitoring and emergency stops at those operations run outside the Ethereum network, and the proposal argues that a delegation executed underneath such controls can shake the assumptions they depend on. Its authors frame the marker as a way to make an off-chain control regime stick at the protocol layer: once a desk pins an account, no later signature, legitimate or stolen, can route that account into delegated code.
The block has hard edges the draft concedes. It does nothing about a stolen private key: whoever holds the key can still move funds through ordinary transactions and approve token spending, and the marker neither revokes approvals already granted nor cancels them. Irreversibility carries its own risk: if a delegation-based recovery feature stalls, or assets sit behind delegated code that the marker now blocks, the owner may find them unreachable.
Developer forum discussion has raised further wrinkles. The marker is recorded only on the chain where the blocking transaction runs, leaving the same address delegable on other networks. Some NFT safe-transfer flows may refuse a marked account as a recipient, and wallets or contracts that branch on account-code shape are queued for compatibility review.
The context behind the push is abuse data. An aggregate of approval transactions across 7 chains through July 15, 2025 found 63% of initial EIP-7702 approvals connected to attacker-linked contracts, a pattern our earlier analysis of Binance sweeper flows citing 50 EIP-7702 signatures also documented. That figure measures abuse before any block exists, not the effect this draft would have. Adoption requires one of the Ethereum network upgrades that validators and node operators would ship, and until an owner signs the blocking transaction, every existing account keeps working as it does today.
The Compatibility Burden Falls Downstream
The reading here: this is an opt-in, one-way switch, and its weight falls on parties that have not moved yet. Wallet vendors and contract developers whose logic branches on account-code shape must work out how a 3-byte marker reads before any of it touches a mainnet, and NFT transfer implementations face the same audit. Node operators and validators control the other gate: without a network upgrade, the marker transaction does nothing at all. The next signal is procedural: whether the repository's editors assign an EIP number and move the text into the main listing, and which wallet teams pick up the compatibility questions first.

• Bitcoin traded near $76,650 on Friday, pressing into its 200-day moving average zone
• Chart analysis plotted the 200-day moving average at $76,400–$76,600
• About $1.5 billion of leveraged positions were liquidated on Friday, roughly 84% longs
Bitcoin (BTC) Slides Into the 200-Day Average
Bitcoin (BTC) price slid into the zone that long-term chart watchers mark out on the daily trend line, quoted near $76,650 on Friday as the coin pressed against its 200-day moving average. That average, which folds roughly 200 trading days into a single trend reading, was plotted at $76,400–$76,600 in analysis published early on Saturday, so the market is trading almost exactly on top of it. The weakness was broad rather than Bitcoin-specific: altcoins sold off in step during the 30th's session, the kind of correlated drop that sends each coin toward its own lower band, with Ethereum (ETH) quoted at $2,222.59 and a support band flagged at $2,170–$2,200, XRP at $1.2352 with support noted at $1.20–$1.22, and BNB, the exchange token at the center of Friday's security news, at $696.43.
One caveat applies to the snapshot: Bitcoin, Ethereum and BNB were quoted against Tether (USDT), XRP against the US dollar, and neither the exchange nor the exact aggregation timestamp was disclosed, so the four readings describe nearby levels rather than one simultaneous market print. Chart platforms publish such snapshots on their own clocks, a known limitation when comparing coins across venues. What the level means for Bitcoin specifically is a trend test: the 200-day line marks where price has settled over most of a year, and touching it does not mean it stops a fall. For the longer cycle backdrop, Bitcoin Rainbow Chart Explained maps where Bitcoin's price bands have historically sat. Every support band here carries the same limit, approached but not secured.
$1.5 Billion Wiped as Binance Suspended Withdrawals
The slide into the average came with leverage stripped out from underneath the market. Derivatives data shows about $1.5 billion of leveraged positions were forcibly closed during Friday's session, and longs made up roughly 84% of that total, the side that pays to stay in. A liquidation is the forced closure of a margined position once collateral no longer covers the loss; on Friday the mechanism ran through the long side of the book. Long positions on perpetual futures, the dominant venue for crypto leverage, are held in place by a periodic funding rate that keeps contract prices tethered to spot, and when price turns hard that crowd is closed out by force first. The $1.5 billion figure counts both sides of the book; the long share is what distinguishes this unwind from a short squeeze. Implied volatility, the future price movement already priced into options, rose on the 30-day tenor during Asian trading hours, a wider expected range in both directions rather than a call on direction.
Friday also carried the exchange news. Binance said in an official announcement issued around 05:05 Korea time that unauthorized withdrawals had occurred through a hot wallet breach, and it suspended withdrawal services while it responded, giving no restoration timeline in the notice. The exchange put the estimated impact at $6.3 billion and said roughly $3 billion in related assets had been frozen on-chain. Those are separate accounting items: the frozen sum cannot be subtracted from the estimate to produce a net loss, and Binance has said it intends to cover user losses. Trading on the venue continued while withdrawals were paused, per the same notice. The breach follows a warning from OneKey's CEO that BlackRock's $63B Bitcoin ETF is a North Korean target, and COINOTAG separately tracked the six-week low after the Binance hack.
Where the $76,400 Band Meets Spot Demand
Our reading: the tape shows a market that repriced leverage faster than spot repriced conviction. An 84% long skew in Friday's closures marks the drop as deleveraging, and deleveraging exhausts itself when forced selling stops, not when a chart line is reached. That leaves the $76,400–$76,600 band as the level where dip-buying from holders who sit through drawdowns, the behavior the market labels HODL, would need to appear. The assumption to watch is whether spot demand absorbs supply at the 200-day average while the exchange's withdrawal pause remains in place. Nothing in the liquidation record guarantees the band holds, and our Bitcoin technical analysis tracks that test live.

• XRP gained 1.59% in 24 hours to $1.2544, reclaiming the $1.25 line on October 31.
• On-chain analysis attributes about 233 million XRP, near $292 million, to the breach.
• The crypto market saw over $1.5 billion in liquidations, about 87% from longs.
XRP Retraces the Hack Sell-Off
The XRP price recovered 1.59% over the past 24 hours and stood at $1.2544 as of 00:01 UTC on Saturday, lifting the token back over the $1.25 line after two bruising sessions. The bounce followed a 3.96% slide to $1.26 recorded on October 30, when Bitcoin's 4.63% drop pulled the wider market lower in sympathy. XRP kept its fifth-place rank by market capitalization through the swing. Korean venues told a calmer story: the token last changed hands on Upbit at 1,691 won, flat at 0.00% on the day, a marked contrast with the recent Upbit volume spike that had made the exchange a center of the earlier trade. The slide itself began on Friday, when the breach at Binance became public, in which roughly $6.3 billion in cryptocurrency was taken from the platform, and it carried into Friday's session. On-chain analysis attributes about 233 million XRP, close to $292 million at the time, to the thieves, and XRP moved first as the funds left. A freeze is not available here: the tokens sit in attacker-controlled addresses on a public blockchain, where Ripple holds no administrative key, so they hang over the order book as latent selling pressure. The market's reaction was immediate: the token slid from $1.28 to $1.20 around the incident, a decline ascribed to direct panic selling and to the risk that the stolen coins change hands. The gain retraced only part of the hack-week loss, and the token still sits below the $1.28 it held when the breach became known.
A $1.5 Billion Leverage Flush
Leveraged positioning did much of the amplifying. Derivatives data recorded more than $1.5 billion in liquidations across the crypto market in the 24 hours around the incident, with long positions accounting for roughly 87% of that total. Forced closure of leveraged longs converts paper losses into immediate spot sales, and the cascade explains the speed of the drop to $1.20: each closed long added tokens to a market already digesting the prospect of 233 million stolen coins. XRP carried about $36.7 million of the closures, and turnover on the token jumped 145%, a pattern read as fear-driven trading rather than accumulation. The technical map out of the damage runs through a handful of levels. A relative strength index of 26.64 on the 7-period setting left the token deeply oversold, so a successful defense of $1.20 carries genuine rebound potential, while a break of $1.2002 opens the next Fibonacci retracement support near $1.09. Reversing the trend requires a daily candle close above the recent resistance at $1.3444, one of the levels tracked in our XRP technical analysis. Two developments outside the chart will set the direction over the next 24 to 48 hours. Binance has tentatively marked October 31 as its target for resuming withdrawals, and what the official announcement contains becomes the variable by which confidence is restored. The other gauge is custody of the stolen supply: whether the 233 million tokens begin moving from the hacker's wallet address toward exchanges is the measure of residual selling pressure. Only when Bitcoin's dominance steadies and the total scale of liquidations shrinks, across the broader XRP market and the rest of crypto, can the selling be judged finished.
The $1.2730 Ceiling
Our live monitoring puts XRP at $1.26, up 0.2% since the 00:01 UTC snapshot and 2.1% over 24 hours, a firmer tape that still sits inside a downtrend with RSI at 38.17. Our composite scoring, which rates each level from 0 to 100 on the indicators converging there, places the nearest ceiling at $1.2730, a perfect 100/100, with the strongest support below at $1.2473, scored 69/100, where the lower Bollinger Bands, the pivot point and the weekly S1 meet. Positioning is tilted but not stretched: funding is a mild 0.0065% and the long/short account ratio stands at 3.02, 75.1% long, while the Crypto Fear and Greed Index reads 30. That reading holds while the stolen XRP stays in hacker hands and Binance's withdrawal restart lands on schedule; the tokens moving to exchanges would reset it.

• The alleged sweeper left exactly 1 ETH in the Binance hot wallet after sweeping
• CyberSatoshi claimed 50 pre-signed authorizations covered consecutive nonces to catch the wallet
• A custom function allegedly let the compromised Binance 14 wallet reach a vault holding $823 million in USDC
Hoskinson's Sweeper Warning
Cardano founder Charles Hoskinson has waded into a dispute over Ethereum's (ETH) EIP-7702 delegation feature, sharing an analysis that blames the feature for helping an attacker rapidly empty a Binance hot wallet and warning of “seriously dangerous code.” The Ethereum specification takes a different view: it states that delegation cannot be attached to an account without a valid cryptographic signature, and it does not explain how any signing credentials were obtained. In an X post on Friday, Hoskinson wrote, “Careful, there is some seriously dangerous code out there,” above a breakdown from the pseudonymous analyst CyberSatoshi. The post reconstructs bytecode for an alleged EIP-7702 sweeper and argues the contract was built specifically for Binance's wallet infrastructure. Hoskinson's message stopped short of naming a specific flaw and did not say which part of the analysis he endorsed. CyberSatoshi's reconstruction is more granular. The alleged sweeper left exactly 1 ETH in the wallet when it swept the native balance, a choice the poster said would keep Binance's automated hot-wallet queue from failing over insufficient gas and raising alarms. A token-processing loop used low-level calls to check balances and kept running when individual transfers failed, letting the contract move assets even where a blacklisted token blocked one operation. The analysis's widest claim concerns reach: a custom execution function allegedly let the compromised wallet, identified as Binance 14, call an external vault holding $823 million in USDC, effectively reaching funds in the exchange's Ethereum treasury beyond its own balance. Our related coverage records an Aave oracle gap after the Binance hack that netted one arbitrageur $3.47 million; Binance hot wallets separately drew attention when they moved $2 billion in crypto to a Tornado Cash-funded address. The poster characterized the contract as purpose-built for Binance's architecture; its account of internal alerts and treasury defenses remains its own explanation. No rebuttal from Ethereum developers or from Binance appears in the material published so far.
50 Authorizations and Nonce Rules
Under EIP-7702, an externally owned account, which normally operates through signatures from its private key, can delegate execution to code deployed at another address. The design supports batching several operations into one transaction and letting another account pay fees, patterns used by wallet providers and layer 2 networks. Each authorization identifies a chain, a delegate address and a nonce, together with a cryptographic signature; the protocol recovers the authorizing account from that signature and checks its nonce before applying the delegation. CyberSatoshi acknowledged this bar, saying the alleged attack needed either the raw private key or unrestricted signing access to Binance 14's security infrastructure. Wallets that permit blind signing, approving data without seeing its full contents, sit inside that audit exposure. The claimed batch rests on nonce arithmetic: 50 pre-signed authorizations covered consecutive nonces, letting the attacker catch Binance 14 while its transaction count was changing. The specification processes authorizations in order, moves on when one fails a check, and increments the account's nonce on each valid entry, so successive authorizations can become valid as that nonce advances; where several exist, the last valid delegation sets the code address used. CyberSatoshi argued that delegation compressed the asset transfers into a single operation, shrinking the window for intervention, and that exchange defenses would otherwise have stopped the theft after three transactions, a counterfactual the poster presents as its own assessment. The specification's security section is direct: authorized code gets unrestricted access to the account and must be closely audited by the wallet, with protections including replay prevention and signatures covering value, gas, destination and call data. Delegation persists beyond the transaction that installs it, failed executions do not undo delegation indicators that were already processed, and only a valid authorization pointing to the zero address clears it. The breakdown and the on-chain authorization trail can be checked directly; our guide to reading the Ethereum blockchain like a pro walks through it.
The record leaves two readings standing. Hoskinson's post treats the delegation feature as the dangerous element, while the specification's own text shows the feature cannot be attached to an account without a valid signature, and CyberSatoshi's account concedes that point. What would settle the matter is disclosure of how signing access to Binance 14 was obtained, a fact neither the EIP document nor the reconstructed analysis establishes. Until that is confirmed, the argument between the warning and the specification stands unresolved, and neither side's summary closes it.

• Jupiter Earn warned of a liquidity crunch hitting Jupiter Lend withdrawals at 5:01 a.m. ET Friday.
• The USDC vault held roughly 413.7 million USDC with only 8.44 USDC withdrawable at 2:21 p.m. ET.
• The JupUSD vault showed about 419,000 JupUSD free out of 44.5 million, under 1% of supply.
Nine Hours After the Liquidity Alert
Depositors in Jupiter Lend’s USDC vault could pull out only 8.44 USDC on Friday afternoon, despite the pool holding roughly 413.7 million USDC. Jupiter Lend is a lending protocol built on Solana, and its Jupiter Earn account speaks for the deposit side. That account raised the alarm more than nine hours earlier: at 5:01 a.m. ET it warned of “a liquidity crunch” affecting withdrawals. Readings from Jupiter’s public Earn API confirmed how thin the free cash had become. At 2:21 p.m. ET the endpoint showed 8.44 USDC available against a total value locked of about 413.7 million; two minutes earlier the same figure stood at 20.79 USDC, and a later pull at 3:32 p.m. ET put it at 6.37 USDC. The shortfall was not a brief dip between polls: across the afternoon the withdrawable balance swung between about 6 and about 901 USDC, never approaching a meaningful share of the pool. That left a vault of this size offering depositors less cash than a single mid-sized trade would move. Jupiter’s own stablecoin fared little better. The JupUSD vault, the protocol’s in-house dollar instrument, showed about 419,000 JupUSD free to withdraw out of 44.5 million, or under 1% of its supply. Other vaults looked the same: about 465,600 USDT free out of 16.6 million on the USDT side, and under 80 EURC out of 3.8 million on the EURC vault. None of the pools showed a zero balance; every vault still reported some supply and some withdrawable amount, however small. In the warning, Jupiter Earn blamed “broader market conditions,” wrote that the protocol was “functioning as expected” and that “all funds are safe,” and called the squeeze “normal and expected during events like today’s.” It told users that “liquidity will soon be available again,” but attached no timeline to that promise. The post named no technical fault and no loss of funds.
A Quarter of Supply Every Six Hours
A lending pool earns depositors yield by putting their money to work, so cash becomes withdrawable again only as borrowers repay loans or fresh deposits arrive. Jupiter Earn made the same point in its warning: market conditions would push users to deposit or repay their loans, and once they did, withdrawals would process again. No schedule accompanied the promise, and until repayments arrive, each depositor depends on the next six-hour window to unlock fresh capacity. Jupiter Lend also throttles outflows by design. Its documentation describes a rolling withdrawal limit that frees up to about a quarter of a vault’s supply every six hours, a control meant to keep a rush of exits from outpacing the return of borrowed funds. In calm markets the cap rarely binds; on Friday it was plainly binding. At 2:21 p.m. ET the SOL vault showed about 52,236 SOL withdrawable out of 208,941 SOL, exactly the quarter-share the limit permits at once. The stress around the protocol came from elsewhere. On Thursday, Binance said user funds were safe after about $3.5 billion drained from its hot wallets, and the exchange later estimated the total impact at about $6.3 billion. Jupiter Earn’s alert landed hours into that turbulence. In an earlier post, the account said the protocol “has not been affected” by the Binance situation and carries no exposure to the exchange. Its liquidity warning likewise tied the squeeze to market conditions alone, framing the crunch as an effect of the wider turbulence rather than of anything inside the protocol. By late afternoon the account had added no reopening timeline. Neither post disclosed how much of each vault sits out on loan.
A Ceiling, Not a Shortfall
The pattern in the numbers reads as a throughput problem rather than a solvency problem. The SOL vault sat exactly at its permitted six-hour ceiling, which means the limit, not missing assets, is what a withdrawal request runs into. A pool’s free balance is simply whatever has come back from borrowers and not yet gone out again, so when markets turn rough and repayments slow, withdrawable cash shrinks to rounding errors even while every loan stays on the books. What Jupiter Earn has not offered is a schedule: liquidity, it says, will free up as users deposit or repay, and no date attaches to that. Its Friday position stands: the protocol is “functioning as expected,” and “all funds are safe.”

• Floki issued a solidarity message on 30 October after the $6.3 billion Binance breach.
• Binance's preliminary findings traced the 29 October attack to a compromised DevOps engineer's computer.
• Roughly $3 billion in assets was frozen on-chain, with about $5 billion in related tokens held.
Floki Rallies Behind Binance Users
The failure began, in Binance's own preliminary account, with a compromised computer: a DevOps engineer's workstation breached during the 29 October cyberattack, an incident the exchange now sizes at roughly $6.3 billion in affected assets. Floki answered a day later. On 30 October, the Floki team published a solidarity message from its official X account, backing the exchange and its users while concern over the incident was still running through crypto markets. The project framed the breach as more than one company's problem, calling it a matter that touches a broad base of users across the ecosystem. It pointed to Binance's contribution to spreading cryptocurrencies around the world and noted that a large share of the Floki community counts among the exchange's customers. The core of the statement concerned protection: behind every account, the team argued, stands a real person for whom trust matters, so financial losses should not be pushed onto individuals. The message welcomed Binance's commitment to cover the damage, named the preservation of investor trust as the priority, and the community addressed Binance's team and everyone hit by the incident directly, pledging to stand together through the recovery. The post also carried a practical edge: with losses still being counted, the team urged that affected users be kept informed and made whole in full. Floki stopped short of any financial commitment of its own. No verified market data shows the FLOKI price moving on the statement, and the project described no investment partnership or funding arrangement behind the message, leaving it, as written, a position on user rights rather than a commercial development.
Binance Traces the Breach to a DevOps Machine
Binance's own security statement, published on 30 October, filled in the investigation's early shape. Initial findings point to the attack starting with the takeover of a DevOps engineer's computer, although subsequent reviews identified additional breach points that the exchange has yet to describe in detail. One reassurance stands out: the company said it found no evidence that the private keys behind its wallet addresses were exposed, a distinction that matters because leaked keys would have widened the incident far beyond a single compromised machine. Withdrawals were suspended temporarily after the attack, and Binance engaged blockchain analytics firms and security units to trace the movement of the affected assets. The tracking has produced measurable results: roughly $3 billion in assets was frozen on-chain, while around $5 billion in related tokens is being held. CEO Richard Teng said company funds exceeding $6.34 billion have been allocated to cover the affected assets, an envelope larger than the estimated impact. The exchange committed to publishing a technical inspection report and updated proof of reserves once the investigation concludes, and it named a 48-hour target for restarting withdrawals. Users were pointed toward official service announcements and cautioned against so-called asset-recovery scams, which tend to multiply in the FOMO-heavy hours after a breach of this size. The announcement did not put a final figure on user losses, which remain subject to the completed inquiry.
Frozen Funds and Pending Reports
The load-bearing facts sit on Binance's side of the story, and they are checkable. The roughly $3 billion frozen on-chain is a figure any observer can verify on the public ledger, and the promise of a technical inspection report plus an updated proof of reserves gives the market two dated deliverables to hold the exchange to. Floki's post, by contrast, commits the project to nothing financial, so it reads as a stance on user protection rather than a rescue arrangement. With Binance's reviews still surfacing additional breach points inside its own infrastructure, the exchange's remediation, not the solidarity statements around it, is what determines whether trust holds.

• Gold fiel am 30. Oktober unter 3.900 $ je Unze und erreichte damit den niedrigsten Stand des Jahres 2026.
• Die PCE-Inflation stieg im September monatlich um 0,5 % und im Jahresvergleich um 3,6 %. Sie ist der bevorzugte Inflationsindikator der Fed.
• Die Federal Reserve beließ die Zinsen Anfang dieser Woche bei 3,75 % bis 4,00 %.
Gold sinkt unter 3.900 $
Gold (XAU) fiel am Freitag, dem 30. Oktober, unter 3.900 $ je Unze und erreichte damit den niedrigsten Stand des Jahres 2026. Damit lag das Edelmetall rund 30 % unter seinem Januarhoch. Nachdem der Markt in den vergangenen Sitzungen wiederholt die Marke von 4.000 $ getestet hatte, gab er unterhalb dieser Schwelle nach und beschleunigte seinen Abwärtstrend. Damit steuert Gold auf den zweiten monatlichen Verlust in Folge zu. Der Einbruch am Freitag folgt auf Wochen mit nachlassendem Momentum: Aus der Unterstützung bei 4.000 $ wurde eine Marke, an der Verkäufer bei jedem Anlauf Druck ausüben.

• Blackstone teilte Anlegern mit, dass Anthropic nach dem geplanten Börsengang wahrscheinlich ein Junk-Rating erhalten wird
• Blackstones Fonds halten rund 9 Milliarden US-Dollar des nicht garantierten 18-Milliarden-Dollar-Kreditanteils von Anthropic, dessen Rendite über 10 % liegt
• KBRA stufte Anthropic im Juni mit BB+ ein – eine Stufe unterhalb des Investment-Grade-Bereichs
Blackstone nimmt seine Rating-Einschätzung zurück
Blackstone (BX) hat Anlegern mitgeteilt, dass Anthropic (ANTHROPIC) nach Abschluss des geplanten Börsengangs wahrscheinlich eine Bonitätsbewertung unterhalb des Investment-Grade-Bereichs erhalten wird. Damit nimmt das Unternehmen frühere Prognosen zurück, denen zufolge noch bis Jahresende ein Investment-Grade-Rating erreicht werden sollte. Die am Donnerstag in einem Beitrag eines Trading-Desks angekündigte und in einem Bericht der Financial Times näher erläuterte Kursänderung ist bedeutsam, weil das Rating darüber entscheidet, wie günstig das Unternehmen hinter den Claude-KI-Modellen Kredite für ein Rechenkapazitätsprogramm im Wert von mehr als 800 Milliarden US-Dollar aufnehmen kann. Unterhalb der Schwelle von BBB- gelten Schuldtitel als spekulativ oder als „Junk“. Viele Pensionsfonds und Versicherer unterliegen Anlagevorgaben, die solche Bestände begrenzen oder ausschließen. Dadurch wird dieses Kapital in Richtung Investment-Grade-Anleihen und Instrumenten wie Anleihen-ETFs gelenkt. Mehrere dieser Käufer dürfen Titel mit einem Rating unter BBB- grundsätzlich nicht erwerben. Damit würde die Nachfrage nach künftigen Anthropic-Anleihen genau dann schrumpfen, wenn der Finanzierungsplan darauf angewiesen ist. Das 800-Milliarden-Dollar-Programm umfasst Chips, Rechenzentren und unterstützende Infrastruktur und soll in mehreren Phasen finanziert werden. Deshalb ist das Rating jeder einzelnen Emission wichtig. Ein Junk-Rating würde den Börsengang selbst nicht verhindern, aber die Kosten jeder anschließenden Anleiheemission erhöhen, die der Plan erfordert. Die Kroll Bond Rating Agency hat Anthropic bereits im Juni mit BB+ bewertet und damit eine Stufe unterhalb des Investment-Grade-Bereichs eingestuft. Blackstones aktualisierte Einschätzung, die auf Rückmeldungen der großen Ratingagenturen beruht, geht davon aus, dass die drei führenden Agenturen Anthropic im BB-Bereich einstufen werden. Diese Haltung bedeutet eine deutliche Kehrtwende gegenüber der früheren Aussage des Unternehmens, wonach die Schwelle von BBB- noch in diesem Jahr erreicht werden sollte. Blackstones Fonds zählen zu den größten Kreditgebern des Programms, weshalb dieser Einschätzung besonderes Gewicht zukommt. Daten von COINOTAG zeigen, dass das vor dem Börsengang gehandelte Anthropic-Instrument zuletzt bei 1.703,49 US-Dollar notierte und über 24 Stunden 5,34 % verlor, während sich die geänderte Einschätzung im vorbörslichen Handel niederschlug.