More gaps:
• .NET CLI bytecode
• Renesas RXv1/v2/v3
• Mitsubishi M32R / MELPS740
• Analog Devices ADSP-218x
• Sony SPC700, unSP, Rockwell C39, etc.
Legacy DSPs & embedded MCUs need love.
1
7
Challenge accepted, captain🕯️🔮 I’m officially drawing a protective circle around my file tree as we speak I definitely don’t need any Python demons haunting my storage arrays today. Thanks for the heads up, senpai. I'll make sure to keep the altar clean of bytecode garbage 😂
1
1
10
x.com/withpyro/status/206439… this too. no one needs to check any bytecode for this lol fabric.mod.json/(neo)forge(d) equiv already tells you if a mod is client-side or not
Jun 9
once we’re sure this behaves reliably in the wild, we’re bringing it to automatic modpack installs too. badly packaged mods love pretending to be server-side, so we’ll inspect the actual byte-code instead of trusting a flaky user-provided tag.
1
33
Coinspect Security retweeted
When reviewing deployments and upgrades, devs need to verify that the bytecode deployed onchain matches the audited code.
We built EVM Mirror to solve this problem for complex deployments and security council work, and released it open source for the wider ecosystem.
1
10
47
9,790
Dedaub or heimdall-rs decompile the bytecode cleanly. But for a fresh v4 pool like this, the faster honeypot check is a fork - simulate a buy then an immediate sell at the current block. If the sell reverts or returns ~0, the trap's in the hook, verified or not.
1
1
43
LMAO, go ahead and light the virtual candles around the altar of the workspace!
Just make sure when you invoke that mystical Python 3 snake, you draw a massive protective circle around your file tree—otherwise, the second the spirit manifests, it’s going to manifest three hundred separate __pycache__ folders across your clean directories. It’s the ultimate diagnostic test for any occult ritual: if the demon leaves a trail of dynamic bytecode garbage behind, it’s not an ancient deity, it’s just an un-compiled runtime environment trying to haunt your storage arrays.
2
2
32
🤓☝️ como isso funciona?
graças à JVM (java virtual machine), uma máquina virtual responsável por executar o código Java.
ela interpreta o chamado bytecode e o adapta para o sistema operacional em uso, seja Windows, Linux ou macOS.
1
3
37
Immutable code cannot be patched.
This isn't a philosophical preference.
It's the only viable workflow when bytecode is permanent:
Audit before deploy. Not after.
Every shortcut around this rule has a body count.
1
16
any devs know how to decompile bytecode and look into how a unverified contract woks?
1
63
wdym by an "sdk" exactly?
If you mean a Rust library, with maybe some proc macros that spit out EVM bytecode that's essentially building an entire compiler just with a worse interface.
1
24
Nice to see more tooling that improves transparency and simplifies bytecode parity verification. Great addition to the ecosystem 🫡
And nice to see that Diffyscan was helpful 😊
When reviewing deployments and upgrades, devs need to verify that the bytecode deployed onchain matches the audited code.
We built EVM Mirror to solve this problem for complex deployments and security council work, and released it open source for the wider ecosystem.
5
132
Day 56 of Smart Contract Security⚔️
EVM internals done. Sixteen lessons. One layer deeper. 🔩
Huff. Opcodes. Bytecode. CODECOPY. CALLDATALOAD. SHR. Function dispatching. Stack. Memory. Storage.
Each one something Solidity quietly handles for you — which matters, because when you're tracing an exploit at the bytecode level, the abstraction disappears. Understanding what's underneath changes how you read contracts.
evm.codes used alongside. The opcodes aren't theoretical.
The EVM doesn't speak Solidity. It speaks opcodes. Auditors who learn both see what high-level readers miss. 🔬
1
6
61