Developers just figured out a way to hide who sent bitcoin, who received it, and how much moved, without changing Bitcoin itself.
This new proposed idea is not a fork around the protocol or new cryptocurrency. This is how Bitcoin was designed, a base layer people can innovate on without asking permission.
On Thursday, researcher Misha Komarov and colleagues published Shielded Bitcoin, a Zcash-style shielded pool for Bitcoin’s base layer.
Encrypted notes and zero-knowledge proofs ride along in ordinary Bitcoin transactions. Separate software checks that no coins are created from nothing and none are spent twice.
There is no company running the pool, no sidechain, and no soft fork. Funds go in and out through cryptographic vaults Komarov has been building, called PIPEs, so no federation has to hold the bitcoin.
Miners do not enforce the privacy rules. Invalid shielded data can still land in a block, indexers simply ignore it.
The trade is: Bitcoin stays conservative, and the experiment lives on top of it. If it works, private transfers arrive the way most of Bitcoin’s best ideas have, not by rewriting the constitution, but by building on the settlement layer everyone already trusts.
Quick Superlogical demo to end the week. This demo is just of the basic functionality, but I want to highlight just how FAST it is. There's a WHOLE lot more functionality already present and coming but I wanted to keep the demo short. But seriously, check out that speed.
I'm showing the macOS app here and I get asked a lot so let me just say up front: its not macOS only. We're still figuring out exactly what platforms will be stable enough for the initial public release, but we're working on others. In particular, the web interface is very functional but I'll demo that another time (or someone else will).
This is also all showing off the architecture I previously talked about for terminal multiplexing which is significantly different from other mainstream multiplexers: this is all a custom binary protocol where the server is maintaining N replica distributed terminal state machines. It works!
Tons of hard work going into this by the team @almonk@dizzyup@pearkes. Hope we can bring you something you can use soon. ❤️ Happy to answer questions in the replies.
Waaat?!? we haven't even started seriously deploying IPv6 to a meaningful adoption and we already got IPv8 now?!? crrrrrazy! (interesting though, give it a read) https://t.co/6W4gTuHDdu
Someone just lost $50.4M on a DeFi swap.
The platform warned them.
They clicked confirm anyway.
The transaction was marked ✅ SUCCESS.
This is the most important DeFi story of 2026. Here's everything that happened. 🧵
@claudeai is down, so I had this revolutionary idea:
engineers ACTUALLY write code themselves 🤯🤯🤯
I call it: "brain coding"
Of course the resulting code won't be as good initially... but over time, with training and memory, it'll be amazing.
#braincoding FTW
> return flight to nyc gets canceled by snowstorm
> call united
> immediately connected with customer service (rare)
> voice is uncanny, def AI but they gave it a human-like accent
> takes ~20 min to get rebooked (pretty good imo)
> I ask if it's AI
> "haha no ma'am but I get that a lot"
> I ask it to calculate 228*6647
> it runs the calculation
> ggs
https://t.co/kxsTlD9jhB
Soon (~4 months) we'll say "bye forever" to #nginx#kubernetes ingress.. this is BAD news and I'm sure will ruin the upcoming weekends/months of many #devops .. sorry to be the bearer of such bad news 😬 enjoy the migration! 🤦♂️ ☠️
1/6 🚨 SECURITY ALERT: LinkedIn Fake Recruiter Malware Campaign 🚨
Got hit (again) with a sophisticated malware delivery attempt via LinkedIn today. Sharing so nobody becomes exhibit B.
The (usual) Attack Flow
1. Initial Contact: Fake recruiter "Anzhelika Anpolska" (https://t.co/cdwEP19JWK) - profile looks legit enough to pass a 5-second glance
2. Social Engineering: Standard recruitment playbook with artificial urgency (because top talent is definitely recruited via cold LinkedIn DMs asking you to run
random code)
3. Malicious Repository: https://t.co/MhxlL38Eha
4. The Trap: "Please review this code" - except it's heavily obfuscated JavaScript that no legitimate company would ever send
The Payload
Found the malicious code in ps.config.js - and by "found" I mean "immediately recognized because legitimate code doesn't look like this."
Technical Analysis:
1/6 🚨 SECURITY ALERT: LinkedIn Fake Recruiter Malware Campaign 🚨
Got hit (again) with a sophisticated malware delivery attempt via LinkedIn today. Sharing so nobody becomes exhibit B.
The (usual) Attack Flow
1. Initial Contact: Fake recruiter "Anzhelika Anpolska" (https://t.co/cdwEP19JWK) - profile looks legit enough to pass a 5-second glance
2. Social Engineering: Standard recruitment playbook with artificial urgency (because top talent is definitely recruited via cold LinkedIn DMs asking you to run
random code)
3. Malicious Repository: https://t.co/MhxlL38Eha
4. The Trap: "Please review this code" - except it's heavily obfuscated JavaScript that no legitimate company would ever send
The Payload
Found the malicious code in ps.config.js - and by "found" I mean "immediately recognized because legitimate code doesn't look like this."
Technical Analysis:
🔔 Set your reminders - Tomorrow 15:00 UTC
The $ADNS presale will be in $SOL ONLY so make sure you're ready
0.000014 $SOL for whitelist
0.000017 $SOL for public