XRPL Strong vs Weak Hook Execution Fees

XRPL Hooks support two types of execution: strong execution and weak execution. Understanding the difference between these execution modes is essential for accurately estimating transaction fees, as strong executions must be paid for by the transaction originator while weak executions operate under different fee rules.

Strong Hook execution occurs when a Hook is set to run as a mandatory part of transaction processing. When Hooks are strongly executed, the originating transaction must pay for all strong executions in the transaction fee. This means the fee payer must account for Hook execution costs on both the sending and receiving accounts involved in the transaction.

With up to 4 strong Hooks possible on each account (sender and receiver), a single transaction could theoretically require fees for 8 Hook executions plus the base transaction fee plus any emitted transaction fees. This is why running all transactions through the fee RPC call before submission is strongly recommended — manual fee calculation in this scenario is error-prone.

Transaction fees with the Hooks Amendment enabled become non-trivial to compute manually — always use the fee RPC endpoint to calculate the exact required fee for each transaction.

Weak Hook execution occurs when a Hook is configured to run in a non-blocking capacity. Weak executions do not prevent a transaction from proceeding even if the Hook encounters an error, and their fee implications differ from strong executions. Developers designing Hooks should carefully consider whether strong or weak execution is appropriate for each use case.

The choice between strong and weak execution affects not only fees but also the reliability guarantees of the Hook. Strong Hooks can block or modify transactions, while weak Hooks cannot. For financial automation use cases requiring guaranteed execution, strong Hooks are necessary — and their fee implications must be carefully accounted for in application design.