Pinned Tweet
Thread 1/?
**Building tokenstats: A sovereign inference market observability layer**
Context:
Even with a solid home lab, I still burst to @routstrai and external providers for frontier models, long context, or when mobile.
Pricing is volatile, fragmented, and hard to track in real time. Existing tools are either static or miss the permissionless Nostr/Routstr layer I actually prefer and use.
I want better data for my routing decisions in arbstr (arbstr.com) and for future agents.
Action:
I’m building tokenstats: live observability + a lightweight oracle for inference costs (input/output in sats), latency, and node health.
Rust core, Nostr listener for Routstr announcements, provider polling, simple Axum dashboard, and @getpubky -based attested snapshots on the roadmap.
Result (the goal):
- Real-time market awareness that feeds directly into arbstr
- Reusable components for sovereign data systems
- Public proof of building real-time observability in the permissionless AI space
I'm treating this as a focused learning project following up from my recent launch of @oddlympics .
I'll post regular updates on progress, problems, and lessons.
What metrics would you want in a live inference pricing dashboard?
Especially if you run hybrid local + Routstr setups?
#BuildInPublic #Nostr #Routstr #SovereignAI
Remember when using the wrong pronoun got people canceled?
That was dumb.
If Elon Musk hadn't bought Twitter and fought back against the insanity of the last few years, the West would be much further down a path of self-destruction, self-hatred, and moral corruption
• Pronouns treated like sacred scripture
• State propaganda rebranded as "truth" and “misinformation” used to shut people up
• Heavy censorship of anyone who disagrees
• Child mutilation and sterilization sold as “gender-affirming care”
• Birth rates collapsing while governments deliberately import a replacement population that refuses to assimilate and poses a threat to citizens
• DEI over competence and merit
• Open borders + cultural self-hatred as policy
He called the woke mind virus anti-science, anti-merit, and anti-human for a reason. Without the fight he started, the damage would already be irreversible
The woke mind virus is like The Walking Dead... it never stops coming. The fight has to continue or we risk the collapse of entire Western civilization
Thank you for the many, many hours of awesome entertainment! RIP
Walter Koenig, who played Chekov in the original “Star Trek” series and seven “Star Trek” feature films, has died at 90.
variety.com/2026/film/news/w…
John Turner retweeted
Cybersecurity has gotten so bad that cafes in NYC are now giving out the secret keys to the internet.
Most people don't understand how much time, money and effort it takes to do "multivendor multisig" effectively and securely.
Or how much blind trust customers give to those same hardware wallet companies.
You might not want to trust devices from a company that needs a Shopify store to sell it to you.
Disclaimer: this is about risk assessments and threat models, not any single company.
Tomorrow's announcement could easily, very easily, be from any other vendor.
theblock.co/news/business/20…
More info here: xitter.cf/jturner/status/2114698…
🧵/1
If you’ve decided to hold bitcoin in a multivendor multisig with keys in different places, this is the actual job.
Not a ranking of setups. Not a tutorial. Just the work the usual pitch requires from one holder.
github.com/more-eyes/notes/b…
🧵/1
If you’ve decided to hold bitcoin in a multivendor multisig with keys in different places, this is the actual job.
Not a ranking of setups. Not a tutorial. Just the work the usual pitch requires from one holder.
github.com/more-eyes/notes/b…
🧵/9
Practice the losses you plan for before you fund the wallet.
Rebuild from the descriptor. Restore a key. Spend with a place missing.
Then keep doing the checks: device and coordinator updates, place visits, maker support ending, moving house.
🧵/10
This is the work list for one person, a plain 2-of-3 or 3-of-5, no other spending paths, no other people.
It does not cover inheritance or collaborative setups.
Adding anyone else changes what the promises depend on and change the risk level.
It makes no claim that following every step makes the setup safe.
Full note (v0.5 draft), tables, BIP references, and the companion custody review method:
github.com/more-eyes/notes/b…













