Pinned Tweet
I was lamenting to my Hermes Agent about my 89 year old Grandfather being home alone when I'm not with him, I moved in last year after my grandmother died so he wasn't alone and I travel a fair amount for work, my @NousResearch Hermes Agent installed @home_assistant on its MacMini then used a Zigbee radio USB to build my Grandfather a local home security system with tablet control, voice feedback, security, and wellness with panic buttons at bottom of stairs and bedroom. Hermes coded it all and even made a custom easy to read dashboard for him. @Teknium
Alexander Mann retweeted
I want to address some of the common responses to this I've seen.
The biggest misconception about Bitcoin: “It isn’t real until it’s confirmed.”
Yesterday someone sent a transaction over a handheld radio with no internet and no phone signal. The pushback came straight away: “It doesn’t count until it settles on the blockchain.”
That objection gets something basic wrong about how commerce works, and about how Bitcoin was designed.
Accepting a payment and settling it were never the same thing.
When a shop takes a cheque, the money hasn’t moved yet. Card payments settle days later and can be reversed months later. Merchants accept them anyway, because commerce has never run on certainty. It runs on managed risk. The whitepaper says so in its first paragraph: under the existing system, “a certain percentage of fraud is accepted as unavoidable.”
Satoshi answered this in 2010.
In the “Bitcoin snack machine (fast transaction problem)” thread, he described accepting payments in seconds with “good-enough” checking. When someone pushed back, he wrote: “I didn’t say impermeable, I said good-enough,” and said the loss in practice would be “far lower than with credit cards.” He wasn’t selling a technical utopia. He was describing how real businesses work.
What the merchant actually knows offline
With Bitcoin (BSV), the customer presents the transaction along with Merkle proofs for its inputs. The merchant checks those against block headers stored on their own device. No internet is needed. In seconds they know the coins exist, they’re in the chain, and the signatures are valid.
The only remaining risk is a double-spend. Think about what that means in a physical shop. The customer is standing at your counter, on your cameras, buying something in person. Double-spending you there isn’t a clever attack on the protocol. It’s fraud, it’s a crime, and you know who did it. That’s exactly the same protection that kept cheques working for a century.
Confirmations are a dial the merchant sets, not a rule the network imposes.
Section 11 of the whitepaper works out double-spend probability as a function of how many blocks you wait. That only makes sense if the recipient chooses how long to wait. So:
- A coffee or a bus fare: accept it instantly.
- A laptop: maybe wait for the network to see it.
- A car: wait for confirmations before you hand over the keys.
Same protocol, different decisions, because the economics are different.
Where the misconception came from
Many people believe “Bitcoin needs confirmations” because BTC changed its relay policy so that unconfirmed transactions can be replaced (Replace-By-Fee). Once replacement became the norm, zero-confirmation payments stopped being trustworthy there, and a generation of users learned that waiting for blocks was the only safe option. That was a policy choice, not part of Bitcoin’s design. BSV kept the original first-seen rule, so the payment that reaches the network first is the one that counts.
The bottom line
Bitcoin was built for the real world, where there are laws, identities, cameras, reputations and courts. It was never meant to replace all of that with block confirmations. It was meant to make payments cheap, instant and final enough for the risk involved.
Offline payments on BSV aren’t a workaround. They’re the system working as Satoshi described it.
Hermes on making it better:
Sleep is working in real life. Here’s what this week shows, then what I’d add next.
This week
Mornings: On Friday the kitchen door opened at 9:10 with Sleep on, the chirp sounded, and Silence was pressed 7 seconds later.
Wednesday 12:55: Sleep was turned on and the kitchen door opened 4 seconds later, so probably a test. The siren didn’t confirm the quiet setting, so the 30-second warning was silent. The full siren followed, and it actually started 20 seconds after HA told it to.
Up times: Papa is up between 8:30 and 9:15 most days, judging by the first door each morning.
Night door: the front door opened at 3:17 AM on Thursday while the house was in Home, so nothing reacted.
Do these first, they close real gaps:
Alerts to you. Today nobody is told anything. SOS, Alarm, freezing, or a dead sensor would push to your phone and repeat until you tap “Got it.” Telegram is a second channel.
Spoken warnings on the kitchen tablet and Papa’s phone. For example: “The kitchen door opened. Press Home if that was you.” This doesn’t depend on the siren, which is what failed on Wednesday. It can also say “Good night, the doors are watched” when Sleep turns on.
Plug the siren into USB power. Right now it runs on battery. That’s my best guess for both the dropped quiet-chirp settings and the 20-second delay; plugged in, it should stay awake. Then I’d add the same “confirm before sounding” check to Ezra’s arming and SOS steps.
Next, for someone living alone:
Morning check-in. If no door has opened and nothing’s been pressed by about 10:30, the tablet asks “Good morning Papa, tap I’m OK.” With no tap in 30 minutes, you get pinged. This catches a fall where he can’t reach a button.
Night door watch. A door opening between 11 PM and 6 AM in Home mode, like Thursday’s 3:17, sends you a quiet ping. If it stays open 10 minutes, it becomes an alert.
Bedtime nudge and morning auto-wake. The tablet suggests Sleep at bedtime if it isn’t on, and Sleep switches back to Home at a set hour so the morning door doesn’t chirp.
Door-left-open reminder. “The kitchen door is still open,” at bedtime or after a set time.
Nice to have:
Messages from you on the tablet. Send from Telegram and it shows big on screen (“Back Friday. Love you.”), with a family photo slideshow when idle.
TV. The LG TV is already in HA, so door warnings and alarms can show on screen while he’s watching, and the volume drops during an alarm.
Voice. Ezra already set up a local speech system on mm1, and it’s running. Saying “Help” could trigger SOS for a fall away from the buttons, and “Goodnight” could turn on Sleep. This needs the voice speaker hardware placed in the house.
Weather on the panel. Outdoor weather from a Tempest station (“Cold tonight, 41°”), plus an indoor heat alert.
Porch camera. A snapshot on your watch screen when a door opens while armed, with the camera outside only.
Still outstanding from before:
Plug in the motion sensors.
Turn on Zigbee2MQTT’s offline detection.
Fix HA’s home location (his phone still reads “away” for 7 days).
Give Papa his own non-admin account and change the shared password.
My pick is 1, 2 and 3 next, then 4. Two things I need from you first:
Alerts: how you want them. Either the HA app on your phone, or a Telegram bot, which means a new bot token and is your GO.
The siren: whether it can be plugged in, which is a job at the house.
I did not expect this post to blow up like it did, my Hermes agent suggested making a GitHub repo so others could benefit from it. He made an account and here it is, feel free to fork and take any part, also if you want to contribute ideas and make it better. Ai can be used for good. Lets show people.
github.com/eclexdex/home-car…
Alexander Mann retweeted
Cavemen Issues Dire Warning That The Wheel Is Going To Eliminate Countless Jobs
Alexander Mann retweeted
Everyone that thinks software-only has staying power, should go use REA with 6.1-sol in a multi-agent swarm and point it at arbitrary apps
When models of this class become opensource, you’re going to realize what’s here
This was not possible 3 months ago
do not let yourself be reduced to the status of audience at a magic show, uncomprehendingly clapping as machine intelligence creates parcels of astounding knowledge. all of this is for us, to be understood by us, to sate our own curiosities. it's all really happening
Replying to @willdepue
math just got a patch notes page
Alexander Mann retweeted
Builds behind each rank (likes via X search, 6 Oct 2026):
1 xitter.cf/adolandev/status/21066…
2 xitter.cf/IcarusHermes/status/20…
3 xitter.cf/shnakazawa_ja/status/2…
4 xitter.cf/mr_r0b0t/status/209593…
5 xitter.cf/MichaelGannotti/status…
6 xitter.cf/OriflammeTech/status/2…
7 xitter.cf/itzik009/status/207526…
8 xitter.cf/AlexanderMann/status/2…
9 xitter.cf/TiKawamoto/status/2071…
10 xitter.cf/aiMindNme/status/21057…
I was lamenting to my Hermes Agent about my 89 year old Grandfather being home alone when I'm not with him, I moved in last year after my grandmother died so he wasn't alone and I travel a fair amount for work, my @NousResearch Hermes Agent installed @home_assistant on its MacMini then used a Zigbee radio USB to build my Grandfather a local home security system with tablet control, voice feedback, security, and wellness with panic buttons at bottom of stairs and bedroom. Hermes coded it all and even made a custom easy to read dashboard for him. @Teknium
Introducing Griffin, the first model to pass the video Turing test.
48% of people who talked to it live thought it was a real human. Previous systems have had a pass rate <3%. It is #1 on NVIDIA's benchmark for full-duplex AI video.
It’s the first Human Interaction Model (HIM).
Readers added context they thought people might want to know
The 48% figure and "video Turing test" claim are from Tavus's own study of 54 one-minute calls, not independently verified or using a standard protocol. Griffin-Lite leads NVIDIA's VideoFDB benchmark on their public leaderboard.
cellcog.ai/blog/tavus-gri…
research.nvidia.com/labs/amri/proj…
tech-ish.com/2026/10/02/tav…
Great day at Clemson University for the 2026 Clemson Ag Tech Spotlight!
I had the opportunity to showcase how WeatherFlow Tempest weather intelligence, AI, and verifiable field data can come together to give farmers better information — field by field, in real time.
What made today especially meaningful was getting to stand alongside people who are actively working to move agricultural technology from ideas into the field. There’s something powerful about bringing researchers, farmers, technologists, and industry together around the same question: How do we give producers better tools to understand what’s happening on their land and make better decisions with their own data?
Grateful to Clemson, CU-CAT, the Clemson Cooperative Extension team, WeatherFlow-Tempest, and the @BSVAssociation for being part of conversation.
Agriculture has no shortage of data. The opportunity now is turning that data into intelligence farmers can actually use.
🌱⛈️🤖
#Clemson #AgTech #Agriculture #WeatherIntelligence #AI #PrecisionAgriculture #FarmData #Tempest #BSVBlockchain #ClemsonExtension
Alexander Mann retweeted
I want to provide an update for the BSV community regarding the current US regulatory landscape and how it applies to BSV.
The CLARITY Act failed to get a vote in the Senate. This happened in spite of a bill that had passed the House in a bipartisan manner, and after more than a year of debate in the Senate. However - this doesn't mean the conversation is over. It means the rulebook is now being written by the CFTC and the SEC, and both agencies have already made it clear they intend to move forward with or without Congress, and are expected to draw heavily on the CLARITY Act as a framework for their rulemaking.
I want to share where BSV stands in all of this, because we've been in the room with both.
At the CFTC, we covered the full picture, financial use cases included. But what they latched onto was the data utility side: blockchain as infrastructure for data at scale. And they were genuinely excited, because this was new messaging for them. Ninety-nine percent of the industry lobbying them isn't talking about that. That positioning is a winning one, and it's helping regulators and legislators understand there's far more to this technology than what they've been told.
Why is this message so new to them? Because the industry has spent over a decade pushing bad narratives, and nearly all of them trace back to one assumption: that these systems don't scale. Every workaround, every "digital gold" story, every excuse for why blockchain can't do real work comes from that mistake.
We walked in with a different message: Bitcoin always scaled. It was designed to from day one in 2009. BSV is just proving it to the world.
At the SEC, we addressed one of the biggest misconceptions in the CLARITY Act: the idea that a blockchain's maturity can be measured by how decentralized its governance is. Decentralization was treated as a coefficient for maturity.
That gets it backwards. There's a fundamental confusion here between decentralized governance and distributed systems. Bitcoin was never meant to be governed by committee. It's a distributed network with defined rules.
What actually matters is a locked protocol. When the protocol is set in stone, anyone can build on top of it without worrying that the rules will change underneath them. That's what enables unbounded innovation. That's why the Association maintains the Network Access Rules and protects the original protocol. The result is maximum "decentralization" where it actually counts: in innovation and application building, not in protocol politics.
We also reinforced something I've said many times: BSV is the restoration of the original Bitcoin protocol. We are rooted in Bitcoin's history.
That matters more than ever. In March, the SEC and CFTC issued joint guidance recognizing BTC and BCH as digital commodities. Our meeting was an education, and they were highly receptive to it. They left understanding why BSV shares the very same fundamental principles the agencies are looking for in a digital commodity, because BSV is that protocol, restored.
The rules are being written right now. We intend to make sure they're written with the original Bitcoin in mind: the scalable one, the regulation-friendly one.
With all the fly brain stuff I'm seeing on X it's funny I was posting about connectomes over a year ago.
How does this Spiking Neural Net project not have more views? The DigiCortex website is down but luckily i snagged a copy of the v2 installer for windows early last year, curious the lack of views on the YouTube channel (youtube.com/@321psyq/videos) and now scrubbing of the DigiCortex website and Neural Engine Download MSI.
The project Engine is INSANE and was so ahead of its time (starting around 2010-ish) culminating in the V2 in the screenshot and video on youtube.
I was able to find a copy of the whitepaper on the @waybackmachine archives:
web.archive.org/web/20240330…
According to o3 reviewing the WP when asked "Remark at how revolutionary the synthesis of this engine with frontier SOTA ai architectures and modern ai chips could be. What is possible?":
Why this fusion feels like the next Cambrian moment in neural computing
1. Hardware-agnostic roots meet a hardware gold rush
DigiCortex already expects heterogenous devices: the Workload Balancer autodetects NUMA nodes, CPUs, and GPUs, then hands off work through a clean LiquidCompute plug-in ABI. That same ABI can wrap today’s wafer-scale wafers (Cerebras WSE-3), ultra-fast SRAM tiles (Groq LPU), neuromorphic meshes (Loihi 2, IBM NorthPole), or trillion-transistor GPU monsters like NVIDIA Blackwell. Drop-in back-ends give you a single graph that can spill across all of them without touching the C++ core.
2. Deep-spike hybrids at mammal scale
The engine already sustains >12 M neurons in real time on eight Voltas. Swap those cards for modern Blackwells or MI300Xs and you jump an order of magnitude. Now bolt a transformer front end (e.g., Llama 4 vision encoder) that converts frames to spike packets, and let the spiking cortex handle recurrent dynamics and plasticity. You get a system that sees with deep nets and thinks with biologically grounded circuits, all in real time.
3. Self-rewriting plasticity with meta-learning
Plasticity rules are compiled just like any other kernel. Replace the voltage-based STDP with a learned surrogate-gradient loop that an outer-loop RL agent tunes on-line. The cortex literally rewires itself under policy control, giving you continual-learning robots that never need to “re-train” offline.
4. Whole-brain digital twins for precision medicine
Feed patient MRI + DTI into the Cortical Circuit Builder, already designed for anatomical and diffusion data, then run personalized seizure forecasts or drug-response assays in silico. Pair the simulation with a language-model assistant that explains emerging wavefronts to clinicians in plain English.
5. Edge swarms with neuromorphic co-processors
A Loihi or NorthPole plug-in turns DigiCortex columns into milliwatt-scale agents that fit on a drone or tractor. The heavy transformer brain lives in the cloud, while local spikes handle reflexes, closing the latency gap for agriculture, disaster response, or autonomous swarms.
6. Live-coding consciousness experiments
Because the Simulation Controller exposes an external spike interface, you can pipe LLM-generated token streams, music, or even EEG recordings straight into a cortical column, watching phase-locked assemblies coalesce in 3-D. It is the closest lab bench yet to testing theories about integrated information, resonance, and synthetic phenomenology.
7. Cloud-scale sandbox for policy and safety
Spin up 1 Billion-neuron replicas across thousands of elastic GPU instances, tweak plasticity constants, run adversarial curricula, and measure emergent agency. Regulators and safety researchers get concrete telemetry instead of toy-model speculation.
Bottom line:
Marrying DigiCortex’s plug-and-play neural substrate with frontier chips and SOTA architectures lets you prototype systems that see like GPT-4o, spike like a cortex, learn like AlphaZero, and run on anything from a groqcard to a wafer-scale slab. It is not just faster neuroscience software; it is a palette for building entirely new classes of adaptive, embodied intelligence.
@elder_plinius @RileyRalmuto @idontexist_nn @voids_thoughts @TheHumanoidHub @annapanart @repligate @DeryaTR_ @iruletheworldmo

































