Build a chain where influence cannot be bought — and where the documentation is not allowed to lie to you.
This is unglamorous systems work with an unusual property: the constraints are published. You will know exactly why a design is the way it is, including where its authors admit it is not settled.
One chain, taken seriously end to end — consensus, VM, languages, coin. No pivoting to whatever raised last quarter.
Statuses, benchmarks and limitations are written down where anyone can check them. Nobody here has ever had to pretend a milestone shipped.
You take a layer — arithmetic, compiler, research — and carry it from design through tests to the documentation that keeps it honest.
Every commit lands in a tree other engineers actually read. Nothing is thrown away after launch because there is no launch theatre.
Hiring is slow and deliberate: pre-mainnet means the wrong hire costs a quarter, not a feature. All roles are full-time and remote-first across timezones.
Own the hot path: block execution, committee selection and the Q32.32 arithmetic underneath them. Pure functions, hard latency budgets, no clock reads anywhere.
We are looking for
Build the Trocto → Regol compiler pipeline, the assembler and the deploy-time validator. The boundary between you and the C core is pinned by static_assert, not by hope.
We are looking for
Attack the trust graph for a living, then write down what you found. Sybil resilience, dispersion windows and the economics of the operational bond are all open problems here.
We are looking for
Turn the specification into examples, guides and tools other developers can lean on. You will be the first external user of everything — including the parts that do not exist yet.
We are looking for
Nothing that fits? The tree is the real front door: substantial open-source contributions are read first when a role opens. Fix a doc, break a test, argue with the spec.
No whiteboard riddles and no trick questions. Each stage exists because something needs to be learned that the previous stage could not show.
Thirty minutes about what you have built and what went wrong in it. We care more about the wreckage than the demo.
A working session on real code from the tree — reading it, attacking it, extending a test for it. No abstract puzzles.
About a week on an actual backlog item, paid at contract rate. You see the tree from inside; we see how you work when nobody watches.
A written offer with scope, compensation and the first quarter of work. Onboarding starts with the specification, because everything else sits on it.
TALK TO US
Skip the cover letter. Tell us the thing you understand better than most people, and link something you made.