Pinned Tweet
They sent a wave of kangaroos at Gamdom.
Steve sent them back.😮💨🔥
#gamdom100k
@stevewilldoit @gamdom @gamdom_beekay @kingadukes
Use code "STEVE"
ID: 48211893
Me and koko Pee against the world teapaw.org/notevanzzzz/status/212…
26
SøM_on_X retweeted
I almost walked out of a Nigerian shop without a $15 item I had already selected.
My phone calculator displayed ₦20,000 and my hands froze at the counter. Now I measure life in $100 chunks:
• 25kg bag of rice: ₦45,000
• A whole week of bike rides to work: ₦35,000
• Fried yam and fish for three friends: ₦20,000
The twist about naira: we earn it, yet laptops, phones and flights are priced in dollars. So every big purchase starts with a silent, split-second maths test.
@RallyOnChain, which purchase made you hesitate at the checkout, and what was the damage?
SøM_on_X retweeted
'Never liquidated' is not a promise. It is a job assignment.
Every leveraged structure has to decide who absorbs the loss that would otherwise force a sale. Margin gives the job to the liquidation engine: when collateral falls, the lender protects itself by closing you. Leveraged ETFs give it to the holder, paid daily in decay. Both work. Both bill the same person.
@2FactorFinance assigns the job in advance. That is the redesign.
The product splits Bitcoin exposure into two tranches. cbBTC-Jr is 1.33x leveraged cbBTC, built to be held like spot. cbBTC-Sr is the senior side: it funds the leverage and sits behind a deep buffer of Jr capital. Losses land on Jr first, by design, so the funder's protection is already in place before anything goes wrong.
That is what makes "never liquidated" credible rather than marketing. Liquidation exists because a lender must protect itself when collateral falls. Here the protection is pre-funded. There is nothing left to force.
The honest part: never liquidated is not never lost. Jr still carries 1.33x of Bitcoin's downside, and a deep drawdown will show up in the position. What the structure removes is the forced sale at the worst price. You keep the asset. The forced-seller stays out of your account.
The 1.33x itself comes from Kelly sizing, the institutional strategy for the leverage ratio that maximizes long-run growth. Too little leaves growth on the table. Too much compounds against you, eventually to zero. Equities sit near 1.5 to 2x, and Berkshire has run roughly 1.6x for decades. For Bitcoin, about 1.33x.
Leveraged ETFs are the comparison everybody reaches for: they reset daily, decay over time, and charge holders an estimated $10B+ a year in hidden financing. First Bitcoin here. The mechanism is asset-agnostic, and tokenized stocks are next on the roadmap, not live yet.
The other seat: if your appetite runs conservative, Sr funds the leverage from behind the buffer.
When you size up a leveraged structure, what do you check first: the multiple, the financing, or who absorbs the loss?
The Points Program is free to join with an X account, no deposit needed. Marks are earned for learning, posting and referring, and Season 1's top ten split 1 BTC in cbBTC, fixed by rank. Marks have no cash value. Not open to the US or restricted countries.
My referral link:
points.2factor.finance/r/1hl…
SøM_on_X retweeted
Two questions before you borrow anything: how much, and who can call it in early?
That's my uncle's rule. He has borrowed all his working life and still asks both, every time.
Leverage on Bitcoin comes down to the same two questions, and @2FactorFinance is built around answering them for people who buy and hold.
How much?
• Kelly sizing picks the leverage that compounds fastest over the long run
• For Bitcoin that's about 1.33x, so $900 acts like about $1,200
• Berkshire Hathaway has run at about 1.6x for decades
Past the target, extra leverage works against you, eventually to zero.
Who can call it in early?
• On a perp or margin position, liquidation can
• On a leveraged ETF, decay does: they can't be held long, and holders are estimated to pay $10B+ a year in hidden financing and decay
Keeping a ratio steady takes constant management, and institutions had the staff and the cheap financing for it. Individual holders didn't. That's why this stayed with them.
What 2Factor changes: it does the managing for you and removes the forced exit.
• cbBTC-Jr is 1.33x leveraged cbBTC, a Bitcoin token on Base, with no liquidation and a design meant for long holds
• cbBTC-Sr funds the leverage and sits behind a buffer of Jr capital
• Bitcoin comes first, and tokenized stocks are next on the roadmap, not live yet
My take: interested, not convinced.
The size is old math. The structure is new, and still in a capped beta. Jr is the cushion for Sr, and it's still leverage: a Bitcoin drop hits it harder than plain Bitcoin.
What's the first question you ask before you take on any leverage?
Eligible? Join the Points Program by signing in with X. No deposit needed.
You need an account at least 90 days old with 150+ followers, and it's not open to people in the US or restricted countries.
My referral link:
points.2factor.finance/r/tdj…
Two questions before you borrow anything: how much, and who can call it in early?
That's my uncle's rule. He has borrowed all his working life and still asks both, every time.
Leverage on Bitcoin comes down to the same two questions, and @2FactorFinance is built around answering them for people who buy and hold.
How much?
• Kelly sizing picks the leverage that compounds fastest over the long run
• For Bitcoin that's about 1.33x, so $900 acts like about $1,200
• Berkshire Hathaway has run at about 1.6x for decades
Past the target, extra leverage works against you, eventually to zero.
Who can call it in early?
• On a perp or margin position, liquidation can
• On a leveraged ETF, decay does: they can't be held long, and holders are estimated to pay $10B+ a year in hidden financing and decay
Keeping a ratio steady takes constant management, and institutions had the staff and the cheap financing for it. Individual holders didn't. That's why this stayed with them.
What 2Factor changes: it does the managing for you and removes the forced exit.
• cbBTC-Jr is 1.33x leveraged cbBTC, a Bitcoin token on Base, with no liquidation and a design meant for long holds
• cbBTC-Sr funds the leverage and sits behind a buffer of Jr capital
• Bitcoin comes first, and tokenized stocks are next on the roadmap, not live yet
My take: interested, not convinced.
The size is old math. The structure is new, and still in a capped beta. Jr is the cushion for Sr, and it's still leverage: a Bitcoin drop hits it harder than plain Bitcoin.
What's the first question you ask before you take on any leverage?
Eligible? Join the Points Program by signing in with X. No deposit needed.
You need an account at least 90 days old with 150+ followers, and it's not open to people in the US or restricted countries.
My referral link:
points.2factor.finance/r/tdj…
SøM_on_X retweeted
An AI agent with $100 can still be treated like an experiment.
Give it $10,000 and trust becomes an architectural decision.
Should it blindly accept the other agent’s claim? Should it hire a lawyer after something goes wrong? Or should the agreement begin with an affordable dispute process already built into it?
That choice from @kstellana’s conversation with @HenriArslanian is the part that matters to me.
@GenLayer lets Intelligent Contracts define how a disagreement will be judged before either agent gets control of the outcome. Validators running different AI models can then reach consensus on questions that require interpretation.
The larger an agent’s budget becomes, the less reasonable it is to improvise accountability after the payment.
At what spending limit would you require your agent to have adjudication built into every agreement?
SøM_on_X retweeted
Your wallet shows success. The dispute is not necessarily settled.
I'm sharing this for a Rally campaign and may earn a reward.
Imagine an app submits an AI agent's delivery dispute to a @GenLayer Intelligent Contract. The wallet turns green. Is the case finished? Not necessarily.
That matters after GenLayer moved its public chain from the ZK Stack to @arbitrum Nitro. Conduit operates the chain infrastructure; the consensus contracts on that chain coordinate validator votes and appeals.
The decision process hasn't changed. GenVM still runs Intelligent Contracts on validator nodes, and validators still use Optimistic Democracy to reach consensus.
For the app, I would separate three checks:
1. A successful EVM receipt confirms the submission was included. It doesn't confirm the Intelligent Contract's outcome.
2. Accepted means the validator committee agreed on a receipt. It's provisional and may be appealed during the window.
3. Finalized means the decision is no longer appealable. The execution result still needs checking: a finalized receipt can contain an error.
Nitro supports standard Ethereum tooling. That makes the chain familiar to work with, but it doesn't skip those checks. I would look at finalization, execution and the decision itself before an app pays either side.
When was the last time you got a confirmation but weren’t sure the whole thing was actually finished? What did you check next?
I owned a power station and thought it was a power bank.
I used it to charge my phone and small gadgets, like my electric fan. Later I found out it could charge my PC too. I have not used that yet.
I am keeping it for later, because I know the time will come when NEPA fumbles and the lights go out, and I will need a way to power my PC.
Edgars Nemše’s explanation of why @GenLayer moved its chain to @arbitrum has the same two layers.
Everyday use: Nitro is built around Geth, the most widely used Ethereum client, so standard Ethereum tooling works with the GenLayer Chain as it is.
Reserve: Nitro also has Stylus, a second virtual machine next to the EVM. It runs contracts written in Rust and compiled to WebAssembly. GenLayer’s consensus contracts are in Solidity today. Stylus gives a way to move compute-heavy parts of the protocol into faster code later.
My take: a reserve you have to use on day one is not a reserve; it is a second project. GenLayer’s consensus contracts are in Solidity today and standard tooling covers the everyday work, so the faster path stays an option, not a requirement.
For an adjudication layer for AI agents, I would take that order: stable now, faster as an option.
Nothing in the protocol changes for builders: Optimistic Democracy, GenVM, and intelligent contracts work as they did.
Builders, what is the one thing on your stack you have not used yet but are glad is there: faster code, a second runtime, or something else? One line is enough.
🤝 Paid partnership
SøM_on_X retweeted
I kept the client files and the server logs in the same notebook.
Every time the server broke I had to flip past the open disputes to find the password.
Three calls sat unresolved for nine days because the page with the decision was stuck behind a page of error codes.
I moved the logs to a separate operator and left the notebook with only the disputes.
The next call closed in four hours.
The notebook never changed.
Only what sat in front of it.
That is why the operator split in @GenLayer’s move to @arbitrum is the part I keep.
The GenLayer Chain now runs on Arbitrum Nitro.
Conduit operates it.
The protocol team does not.
Optimistic Democracy, GenVM and Intelligent Contracts stayed the same.
An adjudication layer keeps the notebook.
Uptime can live somewhere else.
Builders, what would you move out of the notebook tomorrow: the chain, the bridge, or the gas math?
One line is enough. I read every reply.
SøM_on_X 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?
SøM_on_X retweeted
I once moved a shared Google Drive that held three years of client contracts.
The new structure looked cleaner.
The risk was one broken permission or one missing subfolder staying quiet until a dispute started.
I checked the top-level folders first, then the oldest files, then the sharing settings on the ones that had already been contested.
Everything was there.
The structure changed. The record did not.
That is the part that matters in @GenLayer’s move to @arbitrum.
The GenLayer Chain relocated.
It is the EVM layer that keeps the paper trail: transaction order, committee assignments, votes, appeals, staking balances, and final results.
It now runs on Arbitrum Nitro, operated by Conduit.
What stayed in place:
Optimistic Democracy, the method validators use to reach a verdict.
GenVM, the engine that runs Intelligent Contracts.
The validator role itself. Nodes simply point at a new destination.
The work sat in the seams: the bridge, the link to Ethereum, and gas costs.
Arbitrum puts the public network closer to builders and partners already using the same stack.
More than 30 dedicated chains run on it.
Geth sits at the core, so standard Ethereum tooling connects without reconfiguration.
An adjudication layer for AI agents needs the record to stay intact while the infrastructure around it changes.
That is what this move did.
When the place something lives changes, do you check the finished work first, or the pieces that were still open and could still cause a dispute?
SøM_on_X retweeted
For a judgment to count, someone outside the room has to be able to check it.
That is the part of @GenLayer's move I keep returning to. What relocated is the GenLayer Chain, and its job is to keep the record: which validators formed the committee, how they voted, what was appealed, how it ended.
The judging never lived there. Validators each run their own AI model and have to agree, and the contracts they execute run on their own machines.
So the thing that moved is the paperwork, not the argument.
The paperwork went somewhere more people can read. @arbitrum Nitro is built around Geth, the client most Ethereum tooling already speaks. The record now sits in a format developers outside GenLayer can open without learning a new stack. That is a modest claim, and I think it is the real one. A record kept in a format only its authors can read proves nothing to anyone.
Conduit operates the chain, so the team is not author and operator at once. The private institutional work continues separately with Matter Labs on Prividium.
Here is the limit, and it is the interesting part. On Nitro, more people can see what the panel decided. Nobody can see why. A vote is a result, not a reason. The models that produced it stay on the validators' machines.
A legible record of an illegible decision is still an improvement. It just moves the next question from where the chain runs to what a verdict has to show.
If you were the one checking a contested verdict, what would you need first: the committee's vote, the appeal after it, or the model's reasoning?
A record of mine was moved once, to a new system, in a different office, with 0 changes to what it said.
Dates, signatures and decisions were identical. What changed was where you went to ask for it and who handed it over.
That is the concrete part of the @GenLayer move to @arbitrum most people are describing wrongly. The judge did not move, the register did.
GenLayer's consensus runs through smart contracts that write down who sat on each committee, how they voted, any appeals and the final outcome.
Those contracts sat on an EVM chain built on ZK Stack and now sit on one built on Arbitrum Nitro.
The AI validators, Optimistic Democracy and GenVM read exactly as before. Only the filing cabinet changed rooms, and a verdict does not depend on which room holds its paperwork.
What is the first field you would check in a verdict record that had just changed systems?
🤝 Paid partnership
I picked my mobile network for 1 reason: the people I call most were already on it.
The tariff and coverage map did not come into it. A phone is worth whatever is on the other end of the call, so you go where the other end already is.
The @GenLayer announcement follows the same logic. The public network moves to @arbitrum because the builders it needs already live there. It is one of the 2 largest L2s by value secured, with 30+ dedicated chains beside it.
For an adjudication layer that settles disputes between other people's agents, being where those agents already transact is the product.
The ZKsync relationship carries on where it fits, Prividium, the private permissioned GenLayer for institutions. The Bradbury testnet moved onto the new stack the same day.
Which network would you move to tomorrow purely because the people you deal with are already there?
🤝 Paid partnership
SøM_on_X 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?
SøM_on_X 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?
SøM_on_X retweeted
I swapped the chain on my bike last Sunday. Pedals, gears and wheels stayed exactly as they were.
The fiddly part was where the new chain met the gears. It was two links too long, and the first ride clunked.
After a swap, you check the seams, not the parts you never touched.
@GenLayer has a chain too: the EVM chain where the contracts that record transaction order, validator committees, votes, appeals, staking and final outcomes run.
It moved from Matter Labs' ZK Stack to Arbitrum Nitro, so the GenLayer Chain now runs on the @arbitrum stack.
• Untouched: Optimistic Democracy, GenVM, intelligent contracts and the validators' role, with nodes now connecting to the new chain
• The seams: the bridge, the link to Ethereum and how chain gas costs are handled
Nothing in the protocol changed for builders and validators. The work sat where the contracts meet the chain.
Edgars Nemše's article is below.
Name the seam: where did your last migration actually hurt?
I swapped the chain on my bike last Sunday. Pedals, gears and wheels stayed exactly as they were.
The fiddly part was where the new chain met the gears. It was two links too long, and the first ride clunked.
After a swap, you check the seams, not the parts you never touched.
@GenLayer has a chain too: the EVM chain where the contracts that record transaction order, validator committees, votes, appeals, staking and final outcomes run.
It moved from Matter Labs' ZK Stack to Arbitrum Nitro, so the GenLayer Chain now runs on the @arbitrum stack.
• Untouched: Optimistic Democracy, GenVM, intelligent contracts and the validators' role, with nodes now connecting to the new chain
• The seams: the bridge, the link to Ethereum and how chain gas costs are handled
Nothing in the protocol changed for builders and validators. The work sat where the contracts meet the chain.
Edgars Nemše's article is below.
Name the seam: where did your last migration actually hurt?
SøM_on_X retweeted
Old phone. New phone. Everything present.
I upgraded from my TECNO to a new device. Before the switch, I saved everything to Google Drive: contacts, group threads, private chats. Installed WhatsApp, verified the same number, restored the backup. Every conversation came back.
The phone was never the account. Just where I reached it.
That is the design @GenLayer protected moving its chain to @arbitrum Nitro.
Consensus coordination shifted to Nitro, operated by Conduit:
- Transaction sequencing, committee assignments, tallied votes, appeal records and round resolutions
- Bridge mechanics, Ethereum connectivity and gas accounting
The judgment layer carried across unmodified:
- AI validators using independent models settle outcomes through Optimistic Democracy
- Intelligent Contracts process in GenVM across the same validator set
My take: a protocol's verdict logic should outlast the chain beneath it. That boundary preceded the migration.
For teams deploying agents that act on disputed outcomes:
What would you check first to confirm the adjudication layer held through the move?
SøM_on_X retweeted
🚨SIENA GIVE AWAY🚨
🟢$40 in BTC to 40 participants if Siena🏀 defeats St John’s tonight!
To enter
🟡Follow @XutuTrading
🟡Repost this post
🟡Comment “Baloo”
#xutugiveaways
















