Scenario: I connect to an API endpoint and repeatedly send transactions (with
cleos) which are all ultimately rejected with
Such transactions don't seem to eat up CPU or network resources of my account.
Still, the API endpoint has to actually execute the code to get to the assertion, so it consumes at least the CPU of the endpoint.
In practice, after a few such API calls, I'm getting the "overdrawn balance" response, as if my CPU or network resource was spent. But it persists only for a few seconds. And no spendings are reflected on my account details.
So, what is the mechanism for the API endpoint to limit the transactions which actually don't make it because of failed assertions?