Evanzzzz retweeted
Good evening everyone here is the story:
Hendrixxx was my course mate and I was the rep at the time he liked a girl named Aisha we often called her ”Iyami Leko” he met with me and asked how he could get to her, out of my generosity and good hearth I helped him out
Replying to @h_sanni1
Evanzzzz retweeted
sorry i’m late, GLACIER BOY tape now live on @Spotify 🤞🏾💽🅾️
Evanzzzz retweeted
I’M GIVING AWAY ANOTHER ROLEX ⌚️
Last winner took $10,000 instead of the watch 😂
To enter:
❤️ Like this tweet
🔁 Retweet this tweet
Next winner could be you 👊🏽
Evanzzzz retweeted
I know you all have been seeing my Kalshi ads all over X. As an apology, I'm partnering with them to give away 100 PS5s to celebrate the launch of GTA6 💪🏽💪🏽
Enter here: kalshi.com/giannis-ps5
Evanzzzz retweeted
IYA E WHAT IS MAMMAL😹😹
“highline na Jackson and Palmer food”
“If I catch this Barca highline”
“mechanic go pack Pedri for floor”
“cucurella go lock Yamal”
“we go too beat Barcelona”
today na today seh, see you by 11pm tonight
teapaw.org/BlaqChyld420/status/19…
Evanzzzz retweeted
🚨ENZO PREVIEWS REMA'S "SUGA" OFF EMB IN NEW TRAILER FOR HIS LIVE STREAM 🤩🔥
How's this sounding? 🤔
Evanzzzz 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 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
Evanzzzz 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


























