Nishant

@notcodesid @SuperteamIN @solana @tryprovenn Congrats brother 🎉

we’ve won the @solana audit subsidy for Proven @tryprovenn. this helps cover part of our smart contract audit as we prepare the protocol for real users. started as a simple idea: what if an accountability app let you bet on your goals? excited to make Proven secure and ready for launch soon.

@abhijitwt crazy

someone made a city called gitcity where every building represents a github account and its height depends on their contributions 😭😭 you can even place ads there as well crazy idea

@naval AI

It’s not about junior vs senior, it’s about “good with AI” vs “not good with AI.”

I used to think Traits in Rust were scary. Every time I saw: trait Something { ... } I felt like… okay this is advanced stuff. But honestly? Traits are just rules. That’s it. If I say: “Anything that can speak must have a speak() function.” That’s a trait. Then, a User can implement it. A Robot can implement it (crazy, right?) Even a Solana Validator (why not 😄) Different types. Same behaviour. No inheritance. No classes. Just a contract. ``` trait Speak { fn speak(&self); } ``` And when I understood this, a lot of Rust started making sense. Generics. Constraints. Even Anchor’s #[derive(Accounts)]. Traits are just Rust’s way of saying: “If you promise this behaviour, I’ll allow you to use it here.” That’s it. Nothing magical. Just agreements between types. Interesting, right?

First time writing an article about Rust Macros I'm still improving my writing, but I wanted to share what I learned. In this article, I explain how understanding Rust macros helps in writing Anchor program on @solana. If I made any mistake, I'd really appreciate feedback. @solanaturbine @SuperteamIN

When I first saw unsafe in Rust… I thought: “Wait… isn’t Rust supposed to be SAFE?” 😅 The word literally says unsafe. It felt like breaking the rules. But then I understood something important. Rust protects us by default: • No null pointer crashes • No random memory bugs • No data races It acts like a strict teacher. But sometimes… We need full control. Like when: - You work with low-level memory - You call C code (FFI) - You optimize for performance That’s where unsafe comes in. It doesn’t mean “dangerous code”. It means: “I know what I’m doing. Trust me.” Inside an unsafe block, Rust stops checking some rules. Now the responsibility is mine. That’s powerful. And that’s why Rust works so well for systems programming and even blockchains like Solana. Safe by default. Power when needed. Responsibility always. That balance is beautiful. @rustlang

journey

looks good app.skillsync.wiki/profile/nishan…

Why liteSVM ? @solanaturbine

@SuperteamIN 😀

you are not bullish enough

Day 1 at Arena. I learned about Token Extensions during the @solanaturbine accelerator program orientation so, implemented a token in Rust to understand its design and practical use cases. explorer.solana.com/address/98f3Ps… #Solana #Rust

Lecture 6: Practical Guide to SVM with @rektoff_xyz Built solid intuition in a week and broke it all in today’s class Grateful for the amazing session by @danielkcumming 🙌

@SuperteamCAN Rust always 😎

We’re curious, comment below which one you’re choosing: THIS: Learn Rust and go deep THAT: Start with no-code / low-code tools

@notcodesid 👏

getting a job at FAANG is overrated. just want to be forbes 30 under 30

Accelerated orientation @solanaturbine

Is it enough for @solanaturbine accelerated program? Finally completed! 💪🏽

Lecture 5: Solana Virtual Machine (SVM) @rektoff_xyz Today’s live class focused on memory layout and execution flow in SVM. Understanding how programs actually run on Solana makes everything clearer #Solana #SVM #Rust #Web3 #LearningInPublic

Rust Ownership finally clicked today. Exclusive ownership & XOR mutability Lesson 4: Ownership & Memory Safety @rektoff_xyz

@tryprovenn @CyreneAI 🔥