Matt Weatherilt

@realDonaldTrump it’s not too late to declare a federal holiday for Friday the 13th 😬 We can call it Microsoft 364 Day.

Follow up: I found something even more absurd ⚠️ Since context-module 2.7.0, Ledger's SDK sends a SECOND report on every signature, to /v2/blind-signing-events, now with the function selector too. It's on by default, and unlike v1, the SDK gives no option to replace or disable it. So any wallet that turned off the v1 report starts sending again after a routine update. Their signer kit changelog says it plainly: "Require context-module 2.7.0 (sign reporter enabled)" github.com/LedgerHQ/device-s… github.com/LedgerHQ/device-s… Alongside @ambire, @Rabby_io also caught the v1 report from my post below 👏 They replaced Ledger's v1 reporter with a local callback that sends nothing: github.com/RabbyHub/Rabby/bl… But they're still on 2.1.0, which has no v2 reporter yet. The day they update, v2 goes out anyway unless they catch it. So heads up, fellow wallet devs: the builder has no setter for the v2 reporter, so you need to gate `signReport` on the built module yourself. Ambire is safe because we're not on 2.7.0. Since Ledger gives no setting for the v2 reporter, our next SDK update overrides it in code, so it follows the same opt-in privacy toggle we already use for v1 (off by default). @Ledger, is this a test to see if we're paying attention? I guess at this point we should review every SDK update line by line.

The Across domain is currently down while we secure it against an attack from earlier today. At ~18:45 UTC, a social engineering attack on @Namecheap (our domain registrar) gave a bad actor control of the Across domain. Within 15 minutes of this attack, we were alerted and immediately worked to shut the site down. SEAL911 marked across.(to) as a phishing site with major wallets, and Cloudflare worked with us to mark the domain as at risk, and later pulled the site’s DNS records. At the time of this post, Across.(to) is fully down, and the phishing site is no longer available. In the brief period before Cloudflare fully blocked the malware site, some users who visited across.(to) may have been affected. No third-party integrations or API users were affected. Users who believe they were affected should DM us with transaction details and revoke attacker permissions (see next tweet for details). Despite our best efforts, @Namecheap has been unresponsive, and we have not been able to properly secure the domain to bring Across’s services back up. Across’s frontend and API will remain down until we can properly secure them. We will always put user safety first. Across’s domain was fully locked down with best-in-class security practices; this unauthorized takeover should not have been possible. We will be investigating this deeply and will provide a post-mortem on how this domain takeover was possible once we have more information.

🚨 Social login wallets exposed A flaw at @Web3Auth exposed the private keys behind some @keplrwallet Google and Apple login wallets. How the login works, the rescue, the numbers, and what it means for Cardano 👇 youtu.be/8YjLkT094fA Not financial advice.

If only we had a technology where you could access your money 24/7 and you don't have to trust anyone cnn.com/2026/11/05/americas/…

“We’re making Midnight the way you do private stuff among other public chains.” - @DMillarDurrant, CEO of @Sig_Network Together, Midnight and Sig Network are connecting programmable privacy with the assets, apps, and liquidity already out there, so privacy doesn’t stop at the boundaries of one network. The details behind the vision 👇

With all the self-custody and hardware wallet hacks lately, I've had people tell me it's safer to keep assets on exchanges. It looks like nothing is safe or secure anymore.

Midnight mainnet has passed one million transactions. A milestone for @MidnightNtwrk and the builders putting privacy to work.

Bitcoin doesn’t need another custodial bridge. 🚫🏦 Full interview: 🎥 youtu.be/AN3ZPT3pTpc @FluidTokens Bifrost uses Cardano SPOs and a 67% stake threshold to secure BTC, with a path towards borrowing and simpler DeFi. 💰 I got into the design with @elraulito on Builders Bench. Chapters below. 📖👇 0:00 Intro 1:19 What Is Bifrost? 4:20 How Bifrost Secures Bitcoin 8:44 Stake Pool Operators Run the Bridge 10:04 Could Someone Attack It? 11:44 Can Bitcoin Fix Cardano DeFi? 14:57 What Bitcoiners Want 17:44 One-Click Bitcoin DeFi 19:08 Bifrost Testnet Walkthrough

Earlier this year, the SEC classified $ADA as a digital commodity, not a security. However, this classification only appears in the explanation of the new crypto rules, not in the rules themselves. Six blockchain organizations have asked the SEC to write it into the rules. We co-signed the letter, alongside @StellarOrg, @Hedera, @AptosLabs, @AvaLabs and @Chainlink.

1/ Introducing Nightmode 🌑 What if you could access onchain finance without putting your entire financial life on display? Built with @Sig_Network, Nightmode extends Midnight’s shielded privacy and selective disclosure to public chains like Bitcoin, Ethereum, Solana, Tron and more. Using MPC vaults, Nightmode aims to bring privacy to the assets and applications people already use, without requiring them to leave their existing ecosystems. See how it works 👇

It's a must have for cybersecurity. We are going to build a reference cluster and recommend all node builders get one covered by the Treasury next year so we can do continuous security audits for all critical Cardano code

Cardano just handed Plutus maintenance to MidgardLabs, a team already auditing contracts and building with Plutarch and Aiken. That move shows the chain can stand without one org holding every key piece. Decentralisation in practice, not just theory. Which core component would you like to see handed off next?

Caught this on FluidTokens (@FluidTokens) yesterday. Lender payments now go straight back into the pool. No withdraw-and-redeposit loop. Nice feature. Save time. teapawt.net/FluidTokens/status/210…

○ public ○ private ◉ proving what I need to prove and absolutely nothing else