---
title: "Alessio Giannini (@alessiogiannini) | Hashnode"
description: "I'm Alessio Giannini, a Blockchain &amp; MEV Engineer with a background in enterprise software development, now focused on DeFi, MEV, protocol economics, and..."
url: "https://hashnode.com/@alessiogiannini"
---

@alessiogiannini

# Alessio Giannini

@alessiogiannini · Joined March 2026

## Comments

[Thanks for the comment. For anyone seriously working on execution and MEV, the real difficulty is never the single strategy, it's the environment it runs in and how the two influence each other. If you're building something concrete in this space, feel free to reach out directly, I'd be curious to see what you're working on](https://hashnode.com/posts/what-mev-actually-taught-me/6a311af9276567fa4e35a999/comment/6a3276253bc775e0f006db08#reply-6a32a0bfb194649be5e5b50e)

Reply · Article · Jun 17 · [What MEV Actually Taught Me](https://hashnode.com/posts/what-mev-actually-taught-me/6a311af9276567fa4e35a999)

[What you're describing matches exactly the nonce replacement mechanism documented in the article. Bots would send an empty transaction right after block finalization to secure a position in the mempool, then once they spotted a victim transaction, they would replace it using the same nonce but with a higher dispatch class. The separate EVM channel then ensured that transaction would be included before the victim regardless of arrival order. With MEV Shield and the fixes introduced by the Bittensor team, these attack vectors have been mitigated. What do you mean specifically by latent bots and anti-MEV bots?](https://hashnode.com/posts/how-sandwich-bots-extracted-value-from-every-stake-on-bittensor/69d36f57d3f86adca20101db/comment/6a26eba20cd5e614032e235b#reply-6a31283340a5665f311e2925)

Reply · Article · Jun 16 · [How Sandwich Bots Extracted Value from Every Stake on Bittensor](https://hashnode.com/posts/how-sandwich-bots-extracted-value-from-every-stake-on-bittensor/69d36f57d3f86adca20101db)
