dc 🦇🔊 (@dappcoder_) 's Twitter Profile
dc 🦇🔊

@dappcoder_

smart contract engineer | #solidity, #move, #cadence.

ID: 1207661324379013120

calendar_today19-12-2019 13:58:04

1,1K Tweet

671 Takipçi

2,2K Takip Edilen

Securr (@securrtech) 's Twitter Profile Photo

Master Solidity in 2025 🚀🔥 The Learning Tree 🌳⚡️ |── Step 1: Solidity Fundamentals | ├── Data types & variables | ├── Functions & visibility | ├── Events & modifiers | ├── Structs & enums | ├── Mappings & arrays | └── Solidity memory vs storage | |──

dc 🦇🔊 (@dappcoder_) 's Twitter Profile Photo

I lost my gem—my grandfather (1933-2025). He was my greatest inspiration. Who we are today is a result of his hard work and values. He always used to tell me to focus, work hard, and stay on the right path. Miss you, Grandpa. Thank you for everything. 💙

0xb0k0 (@bo4ka7a) 's Twitter Profile Photo

If you really want to deep dive in the EVM and Ethereum specifications, I highly recommend taking a look at this repo github.com/ethereum/execu… It contains the specifications related to the Ethereum execution client. It sure is a more challenging read, but really worth the time

dc 🦇🔊 (@dappcoder_) 's Twitter Profile Photo

I discovered a fantastic tool recently! I used to rely on Excalidraw, which is great, but now I've found tldraw. What's even better is that you can use it directly in VS Code while writing code — super convenient and impressive!

Solidity (@solidity_lang) 's Twitter Profile Photo

The EVM Object Format (EOF) is a long-awaited upgrade for the EVM. We wrote about our stance in support of it. Topics to expect in the post: ✧ Benefits of EOF ✧ Is EOF the only way? ✧ Can we solve "Stack Too Deep" without EOF? ✧ Why not EIP-615/EIP-2315? ✧ Do we really need

dc 🦇🔊 (@dappcoder_) 's Twitter Profile Photo

Yap early, yap only, yap often. Kaito AI 🌊 is connecting AI, attention and capital with Yaps. Just claimed my social card and I'm accumulating Yap points in real-time. Claim yours 👉 yaps.kaito.ai/referral/12076…

dc 🦇🔊 (@dappcoder_) 's Twitter Profile Photo

What does `\x19Ethereum Signed Message:\n32` mean in Solidity? If you've ever verified signatures on-chain, you might’ve seen this strange-looking string:- "\x19Ethereum Signed Message:\n32" It’s not random — it’s a prefix defined by EIP-191, used to make signed messages