
Wow, so shocked that @theburntpeanut didn't win the best vTuber award. Very shocked indeed. Who could've seen this coming! Definitely not me! How could it possibly be that he didn't win such a balanced award and category. 🤣😂

Building AI systems for a living. Writing about AI, politics, and whatever else holds my attention.

Wow, so shocked that @theburntpeanut didn't win the best vTuber award. Very shocked indeed. Who could've seen this coming! Definitely not me! How could it possibly be that he didn't win such a balanced award and category. 🤣😂

Still not your crypto. @Web3Auth, "with assistance from @keplrwallet", moved funds from 46,658 wallets across 11 @cosmos chains, using a "whitehat" recovery method. Keplr's terms say it has "no ability" to do this. Web3Auth promises users "full control" 🧵
Update on Keplr asset recovery: As part of our ongoing response to the security incident affecting certain Keplr wallets, we have been transferring assets into secure recovery wallets, with assistance from Keplr. 🧵

Keplr / Web3Auth social-login drain: what the chain shows so far Two different sweepers moved funds out of the affected Keplr social-login accounts. They behave very differently. Labels below are likelihoods drawn from behaviour, not proof of who controls an address. Data to 01:03 UTC on 8 Nov. Sweep counts to 22:28 UTC on 7 Nov. Bottom line An attacker-likely cluster was draining before the reported pause. The earliest drain we attribute to it is 5 Nov, 01:05 UTC. That is about 44 hours before Web3Auth reported pausing its service at 21:13 UTC on 6 Nov. It drained 153 new keys after the pause, all but one before 03:00 UTC on 7 Nov. It swapped most of what it took on Osmosis. It bridged at least $783k toward Ethereum through the public Squid / Axelar route. A separate collector held about $6.13M at 00:39 UTC on 8 Nov. It swept 45,931 keys, 86% of them after Keplr's reported warning at 04:38 UTC on 7 Nov. None of its 11 addresses had sent anything out when checked between 00:51 and 01:03 UTC on 8 Nov. Nothing had been returned to victims. Its Cosmos Hub staking sweeps carry "lsm recovery" memos. That fits the protective transfers Web3Auth has reported. It stays unconfirmed until Web3Auth publishes the recovery address list it has said is coming. The two figures cover different keys: at least 358 drained against 45,931 swept. Do not add them, or read them as stolen versus recovered. Some keys were drained well before the pause. 19 of the 36 keys the attacker-likely cluster drained on 5 Nov were later swept by the separate collector. The first of them was drained at 01:05 UTC on 5 Nov, about 44 hours before the reported pause. If you used Keplr's social login Follow only official Keplr and Web3Auth channels. Nobody legitimate will DM you to return funds. Do not sign in, connect a wallet or sign a "claim" transaction on any link you are sent. Nobody legitimate will ask for a private key, seed phrase or fee.


And lets not forget the 3rd party websites: Which provide critical information! philipp-payments.pages.dev/ terra-validator-votes.pages.…

