Morada🏕
592 posts


refuelling w/ goldman – ep. 3: honestly, when [@fuel_network] started talking about [@SwayLang], i had the same reaction as most people: "here we go again... another new language i’ll probably never learn." i mean, i’m an experienced coder... and i wish i could just casually spin up some smart contracts and flex my sway skills on the timeline, i might actually do that soon, tbh... but let's see. i'll learn it, and i'll do it. now, the reason fuel did not just go w the normal ethereum solidity is cos - ethereum uses accounts and global state, while fuel runs on something called UTXOs... ...the same type of structure bitcoin has [but way smarter and faster]. the usual tools - solidity, vyper, remix - they weren't built for thattt... it’s like trying to fit a square peg into a round hole. it won’t work, at least not without a mess. so fuel built sway. and honestly, sway is a pretty thoughtful flex. ...it’s rust-inspired, meaning it's strict, safe, and smooth to useee... [not speaking from personal experience tho, not yet...] and since fuel works differently, sway was literally designed around fuel’s entire logic. - parallel execution, -cleaner modular design, -contracts, -scripts, -predicates... all running seamlessly because sway was built exactly for this. fun fact::: i haven't actually really seen any chain rethink dev tooling from scratch like the way [@fuel_network] did w [@SwayLang]... if there arr, someone blz tag them in the comments. and the fact that it's still less talked about is a chance to understand what fuel is actually doing at the deepest level... before the whole noise kicks in. it’s a chance to be early on something that might reshape how we build in crypto/web3... and uhmmm, maybe one day i’ll actually learn sway, maybe you will too. i might even write a script or two w it... and wen i do, trust me to make a post bout it immediately... kek. that's all for now bros... see you in the next episode, we'll discuss somm'n even betterrr. and if there's enough interest in the comments, i'll do a more detailed solid breakdown of the sway language. i'm still goldman.


refueling with goldman... ep 2 how fuel actually works (without breaking into a sweat) so last time we said [@fuel_network] isn’t trying to be everything... it’s just focused on one thing: execution. but it’s not just doing execution better, it’s doing it completely differently! most chains today process transactions like they’re standing in line at the bank. one by one. no matter how small or unrelated, they all wait their turn... but [@fuel_network] doesn’t do that. it runs things in parallel. that means if two transactions aren’t messing with each other, they can go through at the same time. simple idea, right? but somehow... not much people really pulled it off. and it works because [@fuel_network] doesn’t use ethereum’s old account-based model. instead, it uses this UTXO-style setup which sounds fancy, but basically means it can track who owns what without turning the whole thing into spaghetti code. every transaction says exactly what it’s touching. so the system knows when it can run two things at once, and when it needs to chill. that’s the core magic. add to that a clean new language called sway... which, unlike some other languages, doesn’t feel like you’re writing code while trying to hide a boner. it has the FuelVM custom-built in it... haha. and it’s still early. not much people are cruising this ride yet, but when they do, they won’t want to go back to traffic. ep 3 coming – we’ll talk [@swaylang], why devs actually like it. and why it works. until then, i'm still goldman🍷



@goldmanCreates ComputeFi










