Bitcoin has rebounded 26% since its mid August low, helped by record short liquidations on Aug 19 and $2.23 billion in net inflows to US spot Bitcoin ETFs with seven straight days of no outflows, according to Glassnode data cited by ChainThink. Glassnode highlights $83,000 to $86,000 as the most critical resistance zone, with options implying a $69,000 to $89,700 range.

Glassnode reported Bitcoin has rebounded 26% since its mid August low, led by the largest single day short liquidation in its data since 2019 and followed by $2.23 billion of net inflows into U.S. spot Bitcoin ETFs with seven straight days of no outflows. The firm flagged $83,000 to $86,000 as the main resistance zone, with key support near $70,000 and $62,000 to $65,000.

Genius Group said it plans to raise up to $1.2 billion to finance its AI Vault and Bitcoin Vault initiatives, according to a GlobeNewswire release. The capital plan will be funded through the issuance of perpetual preferred securities. The company targets $2 billion in total assets by fiscal year 2031. It expects the AI Vault to reach $800 million and the Bitcoin Vault to total $827 million.

Bitcoin hovered around $80,000 on Wednesday as markets turned their attention to Federal Reserve Chair Kevin Warsh's keynote address at the Jackson Hole symposium, according to CoinDesk. The annual Kansas City Fed gathering opened Wednesday, with Warsh set to speak Friday morning. Inflation remains well above the Fed's 2% target while long-term borrowing costs sit near multi-year highs. The central bank has kept its benchmark rate range at 3.5%3.75% for the past several months. Mark Connors, CIO at Risk Dimensions, said Warsh is likely to keep the door open to further rate increases, though he does not expect a hike before the midterm elections. July's PCE inflation printed at 3.7%, with higher energy prices tied to the Iran conflict cited as a contributing factor. Hashdex CIO Samir Kerbage argued that Bitcoin tends not to trade directly on the September FOMC decision. Instead, he said it tracks shifts in global liquidity and the long-end of the yield curve, echoing the drivers that often underpin gold. He pointed to last week's move after 30-year U.S. Treasury yields reached a 19-year high. The U.S. Treasury then announced increased purchases of long-term Treasuries, after which Bitcoin climbed. Kerbage characterized the rally as "primarily a liquidity event." This year's Jackson Hole agenda centers on financial innovation, payments and policy, with discussions focused on stablecoins, tokenized deposits and faster settlement systems. Kerbage said that if Warsh frames these technologies as core building blocks of the financial system rather than risks to be contained, the ripple effects could go beyond Bitcoin. In that scenario, smart-contract networks and protocols that facilitate tokenized payments and settlement could be among the most direct beneficiaries.

Core Lightning has confirmed several security vulnerabilities in its Lightning Network implementation and is advising node operators to apply an upcoming security release as soon as it becomes available. Until the patch ships, the project recommends that operators who cannot upgrade immediately run their nodes with the "offline" option. This stops peer connections and disables incoming, outgoing, and routed Lightning payments, while keeping the daemon running to continue monitoring the Bitcoin blockchain. Developers said the issues surfaced while triaging a large batch of AI-generated CVE reports, a subset of which turned out to describe real, fix-worthy flaws. The team is not publishing technical details at this stage and is instead urging operators to prioritize the forthcoming security update. Core Lightning also explained why "offline" is preferred over shutting the node down entirely. With the daemon still running, the node can track the Bitcoin chain and react if a counterparty force-closes a channel. A fully stopped node cannot watch the chain; if a channel partner publishes force-close transactions while the node is down, the operator could miss the event and lose the ability to respond. After upgrading, operators must remove the "offline" flag, or the node will remain disconnected and normal Lightning activity will not resume. Key details remain undisclosed. Core Lightning has not published CVE identifiers, severity ratings, the affected components or versions, or any evidence of active exploitation. Operators will need to rely on the guidance included with the security release to determine whether their deployments are impacted. The newly confirmed bugs are separate from earlier denial-of-service issues disclosed this year involving memory exhaustion in connectd (peer handling) and gossipd (network gossip processing). Those DoS flaws allowed remote peers to trigger unbounded memory usage and were patched prior to the current warning. The broader context is familiar across Bitcoin and Lightning software, where occasional security releases require rapid operator action. The report points to recent high-profile fixes such as Bitcoin Core's CVE-2024-52911, a block validation issue addressed in Bitcoin Core 29.0, as well as past Lightning client incidents including LND's 0.16.3 memory leak in mid-2023 and replacement-cycling attack research published later that year. Practical guidance for operators: 1) Monitor Core Lightning channels for the security release and install it immediately once available. 2) If you cannot upgrade right away, restart Core Lightning with "offline" enabled to prevent connections and payment routing while keeping on-chain monitoring active. 3) Avoid fully stopping the daemon unless you understand and accept the risk of missing force-close events. 4) After applying the update, remove "offline" before restarting so the node can reconnect and resume normal payments and routing. Based on Core Lightning's disclosure so far, there have been no reported losses or confirmed successful attacks tied to these newly acknowledged vulnerabilities. Operators are still advised to treat the notice as urgent and use "offline" only as a temporary mitigation until the patched release is deployed.