TERRA PROP 4853: THE LAST STAND FOR CHECKS ON THE PHOENIX FOUNDATION. VOTE NO. 4853 asks Terra to declare the dispute over a failed board vote an "emergency" and to give a supervisor the power to instruct the Phoenix Foundation (PF) board to remove a director. The failed vote is A272: an attempt on 10 October by directors Philipp Mager (@0xPhilipp, ERIS) and @MB_Aejir to remove Vini. If Vini goes, the board becomes 2-of-3 and Philipp and MB can pass anything. That means the PF treasury, and where 31% of all staked LUNA is delegated: the stake that votes on every Terra proposal after this one. Philipp's ERIS keys already hold upgrade control over the treasury and every TLA contract, two years after he promised to hand it over. 87% of the Yes vote is stake the PF board or ERIS placed with five validators: Philipp's own, MB's, one Philipp operates, one that pays Philipp every month, and one that is 83% PF/ERIS funded. If it passes and Vini goes, the two directors this vote is meant to check would control the stake that checks them. This is the last vote before that happens. Vote No. Quorum is already met, so abstaining no longer stops it. Voting ends 31 Oct, 03:40 UTC. WHAT 4853 DOES Philipp submitted it from his ERIS validator key. It asks Terra governance to: - declare "the persistent Stewardship dysfunction surrounding Proposal A272" an Adverse Event under PF's bylaws - appoint Martin as Emergency Supervisor ("MB and I support Martin", Philipp, forum post 85) - confirm his power under Art. 2.4.5.4 to instruct directors "to facilitate removal" - pay him up to $10,000 His declaration of independence comes after the vote, with his acceptance. Not before. While an Emergency Supervisor is in place, Bylaws Art. 1.10 says the Veto Multisig's veto "may be disregarded". That check on the board switches off. The proposal says it does "not predetermine findings" or "directly remove any Director". On 25 Oct, in Lion DAO's public Telegram while Lion's members were voting on 4853, Philipp wrote: "any director will be legally liable if he doesn't follow the notice of removal." Asked whether Vini's seat would be filled if he is dismissed: "Yes." On what happens if the board doesn't follow the supervisor: "it will go to governance and sudo the action. And afterwards the supervisor is contacted for legal action." What follows a removal is not in doubt. A272's own on-chain messages "remove Vini from the multi-sig and convert it to a 2-out-of-3 multi-sig". Philipp, post 5: "a removal necessarily will always come with a move to 2-of-3". Asked to make it binding that no removal leaves him and MB as sufficient authority alone, he replied (post 57): "I couldn't care less about such a clause." He offered instead an off-chain promise to vote only No or Abstain during the 2-of-3 period, except to onboard new directors. He says new directors would be added later, as a separate step (post 57). Neither the promise nor the new directors are in the proposal you are voting on. THE "EMERGENCY" IS A FAILED VOTE A272 tried to remove Vini. Philipp and MB voted Yes, Rose voted No, Vini did not vote. It needed 3 of 4 and failed on 10 Oct. That is the "Adverse Event". Rose, a director (post 72): "I do not consider the failure of A272, or a disagreement between directors, to constitute an Adverse Event in itself. A failed vote is a legitimate outcome of a governance process." She says any independent review should be able to examine "any of the four directors, including my own". Since A272 failed, the board has executed 14 proposals. Vini voted Yes to pay Philipp, MB and Rose for October (A277 to A279). There is no October stewardship payment for Vini. In Lion DAO's Telegram, Philipp listed what "will now fail", including "You want to pay vini -> fail." Paying Vini needs three of four votes and he has voted to pay the other three, so it only fails if two of them refuse. PF already has a standing Supervisor under its bylaws. A272 was never put to them. Philipp's reason (post 91): "not required, and doesn't have the authority to instruct removal." WHO IS VOTING YES As of 25 Oct, 10:06 UTC: Yes 48.0M LUNA, No 25.1M, No with Veto 1.6M, Abstain 18.9M. Yes is 64.3% of decisive votes. Turnout crossed the 30% quorum at 06:50 UTC on 25 Oct, with HighStakes' Yes. Five validators cast 98.9% of the Yes: - Galactic Punks, 14.3M. 89.4% of its stake was placed by PF/TLA or ERIS's hub. Its operator key pays Philipp's validator key every month: 116,735 LUNA in ten payments since February. - ERIS, 8.6M. Philipp's own validator. 98.9% PF/ERIS stake. - Orbital Command, 8.3M. MB's validator ("MB aejir (OC/PD)" in the Phoenix Directive's own 2024 proposal). 73.5% PF/ERIS stake. - Lion DAO, 8.3M. Run by Philipp, per Lion's founder and a Lion team member. 94.7% PF/TLA stake. Its operator key also pays Philipp's key every month: 105,227 LUNA in ten payments, each sent within five minutes of GP's. - HighStakes, 8.1M. 83.2% PF/ERIS stake. Stake placed by the PF board or ERIS's hub is 87% of all Yes voting power. The validators run by Philipp and MB, the two directors who voted to remove Vini (ERIS, Orbital Command and Lion), are 52% of it on their own. Across the network, PF/TLA places 30.9% of all staked LUNA and ERIS's hub another 10.5%. 18 of the top 25 validators get more than half their stake from them. Dependence is not destiny. Smart Stake gets 68.9% of its stake from PF/ERIS and voted No. That is what independence looks like. The Lion and GP payments may be fees for running those validators. Either way, two of the validators voting Yes on Philipp's proposal pay Philipp every month. LION DAO In a pinned post in Lion DAO's public Telegram (12 Jan 2024), Lion's founder Ryan Lion wrote that Philipp "operates our validator", and that on the Terra delegation committee they both "abstained from any vote relating to delegations to Lion DAO". That committee's report lists Philipp under "Eris + validator operations (The Lion Dao)". On the PF board since, Philipp has voted Yes on all ten proposals setting the delegations Lion receives (A4, A5, A6, A20, A21, A194 to A198). On 25 Oct, a Lion DAO team member Usaf, confirmed it in the same group: "Phil provides hosting services the same way Hexagon do but is still required to abide by DAODAO signalling vote." On 4853, Lion's validator first voted Abstain (24 Oct, 04:18 UTC). Lion DAO then opened that signalling vote (A33), closing 26 Oct at 13:16 UTC. Four wallets voted. Ryan's own wallet ("RyanLion" on DAO DAO) is 99.9% of the Yes weight. ERIS's ampROAR hub, which votes 58% of Lion DAO's staked ROAR, abstained, as it has on every Lion proposal it has voted on. No one voted No. As it stands, Lion's members' vote comes down to its founder. The validator (Philip) did not wait for it. It switched to Yes at 05:06 UTC on 25 Oct, 13.5 hours after Ryan voted and 32 hours before the vote it is "required to abide by" closes. Less than six minutes later, the same key executed the ERIS multisig proposal that handed admin of ERIS's ampLUNA hub to the PF board. Ryan also sits on PF's Veto Multisig: the check that Art. 1.10 lets the board disregard once an Emergency Supervisor is appointed. So do Philipp, who proposed 4853, and Rebel, who argued for an Emergency Supervisor on the forum (post 43) and is listed as a partner in Orbital Command in Terra's 2022 governance records. Three of the six members of the check that 4853 switches off are on its side. While Lion's members were voting, Philipp was in their chat. On whether the supervisor's advice binds the board: "It is legally binding, however when they will not follow it, it will go to governance and sudo the action. And afterwards the supervisor is contacted for legal action." Six minutes later: "The only vote is about getting an independent review." Four minutes after that: "any director will be legally liable if he doesn't follow the notice of removal." THE KEYS HE NEVER HANDED OVER When Philipp launched the Terra Liquidity Alliance in August 2024, his proposal said: "Contract Admin will be transferred to PD Stewardship after 1 month" and "Ownership transferred to PD Stewardship after 3 months." Today, the upgrade admin of the PF Treasury and all 13 TLA contracts (the registry and the 12 contracts it lists) is a single ERIS key, terra1q0vny...q5tew. The TLA registry, which tells every TLA contract who controls it, is owned by another single ERIS key, terra1kefa...klgzl. Whoever holds a contract's upgrade admin can replace its code. It's Philip. Philipp (post 55): "Given my unresolved concerns about the current Board, ERIS Team has not considered transferring that authority appropriate." PAY Every director votes on their own pay. On board proposals paying their own wallets, Philipp voted Yes 17 of 19 times, MB 10 of 11, Vini 12 of 16, Rose 6 of 11. October pay: Philipp 8,640 USDC, MB 5,640, Rose 4,800. On top of that, PF approved grants to Philipp's validator key for ERIS projects he proposed: Votion $50,000, Creda $210,000, Estima $125,000. He sat out the final Creda and Estima approvals, then voted Yes on every milestone release paying his own key: $305,000 approved for payout so far. Votion also received $50,000 from the Cosmos Hub's AADAO, whose oversight report lists "Philipp Mager" as its grantee representative. Add the monthly LUNA from Lion and GP: 221,962 LUNA since February. Vini isn't clean either. He proposed and voted Yes on A249, which paid 16,900 USDC to his own wallet for a security audit. He voted Yes on A159, which raised his own monthly pay from 2,800 to 5,000 USDC. Those are real, and an investigation should cover them. That is the point. Self-dealing on this board is not one director's problem. It is all four. 4853 builds its case around one of them. Asked to put directors' votes on payments to themselves and the conflict rules A272 relies on into scope (posts 37 and 39), Philipp said "No" to "an open-ended investigation of every Director, every grant and every PF decision ever made" (post 38), while saying he has "no issue" with his own actions being reviewed. MB (post 40): "No. The scope of this prop is not going to be changed." The final text lets the supervisor examine "the conduct of any Director where relevant". It does not name self-payments, conflicts or retained contract control. THE FORUM The four directors are the forum's admins. - 19 Oct: two critics of 4853 were suspended until 2 Nov for "No constructive purpose to their actions other than creating dissent within the community". Lifted within half an hour. - 20 Oct: one of them was silenced until 30 Nov, a month after this vote ends, for "Personal attacks, swearing, repetitive and obnoxious posts". One of his posts did swear. - At least three posts were removed by staff, not by their authors. Two were from Free Do's validator operator account, which voted No with Veto: one called for term limits, a fifth director and removing both Vini and Philipp; the other linked to a site documenting Philipp's payments. The third, from the other suspended critic, asked how many times the proposal's author had voted on funding his own projects. The on-chain answer: at least seven (A107, A116, A175, A209, A213, A215, A271). Only PF's staff action log shows which admin did what. PF can publish it. PF's own X account (@phoenix_dir) used its 25 Oct post to promote a different Terra governance proposal. Not this one. THE LAST STAND If 4853 passes: - a failed board vote becomes an "emergency", and a precedent - the Veto Multisig can be disregarded - a supervisor can instruct the removal Philipp and MB could not win on 10 Oct - the board becomes 2-of-3, and Philipp and MB are the 2 - they control the treasury and where 31% of staked LUNA sits, while Philipp's ERIS keys keep upgrade control of the treasury and the TLA Any later Terra vote to undo it would be cast largely by validators whose stake they place. Look at who is voting Yes today. What a fair process looks like: one standard for all four directors, with payments to themselves, conflicts and retained contract control written into scope. Contract admin handed over as promised in 2024. A binding rule that no removal leaves two directors with sufficient authority alone. A supervisor's independence declared before the vote, not after. None of that is in 4853. Vote No, or No with Veto. Quorum is met, so Abstain no longer blocks it. It flips if GP moves to No, or any two of the other four Yes validators do, or with about 21.3M LUNA of new No votes. If you delegate to a Yes validator, vote yourself: your vote overrides theirs for your stake. Voting ends 31 Oct, 03:40 UTC. SOURCES Proposal 4853: mintscan.io/terra/proposals/… Forum thread (posts 5, 37 to 40, 43, 55, 57, 72, 85, 91): forum.phoenix.money/t/phoeni… PF Bylaws (Art. 1.10, 2.4.5.4, 2.6): github.com/phoenix-directive… A272: daodao.zone/dao/terra1k8ug6d… PF board proposals cited (A4-A6, A20, A21, A107, A116, A159, A175, A190, A194-A198, A209, A213, A215, A249, A266, A271, A277-A279): daodao.zone/dao/terra1k8ug6d… Philipp's full name: - AADAO oversight report (Votion, "Grantee Representative: Philipp Mager"): forum.cosmos.network/t/aadao… - GitHub commit record, Terra Core, 24 Jul 2024 (author name "Philipp mager", account 0xphilipp; the same author name is on his ERIS commits from 2022 to 2024): api.github.com/repos/terra-m… TLA launch pledge, Aug 2024: github.com/phoenix-directive… PF Treasury contract: chainsco.pe/terra2/address/t… TLA registry: chainsco.pe/terra2/address/t… ERIS multisig handover, 25 Oct: mintscan.io/terra/tx/86E5992… Lion to Philipp's key, 19 Oct: mintscan.io/terra/tx/B77EAB8… GP to Philipp's key, 19 Oct: mintscan.io/terra/tx/C940EBF… Phoenix Directive 2024 proposal (MB "OC/PD", Philipp's key): github.com/phoenix-directive… Delegation committee report (Philipp, Lion validator operations): github.com/phoenix-directive… Lion DAO members' vote A33: daodao.zone/dao/terra1tkersa… Lion validator Abstain: mintscan.io/terra/tx/9531362… Lion validator Yes: mintscan.io/terra/tx/4B356AF… Ryan's Veto Multisig wallet to the RyanLion wallet: mintscan.io/terra/tx/1D67ECA… PF Veto Multisig: daodao.zone/dao/terra15l7567… PF doc listing the Veto Multisig members' wallets (Philipp, Rebel, Ryan): github.com/phoenix-directive… Rebel Defi, "Partner - Orbital Command" (2022): github.com/phoenix-directive… @phoenix_dir, 25 Oct: x.com/phoenix_dir/status/211… Lion DAO public Telegram (t.me/Lion_DAO): Ryan Lion, 12 Jan 2024 (pinned). $LUNA
A new Terra Governance proposal outlines the recovery process following the legacy Terra Station Desktop Ill Bloom compromise. The proposal includes potential reimbursement of verified claims from the PF Treasury. 🌐 forum.phoenix.money/t/update…

