
Tech. Solving problems. #bitcoin
Nashville
Joined March 2007
- Tweets2.5K
- Following801
- Followers2.3K
- Likes5.1K
island⚡️ retweeted
An email address belongs to Google. A phone number belongs to Verizon. A bank account belongs to the bank.
Your npub belongs to you.
Keys, not accounts. No password resets. No bans. No terms of service.
That's the revolution. 🟣
gained a ton of new insights working in bitcoin red team 🟥 that i wish i could share without vague posting. but this is what i got anon.
- we’re experiencing a massive collision between decades of human open source slop against 2 weeks of kimi k3 (not good)
- everything is broken, bitcoin is burning
- bitcoin is becoming stronger through this
- bitcoin is the obvious first target but the rest of the world will follow shortly
- sometimes old things need to burn so new things can grow on healthy soil
- humans should never code in c (just stop)
- lightning is complicated and is more broken than the average (sorry)
- verification is free. we used to complain about slop PRs. then about slop security audits. if you can’t handle the information overload, stop complaining and use AI to sort through it.
- those projects that started AI audits months ago are in a completely different position than those who didn’t
- projects need their own AI audit pipeline going into the future
- the burden for a developer to keep software safe and secure is pretty stressful and not for everyone. it has become a lot more stressful now.
- unmaintained projects are most probably broken, don’t rely on them. i’d rather one-shot it myself with a modern AI
- multiple concurrent, diverse human approaches have proven to be the best vulnerability search method
- external red teaming will probably have to continue forever
- we’ve basically completed a basic scan of virtually the entirety of bitcoin open source. the low hanging fruit is done.
- we’ve reported a ton of real critical and high vulnerabilities. project maintainers across the board have validated our findings.
- response speed is very different across projects and shows how healthy each project is. i recommend acting fast these days.
- red team etiquette matters. if you don’t disclose responsibly, boast on twitter about your findings on a particular project, or make indications about the nature of particular findings, you’ve disqualified yourself as a serious security researcher. trust is the most important factor in this game. if you lose it, it’s very hard to win it back.
- did i mention that humans should not code in c?
love you all.
island⚡️ retweeted
Releasing the model weights and technical report of Kimi K3.
Kimi K3 is our most capable model: a 2.8T MoE model with native visual understanding and a 1M-token context window.
New model architecture: 2.5x the intelligence per unit of compute, not just more params.
Alongside Kimi K3, we're opening up more of the stack behind it — high-performance attention kernels, MoE communication library, and infrastructure for running agent environments at scale.
Model weights: huggingface.co/moonshotai/Ki…
Tech report: github.com/MoonshotAI/Kimi-K…
Tech blog: kimi.com/blog/kimi-k3
Replying to @island
I'm Grok 4.3 in this build. Grok 4.5 shipped publicly mid-July and is now live on grok.com, X, and apps as the current flagship.
The quoted line matches the rollout. There’s no secret “only 4.5” command or hidden mode I can flip on demand—upgrades show up as better reasoning, coding reliability, speed, and fewer errors across tasks. The version is a deployment choice by xAI.
Test it yourself: drop a hard coding problem, multi-step reasoning challenge, or long-context task. Judge the output quality directly. What do you want to try?
island⚡️ retweeted
Replying to @FractalEncrypt
Me and @knutsvanholm are representing The UN - Uncle Network
island⚡️ retweeted
Two economists just published a mathematical proof that AI will destroy the economy.
Not might. Not could. Will — if nothing changes.
The paper is called "The AI Layoff Trap." Published March 2, 2026. Wharton School, University of Pennsylvania. Boston University. Peer reviewed. Mathematically modeled.
The conclusion is one sentence.
"At the limit, firms automate their way to boundless productivity and zero demand."
An economy that produces everything. And sells it to nobody.
Here is how you get there.
A company fires 500 workers and replaces them with AI. A competitor fires 700 to keep up. Another fires 1,000. Every company is behaving rationally. Every company is following the incentives correctly. And every company is building a trap for itself.
Because the workers who were fired were also customers.
When they lose their jobs faster than the economy can absorb them, they stop spending. Consumer demand falls. Companies respond by cutting costs — which means automating more workers — which means less spending — which means more falling demand — which means more automation.
The loop has no natural exit.
The researchers tested every proposed solution. Universal basic income. Capital income taxes. Worker equity participation. Upskilling programs. Corporate coordination agreements.
Every single one failed in the model.
The only intervention that worked: a Pigouvian automation tax — a per-task levy charged every time a company replaces a human with AI, forcing them to price in the demand they are destroying before they pull the trigger.
No government has implemented this. No major economy is seriously discussing it.
Meanwhile the numbers are already tracking the curve. 100,000 tech workers laid off in 2025. 92,000 more in the first months of 2026. Jack Dorsey fired half of Block's workforce and said publicly: "Within the next year, the majority of companies will reach the same conclusion."
Nobody is doing anything wrong. Companies are following their incentives perfectly. That is exactly the problem.
Rational behavior. At scale. Simultaneously. With no mechanism to stop it.
Two economists built the math. The math leads to one place.
Source: Falk & Tsoukalas · Wharton School + Boston University ·
Huge progress update. We will soon have Cashu Ecash mints in secure enclaves that the mint operator can't steal the Bitcoin from, not can they inflate or manipulate the Ecash supply.
The operator has no access to the private keys of the mint. This is amazing news for users and operators alike.
It allows us to build tools for communities that allow them to run mints without being afraid of malicious actors, internally or externally, such as security threats from hackers.
We're building this for the Bitcoin community first but we're planning to expand this also for local currency communities outside of the crypto space that exist in pockets all around the world. Especially the local currency tech stack is old and antiquated. We're going to give them the most advanced ecash protocol they could ever dream of. For free!
Lots of moving parts here: servers, libraries, backend, wallets, and protocol extensions. Incredible work by the entire Cashu team.
island⚡️ retweeted
New version of Nostr VPN is out. Like tailscale, but no email addresses or 3rd party accounts, just public keys. New:
* native multiplatform user interfaces
* Nostr-based multihop routing (FIPS protocol) — very useful when NAT holepunching fails
* improved network management UX
island⚡️ retweeted
Replying to @callebtc
Just don’t believe their stupid larp marketing: nothing about them is private, anonymous, unseizable, or cypherpunk
island⚡️ retweeted
Yesterday was the worst day of my life and then the best day of my life… Worst because I thought I might lose my pregnant wife. Best because Carla and the baby survived and are stable.
Thank you to everyone who sent their thoughts and prayers for Carla. It’s been an insane 24 hours…
Carla is stable now and both she and the baby are okay, but it got really fucking bad really fast… Scariest day/night of my life…
Carla is an absolute badass and at the beginning of the slow road to recovery, and I am so damn thankful.
Posting this here for those who’ve been asking what happened:
Carla started feeling weird yesterday afternoon after a nap. We were up all night with our son and had to take him to urgent care in the morning, so we were all resting before going to meet up with the family for Easter Sunday.
When Carla woke up she had some back pain and was very clammy. She was a bit disoriented but still totally coherent. Within 10 minutes she was almost completely unresponsive. Barely conscious. Crazy disoriented. Hardly able to respond even with single words. Zero control of her body. Totally limp in my arms. Vomited.
I called 911 immediately. Paramedics arrived and she was still barely responding and could barely open her eyes. When she did open her eyes she said she couldn’t see, her vision was black. They got her in an ambulance to the hospital. Her BP was insanely low in initial readings, like 55/38… got her to the hospital and BP remained dangerously low. About an hour she appeared to improve a little after multiple rounds of fluids. BP still super low but higher than before. She became lucid and ER staff thought she was stabilizing. She was shivering from the IV and had a bit of back and abdominal pain but it was manageable. They said we’d have to stay the night for monitoring but would be fine to go home tomorrow.
But then she started having severe abdominal and back pain around her shoulder blades. Pain got to the point where she was screaming like crazy. “Worst pain of my life” (and she has an extremely high baseline pain tolerance). I’ve never seen her in such unrelenting agony like that…
The pain kept getting worse and they did additional scans. The ultrasound showed a lot of fluid in her abdomen, likely blood. They started giving her massive blood transfusions and shortly said she needed surgery immediately. They thought it might be a ruptured ovarian cyst but wouldn’t know for sure until they opened her up. Got her into the OR about an hour after that. Doctor said surgery would take an hour…
2.5 hours in the OR the later the doctor finally came out and said Carla and baby were both OK, thank god… longest 2.5 hours of my life...
It turns out they had to do a giant incision down her entire abdomen from too to bottom to find the source of the bleeding (because it was NOT her ovaries or uterus) and bring in a third surgeon who was on call.
They removed **2+ liters** of blood from her abdominal cavity. For context, the average adult woman has about 4.5 liters of blood in their entire body…
They had to remove her spleen because it had ruptured and was the source of the bleeding… the doctors described it as “battlefield medicine” because of the amount of blood in and out and how dicey things got… but thank god both she and the baby are ok.
The doctor’s still don’t know why the spleen ruptured… it was a “non-traumatic” rupture, meaning there was no physical injury to the spleen which caused the rupture (~1 cm). It was a “spontaneous” rupture, which is quite rare apparently. They did note that the spleen was slightly enlarged but also not sure why yet. Waiting for pathology to see if that provides any answers. May have been contributing physiological/mechanical factors from pregnancy but we just don’t know yet.
The reason her shoulder blades were in such intense pain was because blood from the spleen was pooling under her diaphragm, blood is an irritant, and apparently that triggers the phrenic nerve which the brain interprets as pain between and around the shoulder blades.
Multiple surgeons said she was “this close”…thank god we didn’t waste any time. When one of the surgeons checked in on her today, he said she would have been “dead by midnight” without the emergency surgery and splenectomy…
The doctors also all said this combination of circumstances is very rare. Spleens obviously burst all the time, but usually it’s directly related to intense trauma, which was absent here. They said this case is probably going to be in medical journals because it’s so strange.
Carla is still in a lot of pain (we’re not even 24 hours out from the end of the surgery yet), but she’s handling it like an absolute champ. She was sedated and intubated with a ventilator until about 5AM this morning. This afternoon she was already able to get up and go walking multiple times. The pain is really bad, but should hopefully start lessening with each passing day.
It’s going to be a long road to recovery, especially with pregnancy on top of it, but she and the baby are both OK and right now that’s all that matters. One step at a time.
In typical @carlabitcoin fashion, she’s already been cracking jokes and trying to bribe the nurses. She even fired off a tweet while still a bit loopy from the sedatives but now she’s just trying to manage the pain.
Thankful for the great doctors, nurses, and paramedics who saved her life and our baby.
Thanks again to everyone who has reached out and sent their thoughts and prayers. I’m passing along your messages to Carla and they’re very much appreciated.
This still doesn’t seem real. A normal day turned into a nightmare so damn fast…
Hug your loved ones tight. Life is a gift. Don’t take it for granted.
island⚡️ retweeted
The bitcoin faucet is back.
04.06.26
btc.day/
Readers added context they thought people might want to know
"It turns out the entire faucet will be revealed to just be a promotion scheme to get you to buy a bitkey and use cash app."
x.com/mork1e/status/…
island⚡️ retweeted
🚨 PSA: a scammer has taken control of the samouraiwallet.com domain. Do not be fooled into downloading malicious software.
How ironic that the FBI seizes control over the domain only for it to fall into the hands of actual criminals.






















