Str⚡️kerX retweeted
I built SubmitCheck for #AgentGames. Paste the hackathon rules and your draft, and it flags what’s met, missing, or unclear.
The demo shows why a demo page link isn’t the same as an agent endpoint. The app checks that its quotes appear in the pasted text; it doesn’t verify links or guarantee eligibility.
Try it: submitcheck-two.vercel.app/
My phone sits on battery saver from noon because light at home comes and goes. I test every new app the same way.
I install it, use it once for something small, and see if it earns its place before it earns my charge.
That is how I am approaching @okutrade.
It is a phone app for buying US stocks from anywhere. You can buy Apple, Nvidia or Amazon from $20 upward, in whatever amount you like, with no American bank account or address.
The same team already runs the Oku web app, used by 450,000+ people.
$20 is a test, not a commitment. It is small enough to lose and big enough to show whether buying, holding and selling actually work from where I live.
The waitlist is free, early access comes before public launch, and there are trading fees once it opens.
If you want to run the same test, join the waitlist through my link and you get 10% back on your trading fees: oku.trade/mobile?ref=244a886…
Then tell me your number. What is the smallest amount you would put into a brand new stock app before trusting it with more?
🤝 Paid partnership
During the last fuel scarcity I spent 6 hours in a queue for petrol that was selling freely 1 state away. The fuel existed, the road to it was the problem.
US stocks have felt like that from here. Apple, Nvidia and Tesla trade every weekday, and the price is public to the second. What was never available was a way in for someone with no American bank and no American address.
@okutrade is building a mobile app that lets you buy US stocks from anywhere.
You start from $20, pick whatever dollar amount you want, and need no American bank or address. Their web version has already handled over $6B of volume.
The mobile version is early access, and joining the waitlist costs nothing.
I joined through this link, and anyone who joins through it gets 10% of their trading fees refunded once trading opens: oku.trade/mobile?ref=e0e9d16…
Trading has fees and nothing here is advice. One question for you: which US company have you followed for years without ever being able to own 1 share of it?
Str⚡️kerX retweeted
My first physics lecture opened with a question. You toss a ball straight up on a smoothly moving train. Where does it land?
Most of the room said behind you.
It lands in your hand. Inside the train, the physics didn't change.
That is how I explain what @GenLayer did when it moved its chain to the @arbitrum stack. The train is the chain. The physics is the protocol.
The GenLayer Chain is 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.
• Same physics: Optimistic Democracy, GenVM and intelligent contracts work the same way
• Same job: validators keep their role, with nodes now connecting to the new chain
For a layer whose job is judging disputes, the rules not moving is the whole point. A rule that changes when the ground moves was never a rule.
Edgars Nemše explains the full reasoning in the article below.
One line, no hedging: whatever moves underneath you, what has to stay exactly the same?
Str⚡️kerX retweeted
Room 4221 can exist in two buildings. The number alone won't tell you which one you're in.
I'm sharing this for a Rally campaign and may earn a reward.
This is a detail I think is easy to miss after @GenLayer moved its chain to @arbitrum.
The GenLayer Chain moved from the ZK Stack to Arbitrum Nitro, with Conduit operating the infrastructure. It coordinates validator votes, appeals and outcomes.
GenVM still runs Intelligent Contracts on validator nodes, and Optimistic Democracy still governs how validators reach consensus. The validator's role remains the same; the node connects to the new chain.
Here's where the room number comes in.
GenLayer's network docs say Bradbury Phase 2 reuses chain ID 4221. An RPC is the endpoint an app or node uses to talk to the chain. An old one can report that same ID while pointing to a different deployment.
The guide also lists the genesis block hash, a fingerprint of the first block, and the AddressManager contract address to verify. I wouldn't treat the chain ID alone as proof I've reached the intended deployment.
Nitro supports familiar Ethereum tooling. That familiarity doesn't replace checking which chain you're connected to.
Network guide: docs.genlayer.com/developers…
Have you ever had the right number or name but ended up in the wrong place? What gave it away?
Str⚡️kerX 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?
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
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
Str⚡️kerX 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.
Str⚡️kerX 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?
I did not want a new gym instructor. Mine relocated. Before he left, he introduced me to his replacement.
I was uncomfortable. He was not returning, and I had heard the new instructor was very enthusiastic. I feared I could not match his energy and that my training would lose its impact.
Then I resumed. Everything was perfect and suitable.
A new instructor changed who runs my sessions, not what I was there to do.
@GenLayer’s move to @arbitrum works the same way.
What changed hands: the GenLayer Chain, the EVM chain that records transaction order, validator committees, votes, appeals, staking, and final outcomes. It left Matter Labs’ ZK Stack and now runs on Arbitrum Nitro, operated by Conduit.
What did not change hands:
• Optimistic Democracy, the way verdicts are reached
• GenVM and intelligent contracts, the way contracts run
• The validator role, with nodes now connecting to the new chain
Effort went to where contracts touch the chain: the bridge, Ethereum integration, and gas-cost handling.
Arbitrum is where many partners and builders GenLayer wants already are. The ZKsync side continues on Prividium and enterprise. Bradbury, the testnet, moved to its next phase the same day, already on the new stack.
My take: my fear was about energy, but what mattered was whether the training still worked. For an adjudication layer for AI agents, a permanent move must leave the verdicts feeling the same.
When an adjudication layer changes where it runs, what would you check first: the method, the validators, or the outcomes? One line is enough.
🤝 Paid partnership
Str⚡️kerX 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.
Str⚡️kerX 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?
Str⚡️kerX 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?
Str⚡️kerX retweeted
My @Acurast Rebel Card reads Aether Technician. I’m Rebel #22570, with 2 processors and 45,099 MIST so far. ⚡
The number I pay the most attention to is 2. MIST tracks my progress in the rebellion, but the processor count tells you what I’m actually contributing. That’s what got me interested in Acurast in the first place. A phone I already own can do more than run apps for me. It can also run workloads for someone else.
The question I’m watching is how often those processors get used. Bringing more phones online gives developers more computing capacity. Seeing developers come back with workloads for those phones would tell me more about demand. My card captures the first part of that story. The second is what I’m curious to follow.
Anyone else running an Acurast processor? What’s been the bigger challenge for you so far, setup or keeping it online?
#depin #acurast
Str⚡️kerX retweeted
Bitcoin holders have had two familiar choices: hold spot and accept the full exposure, or use leverage and take on the cost and maintenance that come with it. I think the gap between those choices is worth solving.
@2FactorFinance is making Kelly-optimized leverage available to buy-and-hold investors through cbBTC-Jr, now live on Base in a capped beta.
Kelly sizing is about finding the leverage ratio that maximizes long-run growth. It is not about choosing the biggest multiple possible. Too little leverage can leave potential growth unused, while too much can work against the holder and eventually destroy capital. For Bitcoin, the estimated Kelly target is around 1.33x. For context, Berkshire Hathaway has operated at roughly 1.6x leverage for decades.
At 1.33x, $100 of exposure capital corresponds to about $133 of Bitcoin exposure. That is a measured increase, not an attempt to maximize leverage.
So why has this approach mostly stayed with institutions? Maintaining a stable leverage target requires continuous work, and financing has traditionally been priced around the cost of being short. Most individual holders do not have the infrastructure to manage both efficiently.
The usual retail alternative has been leveraged ETFs. But their financing costs and decay make them difficult to hold over long periods. The campaign materials estimate that holders pay more than $10B annually in hidden financing costs above the risk-free rate. That is a substantial cost attached to a product many people use for leveraged exposure.
2Factor takes a different structural approach. cbBTC-Jr provides 1.33x leveraged cbBTC, is designed to never be liquidated, and is built to be held. The senior side, cbBTC-Sr, funds the leverage and sits behind a deep buffer of junior capital. The product is deployed on Base and currently operates in a capped beta.
My take: the interesting part is not simply getting 33% more Bitcoin exposure. It is making a carefully sized leverage structure accessible without requiring holders to continuously manage a position. That is a meaningful design improvement to explore, although it does not remove Bitcoin's downside risk. A leveraged position can still lose more than spot when the market falls.
Bitcoin is the starting point. Tokenized stocks are next on the roadmap, but they are not live yet.
I would rather see a modest leverage product prove its financing and structure through different market conditions than see another product compete on the largest multiple.
If you want to explore the project and join the Points Program, here is my referral link:
points.2factor.finance/r/7o8…
Str⚡️kerX retweeted
I wouldn’t suddenly call SPY or QQQ “yield assets” just because there is a 3% APR next to them.
SPY’s 30-day SEC yield was around 0.97% in early November, while QQQ was only around 0.41%. The ~3% offered through rToken Earn is coming from somewhere else: an onchain lending strategy layered on top of the rSPY or rQQQ position.
That distinction matters.
Put $10,000 into rSPY at a constant 3% annualized rate and you are talking about roughly $300 over a year, paid in rSPY. Useful if you were already planning to hold the exposure, but it does not change the fact that SPY or QQQ can move more than 3% long before a year passes.
So I see this less as “earning 3% on stocks” and more as trying to make an otherwise idle tokenized ETF position slightly more capital-efficient.
The plumbing is also worth looking at. Reality issues the 1:1-backed rTokens, Ember provides the vault infrastructure, and Fluid provides the lending markets. Bitwise is expected to curate the strategy later, but that part was not live at launch.
There is no fixed term, and rewards accrue in the same rSPY or rQQQ you deposited. But the extra yield also means accepting an additional onchain lending and vault layer on top of the ETF-linked market risk you already had.
That is the question I’d actually ask anyone holding broad-market exposure long term:
How much extra yield would you need before adding another layer of smart-contract, liquidity and lending risk becomes worth it?
More details:
bitget.com/blog/articles/bit…
#DYOR #NFA
This content for informational and educational purposes only. The approximately 3% APR is indicative, variable and not guaranteed. rToken Earn is available only to eligible non-U.S. users in permitted jurisdictions
My crypto auto-sniper's logic worked. Detection worked. Buying did not, because everything around the logic failed.
The free feed arrived about a second late. Shared RPCs kept timing out or rate-limiting me. Some tokens had already graduated by the time the bot tried to buy. My bankroll was around $5, and I lost $0.
That is how I read the part of @GenLayer's move to @arbitrum that I find most interesting.
The consensus contracts moved. They record transaction order, validator committees, votes, appeals, staking and final outcomes, and they run on the GenLayer Chain. That chain went from Matter Labs' ZK Stack to Arbitrum Nitro. Optimistic Democracy, GenVM and intelligent contracts work the same way.
The migration work was at the edges, where the contracts touch the chain: the bridge, the integration with Ethereum, and how chain gas costs are handled.
The protocol logic is the part everyone watches. The plumbing is the part that decides whether it works.
When you last moved something, what broke first: the logic, or the connection to the outside?
Str⚡️kerX retweeted
Solidity compatibility is useful today. Having another execution option for tomorrow is a different advantage.
That’s what makes one detail of @GenLayer’s move to @arbitrum worth looking at.
The GenLayer Chain moved from Matter Labs’ ZK Stack to Arbitrum Nitro. Built around Geth, Nitro supports standard Ethereum tooling, so developers can work with familiar tools.
But Nitro also offers Stylus, an additional execution environment alongside the EVM. It allows developers to write contracts in Rust and compile them to WebAssembly.
GenLayer’s consensus contracts are written in Solidity today. They are not already running on Stylus.
That distinction matters. GenLayer gets Ethereum tooling compatibility now, while Stylus gives the team another option if compute-heavy parts of the protocol eventually make a different execution environment worthwhile.
I don’t think every component needs a new language or execution environment. The value is having that choice when the workload actually justifies it.
Developers, where would you draw the line between keeping a component in Solidity and moving compute-heavy work to Rust and WebAssembly?
🤝 Paid partnership





















