From 128134914ac5aee70e17ffa4095e3945a5bb9b9e Mon Sep 17 00:00:00 2001 From: freddmannen <56002059+freddmannen@users.noreply.github.com> Date: Tue, 4 Jul 2023 10:00:56 +0200 Subject: [PATCH] Delete uncle-bandits.md Outdated --- docs/flashbots-protect/rpc/uncle-bandits.md | 13 ------------- 1 file changed, 13 deletions(-) delete mode 100644 docs/flashbots-protect/rpc/uncle-bandits.md diff --git a/docs/flashbots-protect/rpc/uncle-bandits.md b/docs/flashbots-protect/rpc/uncle-bandits.md deleted file mode 100644 index 6b271b46..00000000 --- a/docs/flashbots-protect/rpc/uncle-bandits.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -title: uncle bandit risk ---- - -Transactions using Flashbots for frontrunning protection in theory never reach the public mempool and therefore should not be visible to bot operators until successfully included on-chain. However, if the block in which the transaction is included is uncled (honestly or maliciously), the transactions are revealed and can be targeted. This type of exploit is dubbed an “[uncle bandit](https://twitter.com/bertcmiller/status/1382673587715342339?s=20)”. On average, [1 in 20 blocks](https://ycharts.com/indicators/ethereum_uncle_rate) are uncled. - -In order to protect against uncle bandits, users looking for frontrunning protection should include a check on the parent hash in their transaction: - -```solidity -require(blockhash(block.number - 1) == expectedParentHash, "block was uncled"); -``` - -Note that this check needs to be done in the smart contract that you are interacting with, and is not widely supported at this time.