Pinned Tweet
#Bitcoin competes with central banks and base money
#LiquidNetwork competes with SWIFT
#LightningNetwork competes with Visa
xitter.cf/btc/status/10529730038…
Vortex | BIP448 retweeted
Replying to @DrJackKruse
False. Mob didn't rule anything, logic did. 110 folks were told EXACTLY what would happen for years and didn't listen so now they created an altcoin. Learn your history.
Vortex | BIP448 retweeted
Bitcoin is older than
instagram
The iPad
snapchat
Uber
TikTok
Robinhood
The walking dead
Game of thrones
And you still think Bitcoin is too new to take seriously ?
Vortex | BIP448 retweeted
Replying to @DrJackKruse @knutsvanholm
He sure had no idea wtf he was talking about with BIP110 that's for sure.
Vortex | BIP448 retweeted
There really is a core of this space whose entire business model is elevating and platforming irrational mental illness solely because it drives controversy, which drives engagement.
They thrive even more when rational people take a rational approach, rightfully dismissing mental illness and irrationality for what it is, because they can drum that up into even more controversial mental illness and irrational claims: there is a conspiracy. Irrationality spawned from mental illness isn't dismissed because of it's nature, it's dismissed because of conspiracies, and imaginary conflicts of interest, and then eventually whole parallel narratives spinning self-reinforcing justifications for the irrationality that are totally disconnected from reality.
It's time for serious people in this space to stop humoring this nonsense. It is literally toxic and destructive for everyone involved except the people who perpetuate it and benefit from it.
Vortex | BIP448 retweeted
🚨 MAJOR SECURITY ALERT: bitcoinjs patches multiple high security issues in their packages
We hit some of the most critical infrastructure in Bitcoin is dependent on bitcoinjs packages—bitcoinjs-lib, bip39, tiny-secp256k1 were affected are ato multiple high security issues affecting major wallets, protocols, bitcoin infra and sdks :
> bitcoinjs-lib: CVE-2026-107846, GHSA-8247-5gp7-95qh, GHSA-4mfv-5394-26c7, GHSA-88jr-9qj4-ccm4, GHSA-h52v-8xwg-7j95
(patch versions: 7.0.5, 6.1.10, 5.2.3)
> bip39: CVE-2026-107847, GHSA-39w3-8jr6-f676
(latest patch version: 3.1.12)
> tiny-secp256k1: CVE-2026-107853, GHSA-85g9-f6v5-wqq7, GHSA-rm9w-7fv8-3rhx
(latest patch version: 2.2.5)
All of the above packages have ~500k downloads/week.
Also, multiple other CVEs/disclosures took place over more libs of bitcoinjs by other researchers like the ARSB and Bitcoin Red Team:
> bitcoinjs-lib: GHSA-4vm8-79jj-j6w4 (patch versions: v7.0.5, 6.1.10, 5.2.3)
> bip38: GHSA-mj7w-64jg-8f98
> bip32-utils: GHSA-wvw7-chj5-hr2g(patch version: 0.11.2)
> merkle-lib: GHSA-g353-54jg-j6gg (patch version: 2.0.11)
> bolt11: CVE-2026-107855 (patch version: 1.4.2)
There are a total of 15 findings (14 highs, 1 medium) and cover areas including transaction and block parsing, PSBT fee calculations, proof verification, mnemonic handling and elliptic-curve operations. Their impact depends on the affected version and how an application uses the library. Each advisory explains those conditions and the required remediation.
It was greating coordinating with @junderwood4649, @landabaso.
Vortex | BIP448 retweeted
Please update your BitcoinJS and related dependencies. We have backported some fixes all the way to BitcoinJS v5.
Big thanks to everyone mentioned in this post, especially to @landabaso who helped coordinate with the reporters and publish fixes.
We've just published 15 security advisories across BitcoinJS libraries (14 High and one Medium), with patched releases available on npm.
This follows work with @junderwood4649 and the reporters to investigate the issues, prepare fixes and provide backports for the maintained release lines.
The findings cover areas including transaction and block parsing, PSBT fee calculations, proof verification, mnemonic handling and elliptic-curve operations. Their impact depends on the affected version and how an application uses the library. Each advisory explains those conditions and the required remediation.
If you maintain an application using BitcoinJS packages, please check your direct and transitive dependencies and upgrade affected versions.
For bitcoinjs-lib, the patched releases are 7.0.5, 6.1.10 and 5.2.3, depending on your release line. Both tiny-secp256k1 and bitcoin-js/tiny-secp256k1-asmjs have fixes in 2.2.5.
The other patched releases are bip39 3.1.2 and 2.6.1, bip38 3.1.2 and 2.0.4, bolt11 1.4.2, merkle-lib 2.0.11 and bip32-utils 0.11.2.
Some fixes require changes in the application as well as a dependency update.
You can find the affected ranges, technical details and upgrade guidance here:
github.com/bitcoinjs/bitcoin…
github.com/bitcoinjs/tiny-se…
github.com/bitcoinjs/bip39/s…
github.com/bitcoinjs/bip38/s…
github.com/bitcoinjs/bolt11/…
github.com/bitcoinjs/merkle-…
github.com/bitcoinjs/bip32-u…
Thanks to the researchers and reporters: the Bitcoin Red Team (@Rob1Ham, @callebtc and @danielabrozzoni), @0xaudron, @real_a_kalout and ARSB (github.com/ARSB1).
Vortex | BIP448 retweeted
Post-quantum signatures have to work for low-power hardware wallets, miners, Lightning nodes and every node verifying blocks.
@n1ckler of @blksresearch at @LuganoPlanB on how SHRINCS balances signature size against those needs.
Test your use case in our open-source explorer 👇
Vortex | BIP448 retweeted
A decade ago we used to joke that some day folks would spread fear about bitcoin crashing to being worth tens of thousands of dollars. Thanks for the laugh!
xitter.cf/Jason/status/211495698…
A brutal year for Bitcoin is just getting started.
Give me three minutes to explain why you should dump it now.
Outflows from ETFs are signal and will continue.
We will test the 57k low again in the next 12 months.
Why?
Because there are far too many dynamic places to put your money that are creating MUCH more value.
Why put your resources into a dead network that offers nothing beyond a store of value?
What's the point of place the BTC be if Bitcoin's Ponzi-scheme nature has gone away!?!
The viral nature of bitcoin was it's power... if you didn't own you were MOCKED!
Now? Completely reasonable, heck, SMARTER, to ignore bitcoin and place other bets!
No one is trying to convince people to buy Bitcoin anymore... the memes and NFTs are gone.
No one is saying $ BTC can change the world, because it won't — and BECAUSE AI HAS!
Just sell and shift from Bitcoin to Super Intelligence because one provides little to no value, and the other provides unlimited upside for humanity.
This should be obvious to everyone right now.
Bitcoin will never break its all-time high again.
Vortex | BIP448 retweeted
BREAKING: LIGHTNING LABS JUST LAUNCHED A TOOL THAT LETS AI AGENTS BUY, RECEIVE, AND HODL #BITCOIN AUTONOMOUSLY
BTC IS THE CURRENCY OF AI
NOT PRICED IN 🚀
Vortex | BIP448 retweeted
Lightning Labs ha abierto Wavelength a todos, permitiendo que los agentes de IA envíen y reciban pagos en Bitcoin a través de Lightning sin necesidad de aprobación humana para cada transacción.
Los agentes pueden pagar de manera autónoma por llamadas a APIs, comprar datos y realizar transacciones con otros agentes por fracciones de centavo utilizando Lightning y L402, sin tarjetas de crédito, cuentas ni claves de API.
Wavelength is now live on mainnet! 🌊
Humans and agents can now send and receive bitcoin payments with the Wavelength SDK.
A few API calls, self-custodial from the first command, with no node or liquidity to manage.
Read more and start building: lightning.engineering/posts/…
Vortex | BIP448 retweeted
Tested Wavelength × Lightning Enable on mainnet. It worked.
Our agent bought a 1-sat API response using Wavelength’s credit-backed Lightning flow.
402 → pay → verified preimage → 200 + data.
Good to see the L402 ecosystem growing.
Wavelength is now live on mainnet! 🌊
Humans and agents can now send and receive bitcoin payments with the Wavelength SDK.
A few API calls, self-custodial from the first command, with no node or liquidity to manage.
Read more and start building: lightning.engineering/posts/…
Vortex | BIP448 retweeted
Through all the challenges & AI attacks the @BtcpayServer still continues to ship the updates & fixes!
Thanks to all of you reporting issues, opening PRs and testing new versions on your servers.
Onwards ✊🗽
Vortex | BIP448 retweeted
FOUNDATION REVEALS HOW CUSTOMER DATA SURVIVED DELETION AND FUELED MASS PHISHING CAMPAIGN
Foundation Devices says attackers exploited access to historical customer records that the company believed had been deleted, helping fuel more than 23,000 phishing email attempts targeting its hardware wallet customers.
The company discovered that its former WooCommerce store had retained personal information in legacy database tables, even though its admin dashboard showed customer orders as redacted.
During previous database migrations, customer records were copied into new tables, but older copies remained. The company's automatic deletion process only removed information from the newer tables, leaving names, shipping details, refund records and even abandoned checkout information accessible.
Foundation also confirmed that customer information from recent Shopify orders may have been exposed, as automatic data deletion had not yet been implemented.
Investigators identified 19,057 phishing messages delivered through Mailgun and another 1,503 sent through Google Workspace. The total number of affected customers remains unknown.
The attackers used authentic personal details to make fraudulent emails more convincing and trick customers into revealing their Bitcoin wallet recovery phrases.
Foundation says it has found no evidence that Passport hardware wallets or their private keys were compromised.
The investigation remains ongoing.
INVESTIGATION UPDATE
Many of you have asked how personal information ended up in the phishing emails, particularly those who ordered from us years ago. Here is what we have found so far.
Phishing emails:
We have identified more than 23,000 phishing email attempts across our email systems, including 19,057 messages delivered through Mailgun and 1,503 messages sent through Google Workspace. Some addresses received multiple messages, and some attempts failed or were stopped before delivery.
These numbers do not tell us how many people had personal information exposed. We are still determining that number and will share it once we can confirm it.
Older orders and abandoned carts (WooCommerce):
Before moving to Shopify in May of this year, our store ran on WooCommerce. We had configured automatic redaction of customer details 60 days after shipping. When we viewed those orders in our store admin, the customer details were no longer visible and the orders showed as redacted.
During past database migrations, orders were copied into a new set of tables, but copies remained in the old tables. The redaction process updated the newer tables, which were also what our store admin displayed. Orders therefore appeared redacted even though older copies still contained personal information.
We also found personal information in other order and refund records, as well as abandoned carts. This included shipping details entered by someone who never completed a purchase. We are still checking the historical settings and redaction process to understand why these records retained data.
Those older records were held in systems the attackers were able to reach. We relied on the redaction shown in our admin dashboard, and we now know that was insufficient to verify that the underlying data had been removed. Whatever the shortcomings in the tools we used, protecting your information was still our full responsibility.
We plan to share our findings with WooCommerce and the relevant plugin developers. When an order is marked as redacted, its personal information should not remain in another table in the same database.
For other WooCommerce store owners: do not rely solely on what your admin dashboard shows when personal data is redacted. Have your developer or agent check the entire database for information left behind, including legacy tables, refund records, and abandoned carts. This is especially important if you have used WooCommerce for years or have been through database migrations.
Recent orders (Shopify):
Customer details from orders placed on our Shopify store since May may also have been exposed. We are still investigating the extent of any unauthorized access.
These orders had not yet been manually redacted. We updated our privacy policy when we moved to Shopify and were building a tool to automate redaction, but automatic deletion was not yet active.
Other possible sources:
We have received reports of phishing emails containing personal details that customers say they never shared with us. We are investigating whether the attackers combined information from our systems with data obtained elsewhere, but we have not confirmed a connection to breaches at other companies. Historical support records are also part of our investigation.
What we have done:
We have revoked affected email credentials, cleared queued phishing messages, and taken affected legacy services offline while preserving evidence. Our investigation into the full extent of the compromise is continuing.
We have found no evidence that this incident compromised Passport devices or the private keys they hold. The phishing emails are designed to trick you into revealing your recovery phrase, and including your correct personal information makes them more convincing.
Never enter your recovery phrase into a website or share it with anyone, including someone claiming to be Foundation.
We will continue sharing confirmed findings and publish our full report when the investigation is complete.
Vortex | BIP448 retweeted
New BIP published:
BIP139: Wallet Metadata Export Format
github.com/bitcoin/bips/blob…
Vortex | BIP448 retweeted
💥 NEW: Bitcoin hashrate SKYROCKETS to 1.2 ZH/s as difficulty climbs to 150T
> Hashrate and difficulty both reclaim at all-time highs
> More computing power secures the network than ever before
> Higher difficulty makes attacking the chain more expensive than ever
> Mining competition is at the most extreme it has ever been
Vortex | BIP448 retweeted
Just a few of the biggest security incidents in the past week... we're still accelerating:
* PHP2Shell: Two critical RCE bugs in PHP core
* eMudhra: Eight intermediate certificates had extremely weak private keys due to a key-generation script error that created keys with tiny values.
* GitLab: integer overflow RCE
* Plex Media Server: flaws compromised internet-facing servers used for cryptominers and proxy tools.
* Arista VeloCloud Orchestrator zero-day: Actively exploited authenticated SQL injection enabling privilege escalation.
* Node.js Brotli decoder RCE
* NGINX critical heap/use-after-free issues
* Railway breach: Attacker accessed systems storing customer environment variables and, for some, obtained decrypted contents (API keys, database credentials, private registry logins, etc.)
* Zeabur breach: ~321,810 accounts and over 3.2 million environment-variable records exposed. Company announced it is shutting down.
* LiteLLM supply-chain compromise: Malicious version 1.107.0 pushed to PyPI and Docker Hub containing a credential stealer and remote-access/backdoor capability.
* California public school data theft: 5.7M+ student records leaked, including names, dates of birth, addresses, demographics, and disability status.
* Capcom breach: Unauthorized access to ~11.77 million CAPCOM ID records
* Quest Diagnostics: Unauthorized access to Quanum Lab Services Manager system used by some clients; potential access to certain patient records.
* State Bank of India breach: customer records appearing on dark web
Vortex | BIP448 retweeted
Everyone is talking about agent swarms, usually in the context of bad stuff like hacking. But if you ever wanted to watch an agent swarm in action (this time working for good), the discussion board of the Integer Multiplication open research repo is really cool to watch
Vortex | BIP448 retweeted
“COBOL is still deeply load-bearing in banking, especially at the core: account ledgers, overnight batch processing, and card/ATM authorization. The widely cited estimates are that roughly 43% of banking systems and 95% of ATM swipes run on COBOL code, and that around 80% of in-person banking transactions pass through it.”


































