This faketoshi cryptocult leader is back to launch an altcoin. He's picked up some tricks from Craig Wright, such as the three-piece suit and getting angry when asked to sign.
Will you allow him to be your arch angel?
🇳🇴 Meet Bobafet from Norway
Bobafet:
• Mines bitcoin sovereignly in the Norwegian mountains.
• Dries his shoes with a miner running Braiins OS.
• Dries firewood from his own forest with the same heat.
• Helped build Braiins Manager and uses it to run his other farms remotely.
Bobafet is cool. Be like Bobafet.
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
Today, ICANN just published the 2026 new gTLD applications! Wiz & Associates filed a community priority application for the .bitcoin TLD, on behalf of the people and organizations that run, build, and provide the infrastructure, software, and services of the Bitcoin network. 🧵
A strong VPN option from privacy-principled and Bitcoin-aligned people, now available on Linux. I helped test this on Arch btw. 😊
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
Here's what you're missing. Freezing their coinbase rewards isnt confiscation, it's fixing an inflation bug.
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
It looks like ~4,000 BTC just moved from the Liquid Network bridge all at once with an OP Return saying, "we are whitehats. contact us on chain".
TXID:
c103de95817b43f2df635ec6f35ff126ca26a7c6d20570c4b01866b2b3e69a19
The UK arm of Teranode, Calvin Ayre's premier BSV company supposedly developing revolutionary next-generation node software, has changed its name to Neobridge Solutions Limited.
Perhaps there just isn't money in BSV.
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
Sparrow v2.5.4 has been released, delivering the results of several extensive security reviews.
Thank you to all the contributors and security researchers who provided input on this release.
Changelog: github.com/sparrowwallet/spa…
Download: sparrowwallet.com/download
Sparrow v2.5.0 released with:
Silent Payments (SP) wallets
SP-capable Frigate public server @2140_dev
bitview.space fee rates source
sparrowwallet.com/download
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
Today, we're publishing BIP SHRINCS, the first concrete proposal for a post-quantum signature scheme designed specifically for Bitcoin.
The BIP draft turns what began as a rough idea into exact algorithms with an executable reference implementation.
This is an important milestone: the discussion can now focus on analyzing, criticizing, and improving a concrete proposal.
The BIP makes choices ranging from major design questions, such as whether to support flexible XMSS and how to balance signature size against verification time, to the many smaller decisions involved in saving a byte here or there.
All of these choices are up for debate.
Big thanks to Mike Casey, @conduition, @Ethan_Heilman, @kudinov_mikhail, @olkurbatov, Boris Nagaev, and @remix7531 for their contributions to the BIP.
A lot more work lies ahead:
- The draft BIP specifies only the cryptography. Using SHRINCS in Bitcoin Script will require a separate BIP.
- We are working on a security proof for the exact construction and parameters.
- Wallet integration and user experience, for example around backups and recovery after state loss, are still at an early stage. The design space remains wide open.
SHRINCS is not intended to be Bitcoin's "final" signature scheme, and it is not optimal along every axis.
I do think it is a very good trade-off among the options we have now.
bitcoin-dev post:
groups.google.com/g/bitcoind…
Draft BIP:
github.com/SHRINCS/shrincs-b…
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
Looks like a severe Core Lightning (CLN) issue was discovered.
It sounds like you should consider restarting your CLN node with `--offline` and be on the lookout for the point release coming in the next few days. (Messages from CLN discord via stacker.news/items/1555439).
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
New @mempool feature: BIP54 Compatible Coinbase detection
BIP-54 aka. Consensus Cleanup specifies (among three other rules) that coinbase transactions must set nLockTime = height - 1 and nSequence ≠ 0xffffffff.
Ahead of activation, the BIP encourages mining pools to craft coinbase transactions that are forward-compatible with this rule.
Whitepool was the first to adopt, with block 937,404 in February 2026; a handful of other pools and unknown miners have followed since. Now you can easily see when a block is compatible.
For now it only shows if a block is compatible, signaling incompatibility will be added when support is more widespread.
Implemented by @rodribp21 🫡
mempool.space/block/00000000…
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
“Asked twice by email as to whether any of the preprints being submitted were produced using generative AI, Wright did not respond.” ft.com/content/fe3a8ce6-e348…
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
Will interview @kurtwuckertjr on Friday
7 PM CET / 1 PM EST
This is part of my research project to document Bitcoin forks
But my first question will be: why did you dox my friend Hodlonaut?
Then we can talk about BSV’s upgrades & what makes it different
See you on Friday!
Haakon Nilsen aka Norbert ⚡️ Activate CTV + CSFS retweeted
When you download Bitcoin Core today, the binary doesn't contain everything your node runs. It still loads the C library (glibc and friends) from your operating system which means there are version requirements, behavior that can vary from machine to machine, and code that your node executes that isn’t covered by reproducible builds.
New static test builds pack it all into one deterministic Bitcoin Core binary.
@fanquake is asking node runners to test out these new static binaries and report results.
The more you learn. #Faketoshi
Replying to @sergeynazarovx
Yeah what the fuck is prof. dr. dr.?
I had no idea you could be a triple doctor.
Critical vulnerability in the bip322 Rust crate: BIP-322 proofs for P2WPKH and
P2SH-P2WPKH addresses could be forged with any attacker key. Full
address-ownership bypass. Fixed in 0.0.11, affected versions yanked. If you
verify Bitcoin address ownership, please upgrade now.
This is ridiculous, but you have to assume it will happen.
Ordering a hardware wallet to your home address is irresponsible at this point. Get a P.O. box – Trezor will deliver to them. Use one-time email addresses (I like SimpleLogin dot io). Get a burner phone number for receiving SMS for the order.
Give them as little as possible of your real information, because it will leak.
We have some difficult news to share. Unfortunately, one of our shipping providers has experienced a data breach that exposed sensitive order data. This affects new customers in the US, UK, Sweden, Colombia, Brazil, Italy, and Portugal who received an order within the 90 days prior to August 8th, 2026.
The data exposed:
- Full names
- Shipping addresses
- Phone numbers
- Email addresses
The incident affects 11,742 customers with full exposure (name, email, phone number, shipping address) and 1,947 customers with partial exposure (name, city, email). The breach is limited due to Trezor’s strict 90-day data storage policy (we were also able to negotiate the same terms with fulfillment partners, who follow the same policy).
All affected customers have been contacted separately by email.
Our systems and devices remain secure, but affected customers could experience an increase in phishing attempts.
NEVER enter your wallet backup on a website or share it with anyone, and only check for updates on official Trezor channels.
We are deeply sorry to the community and those affected.
We are investigating this situation and will post updates on our blog:
trezor.io/blog/news/recent-c…





































