diff --git a/docs/02-developers/03-blockchain-essentials/02-overview/index.md b/docs/02-developers/03-blockchain-essentials/02-overview/index.md
index f4ca8595..27573244 100644
--- a/docs/02-developers/03-blockchain-essentials/02-overview/index.md
+++ b/docs/02-developers/03-blockchain-essentials/02-overview/index.md
@@ -89,7 +89,19 @@ Note that when `eth_estimateGas` is called, the node simulates the transaction e
 The simulation runs through the entire transaction process as if it were being executed, including checking for sufficient balance, contract code execution, etc.
 During the simulation, the method calculates the exact amount of gas that would be consumed by the transaction if it were to be executed on the blockchain. The estimated gas amount is returned, helping users set an appropriate gas limit for the actual transaction.
 
-There is a difference in Rootstock compared to Ethereum, and it is that if one of the steps of the simulated transaction fails, the node will return the gas estimation needed for the transaction, while on Ethereum, the node will return an error instead of the gas estimation.
+:::info[Info]
+
+**Prior to Arrowhead 6.5.0**, there was a difference in Rootstock compared to Ethereum:
+
+- If one of the steps of the simulated transaction fails, the node would return the gas estimation needed for the transaction
+- On Ethereum, the node would return an error instead of the gas estimation. 
+
+**Starting with Arrowhead 6.5.0:**
+
+- Rootstock will behave same way as Ethereum's behavior for simulated transaction failures.
+- If a simulated transaction step fails, the node will now return an error, mirroring Ethereum's response.
+
+:::
 
 You can see this behavior in the following example, where a call for `eth_estimateGas` on a transaction that would be executed from an address without enough balance.
 
diff --git a/docs/02-developers/07-rpc-api/02-rootstock/02-methods.md b/docs/02-developers/07-rpc-api/02-rootstock/02-methods.md
index cdff10a7..0e1dffd5 100644
--- a/docs/02-developers/07-rpc-api/02-rootstock/02-methods.md
+++ b/docs/02-developers/07-rpc-api/02-rootstock/02-methods.md
@@ -199,7 +199,19 @@ Note that when `eth_estimateGas` is called, the node simulates the transaction e
 The simulation runs through the entire transaction process as if it were being executed, including checking for sufficient balance, contract code execution, etc.
 During the simulation, the method calculates the exact amount of gas that would be consumed by the transaction if it were to be executed on the blockchain. The estimated gas amount is returned, helping users set an appropriate gas limit for the actual transaction.
 
-There is a difference in Rootstock compared to Ethereum, and it is that if one of the steps of the simulated transaction fails, the node will return the gas estimation needed for the transaction, while on Ethereum, the node will return an error instead of the gas estimation.
+:::info[Info]
+
+**Prior to Arrowhead 6.5.0**, there was a difference in Rootstock compared to Ethereum:
+
+- If one of the steps of the simulated transaction fails, the node would return the gas estimation needed for the transaction
+- On Ethereum, the node would return an error instead of the gas estimation. 
+
+**Starting with Arrowhead 6.5.0:**
+
+- Rootstock will behave same way as Ethereum's behavior for simulated transaction failures.
+- If a simulated transaction step fails, the node will now return an error, mirroring Ethereum's response.
+
+:::
 
 You can see this behavior on the following example, where we call `eth_estimateGas` for a transaction that would be executed from an address without enough balance.
 
diff --git a/docs/03-node-operators/03-json-rpc/01-methods.md b/docs/03-node-operators/03-json-rpc/01-methods.md
index f9e9d8c3..6abfbb38 100644
--- a/docs/03-node-operators/03-json-rpc/01-methods.md
+++ b/docs/03-node-operators/03-json-rpc/01-methods.md
@@ -1089,7 +1089,19 @@ Note that when `eth_estimateGas` is called, the node simulates the transaction e
 The simulation runs through the entire transaction process as if it were being executed, including checking for sufficient balance, contract code execution, etc.
 During the simulation, the method calculates the exact amount of gas that would be consumed by the transaction if it were to be executed on the blockchain. The estimated gas amount is returned, helping users set an appropriate gas limit for the actual transaction.
 
-There is a difference in Rootstock compared to Ethereum, and it is that if one of the steps of the simulated transaction fails, the node will return the gas estimation needed for the transaction, while on Ethereum, the node will return an error instead of the gas estimation.
+:::info[Info]
+
+**Prior to Arrowhead 6.5.0**, there was a difference in Rootstock compared to Ethereum:
+
+- If one of the steps of the simulated transaction fails, the node would return the gas estimation needed for the transaction
+- On Ethereum, the node would return an error instead of the gas estimation. 
+
+**Starting with Arrowhead 6.5.0:**
+
+- Rootstock will behave same way as Ethereum's behavior for simulated transaction failures.
+- If a simulated transaction step fails, the node will now return an error, mirroring Ethereum's response.
+
+:::
 
 You can see this behavior on the following example, where we call `eth_estimateGas` for a transaction that would be executed from an address without enough balance.
 
diff --git a/docs/03-node-operators/03-json-rpc/05-management-api-methods.md b/docs/03-node-operators/03-json-rpc/05-management-api-methods.md
index 78d9e558..87da8475 100644
--- a/docs/03-node-operators/03-json-rpc/05-management-api-methods.md
+++ b/docs/03-node-operators/03-json-rpc/05-management-api-methods.md
@@ -32,8 +32,8 @@ description: "The JSON-RPC methods supported by Rootstock nodes."
 | `debug_startGoTrace` | NO | |
 | `debug_stopGoTrace` | NO | |
 | `debug_traceBlock` | NO | |
-| `debug_traceBlockByNumber` | NO | |
-| `debug_traceBlockByHash` | NO | |
+| `debug_traceBlockByNumber` | YES | |
+| `debug_traceBlockByHash` | YES | |
 | `debug_traceBlockFromFile` | NO | |
 | `debug_traceTransaction` | YES | |
 | `debug_vmodule` | NO | |