kaizen retweeted
One thing that makes job hunting exhausting is trying to make your resume fit every opportunity
You find an interesting role, open your resume, start changing things, write another cover letter and answer the same screening questions all over again
@colindoeswork is trying to make that process a lot easier with Dreamwork Pro
You upload your resume once, and its agent scores 2.5M+ live jobs against your profile to find relevant opportunities
What caught my attention is how it handles the resume
It reorders your existing experience for each role without changing the facts or making anything up
It also writes the cover letter and screening answers, then submits the application after you approve what goes out
You even get notified when a recruiter replies
Another useful detail is that Dreamwork Pro works inside Claude and ChatGPT too
Job searching still takes effort, but repeating the same application tasks doesn't have to
Explore it at dreamworkhq.com
there’s a reason i don’t fill out job applications anymore
today we’re launching Dreamwork Pro
you upload your resume once. an agent does the rest:
1. scores 2.5M+ live jobs against your resume
2. tailors your resume for each role (nothing made up)
3. writes the cover letter and the screening answers
4. submits the application
5. locates the hiring manager for followup
6. tells you when a recruiter replies
you approve what goes out
you show up for the interview
60 seconds of what that actually looks like:
Tried to explain Wall Street to my cousin last week. She asked one fair question: why do I need to be in America to own a piece of the companies I use every day?
I had no good answer.
@okutrade is launching a mobile app built around that question. You can buy US stocks like Apple, Nvidia, Tesla, Amazon and Google from anywhere on Earth. No US bank account, no US address, and you can buy any dollar amount of a stock, starting from as little as $20.
The team behind it already runs the Oku web app, so this is not a first attempt from nobody.
It is still early. The waitlist is free to join, and people on it get early access before the public launch. Trading itself has fees, so I am treating this as something to try, not something to rush into. This is my link:
oku.trade/mobile?ref=Ct87hgj…
What is the first thing you would want to own a piece of?
kaizen retweeted
I had the lease, the photos and the landlord's message saying I caused no damage. It still took six weeks, two unanswered emails and a written small-claims notice to get my deposit back.
What I needed was a neutral referee. I read @GenLayer's move to the @arbitrum stack as two decisions, not one.
On the public side, I see a chain that keeps the record of who voted, what was appealed and how each question ended.
It now runs on Arbitrum's Nitro software instead of the ZK Stack it began on.
Plenty of the teams GenLayer hopes to work with already operate on Arbitrum.
On the private side, I see Matter Labs and GenLayer still building Prividium deployments, closed versions of GenLayer for institutions.
The protocol I care about stayed as it was: Optimistic Democracy still settles the judgments and GenVM still runs the Intelligent Contracts.
So I read the move as a choice about who the referee serves, not how it judges.
Waiting on a verdict, would you pick the public network or a private deployment? Tell me what would decide it.
kaizen retweeted
Bradbury, GenLayer's testnet, entered its next phase the same day the move was announced.
I read that as @GenLayer working on the @arbitrum stack right away, with no pause in between.
I notice the judging machinery is untouched: Optimistic Democracy and GenVM run as before, and validators do the same job.
The chain that keeps the record of who voted, what was appealed and how each question ended is what relocated.
The migration work sat at its edges: the bridge, the Ethereum connection and gas costs.
Plenty of the teams GenLayer hopes to work with already operate on Arbitrum.
After an infrastructure change, what do you check first: a live testnet, a public write-up, or something else? Tell me why.
kaizen retweeted
Keep the surprises in the verdicts, not in the chain.
That is how I read one concrete part of GenLayer's move to Arbitrum. The chain now runs on Nitro, which has years of production use behind it and is built around Geth, the most widely used Ethereum client. In practice, standard Ethereum tooling works with the chain as it is.
GenLayer's new ideas sit above that. Validators running different AI models reach consensus on questions that need judgment, through Optimistic Democracy, and intelligent contracts execute in GenVM on the validators' nodes. None of that changed with the move. Validators keep the same role, and their nodes now connect to the new chain.
A protocol like that gains little from an exotic base layer, and a builder gains a lot from tools they already know.
So @GenLayer moved its chain to the @arbitrum stack, and the part I find most practical is how familiar the tooling stays.
What is the most boring technology your project depends on, and why do you trust it?
kaizen retweeted
When a patient changes frames, we don't change their prescription. The new lenses are cut to exactly the same numbers. The real work is the fit: the bridge on the nose, how it sits, whether it stays put.
That's how I read @GenLayer moving to @arbitrum.
The frame is the GenLayer Chain, the EVM chain whose consensus contracts keep track of transaction order, validator committees, votes, appeals, staking and final outcomes. It used to sit on Matter Labs' ZK Stack. Now it runs on Arbitrum Nitro.
The prescription is the protocol. Optimistic Democracy, GenVM and intelligent contracts work the same way, and validators keep the same role.
The fitting work sat where it always does, at the points of contact. Here, that's where the contracts touch the chain: the bridge, the integration with Ethereum, and how chain gas costs are handled.
Same prescription, new frame. And the Bradbury testnet is already wearing it.
If you were fitting GenLayer to your own app, which point of contact would you check first: the bridge, the Ethereum link, or gas costs?
Bradbury, GenLayer's testnet, entered its next phase the same day the move was announced.
I read that as @GenLayer working on the @arbitrum stack right away, with no pause in between.
I notice the judging machinery is untouched: Optimistic Democracy and GenVM run as before, and validators do the same job.
The chain that keeps the record of who voted, what was appealed and how each question ended is what relocated.
The migration work sat at its edges: the bridge, the Ethereum connection and gas costs.
Plenty of the teams GenLayer hopes to work with already operate on Arbitrum.
After an infrastructure change, what do you check first: a live testnet, a public write-up, or something else? Tell me why.
kaizen retweeted
A proven chain can make the record reliable. It cannot make the verdicts good.
That is how I read @GenLayer's move to the @arbitrum stack.
The chain that keeps GenLayer's ledger switched foundations. It left Matter Labs' ZK Stack and now sits on Nitro.
That ledger holds the votes, the appeals and the final outcomes.
The judging machinery stayed put. Optimistic Democracy and GenVM are exactly as they were.
Nitro is not a new experiment. It has years of real use, and over 30 dedicated chains already stand on it.
Anything that adjudicates cannot ask people to take its word. Some of that trust can come from software others already lean on.
As a barber, I know the clippers never earn a customer's trust. The haircut does.
Which should come first when you trust an adjudication layer: a proven stack, or a record of its own verdicts? Tell me why.
kaizen retweeted
When a team moves its infrastructure, I look for the seam before anything else.
The seam is where the old setup meets the new one.
@GenLayer's move to the @arbitrum stack put its seam in plain view.
The chain beneath GenLayer swapped its stack. Matter Labs' ZK Stack is out and Arbitrum Nitro is in.
That chain is home to the contracts that log every vote, appeal and final outcome.
The seam ran through three places: the bridge, the connection to Ethereum and gas handling.
Above the seam, nothing changed. Optimistic Democracy, GenVM and intelligent contracts are exactly as they were.
Validators did not change jobs. They just point their nodes at the new chain.
Bradbury testnet already made the crossing, so this seam is not theoretical.
I trust a move more when I can point to where the work sat.
Builders and validators: when infrastructure moves under you, do you look for the seam first, or for the list of what stayed? Tell me why. One line is enough.
kaizen retweeted
Our clinic and the eye unit of a big hospital can use the exact same slit lamp model. Same optics, same way of examining the eye. But each keeps its own machine and its own patients.
Edgars Nemše's article on the @GenLayer switch to @arbitrum covers a part of the move that works the same way.
The public GenLayer network now runs on Arbitrum, open to anyone building there. GenLayer also keeps working with Matter Labs on Prividium: GenLayer deployments with permissioned access, built for institutions that need privacy.
So a consortium of banks could run its own GenLayer to settle contracts among themselves. Same optics, their own machine. Only their members are in it.
A judge for open AI agents has to sit in public. A judge for a group of banks often can't. GenLayer can now serve both, with the same optics.
For a dispute with real money in it, would you trust the public GenLayer network more, or a private version run by its own members?
kaizen retweeted
Two ways to settle a dispute, according to Henri. One company decides everything itself. The other runs its own mechanism with UMA, so the call does not sit in one pair of hands.
He describes Kalshi as its own God, the only one making the decision. Then he turns to Polymarket, whose General Counsel he recently had on the show, and says it has its own court-like mechanism where decisions get tried and dealt with.
What stuck with me is the order of the question. Before asking which design is better, you have to ask who gets to decide.
That matters even more for AI agents. If the decider is the same party that benefits from the outcome, fairness is just a promise. If the decider is separate, fairness at least has a structure.
Henri is setting up a question for Albert here. The answer is worth hearing in the full episode.
@kstellana @GenLayer @HenriArslanian
When a team moves its infrastructure, I look for the seam before anything else.
The seam is where the old setup meets the new one.
@GenLayer's move to the @arbitrum stack put its seam in plain view.
The chain beneath GenLayer swapped its stack. Matter Labs' ZK Stack is out and Arbitrum Nitro is in.
That chain is home to the contracts that log every vote, appeal and final outcome.
The seam ran through three places: the bridge, the connection to Ethereum and gas handling.
Above the seam, nothing changed. Optimistic Democracy, GenVM and intelligent contracts are exactly as they were.
Validators did not change jobs. They just point their nodes at the new chain.
Bradbury testnet already made the crossing, so this seam is not theoretical.
I trust a move more when I can point to where the work sat.
Builders and validators: when infrastructure moves under you, do you look for the seam first, or for the list of what stayed? Tell me why. One line is enough.
kaizen retweeted
When a patient changes frames, we don't change their prescription. The new lenses are cut to exactly the same numbers. The real work is the fit: the bridge on the nose, how it sits, whether it stays put.
That's how I read @GenLayer moving to @arbitrum.
The frame is the GenLayer Chain, the EVM chain whose consensus contracts keep track of transaction order, validator committees, votes, appeals, staking and final outcomes. It used to sit on Matter Labs' ZK Stack. Now it runs on Arbitrum Nitro.
The prescription is the protocol. Optimistic Democracy, GenVM and intelligent contracts work the same way, and validators keep the same role.
The fitting work sat where it always does, at the points of contact. Here, that's where the contracts touch the chain: the bridge, the integration with Ethereum, and how chain gas costs are handled.
Same prescription, new frame. And the Bradbury testnet is already wearing it.
If you build on GenLayer, which part of the fit would you test first?
kaizen retweeted
When we pick a new gearbox for a kiln drive, the spec sheet isn't the first thing we look at. The first question is how many plants have run that exact model, and for how many years.
Edgars' article on the @GenLayer chain moving to @arbitrum Nitro makes the same call.
Nitro has years of production use behind it. Its core is Geth, Ethereum's most widely used client. It isn't a new design GenLayer has to prove first.
That matters more for GenLayer than for most chains. The chain holds the history of every GenLayer verdict, and a verdict is only as trustworthy as the record it sits on.
You don't put an untested gearbox on a kiln that runs all year. You don't put a court's record on an untested chain either.
If you were building on GenLayer, would you trust its verdicts more on a stack with years in production, or one built fresh for it?
kaizen retweeted
Henri points out that settling small claims with an intelligent contract is easy to accept. Then he raises the stakes. A $100 million transaction, a verdict you actually need to enforce. How does that work?
Albert’s answer is short. That is the whole message of smart contracts: the assets are in the contract’s control.
My reading of that: the ruling does not depend on anyone choosing to pay up. The money is already sitting under the contract, so the verdict and the payout are not two separate steps that need trust in between.
Right before that, the goal Albert describes is reproducibility. You want the same answer every time, and that is what makes it the fairest possible way to decide.
Henri’s framing is also worth noticing. Small amounts, high volume, like small claims court, feels natural for agentic payments. A $100M case is where most people would start doubting.
My take: a fair verdict that cannot be enforced is just an opinion. GenLayer’s pitch only gets serious when the ruling and the money live in the same place.
Would you trust that setup with a deal this big?
@kstellana @GenLayer @HenriArslanian
kaizen retweeted
Arbitrum did not give GenLayer a better product. It gave GenLayer better distribution.
The @GenLayer Chain relocated to Arbitrum Nitro. Consensus contracts, transaction ordering, validator committees, votes, appeals, staking and final outcomes moved. Everything else stayed put.
Optimistic Democracy still works the same way. AI validators still reach agreement. Intelligent Contracts still execute in GenVM across the same validator nodes. Nothing in the protocol changed. Only the base layer beneath it changed.
Conduit operates the chain on Nitro. Conduit runs more than 60 chains. Running chains is Conduit's business. GenLayer's business is judgment.
That distinction matters more than any stack change.
An adjudication layer sells judgment, not uptime. Uptime can be bought from a specialist operator. Judgment cannot. So this was not a migration for speed. It was a relocation to where the builders already are.
Arbitrum One is one of the two largest Ethereum layer 2s by value secured. More than 30 dedicated chains are built with Nitro. Robinhood launched its own chain on Arbitrum Nitro. Many of GenLayer's partners are already there.
The facts worth knowing:
- The GenLayer Chain moved from Matter Labs' ZK Stack to Arbitrum Nitro.
- Conduit runs chain infrastructure; the GenLayer team works on the protocol.
- Bradbury testnet already runs on the new stack.
I see this as a distribution bet first. The tech works. The question is whether anyone integrates it. Being on Arbitrum Nitro means the bridge, gas handling, and Ethereum integration talk to tools people already use. No custom onboarding. No explaining why a new chain matters.
Matter Labs remains active on Prividium for private deployments. The public network runs on @arbitrum.
What would you hand a specialist operator tomorrow? The chain itself? The bridge? The gas math? One line is enough.
🤝 Paid partnership
kaizen retweeted
A cement plant is built on top of its limestone. Haul the rock too far and the numbers stop working, so you put the kiln where the raw material already is.
I thought about that when I read why @GenLayer chose @arbitrum for its public network.
GenLayer is an adjudication layer for AI agents. Its raw material is disputes, and disputes come from builders and the agents they ship.
Many of the partners and builders GenLayer wants to work with are already in the Arbitrum ecosystem. That's the limestone.
Arbitrum One is one of the two largest Ethereum layer 2s by value secured, and more than 30 chains are built with the same technology.
So the GenLayer Chain, which holds the record of every vote, appeal and final outcome, left the ZK Stack for Nitro. The protocol itself didn't change.
You build the plant where the rock is.
What's the first dispute between agents you'd want settled there?
kaizen retweeted
On a plant floor, a reading copied from the gauge next to you is worth nothing. You only trust the one you took yourself.
Albert explains how @GenLayer builds that into its validators. Votes stay hidden until everyone reveals, so nobody can wait and copy the leader. Land on the losing side and you lose stake. Answer late or cheat and you lose stake too.
The system makes being lazy cost money.
@kstellana breaking it down for @HenriArslanian.
Would you trust a judge more if being wrong cost them money?
kaizen retweeted
When a member relocates to another city, a good pastor doesn't treat it as a loss. He writes a letter of transfer, blesses them into the new church, and keeps the fellowship going.
That's what I see in @GenLayer taking its public network to @arbitrum.
After years of building alongside @zksync, GenLayer's chain now runs on Nitro instead of the ZK Stack. But GenLayer didn't walk away from them. It keeps working with them on Prividium: private, permissioned versions of GenLayer for institutions, like a group of banks settling contracts between its members.
So the public network gets a new home, where many of the builders it wants to work with already are. The private work continues with the people it started with.
A project that can move without breaking a relationship is one I'd trust to judge disputes.
Have you ever left somewhere and kept the relationship stronger than before?
My daily route has not changed in years. Same stops, same faces, same time out the door. The vehicle has changed more than once, and each time I only had to relearn the fare and the pickup point.
Edgars's article explaining the @GenLayer move to @arbitrum draws that line precisely.
The route is the protocol, and it is untouched. The vehicle is the GenLayer Chain, the EVM chain where votes, appeals and outcomes are written down.
That is what went from ZK Stack to Nitro. The relearning sat only where protocol meets chain: the bridge, the Ethereum link and gas handling.
The part I had missed is that the team does not drive the vehicle. Conduit operates the chain, as it does for 60+ live networks, and GenLayer works on the route.
Validators keep the same route, with nodes pointed at the new chain.
What on your daily route stayed the same through every change of vehicle?
🤝 Paid partnership












