docs: Add new features

Author: marioevz

docs/running_tests/execute/hive.md

@@ -4,12 +4,20 @@ Tests can be executed on a local hive-controlled single-client network by runnin
 
 ## The `eest/execute-blobs` Simulator
 
-The `blob_transaction_test` execute test spec sends blob transactions to a running client in order to verify its `engine_getBlobsVX` endpoint behavior. These tests can be run using:
+The `blob_transaction_test` execute test spec sends blob transactions to a running client. Blob transactions are fully supported in execute mode:
+
+- Blob transactions can be sent via `eth_sendRawTransaction`
+- Blob validation via `engine_getBlobsVX` endpoints (when Engine RPC available)
+- Automatic gas pricing for blob gas fees
+
+Tests can be run using:
 
 ```bash
 ./hive --client besu --client-file ./configs/osaka.yaml --sim ethereum/eest/execute-blobs
 ```
 
+**Note**: If Engine RPC is unavailable, blob transactions will be sent but `getBlobsV*` validation is skipped.
+
 See [Hive](../hive/index.md) for help installing and configuring Hive.
 
 ## Running `execute` tests with Hive in Dev Mode

docs/running_tests/execute/index.md

@@ -39,4 +39,12 @@ Reasoning behind the random generation of the sender keys is that one can execut
 
 The `fill` plugin will use a fixed and minimum gas price for all the transactions it uses for testing, but this is not possible with the `execute` plugin, as the gas price is determined by the current state of the network.
 
-At the moment, the `execute` plugin does not query the client for the current gas price, but instead uses a fixed increment to the gas price in order to avoid the transactions to be stuck in the mempool.
+The `execute` plugin queries the network for current gas prices and defaults to 1.5x the network price to ensure transaction inclusion. Gas prices can be overridden via command-line flags (`--default-gas-price`, `--default-max-fee-per-gas`, `--default-max-priority-fee-per-gas`).
+
+### Deferred EOA Funding
+
+EOAs are funded after gas prices are determined, enabling accurate balance calculations based on actual network conditions. This ensures sufficient funds are allocated for all test transactions.
+
+### Blob Transaction Support
+
+Blob transactions are fully supported in execute mode, including automatic gas pricing for blob gas fees and validation via `engine_getBlobsVX` endpoints when Engine RPC is available.

docs/running_tests/execute/remote.md

@@ -24,6 +24,41 @@ One last requirement is that the `--chain-id` flag is set to the chain id of the
 uv run execute remote --fork=Prague --rpc-endpoint=https://rpc.endpoint.io --rpc-seed-key 0x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f --chain-id 12345
 ```
 
+## Test Accounts and Contracts
+
+Since `execute remote` does not control the blockchain where it runs the tests, and therefore cannot modify the genesis pre-allocation like `fill` does, all accounts and contracts need to be deployed via transactions sent to the network.
+
+These transactions are created from the seed or worker accounts provided via the command flags.
+
+When the test is executed, all instances of `pre.fund_eoa` and `pre.deploy_contract` calls, instead of placing the account directly in the `pre` object like `fill` does, they generate transactions that result in the creation of the accounts when executed on chain.
+
+The transactions are collected and only sent after the test function finishes execution. This is done in order to perform optimizations based on the transactions that the test requires to perform its verifications.
+
+One optimization is the deferred calculation of the funding amount for the EOA, which is calculated on the fly depending the test transactions that use the account as sender, and this amount is the minimum balance that the account would need in order for the transactions to be included given the current network gas prices.
+
+### Dry Run Mode
+
+Calculate minimum balance requirements without executing any transactions on chain:
+
+```bash
+uv run execute remote --fork=Prague --rpc-endpoint=https://rpc.endpoint.io --dry-run ./tests/prague/eip7702_set_code_tx/
+```
+
+This outputs the minimum balance needed and total gas consumption per test, useful for:
+- Estimating costs before execution
+- Verifying seed account has sufficient funds
+- Planning parallel execution funding requirements
+
+### Limit Gas Used By Tests
+
+A limit of the total gas consumption per test can be specified with the `--max-gas-per-test` flag:
+
+```bash
+uv run execute remote --fork=Prague --rpc-endpoint=https://rpc.endpoint.io --max-gas-per-test 30000000 --rpc-seed-key 0x... --chain-id 12345
+```
+
+Tests exceeding this limit will fail with an assertion error and will not send any transactions to the chain.
+
 ## Engine RPC Endpoint (Optional)
 
 By default, the `execute remote` command assumes that the execution client is connected to a beacon node and the chain progresses automatically. However, you can optionally specify an Engine RPC endpoint to drive the chain manually when new transactions are submitted.