NEW: @zachxbt SAYS "THE ALLEGED DPRK ATTACKERS HAVE JUST BEGUN SHIELDING ~2.7K ZEC ($3.8M) TOTAL FROM THE BITGET EXPLOIT INTO THE IRONWOOD POOL" SOURCE: t.me/investigations/364

Bill and Keonne Donation Update 0.03200287 BTC Donated!!! After donating the most recent funds from the billandkeonne@getalby.com account it should be noted how grateful we are to have the Local Bitcoiners (@HodlRev and Reed) in our circles. They did a tremendous drive of donations to the Alby account and if you go to localbitcoiners.com/stats you can see the 0.02385530 BTC they have raised so far. Check out their podcast, attend a meetup and/or make one yourself. As for all of the Ungovernables out there, thanks to you all as well for the contributions to the fund too!

More details on the current #fUSD and zano:native situation. freedomdollar.com/en/blog/fu…

Zano network update: Recovery solution for Gateway Address vulnerability The core team has identified a serious issue involving Gateway Addresses, which enabled unauthorized ZANO and fUSD to enter circulation. Our investigation has found no compromise of wallet spend keys or ordinary transaction privacy. Zano core consensus is unaffected. The team has developed a solution to eliminate all unauthorized activity with a coordinated network upgrade. To ensure full network integrity, the Zano blockchain has been restarted from block height 3,833,000, immediately prior to Hard Fork 6. This affects approximately one month of chain history. The recovery requires participating nodes, miners, stakers, and services to adopt the update. We are relaunching services such as the mobile wallet node and the wrap service one by one. It is up to each third-party wallet, exchange, and service to update on their own behalf. Before sending funds to or from any of them, check that they have moved to the recovered chain. Transactions confirmed during the affected period are not part of the recovered chain. Keep transaction IDs and trade records, and do not resend a payment until you have updated your wallet and checked its final status on the recovered chain. If you run a full node, mine, stake, operate a pool, or provide exchange, bridge, or payment services, please install the emergency release as soon as possible. Use only zano.org/wallets or the official GitHub releases page, and verify the published checksums. Ordinary wallet users can now download the updated wallet from our website as well. Seed phrases are not required to perform this upgrade. This update removes all unauthorized activity from Zano's chain. It cannot affect payments already settled in USDT, DAI, or other assets on separate networks. The team is working with affected projects and counterparties to account for any losses and will publish the reimbursement and claims process. Real people and businesses have been affected. We intend for the community to be made whole throughout this process. Certain community members have already pledged support to ensure that assets are restored. Pushing innovation carries risk, and this is a clear example. Serious incidents have occurred elsewhere: Bitcoin recovered from an exploited supply bug and chain reorganization in 2010; Zcash recently patched a potential counterfeiting flaw before any known exploitation; and Ethereum made an exceptional state change after the DAO attack. Each case was different, and none diminishes the harm here. We will publish the technical cause, the results of reviewing adjacent Gateway Address code, and the criteria for safely resuming activity. Confidence must be earned through that work, and the team is committed to working with the community to deliver on these efforts.

𝗜𝗠𝗣𝗢𝗥𝗧𝗔𝗡𝗧 𝗨𝗣𝗗𝗔𝗧𝗘𝗦: The withdrawal plan will be announced by September 26th, 4:00 AM UTC. We appreciate your patience on this matter. Based on the latest onchain tracing and classification of transactions, assets equivalent to approximately $387.5 million were transferred to attacker-controlled addresses across multiple networks. The revised figure reflects a more complete accounting of transfers that occurred during the incident, adding affected assets on Zcash and TRON that were not included in the initial estimate. It does not reflect further unauthorized transfers. The incident remains contained and no further unauthorized transfers are possible. The incident involved assets across Ethereum and several EVM networks, XRP Ledger, Zcash and TRON. The primary attacker-controlled receiving addresses identified to date are: → EVM: 0x770b10b273fc44fe9197d6bf20f145c2e98463ee → XRP: rwNhefsz1UQEusxhCvHip3RANinWi4CTck → ZEC: t1WgMdtND8NF7NDUuYmq8MpMj1NTCXkMDVG → TRON: TBWNguTTgezw9dVorX441C6nDrZpRxYwKD The confirmed affected assets include XRP, ETH, USDT, ZEC, USDC, USDT0, XAUt, BNB, AVAX and TRX. Our investigation and tracing efforts remain ongoing. The figures above reflect information confirmed at the time of publication and may be updated as additional transactions are classified and traced. The incident remains contained, with no further unauthorized transfers since the incident was contained, and the investigation with Mandiant and SlowMist remains ongoing Withdrawals remain temporarily paused while additional security checks and remediation are underway. Bitget will continue to provide verified updates on the investigation, asset recovery, withdrawal restoration and the User Protection Fund through its official channels. 𝘍𝘰𝘳 𝘪𝘯𝘧𝘰𝘳𝘮𝘢𝘵𝘪𝘰𝘯𝘢𝘭 𝘱𝘶𝘳𝘱𝘰𝘴𝘦𝘴 𝘰𝘯𝘭𝘺.

⚠️Cake Wallet's Yesenia Gonzalez's Telegram account was hacked and the account is now attempting to convince people to install malware Cake knew about this for over a week, but made NO PUBLIC WARNING Multiple of Cake's partners are already affected