wow. I don't really pay much attention anymore to #terra2 anymore but this is getting too much - forum.phoenix.money/t/phoeni… Phil is having a spat with one of the other stewards, and is trying all means of tricks to kick him out. @Rarma_ then raised this.. no response

I think now is a good time to provide an update on my Cosmos 10k Challenge. Disappointed I'm down a bit from last time. But overall I think the investments have worked out well. 23 Oct 2026 vs 26 Aug 2023. cosmos:native $OSMO secret:native $LUNA $JUNO $BTC $ETH
We’re back! Another update on the famous Cosmos 10k challenge! Significant improvement on last time. And very happy with my original 10k investment. I started this one 28/08/2023. And as you can see my investments are significantly up. Let’s see where we go from here. But I have very high confidence. Now vs 2023 $ATOM $OSMO $SCRT $LUNA $JUNO $BTC $ETH

Hilarious seeing @theburntpeanut rage baiting all the VTuber community. The community that wants everyone to accept them for who they choose to identify as, but are now mad as hell at him for not wanting to identify as a VTuber but being nomintated for the best VTuber streamer of the year (when he is literally the definition of a VTuber). Can't make this shit up 😂😂😂


Stratos (stratos-1), a Cosmos EVM chain, was exploited and its validators halted the chain. Here is what happened and where the funds went, read directly from the chain. The chain is frozen at block 16,008,475, last block 05:21 UTC. The bug is a custom EVM precompile at 0x0000000000000000000077656233636f736d6f73 — the tail bytes spell "web3cosmos". It takes a Cosmos message in its calldata and runs it as whatever "from" account is named inside, without checking the caller owns that account or was authorised by it. The attacker wrapped calls to it in a Cosmos authz MsgExec, each carrying a forged bank MsgSend from a victim to the attacker. In a single transaction, block 15,986,214, this drained 50,616,206 STOS from 11 accounts into the collector 0x57e1… / st12lsj78…. Proof it is an authorisation bypass and not stolen keys: the largest victim lost 23M STOS and now holds 1 wei. That account has a null public key. It has never signed a transaction, so it could not have authorised anyone. The precompile moved its funds anyway. Where the funds went: - ~40M STOS was IBC-transferred to Osmosis (osmo14qpeg…) at block 15,991,081, about a day before the halt. Around 10M of that was later sent back to Stratos. So on the order of 30M net left the chain before validators stopped it. - ~10M of the loot sits frozen in the Stratos WSTOS bridge vault (0x2a7157…), which also holds ~22M of pre-existing TVL, all frozen by the halt. The halt did not catch the bulk. A validator halt only protects what is still on the chain, and most of the stolen STOS had already gone to Osmosis over plain IBC, where it was swapped and moved onward. Attacker cluster: - collector: 0x57e12f1d41b7daeb9716da758f05bec2636daea2 / st12lsj78… - authz operator: st13v7qxgvv9ncs6t25jc5kqku4wxq8d6wyvtv66t - Osmosis landing: osmo14qpeg04hyx6s6dax44q9sx268ckgr6zzhhswja Root cause for the team: an EVM precompile that executes Cosmos messages has to verify the caller is authorised for the "from" account named in the message. This one does not. Same class as the KiiChain/MANTRA Cosmos EVM precompile incidents, distinct root cause. Every figure is read from Stratos and Osmosis RPC. The onward path of the Osmosis portion is still being traced. @Stratos_Network

