Sabitlenmiş Tweet
fucory
17.1K posts

fucory
@FUCORY
Building - JJHub, Smithers, Tevm, Voltaire,
San Francisco, CA Katılım Mart 2011
1.6K Takip Edilen4.2K Takipçiler

@krzKaczor @continuedev I got a workflow to validate a bug is real and then comment on the issue
English

@FUCORY AI powered CI checks are really intriguing. Recently I've started exploring @continuedev. For now I use them mostly to enforce again some things from AGENTS.md. Do you have some inspiring examples?
English

The power of Smithers is gonna really be unlocked when people start combining it with jjhub
JJHub is like if we took github actions, replaced yaml with typescript, and made the workflows super fast to run locally and in the cloud.
In this world you want your workflows to be composable reusable and easy to improve over time. You start with a simple set of high impact workflows
- ReproduceBug
- CIChecks
- VerifyDeploymentSuccess
- ReviewPr
You run these checks developing with clankers both locally and in cloud
Engineers invest time into improving the workflows over time. They factor out reusable pieces to build more sophisticated workflows. Just one step at a time. Slow careful evolution
12 months later that engineering team will have a secure, robust AI automated set of workflows improving the velocity and quality of the codebase unlike any engineering teams before

English

@sameandnot @agenticklabs Yea you can also use the CLI agents like Pi Amp ClaudeCode Opencode or Codex
Your API got some things I should have been doing better so if you notice anything where you think your approach was much better open issue and I'll definitely make any changes you suggest
English

@FUCORY @agenticklabs This looks really cool. I’m not very familiar with JJ but from what I understand of it this approach makes a lot of sense. Agents are run with ai-sdk under the hood, yeah?
English
fucory retweetledi

@MiniMax_AI @ryancarson in case you're code factory doesn't do this, it's likely a helpful overview for you
cc @FUCORY re agents reading transcripts + metrics from smithers flows, updating the workflow / agent (e.g. pi extension writing on the go) -> it hot reloads and they watch for eval.
English

Introducing MiniMax-M2.7, our first model which deeply participated in its own evolution, with an 88% win-rate vs M2.5
- Production-Ready SWE: With SOTA performance in SWE-Pro (56.22%) and Terminal Bench 2 (57.0%), M2.7 reduced intervention-to-recovery time for online incidents to 3-min on certain occasions.
- Advanced Agentic Abilities: Trained for Agent Teams and tool search tool, with 97% skill adherence across 40+ complex skills. M2.7 is on par with Sonnet 4.6 in OpenClaw.
- Professional Workspace: SOTA in professional knowledge, supports multi-turn, high-fidelity Office file editing.
MiniMax Agent: agent.minimax.io
API: platform.minimax.io
Token Plan: platform.minimax.io/subscribe/toke…

English

I imagined myself working there. I'd think about the trust assumptions of stablecoins. I'm generally a product first person. And state channels produces the best product. I would have felt very strongly about this to the point where if I couldn't convince leadership that this is the correct path I would lose faith in leadership and leave
So that combined with knowing leadership does in fact know what they are doing made it clear to me it's inevitable
English

@FUCORY @samuellhuber Thank you for keeping the spirit alive 🙏
English

A billion Wei idea for all you fancy VCs here:
An Ethereum node that just works.
Not stateless.
No GigAgAss.
No L2.
No zk.
But an unbelievable killer feature that nobody tried yet:
You can query state and logs and the node
(a) always responds with sub-minute latency and
(b) actually responds correct data.
I'm happy to invest the first 10k Wei myself.
English

@FUCORY @samuellhuber Interesting, thanks for that. Suggestion: add this to your bio - it's hard to find here.
IIRC there was some drama around the Ethereum JS team getting laid off from EF last year, is that the revival of those efforts or entirely separate?
English

@sameandnot @agenticklabs Very cool! I'm building jjhub.tech to try to get this type of orchestration running in easy to manage containers in an alternative github. If we got similar interests might be an opportunity to collaborate
English

@FUCORY @agenticklabs I did… Smithers likewise looks very cool! And I love the name. :) When I said “should have” what I really meant was “wish you had”! It’s exactly the kind of higher order system I built agentick to be able to support.
I am using it to build github.com/agenticklabs/t…
WIP
English

@sameandnot @agenticklabs Looks cool! I think smithers is a bit of a higher level of abstraction than this. This looks useful for managing context windows at a low granular precise level and likely would work with smithers with minimal effort
Did you build it?
English

tevm.app is an abandoned project. A block explorer I built in 2 days using voltaire
The Tevm universe is vast
We got the original tevm: github.com/evmts/tevm-mon…
We got voltaire: github.com/evmts/voltaire
We got guillotine and guillotine-mini: github.com/evmts/guilloti…
We got zevm (unreleased but likely next week) which includes light client consensus and lightweight way to sync and index
There is also friends of tevm @trueblocks that has a powerful indexer I used in my prototypes of a local first fast syncing ethereum node
English

@FUCORY @samuellhuber I'm confused what I'm looking at
tevm.app
Docs links all send me to some generic Base docs.
How do I run this locally on my laptop?
English


The key is to just constantly look out for repetitive things you can abstract. Start with things smaller than smithers. Maybe set up a postcommit hook to have an llm review the code. Maybe use bun to just create a super simple script or make some custom pi plugins. Abstract prompts you repeat a lot into reusable skills.
As you climb that ladder of automation eventually the problems smithers solves will appear and why you should use it becomes obvious
English

@0xDrewF @powdr_labs @openvm_org Whoah that sounds cool. I would have to look into it but that would be awesome feature
English

@powdr_labs @openvm_org Does this mean proofs of Voltaire are straightforward now? @FUCORY
For example I could prove there are X logs that match a filter over some blockrange?
English

Announcing powdr-wasm!
powdr-wasm is an optimized zkVM for WASM, built on top of @openvm_org and the novel 𝑐𝑟𝑢𝑠ℎ ISA.
Early benchmarks already show 1.5x fewer trace cells & faster proof times compared to RISC-V (OpenVM).
It also supports Go guests via WASI!
👇
English







