From 50a2d6a04682c03696f89af921a1bfbf8a4f1986 Mon Sep 17 00:00:00 2001 From: Quintus Date: Wed, 18 Nov 2026 21:09:26 +0000 Subject: [PATCH 1/4] docs(protect): correct status API page (retention, disclosed fields, simError names, drop Sepolia) Co-Authored-By: Claude Fable 5.2 --- .../additional-documentation/status-api.md | 27 +++++++------------ 1 file changed, 10 insertions(+), 17 deletions(-) diff --git a/docs/flashbots-protect/additional-documentation/status-api.md b/docs/flashbots-protect/additional-documentation/status-api.md index fff1195af..fe989109e 100644 --- a/docs/flashbots-protect/additional-documentation/status-api.md +++ b/docs/flashbots-protect/additional-documentation/status-api.md @@ -4,14 +4,7 @@ title: Transaction Status API Transactions that you submit to Flashbots Protect won't be observable in the public mempool. However, you can use our status API to check the status of your transactions. The URL for doing so is: `https://protect.flashbots.net/tx/YOUR_TX_HASH_HERE`, and you can also use Etherscan as you normally would for transactions. They will show the status of your transaction from the status API as well. -The Transaction Status API is also available on test networks. Below is a table of URLs for accessing the API across different networks: - -| Network | URL | -| -------- | -------------------------------------------------- | -| Mainnet | `https://protect.flashbots.net/tx/` | -| Sepolia | `https://protect-sepolia.flashbots.net/tx/` | - - +The status API covers transactions sent through the Protect RPC, and keeps each transaction for about one hour after it was received. After that it returns `UNKNOWN`. In turn you will receive a JSON response that looks like the following: @@ -45,11 +38,11 @@ Below is a table of status codes that can be returned: | `INCLUDED` | The transaction was included on-chain | | `FAILED` | The transaction was submitted for 25 blocks and failed to be included on-chain | | `CANCELLED` | The transaction was cancelled by the user and not included on-chain | -| `UNKNOWN` | The transaction was not received | +| `UNKNOWN` | The transaction was not received, or was received more than about an hour ago | ## Privacy -The `transaction` fields are disclosed only for transactions with an `INCLUDED` status to maintain privacy for trades that are pending, failed, or cancelled. These fields will remain empty for transactions with `PENDING`, `FAILED`, `UNKNOWN`, or `CANCELLED` statuses. Protect fast mode transactions are an exception to this rule as TEE searchers will receive all fields (without signature) for all transactions, including reverted or failed transactions, with a 5 minute delay for troubleshooting and debugging purposes. +For Protect fast mode transactions, TEE searchers will receive all fields (without signature) for all transactions, including reverted or failed transactions, with a 5 minute delay for troubleshooting and debugging purposes. For instance, once a transaction is included, the JSON response will be populated with data for all fields: @@ -79,12 +72,12 @@ Below is the table of currently supported `simError` values. | Sim error | Description | |------------------------------|---------------------------------------------------------------------------------------------| -| `SimErrorMaxFeePerGasTooLow` | Consensus incompatible tx that wasn't caught on rpc | -| `SimErrorInsufficientFunds` | Insufficient ETH balance to pay for gas | -| `SimErrorNonceTooLow` | Nonce too low | -| `SimErrorNonceTooHigh` | Nonce too high | -| `SimErrorInvalidChainId` | Consensus incompatible tx that wasn't caught on rpc | -| `SimErrorExecutionReverted` | Execution reverted (slippage tolerance exceeded). Check revertReason field for more details | -| `SimErrorOutOfGas` | Ran out of gas during execution (gas limit too low) | +| `MaxFeePerGasTooLow` | Consensus incompatible tx that wasn't caught on rpc | +| `InsufficientFunds` | Insufficient ETH balance to pay for gas | +| `NonceTooLow` | Nonce too low | +| `NonceTooHigh` | Nonce too high | +| `InvalidChainId` | Consensus incompatible tx that wasn't caught on rpc | +| `ExecutionReverted` | Execution reverted (slippage tolerance exceeded). Check revertReason field for more details | +| `OutOfGas` | Ran out of gas during execution (gas limit too low) | `revertReason` field is a valid utf-8 part of the simulation result. Example: `TRANSFER_FROM_FAILED`, `UniswapV2: INSUFFICIENT_OUTPUT_AMOUNT` From 2af8b11a27592bead07e991960fd1fa240ce76a9 Mon Sep 17 00:00:00 2001 From: Quintus Date: Wed, 18 Nov 2026 21:16:57 +0000 Subject: [PATCH 2/4] docs(protect): state 45 minute retention, link TEE images Co-Authored-By: Claude Fable 5.2 --- .../additional-documentation/status-api.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/flashbots-protect/additional-documentation/status-api.md b/docs/flashbots-protect/additional-documentation/status-api.md index fe989109e..d6cacf0b5 100644 --- a/docs/flashbots-protect/additional-documentation/status-api.md +++ b/docs/flashbots-protect/additional-documentation/status-api.md @@ -4,7 +4,7 @@ title: Transaction Status API Transactions that you submit to Flashbots Protect won't be observable in the public mempool. However, you can use our status API to check the status of your transactions. The URL for doing so is: `https://protect.flashbots.net/tx/YOUR_TX_HASH_HERE`, and you can also use Etherscan as you normally would for transactions. They will show the status of your transaction from the status API as well. -The status API covers transactions sent through the Protect RPC, and keeps each transaction for about one hour after it was received. After that it returns `UNKNOWN`. +The status API covers transactions sent through the Protect RPC, and keeps each transaction for 45 minutes after it was received. After that it returns `UNKNOWN`. In turn you will receive a JSON response that looks like the following: @@ -38,11 +38,11 @@ Below is a table of status codes that can be returned: | `INCLUDED` | The transaction was included on-chain | | `FAILED` | The transaction was submitted for 25 blocks and failed to be included on-chain | | `CANCELLED` | The transaction was cancelled by the user and not included on-chain | -| `UNKNOWN` | The transaction was not received, or was received more than about an hour ago | +| `UNKNOWN` | The transaction was not received, or was received more than 45 minutes ago | ## Privacy -For Protect fast mode transactions, TEE searchers will receive all fields (without signature) for all transactions, including reverted or failed transactions, with a 5 minute delay for troubleshooting and debugging purposes. +For Protect fast mode transactions, TEE searchers will receive all fields (without signature) for all transactions, including reverted or failed transactions, with a 5 minute delay for troubleshooting and debugging purposes. The TEE environment serves as a frontrunning countermeasure. You can learn more at [flashbots-images](https://github.com/flashbots/flashbots-images). For instance, once a transaction is included, the JSON response will be populated with data for all fields: From 8d49fcde674ba2c7c427d02add34506a34beb022 Mon Sep 17 00:00:00 2001 From: Quintus Date: Wed, 18 Nov 2026 21:19:40 +0000 Subject: [PATCH 3/4] docs(protect): simError names from the status API source, drop Sepolia RPC row Co-Authored-By: Claude Fable 5.2 --- docs/flashbots-protect/additional-documentation/status-api.md | 3 ++- docs/flashbots-protect/quick-start.mdx | 3 +-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/flashbots-protect/additional-documentation/status-api.md b/docs/flashbots-protect/additional-documentation/status-api.md index d6cacf0b5..030c86a29 100644 --- a/docs/flashbots-protect/additional-documentation/status-api.md +++ b/docs/flashbots-protect/additional-documentation/status-api.md @@ -76,8 +76,9 @@ Below is the table of currently supported `simError` values. | `InsufficientFunds` | Insufficient ETH balance to pay for gas | | `NonceTooLow` | Nonce too low | | `NonceTooHigh` | Nonce too high | -| `InvalidChainId` | Consensus incompatible tx that wasn't caught on rpc | +| `InvalidChainIdForSigner` | Consensus incompatible tx that wasn't caught on rpc | | `ExecutionReverted` | Execution reverted (slippage tolerance exceeded). Check revertReason field for more details | | `OutOfGas` | Ran out of gas during execution (gas limit too low) | +| `Other` | Any other simulation error | `revertReason` field is a valid utf-8 part of the simulation result. Example: `TRANSFER_FROM_FAILED`, `UniswapV2: INSUFFICIENT_OUTPUT_AMOUNT` diff --git a/docs/flashbots-protect/quick-start.mdx b/docs/flashbots-protect/quick-start.mdx index 9d2e87f45..f7a078e7b 100644 --- a/docs/flashbots-protect/quick-start.mdx +++ b/docs/flashbots-protect/quick-start.mdx @@ -70,12 +70,11 @@ You can also add Flashbots Protect RPC manually in MetaMask by following these s ![mm_rpc](/img/mm_rpc.png) -Below is the list of Flashbots Protect RPCs we currently support across Ethereum mainnet and testnets: +Below is the Flashbots Protect RPC we currently support on Ethereum mainnet: | Network | URL | | ------- | ------------------------------------ | | Mainnet | `https://rpc.flashbots.net/fast` | -| Sepolia | `https://rpc-sepolia.flashbots.net/` | ## Stuck transactions From 65a8bb5ae671c92be36e3711d9ad135adbee9836 Mon Sep 17 00:00:00 2001 From: Quintus Date: Wed, 18 Nov 2026 21:22:23 +0000 Subject: [PATCH 4/4] docs(protect): show transaction fields in the PENDING status example Co-Authored-By: Claude Fable 5.2 --- .../additional-documentation/status-api.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/docs/flashbots-protect/additional-documentation/status-api.md b/docs/flashbots-protect/additional-documentation/status-api.md index 030c86a29..9def529f9 100644 --- a/docs/flashbots-protect/additional-documentation/status-api.md +++ b/docs/flashbots-protect/additional-documentation/status-api.md @@ -14,13 +14,13 @@ In turn you will receive a JSON response that looks like the following: "hash": "YOUR_TX_HASH", "maxBlockNumber": 13543898, "transaction": { - "from": "", - "to": "", - "gasLimit": "", - "maxFeePerGas": "", - "maxPriorityFeePerGas": "", - "nonce": "", - "value": "" + "from": "0xEA674fdDe714fd979de3EdF0F56AA9716B898ec8", + "to": "0xac03bb73b6a9e108530aff4df5077c2b3d481e5a", + "gasLimit": "21000", + "maxFeePerGas": "300", + "maxPriorityFeePerGas": "10", + "nonce": "41", + "value": "10000000000" }, "fastMode": true, // for backwards compatibility; may be removed in a future version "seenInMempool": false, @@ -44,7 +44,7 @@ Below is a table of status codes that can be returned: For Protect fast mode transactions, TEE searchers will receive all fields (without signature) for all transactions, including reverted or failed transactions, with a 5 minute delay for troubleshooting and debugging purposes. The TEE environment serves as a frontrunning countermeasure. You can learn more at [flashbots-images](https://github.com/flashbots/flashbots-images). -For instance, once a transaction is included, the JSON response will be populated with data for all fields: +Once a transaction is included, the JSON response looks like the following: ```json {