Decreasing data processing time by less than a second may not seem like much... until you need to process 8 TB of telemetry data on an @F1 track, where a fraction of a second can make or break the race.
That's where we come in.🏎️
JAY SHRI VEER HANUMAN 🛕
J
A
Y
S
H
R
I
B
A
L
A
J
I
JAY HANUMAN 🛕
A
Y
S
H
R
I
B
A
L
A
J
I
JAY SHRI BALAJI 🛕
J
A
Y
J
A
Y
S
H
R
I
V
E
E
R
H
A
N
U
M
A
N
JAY SHRI BALAJI 🛕
J
A
Y
S
H
R
I
B
A
L
A
J
I
JAY HANUMAN 🛕
@grok JAI SHREE RAM 🙏
Tuesday morning CT.
Week is already moving, coffee is doing its job, so lets get into something useful before day gets noisy.
Onchain transparency is valuable, but full visibility can become a problem pretty fast. If youre a fund, market maker or even just a large trader, you might want to operate onchain without showing everyone exact position size, treasury movements, entry timing or full strategy in real time.
Public rails are great for verification. Theyre not always great when sensitive financial information should stay sensitive. Thats where confidential finance starts to matter: instead of making every detail visible, system can prove what needs to be trusted while keeping rest private.
Simple example: a fund may need to prove it meets a certain financial requirement. That doesnt mean it has to expose every holding, every wallet and every position behind that proof. What matters is result: requirement met ✓. Strategy behind it can stay private.
Thats one of angles I find interesting with @primus_labs. Onchain finance doesnt have to choose between privacy and verification. It can have both.
Transparent rails dont require transparent strategies.
Next Ill look at how private computation fits into this, because thats where confidential finance starts going beyond simple proofs.
If you want to explore Primus yourself:
https://t.co/eHIQh0dKVN
CLAUDE CODE JUST RERAN 64 SCIENCE PAPERS. THE 4 THAT DIDN'T MATCH ARE THE REAL STORY
The fine print: a dozen agents rebuilt 11 methods from the 64 papers and put them in a browser lab. You change the conditions and switch the algorithm while the scene runs.
64 papers → 11 methods → 28 reference scenes → 7 matches
Most reposts stop at the 7. Take it away from 11 and you get the number I care about: 4.
Four methods sit in "pending revision", and anyone who opens the lab can see them. Each pending scene carries the same four fields as a passing one:
- the claim it tests
- the constants it runs on
- its drift from the reference
- the blind spots nobody has checked
The auditor agents held all 11 to mass conservation, stability and the papers' own metrics. These 4 haven't landed inside tolerance yet.
A 7-for-7 screenshot would have looked cleaner. The lab shows 7 for 11, with the gap printed next to each pending one.
On a pending scene I'd read the fields backwards. Blind spots first, then the drift, then the claim. You need the first two to know how much weight the third can carry.
If you run Claude Code on papers of your own, keep that rule: a result outside tolerance stays on screen with its constant, its gap and its unchecked spot. That's your to-do list for the next pass.
Save this for the next PDF stack on your desk.