Hey @solana_devs , I’m building a Geyser plugin for ClickHouse! 🚀 The GitHub link is in the thread. Would love some feedback—it's still in development. The motivation? @SolanaFndn previously opened an RFC for an end-to-end open-source indexer supporting ClickHouse & Google.

RT @shek_dev: @ParvatRajSingh Checkout Saga pattern I would also recommend learning how phased commits work (2pc/3….

What's the best way to implement ACID properties for a sequence of tasks, where a failure in any one task should trigger a rollback of all previously completed ones? For instance, one of the tasks might include writing 'X' to a remote database over the network. If anyone has.

I was checking out blogs on Solana dev tools for 2025, and LamportDAO IDE keeps popping up. Is it a real web-based IDE, or just some AI hallucination that's snuck into these posts?. @SuperteamIN @IrffanAsiff @paarugsethi

A Deep Dive into 2025's Thriving Solana Developer Tooling Ecosystem

Thanks for reading! Let me know if I missed anything important or if there's something you'd add.

6. Transmute. "Get out of our way type system! We're going to reinterpret these bits or die trying!" - This is the exaclt starting of the topic. Give it a read you will enjoy it:

5. References & aliasing. Rust’s Core Rule: Either multiple immutable references or one mutable reference—never both. Read More: Ch 3 of nomicon.

4. Representation (repr). In Rust, #[repr(. )] is an attribute that controls the memory representation (layout) of a type. It tells the compiler how to arrange data in memory, which is critical for scenarios like FFI, hardware interaction, or zero-copy deserialization of byte.

3. Global allocator. In no_std or embedded contexts, you can’t use Rust’s default allocator. Implementing GlobalAlloc and tagging it with #[global_allocator] lets you control heap behavior. Read More:

2. Raw pointer dereference. Raw pointers (*const T, *mut T) let you sidestep the borrow checker. But dereferencing them with *ptr is unsafe because you must manually ensure:.- the pointer is not null.- it's aligned.- it points to initialized memory.- and lives long enough.

1. In Rust, unsafe unlocks 5 superpowers (and nothing else):.- Dereference raw pointers.- Call unsafe functions.- Access/modify static mut variables.- Implement unsafe traits.- Access union fields. read more:

If you're diving into the Pinocchio codebase, here are some core unsafe Rust concepts that will come in handy. - 5 things we can do in unsafe Rust.- Raw pointer dereference.- Global allocator (GlobalAlloc, #[global_allocator]).- repr attributes (repr(C), repr(u8), etc.).-.

Learned today that @anza's Pinocchio name is inspired by the Disney Pinocchio, with "no strings attached.".Here's the link if you're interested:

RT @heliuslabs: Read the full article here:.

RT @OkohEbina: Here are the Solana issues Dean highlighted, dubbed Dean's List:. Link:

RT @shl: Thinking before you speak is a skill.

RT @Pratikdevv: Finally shipping Anchor Studio – a visual interface for your Solana programs. Explore accounts.Invoke instructions.View pa….

Aliasing XOR Mutability.

RT @jarredsumner: little-known feature of Bun. ```.await import(“any-npm-package@version”).```.