What happens after you call a contract?
Follow calldata into bytecode, inspect a transaction trace, and see how the execution context changes between calls.
Explore the EVM writing →About
I am Andrey Obruchkov, a blockchain engineer and protocol builder.
My work has involved smart contract integrations, DEX tooling, multichain wallets, infrastructure, protocol-level debugging, Go, and Rust. A large part of that work required going beyond documentation: reading implementations, tracing transactions, and understanding what happens when assumptions meet a real network.
0xByteBeetle is the name I write under when exploring blockchain internals. I start with a question, follow the mechanism, and use examples to make it easier to see. The writing is for technical people, whether you build software, work with blockchain systems, or simply want to understand them.
The articles let you follow one question at a time. The bootcamps bring related ideas together into a longer path with exercises and projects. EVM is the first course track; the publication also explores Solana and Hyperliquid, with room for other chains as the work grows.
The questions I follow
Follow calldata into bytecode, inspect a transaction trace, and see how the execution context changes between calls.
Explore the EVM writing →Start with accounts, then connect their data to instructions, serialization, and token extensions.
Explore the Solana writing →Look at HyperCore and HyperEVM, and how Hyperliquid’s architecture connects them.
Explore the Hyperliquid writing →Elsewhere