Shor's algo is a really unlucky reality for elliptic curve cryptography
Most problems don't get enormous speedup from quantum computers
EXCEPT breaking elliptic curve cryptography. That gets a huge (exponential) speedup, because Shor's uses a math trick
Trigger ⚡ retweeted
🚨 We are receiving reports of hot wallets on BTCPay Servers being swept by unauthorized attackers.
If you're running an instance, please shut it down (./btcpay-down.sh) until we complete the investigation.
Trigger ⚡ retweeted
🚨 We're releasing BTPay Server 2.4.7 an emergency update fixing one critical and several medium-severity security vulnerabilities brought to our attention through @Anthropic's frontier OSS scanner.
We recommend that you update your BTCPay Server as soon as possible.
Trigger ⚡ retweeted
Replying to @CryptoRevoltFR
On dirait que tu aimes le KYC. Tu dois être à peu près certain que tes pièces d'identité finiront par fuiter dans un hack.
Trigger ⚡ retweeted
Introducing Glow⚡️
The bitcoin app anyone can use, and any developer can explore.
Passkey Login. Stable Balance. Lightning Address. Send USDT/USDC. And so much more.
This is what bitcoin UX should feel like. Powered by Breez.
Available now on:
• @AppStore → apps.apple.com/us/app/glow-l…
• @GooglePlay → play.google.com/store/apps/d…
Trigger ⚡ retweeted
Bitcoin Core v32.0 is targeted for release in October:
- Up to 3x faster initial sync. Block validation now fetches transaction inputs from disk in parallel instead of one at a time
- The libevent external dependency is fully removed, continuing Core's push to cut third-party dependencies
- Max peer connections raised from 125 to 200 to have more open slots for new nodes to sync from, faster block propagation, and a harder network to eclipse or partition
- Mempool-based fee estimation to cut fee overestimation (in progress)
- Transaction relay rate limiting is now global instead of per-peer, keeping a node's CPU and memory usage steady when transaction volume spikes
- Ships with features from libsecp256k1 0.8.0 with verification up to 11% faster, plus the new Silent Payments module (BIP 352)
- PSBTv2 (BIP 370) support, now the default for PSBT-creating RPCs for better coordination of unsigned transactions for multisig and hardware wallet setups
- New exportwatchonlywallet command to export a wallet as a watch-only file, no private keys, and restore it on your online node
- Core now enables Tor's proof-of-work DDoS defense on the onion service it creates for your node, where the Tor daemon supports it
Additional tests, bugfixes, and features included as well.
Feature freeze is ~August 20, rc1 ~September 10, final release targeted for ~October 10. (Test the release candidates when they ship!)
Trigger ⚡ retweeted
Il y a toutes les informations nécessaires sur la faille Coldcard dans cet article :
- Ce qu'il s'est passé en détail
- Qui est concerné et à quel degré
- Ce qu'il faut faire MAINTENANT
- Les conséquences de la faille sur les fonctions annexes des coldcard
- Les conséquences indirectes pour tous les autres utilisateurs de Bitcoin
- Les stratégies de sécurisation à adopter pour être protégé en cas de faille similaire chez un autre fabriquant de hww
Here is our blog post.
- Section 1 is for Liana users, and anyone interested in "game theory" of descriptors and Miniscript/Taproot/Segwit.
- From section 2 its our Post-Mortem of Coldcard.
TLDR: It's worse than you think. Even users who have a safe mnemonic (dice rolls) have BROKEN FEATURES on their Coldcard.
wizardsardine.com/blog/coldc…
Trigger ⚡ retweeted
For my first post, I’m sharing a letter @NVIDIA signed on why open models matter.
AI will transform every industry, power every company, and be built by every country.
Open models strengthen safety and cybersecurity, accelerate innovation and diffusion, and enable sovereignty.
The world needs both frontier closed models and frontier open models.
images.nvidia.com/pdf/Open-W…
Trigger ⚡ retweeted
Comprendre la manière dont les timelocks fonctionnent sur Bitcoin :
→ la différence entre les champs de transaction (nLockTime et nSequence) et les opcodes (CLTV et CSV),
→ pourquoi l'un ne fonctionne jamais sans l'autre.
Thread complet ↓
Trigger ⚡ retweeted
Introducing Kimi K3: Open Frontier Intelligence
🔹 2.8 Trillion Parameters, 1 Million Context, Native Multimodal
🔹 Kimi Delta Attention enables up to 6.3x faster decoding in million-token contexts
🔹 Attention Residuals deliver ~25% higher training efficiency at <2% additional cost
🔹 Built for long-horizon agentic coding and self-evolving workflows
Kimi K3 is now live on on Kimi.com, Kimi Work, Kimi Code, and the Kimi API.
Open Weights by July 27, 2026.
🔗 API: platform.kimi.ai
🔗 Tech blog: kimi.com/blog/kimi-k3
Trigger ⚡ retweeted
Apple and Google are gradually expanding their use of hardware-based attestation. They're convincing a growing number of services to adopt it. Google's Play Integrity API and Apple's App Attest API are very similar. Apple brought it to the web via Privacy Pass, which Google intends on doing too.
Google's Play Integrity API requires hardware attestation for the strong integrity level and is gradually phasing in requiring it for the more commonly used device integrity level. Apple already has it as a requirement. Over the long term, this will increasingly lock out hardware and OS competition.
The purpose of these systems is disallowing people from using hardware and software not approved by Apple or Google. This is wrongly presented as being a security feature. Banks and government services are the main ones adopting it but Apple and Google are encouraging every service to use it.
Apple's Privacy Pass brought hardware attestation to the web to help with passing captchas on their own hardware. Many people saw that as harmless since few sites would be willing to lock out non-Apple-hardware users. Apple and Google are both likely to bring broader hardware attestation to the web.
Google's reCAPTCHA is planning an approach where they use Privacy Pass on Apple hardware, their own approach on Google Mobile Services Android devices and a QR code scanning system to require an iOS or Google certified Android device for Windows and other systems:
support.google.com/recaptcha…
Banking and government services increasingly require using a mobile app where they can use attestation to force using an Apple or Google approved device and OS. Apple's privacy pass, Google's 'cancelled' Web Environment Integrity and now reCAPTCHA Mobile Verification are bringing this to the web.
Current media coverage for reCAPTCHA Mobile Verification misunderstands it and the impact of it. They're bringing a hardware attestation requirement to Windows, desktop Linux, OpenBSD, etc. by requiring a QR scan from a certified smartphone to pass reCAPTCHA in some cases. They could expand it more.
Control over reCAPTCHA puts Google in a position where they can require having either iOS or a certified Android device to use an enormous amount of the web. Google defines certification requirements for Android which includes forcing bundling Google Chrome, etc. It's enormously anti-competitive.
Google's Play Integrity API bans using GrapheneOS despite it being far more secure than anything they permit. It also bans using any other alternative. This isn't somehow specific to an AOSP-based OS. You can't avoid this by using a mobile OS based on FreeBSD instead. You'll just be more locked out.
Google's Play Integrity API permits devices with no security patches for 10 years. The device integrity level can be bypassed via spoofing but they can detect it quite well and block it once it starts being done at scale. The strong integrity level requires leaked keys from TEEs/SEs to bypass it.
It doesn't provide a useful security feature, but it does lock out competition very well. Services requiring Apple App Attest or Google Play Integrity are primarily helping to lock in Apple and Google having a duopoly for mobile devices. Play Integrity is more relevant due to AOSP being open source.
Governments are increasingly mandating using Apple's App Attest and Google's Play Integrity for not only their own services but also commercial services. The EU is leading the charge of making these requirements for digital payments, ID, age verification, etc. Many EU government apps require them.
Instead of governments stopping Apple and Google from engaging in egregiously anti-competitive behavior, they're directly participating in locking out competition via their own services. Requiring people to have an Apple device or Google-certified Android device is anti-competition, not security.
reCAPTCHA Mobile Verification will currently work with sandboxed Google Play on GrapheneOS but it clearly exists to provide a way for them to start using hardware attestation on systems without it. People without an iOS or Android device will be locked out when this is required even without that.
This isn't about security or any missing functionality. GrapheneOS can be verified via hardware attestation. Google bans using GrapheneOS for Play Integrity because we don't license Google Mobile Services and conform to anti-competitive rules already found to be illegal in South Korea and elsewhere.
Services shouldn't ban people from using arbitrary hardware and operating systems in the first place. Google's security excuse is clearly bogus when they permit devices with no patches for 10 years but not a much more secure OS. It's for enforcing their monopolies via GMS licensing, that's all.
Trigger ⚡ retweeted
Introducing the new /crawl endpoint - one API call and an entire site crawled.
No scripts. No browser management. Just the content in HTML, Markdown, or JSON.
Trigger ⚡ retweeted
Latest Strikes is out! 🚀
In this issue we cover:
- the recent @cakewallet Lightning/Spark integration
- @Boltzhq mandatory update announcement
- changes in @lightningdevkit (rust-lightning), @lightning and Eclair (@acinq_co )
Link below 👇
working for yourself is addictive in a way most people don’t anticipate & the stress that comes with it is genuinely difficult to manage. when you’re the principal, nothing happens without you. you set the tone, the structure, the culture, & the motivation. you are the foundational layer.
most ppl have never had to operate this way cuz they’ve always been embedded in a system & told what to do, when to do it, & what matters. aka the shawshank lifestyle. the human mind runs surprisingly well on prescription. strip that away & you discover pretty quickly whether you actually have an interior architecture or just a talent for compliance.
that’s what makes it so damn dichotomous. the freedom is so fucking real, but so is the weight. all i’m saying is that most ppl have never had to locate their own gravity before.



