.@Tesla on your developer.tesla.com/ site, you need small borders on the text boxes, they're invisible until you randomly click into them

Bros before hoes Dumb mfer
I’ll be stepping away from the CDL for the foreseeable future. As some of you know, I was very close to my casting partner Joe and his family. Maurisa was one of my best friends. We remained friends, after they divorced, and along the way it became more than that and we started dating. I understand how unconventional/taboo it is. It’s truly not something I ever foresaw happening. I hope that one day I’ll be back working on the CDL. If not, it was a hell of a ride, and I appreciate the love over the years. Please continue to show support to Joe, the CDL, and its talent!

Cito back to being paid to talk shit, with a hint of Cosmos current narrative and direction. What’s this? The 6th or 7th time he’s done this and been wrong and got people rekt every time? lol.
Institutions are not buying altcoins. They are buying Bitcoin exposure, stablecoin rails and tokenization infrastructure.

Demex / Carbon incident, 25 Sep: what the chain shows About 71 ETH (~$190k) was taken from Carbon's Axelar bridge gateway, 0x4AB44c7e881Ee37CB02bc0c98547A0bBfaD9291B. The attacker didn't break the bridge's signing. He got it to treat a low-value Carbon token as WETH, then withdrew it. How it worked Carbon's bridge has a "deploy token" flow. The TokenController on Ethereum (0xad02bf7361761eb3344070873adf10cf83c12fef, verified source) takes a deployer address, a name and a Carbon denom. It calls deployer.deploy(), and whatever address comes back, it reports to Carbon as the new token. Three problems lined up: Anyone on Carbon could trigger it. The controller only checks that the call came through Carbon's relay contract, not who asked on Carbon. The attacker's own account sent it. The deployer address comes from the caller. The attacker deployed a 488-byte contract (0x064e20ae25a9d8181b168cf92fa8db7c840214c5) whose deploy() deploys nothing and just returns WETH's address. Carbon trusted the callback. It linked the denom nlend (an existing Carbon token) to WETH and registered WETH on the gateway as a Carbon-owned token. The gateway still reports isCarbonOwned(WETH) = true. For a Carbon-owned token, the gateway "mints" and then transfers. WETH has no mint function, so the call fell into WETH's fallback and did a 0 ETH deposit. You can see it in the payout transaction as Deposit(gateway, 0). The gateway then sent the WETH it already held from users. He withdrew exactly the gateway's entire balance: 64.776 WETH before, 0 after. He did the same on BSC with WBNB. The gateway's WBNB balance is now 0 too. nLEND being cheap only made it cheap to do. The bug is in the code: any 18-decimal denom he held would have worked. What left 18:50 UTC: the callback maps nlend to WETH (Carbon block 100,276,398) 19:08: withdraws 64.776 nLEND 19:09:59: the gateway pays 64.776 WETH to 0x72a4712a8d4368c98f1feb7e55091194ba5d6daa 19:37: withdraws 22.49 nLEND on BSC, paid in WBNB. Bridged to Ethereum through deBridge (6.448 ETH) 19:47: third attempt on Base. The chain halted before the callback came back 20:01:25: Carbon halts at block 100,279,059 In the last block before the halt, Demex's group account executed a 3/3 proposal. Its contents aren't in the event logs. Where it is now The WETH was unwrapped and sent to 0x8efc2234ea01d4ec8823a06acb7459f38234c5f6. It still holds 51.27 ETH. 20 ETH went via 0x0e366f07b9d503ed908107b96353d58eae979c40 into Tornado Cash, in two 10 ETH deposits on 25 Sep and 27 Sep. The attacker's Carbon account swth1y4mm88wfeeyenh6hmapsql2qeeu6y3yg2fwg4c still holds 7.73 nLEND and 1,197 SWTH. That's frozen with the chain. It's account #67,099, which suggests the account is old. Funding The gas came from Arbitrum. 219 USDC went from 0x28cf68d078594cfd6639f7b2e3d722e4859073c0 through LI.FI and a Relay solver, then two hop wallets, to the attacker on 24 Sep at 20:58 UTC. The Arbitrum wallet had made only two transactions. Ignore the dust from lookalike addresses (0x8efCa9ca…, 0x0e36eEA2…, 0x72A4c797… and others). Those are address-poisoning bots. For exchanges and bridges: please flag 0x8efc2234ea01d4ec8823a06acb7459f38234c5f6 and 0x72a4712a8d4368c98f1feb7e55091194ba5d6daa. @demexchange
Hi Demex community, We want to update you on the timeline for our incident post-mortem report. Our team has been conducting a thorough review of what happened, and its impact. We will publish the full post-mortem within the next 48 hours. It will include: - A detailed timeline of the incident - Root cause analysis - Impact assessment We appreciate your patience as we make sure this report is thorough and accurate.

They had ~13 hours to apply the new binary and save the additional ~300k USD (170k cosmos:native) from when I notified them to when they scheduled the restart. It took them ~8 hours to plan, write and apply the 28.3.0 patch.
A full recap of the Cosmos Hub halt to recover ATOM taken in Neutron’s governance attack is now live on the Cosmos Hub Forum. It covers the timeline, validator response, and the movement of the 1.7M ATOM that reached the Hub from Neutron. Full details: forum.cosmos.network/t/neutr…