Bitcoin is trading around $79,000 after briefly pushing above $81,000 earlier this week, with market participants focusing on a potential resistance test near $83,000. BlackRock's head of digital assets, Robbie Mitchnick, said mounting concerns over government debt and widening deficits are reinforcing Bitcoin's role as a portfolio diversifier. In an interview published August 26, Mitchnick argued that Bitcoin's scarcity and its distance from government policy make it distinct from equities. He also pointed to periods in which Bitcoin and gold advanced while stocks softened and bond markets swung. Mitchnick acknowledged Bitcoin can still trade like a risk asset during speculative phases or when leverage is elevated. He framed the diversification thesis as a long-term driver rather than protection in every selloff. He added that Bitcoin already enjoys meaningful regulatory acceptance, and said proposed legislation such as the CLARITY Act is more consequential for decentralized finance and other crypto activities. More regulatory clarity could provide upside, he said, but is not essential to the core investment case. Flows into spot Bitcoin ETFs have also turned supportive. Data from Farside Investors show the funds took in $232.2 million in net inflows on August 26. BlackRock's iShares Bitcoin Trust (IBIT) accounted for $200.8 million, while Fidelity's FBTC added $25.6 million. The tally extends the streak to eight consecutive sessions of net inflows across the group. Grayscale's GBTC, though, posted $50.4 million in net withdrawals on Wednesday. On market structure, Wintermute trader Jasper De Maere said Bitcoin's correlation with the Nasdaq has eased to about 0.3 from a prior peak near 0.9, noting the figure reflects recent co-movement and does not guarantee a lasting break from equities. Technically, analyst Ted said Bitcoin has regained two widely watched levels: the 200-week exponential moving average and the bull market support band. He flagged $83,000 as the next key resistance zone, arguing a weekly close above that area would signal the bear-market bottom is in. De Maere identified nearer-term resistance between $80,000 and $81,000 following an earlier rejection around $81,200, and placed the next support region in the mid-$70,000s. Disclaimer: This content is for informational purposes only and does not constitute financial advice. CoinCryptoNewz is not responsible for any losses incurred. Readers should conduct their own research before making financial decisions.

U.S. spot Bitcoin ETFs posted net inflows of $232.12 million yesterday.

