Every day that passes, otigen gets a little closer to v1-ready, and the story behind it is kind of a fun one. It actually started its life as a programming language. .oti extension, working compiler, the whole thing. But somewhere along the way, I caught myself walking the same path other networks walk, telling devs they have to learn yet another language before they can ship anything on the chain. And honestly, I just did not want to do that to people. So otigen pivoted into what it is today, a pyde developer toolchain that lets you scaffold a contract in a language you already know, currently Rust, Go, AssemblyScript, C, and C++, and gives you everything you need around it, build, test, deploy, inspect, interact, basically the full loop. The flow is deliberately shaped to match Foundry, so if you have ever used it, you pretty much already know how to use otigen, and the learning curve stays soft for everyone else too. For Rust devs in particular, otigen ships a small set of vendor helper macros into the scaffolded projects, just to take the boilerplate out of the way so you can stay focused on the contract. And while the public testnet is still baking, the local devnet is fully alive today. One command and you have a chain running on your machine. Deploy contracts, send native PYDE between accounts, manage your wallet keystore, watch your transactions land, the full loop, locally, on your laptop. Wanna try it out? book.pyde.network/otigen/ins… Soon, otigen will open up for public collaboration. If you have experience in a language not in the list yet (Zig, I am looking at you😎), or you want to write macros that improve the DX for your stack, there will be room for you. Everything follows a canonical spec you can read here: book.pyde.network/companion/… And if anything in here is unclear or you just want to talk about it, my DMs are open. ps — the old otigen language book is still up if you want to peek at the prehistory: github.com/pyde-net/otigen-b…