Coin Brief ENDE

rippled now bills the simulate RPC at the heavy burden level of sign

The rippled repository merged pull request 6841 on 4 November, a fix to how the server's resource manager charges the simulate RPC method. The method had been charged at feeMediumBurdenRPC; it is now charged at feeHeavyBurdenRPC, the level already used for sign and sign_for. The change fixes issue 6801.

According to the pull request, the bug has existed since the simulate endpoint was introduced. Simulate performs full transaction execution: it autofills fields, parses the JSON into a transaction object, creates a copy of the open ledger view and runs the transaction through the transaction queue's apply logic, including preclaim and apply. That is substantially more work than submitting a pre-signed transaction blob, which only deserialises and queues, yet both were charged the same medium burden.

The pull request describes the consequence as a partial denial-of-service risk. Because rate limiting works on resource charges, a low charge for an expensive call lets a client send more simulate requests before limits apply than the CPU and memory cost would justify, exhausting server resources disproportionately. The root cause was a single line in the handler that set the load type to the medium level.

The author marks the change as neither a new feature nor a breaking change to the public API. Operators running public rippled servers get the fix with the next release that includes it.

rippled now bills the simulate RPC at the heavy burden level of sign
rippled now bills the simulate RPC at the heavy burden level of sign — Coin Brief

What it means

Public XRPL servers price every call they accept. A simulation endpoint is useful precisely because it does the full work, so it has to be billed like it.

Primary source
rippled pull request 6841
https://github.com/XRPLF/rippled/pull/6841