Core Lightning (CLN) is asking Lightning node operators to act before they can independently verify the underlying threat details. In an Aug. 23 post on Stacker News, CLN urged operators to install new binaries that address multiple reported vulnerabilities. Operators who choose not to upgrade were told to take nodes offline. CLN said it will keep technical specifics under embargo for two weeks. To reduce the amount of blind trust required, CLN plans to attach team signatures to the binaries so users can verify provenance and reproducibility. Core Lightning's release process already relies on signed tags, signed checksums, and reproducible builds, controls designed to let operators confirm that packages were produced through the intended release pipeline. What operators still cannot do during the embargo is inspect the evidence behind CLN's threat assessment, understand the exploit mechanisms from public materials, or determine whether their own node configuration is exposed. CLN's warning highlights a recurring tension in Bitcoin-adjacent software: monetary rules can be verified independently, but live security incidents often limit what can be published without also helping an attacker. What can be verified now vs. what remains unknown during the embargo - Software provenance: Operators can confirm binaries came through CLN's release process; it remains unclear whether the patched issues affect every node setup. - Release authenticity: Signed tags and signed checksums can be checked; the exact vulnerability mechanisms are not public. - Build integrity: Reproducible builds can link source and binary; it is unknown whether older binaries expose a specific attack path. - Maintainer approval: Team signatures can confirm release ownership; the severity of each reported issue is not yet established publicly. - Operational response: CLN recommends upgrading or going offline; it remains uncertain whether going offline is necessary for every operator. A timeline shaped by AI-generated report volume CLN said the sequence began around Aug. 13, when it received multiple AI-generated CVE reports from several sources over roughly 10 days. The team began validating the reports with help from outside open-source contributors, while developers prepared fixes. By Aug. 23, CLN said it had binaries ready that addressed many of the reported vulnerabilities and would stop supporting prior releases, including 26.04, "given the known risks." Blockstream shipped two CLN versions during Q2: 26.04 in April and 26.06 in June. Blockstream's Q2 update listed 26.09 on the Q3 roadmap. CLN has not presented evidence of exploitation in the wild, and the public information does not support treating every report as equally severe. Operators therefore face two separate verification problems: first, authenticating the software artifacts; second, evaluating the threat itself, which is constrained by coordinated disclosure. Disclosure trade-offs: speed, safety, and trust CERT's coordinated vulnerability disclosure guidance aims to reduce adversary advantage during remediation and distinguishes between patch availability and patch deployment. In practice, the trade-offs look like this: - Immediate full technical disclosure: enables independent risk assessment, but can hand attackers an exploit path before nodes patch. - Embargo with signed binaries: creates time for safer upgrades, but requires temporary trust in maintainer judgment. - Patch exists but is not broadly deployed: helps prepared operators, leaves others exposed. - Delayed public details: can reduce attacker advantage during rollout, but may increase suspicion or hesitation. - Post-embargo disclosure: restores independent verification, contingent on publishing clear evidence. A detailed write-up can also help skilled attackers map vulnerable code paths in older software. Signed binaries narrow the trust requirement by letting operators authenticate who produced the release, while reproducible builds can validate the source-to-binary relationship. Still, emergency handling depends on human judgment: maintainers decide whether a report warrants urgent action, release engineers decide when fixes can ship, and security teams decide what users can safely know before disclosure changes the attacker's information set. Potential network impact if operators hesitate If operators delay upgrades because they cannot inspect the threat model, some may opt to run offline instead. CLN documents offline mode as preventing the node from binding to ports or reconnecting to peers. A meaningful share of delayed upgrades or offline nodes could reduce routing availability across parts of the Lightning Network. A prolonged gap between warning and evidence could also turn a standard disclosure process into a credibility test for maintainers. AI compresses the "verify later" window The incident also reflects a broader shift in vulnerability reporting. Google revised its Open Source Software Vulnerability Reward Program in March after a "massive surge" in AI-generated reports, saying many submissions included incorrect information or hallucinated exploit paths. Google raised proof requirements in some tiers to help triage teams focus on credible threats. In the AI era, each stage of disclosure faces new pressure: - Report intake: bursts of AI-generated submissions can arrive at scale. - Triage: maintainers must filter noise faster. - Validation: developers must reproduce issues amid higher volume. - Patch development: fixes may be built while multiple parties search for similar flaws. - User rollout: attackers may use diffs, binaries, or clues to accelerate rediscovery. - Final disclosure: the time window for independent verification may shrink. CLN's account mirrors that dynamic: multiple AI-generated reports arrived quickly, but humans still had to validate them before treating them as real vulnerabilities. Google has also shown AI-driven fuzzing can find issues in mature open-source projects, including OpenSSL. Lower-cost discovery can also lower the cost of rediscovery once a patched binary, code difference, or other technical signal exists. Cryptography can minimize trust when verifying transactions, balances, and software artifacts. Operational security incidents can still require temporary trust in maintainer judgment when immediate disclosure would improve an attacker's position. CLN's post-embargo disclosure will determine whether that temporary trust expires into independently inspectable evidence. Source: CryptoSlate

Aug. 27 update — Bitcoin ETFs recorded 1-day net inflows of +3,085 BTC (+$244.63M) and 7-day net inflows of +23,884 BTC (+$1.89B). Ethereum ETFs posted 1-day net inflows of +61,948 ETH (+$154.98M) and 7-day net inflows of +336,534 ETH (+$841.94M).