1/. After 6 months working on the Stellar Contract Library at @OpenZeppelin, I started seeing chains thru a more practical lens:. A transaction's structure quietly reveals what a blockchain can and can’t do. My latest article explores this across Ethereum, Stellar & Solana 🧵👇.

RT @OpenZeppelin: Calling all devs who @BuildonStellar — Stable Release v0.3.0 is now live ✨. Advanced Access Control modules, dedicated fe….

RT @tomerweller: Protocol 23, the biggest protocol change to the Stellar network since smart contracts went live, is rolling out with an ab….

RT @BazziBazzani: 💾 Just launched EVM-Storage codes!. Visualize, compare, and analyze Ethereum smart contract storage layouts with this onl….

RT @lumenloop: Learn from @BoyanBarakov how @StellarOrg's flexible authorization model enhances blockchain transactions, offering features….

10/. Let me know what other chains and/or topics you'd like to see explored next 😃. Full article here ⤵️.#Stellar #Soroban #Solana #Ethereum.

9/. Takeaways. Just looking at how different chains structure transactions can tell us a lot about their underlying design choices 🤓. On a personal note, I wasn’t familiar with Solana, but this comparative approach helped me pick it up quickly 🧑‍🎓. Was it useful for you too❓.

8/. On Ethereum, EIP-7702 introduced support for fee sponsorship. A new transaction type lets EOAs temporarily “borrow” contract code, making them “callable” like smart contracts. This mechanism is powerful but …still requires some setup and another contract to work 🔧

7/. On Solana, fee sponsorship is also natively supported. The fee payer is just the 1st account in the “accountKeys” array, even if it doesn’t take part in any of the instructions. No special handling needed at the contract level ✅

6/ . On Stellar, you can fully separate who pays for the transaction from who authorizes a contract call. The authorization is embedded in the "auth" field, making fee sponsorship straightforward:. No extra logic or custom setup needed ✅

5/. The setup is simple:. 1⃣ Counter contract with a permissioned increment function.2⃣Owner who’s the only one allowed to call that function.3⃣ Sponsor who pays the transaction fee.

4/. Here, I’d like to highlight “Fee sponsorship”:. Who pays for the transaction, and how is that determined?.How is authorization for the contract call handled?. The article covers other scenarios too, but this one is especially revealing 💡.

3/. Deployed a pair of similar contracts on Stellar, Solana, and Ethereum and explored a few scenarios:. ➡️ A simple permissioned contract call.➡️ Fee sponsorship.➡️ A call wrapping: a call to contract A gets forwarded to contract B.

2/. Most comparative analysis of L1s focuses on consensus or architecture. I looked at something simpler and still fundamental:. What does the transaction’s structure tell us about the blockchain, especially in terms of authorizations?.

RT @OpenZeppelin: 📢 New Release — OpenZeppelin Contracts for Stellar v0.2.0 💫. Secure, modular smart contract building blocks for @StellarO….

RT @ernestognw: 💵 Just sponsored an EOA transaction with another EOA. What's going on? 👇.

RT @ethereum: Pectra is live on Ethereum mainnet!. - Smart account wallet UX features now active.- L2 scaling data storage blobs increased….

RT @BuildOnStellar: hopefully by now you've seen the Contract Wizard from @OpenZeppelin, but if you haven't, check out this Developers meet….

1️⃣ Upgradeable Contracts – A standardized approach to keep smart contracts secure & flexible. 💬 2️⃣ Non-Fungible Tokens – Proposing a robust standard to enhance NFT interoperability on Stellar. 💬 Would love to hear your thoughts🚀.

We’ve been grinding hard on the @OpenZeppelin smart contracts library for @BuildOnStellar .✅ first audit.✅ first release. Now it's time to make a bigger impact on the ecosystem 🚀. Özgün Özerk and I just submitted our first two SEPs (Stellar Ecosystem Proposals) 👇👇👇.