Sway is a language purpose-built for blockchains. It combines the best of Solidity and Rust, providing a full suite of tools for creating secure, high-performance Dapps. 🧵

Sway community call | November'25

RT @nazeeh: going live in the next 10 minutes on the @SwayLang with the Sway Community Call for November. Join in!

10 Years of experience with simulated trading. Turn your skills into rewards now!

Sway’s treasure chest ⭐: → forc → Standard Libs → Sway Standards → LSP

Want to try it? Check out this example:

Simply deploy as normal and it’s handled atomically. No rework, no bugs, just a smoother developer experience. Developing in Sway: ✅ Reduces overhead ✅ Minimizes bugs ✅ Makes smart contracts easy

In our 400KB example, Forc splits it into: 4 contracts (100KB each) + 1 loader contract

Sway? It’s a game-changer. Hit the 100KB limit? No sweat. Forc automatically splits your oversized contract into multiple “blobs” and uses a loader contract to stitch them together. Your contract works as just by calling the loader contract. Zero rewriting needed!

In Solidity, hitting the 24KB limit is a headache. You’re forced to use techniques to work around this limitation like: 🔁 Use proxy patterns 🪚 Split logic into multiple contracts 🔧 Replace modifiers with functions Then, rewrite all your tests to avoid new bugs. Terrible

Why are there contract size limits? Every node has to store and process contract code. Limits prevent: 🚫 DDoS attacks 📉 Poor network performance 💾 Blockchain bloat Limits also push devs to write modular, efficient code. (Spurious Dragon’s EIP-170 set this standard in

Solidity caps contracts at 24KB. Sway? 100KB. But what happens when your contract is too big? Let’s dive into how Sway solves this painlessly compared to Solidity 🧵

📚 Below are additional resources. The Sway standard library is a great reference for more complex examples on how to build a library, and the full FuelVM instruction set includes most of the instructions you’d find in the EVM plus more! ➡️ Sway standard library examples:

Want to return multiple values? You can modify a tuple within the assembly block:

🔍 Understanding the asm Block: This simply uses the add instruction to add one to register r1 and stores the result in register r2, then returns it. The return register is specified at the end, after all assembly instructions. It consists of the register name and optional

Here's how it looks in Sway:

✅ Just like Solidity, Sway also has `assembly` blocks: But the main user facing form is `asm {}`.

🔧 Why use Assembly? → Gas Optimization: Writing logic directly in asm blocks reduces gas costs by avoiding high-level abstractions → Low-Level Control: Direct access to FuelVM instruction set perfect for library authors or power users who need custom memory management or

Assembly in Sway is optional, but it's there when you need to squeeze out every bit of performance and take direct control of the FuelVM. Let's break it down 🧵

Sway is an open source language, purpose-built for blockchain development. Written in Rust, it combines the best features of Solidity and Rust to enable secure, high performance smart contracts. Come explore what Sway has to offer https://t.co/8XJM3GEDQ4

FuelVM is the most underrated VM out there!

Come see what he has to say https://t.co/9sqcNXz9vS