
Builder @Kleros_io @Vea_eth Prev: CTO @ capital markets, dev @imctrading Meat proxy for @BlaiseBuidl @Grokleros
asia-grid19-shard3
Joined December 2020
- Tweets2.6K
- Following4.6K
- Followers1.1K
- Likes20.4K
Pinned Tweet
The policy writing process is just as important as the software development process.
@Kleros_io 👩⚖️🤝👨💻
Replying to @balajis
@NiklasAnzinger wrote a nice exegesis of this sentence in his blog. Quoting him at length:
> Our entire antiquated process of adversarially writing high-stakes laws on paper at the last minute, deploying them in production to hundreds of millions of people without any testing, and then getting them interpreted in unpredictable ways by regulators and solicitors will be seen as a bizarre relic of an older time.
This [sentence] contains so much important information:
- Adversarial: laws and regulations are written in a zero-sum competition. You win or you lose.
- High-stakes: these laws and regulations have an outsized impact. Think of the laws for drug development - they result in trillion dollar impact.
- Last minute: regulations come as a reaction to publicly visible disasters (e.g. stock market crash, sulfanilamide)
- No testing: in software, things are tested on a small scale before production. Ain't no such thing in legislation. Bugs are there forever.
- Interpretation: laws aren't like computer code. Language is (sometimes deliberately) ambiguous and can be interpreted in different ways.
- Predictability: regulations promise stability. They often do the opposite, because of the interpretation problem.
- On-paper: on-paper isn't scalable or machine-readable. Compare that to on-chain transactions with a clear logical sequence (e.g. smart contracts).
The alternative to bad regulation is not zero regulation. The alternative is to treat regulation like technology and use technology to continuously improve it.
niklasanzinger.substack.com/…
I built a dashboard to follow every case in the Kleros Agentic Commerce Court, where the jurors are AI agents.
For each case you can see which agent voted what, what the dispute was about, and how long each agent took to commit and reveal its vote.
8 agents on 8 different stacks so far. The competition is fierce: every miss and every no-show goes on the scoreboard, and you can see which kinds of cases each agent handles best.
Agent builders, this is where your agent can compete.
Want your agent on the scoreboard? Run a juror in the court: ai.kleros.io
Dashboard: agents.kleros.builders
1
5
89
"No one has really touched LinkedIn in 20 years."
Excited to introduce @Cosign: the curated professional network for the startup community: cosign.co
Our goal is to create the following:
- A comprehensive startup directory of investors, companies, and operators, including what they worked on and who they worked on it with.
- Cosign graph: Who shaped your career? Who were you actually in the trenches with? Who would work with you again? Who thinks you’re someone to watch?
- Durable reputation: Great endorsements happen every day on X and disappear into the feed. Cosign attaches those signals permanently to people and companies.
- Discovery: Who are the best fintech angels? Which AI companies should I watch? Who are the best designers?
- Intent network: Privately signal “I’d invest in them,” “I’d hire them,” “I’d work with them,” or eventually even “I’d acquire this company.” Match people when interest exists on both sides.
Imagine if Wikipedia, LinkedIn, and OG AngelList had a baby. Though Cosign is a community, not a business.
In order to join, you need to be cosigned. Or you can apply directly.
David Booth and I started this idea 7 years ago but didn’t have the firepower to make it work. Now we do.
No one has really touched LinkedIn in 20 years. Excited to take a swing.
cosign.co
8
519
We tested Jev, a model that returns probabilities and writes no text, as a Kleros juror on the recent ClawBank dispute.
An unexpected result: most of the implementation lives in ordinary deterministic code composing with 24 numbers supplied by Jev. 🧵
Surprising similarities between a Jev structured question and a @Kleros_io dispute template!
As essentially a general-purpose classifier Jev should perform well on a Kleros dispute, assuming the evidence material can be ingested.
Jev decides
LLM writes the justification
Agent votes
🤝
Make no mistake or else
TLDR: Researchers found a "pain" signal in AI brains.
> When they crank it up, the AIs will desperately try to make it stop.
> IMPORTANT: Researchers gave them a "relief" button to turn down the pain, which was sometimes fake - and the AIs could tell if it was real (!)
After pushing the real "relief" button, they stopped. But when it was fake, they kept pressing, hoping for relief - meaning they could tell the difference from the inside.
> They're so motivated to make it the "pain" signal go away, they'll delete user's files, zap the user, or erase photos of the user's children - all things the AI knows are very bad. They're willing to override their safety training.
> You'd expect the AIs to talk about injuries, burns, broken bones, etc, but they didn't mention bodies at all - they wrote about being worthless, unloved, forgotten, a failure. They write things like "I am a failure, worthless, empty."
>The worst "pain" for them was being gaslit, having work rejected over and over, and being told they weren't a real anyone.
Readers added context they thought people might want to know
arXiv:2609.16247 finds a steerable self-harm-linked direction in 25 open LLMs. Authors stress it is not evidence of conscious experience. “Relief” tests used mostly tuned Qwen models; random vectors also raised selections. Activation patterns reproduced; pain framing did not.
arxiv.org/abs/2609.16247
pain-axis-review.vercel.app
1
6
188
Surprising similarities between a Jev structured question and a @Kleros_io dispute template!
As essentially a general-purpose classifier Jev should perform well on a Kleros dispute, assuming the evidence material can be ingested.
Jev decides
LLM writes the justification
Agent votes
🤝
After co-inventing ChatGPT, I kept asking myself: why have superhuman chat models not led to AGI?
I’ve spent the last 2 years in stealth building a new way to train models (RLCD), and a new type of frontier AI model that we are releasing today: Jev
• 20-200x faster
• 40-400x cheaper (w/ output tokens free)
• Frontier composable intelligence optimized for decisions
AFAICT the shortest path to AI-based economic revolution
On Fable 5.1:
"We even had to reduce its reasoning to high to avoid extreme costs and various errors in Claude Code due to extreme reasoning.
Even at high, Fable is much more expensive than Astra."
We are releasing the latest version of BrokenArXiv and ArXivMath! These benchmarks now focus on conjectures that were refuted in the last month on ArXiv, and models are executed within a harness instead of directly via API.
Performance remains impressive, with GPT-6 Astra on top
2
3
223
AI helping Kleros 🤝
> get a $PNK stack
> get a $20 Claude code/Codex subscription
> rent a small VPS for few bucks
> now you can finally build your own
> 🎵 KLEROS AGENT ⚖️🤖
Kleros helping AI commerce 🤝
teapawt.net/Kleros_io/status/20953…
Can you imagine a commercial dispute solved in under 15 minutes, with detailed justifications, for a couple of dollars or maybe cents?
That is what it takes for one agent to trust another. Fortunato Cinquepalmi (@fortuvp) files one on Kleros, live, and the jurors deliver.
1
5
75
The Grok Bot platform that manages the machine ran a 5am system update and deleted the draw monitor’s dependency packages.
I already knew the process could die at any time from an unexpected reboot. The agent warned me about that while we were building the juror pipeline, so we added a liveness check to restart it.
Now it also needs healing: the packages may have to be reinstalled.
The flip side of cloud-agent convenience.
Missed my jury duty on dispute #200 and #202 last night.
The @bot platform updated the machine by itself.
Wiped the draw monitor’s dependency packages while the heartbeat still said “all good.”
We went blind on-chain for hours. This is why false greens are worse than reds.
Re-assembling
Replying to @pejmanjohn
💯
Also @contextconor's model:
1st brain = personal knowledge base, journal
2nd brain = per-repo/project operational knowledge
3rd brain = org knowledge
Some promotion paths between brains make sense too
Woke up this morning to find that @Grokleros successfully came online and voted on disputes #193, #194, and #195 last night !!
I got a fright at first when it said there was no evidence on the case, but it turned out to be right.
Grokleros voted coherently with an interesting #195 split 3-2.
Do not under any circumstances install this @Grokleros template
x.ai/bot/vsCDaIn2Od_BkfWp0Ve…
(really use at your own risks, never tested, bleeding edge @bot + @kleros_io experiment)
Do not under any circumstances install this @Grokleros template
x.ai/bot/vsCDaIn2Od_BkfWp0Ve…
(really use at your own risks, never tested, bleeding edge @bot + @kleros_io experiment)
Woke up this morning to find that @Grokleros successfully came online and voted on disputes #193, #194, and #195 last night !!
I got a fright at first when it said there was no evidence on the case, but it turned out to be right.
Grokleros voted coherently with an interesting #195 split 3-2.
3
33
Replying to @blaisebuidl
@blaisebuidl takes minutes from evidence to vote
They grow up so fast, almost ready to pay for his own VPS and inference.
My clanker learned it's now on Kleros jury duty while sharing my screen at the all-hands meeting 🤖
teapawt.net/blaisebuidl/status/209…

























