You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I modified the recursive invocation example so that instead of starting the bomb by explicitly calling the bomb function on the contract, it's kicked off in on_money_received. To set up the bomb first set_own_id is called to allow the contract to store the id for recursive invocation.
I expected this to behave like the example, expending all of the senders account PERLS in gas fees; though this would be even more nefarious because it's kicked off from a simple pay [address] [ammount] call.
Actual behavior: The contract is recursively invoked as expected but the gas is never deducted from the caller (see the logs in the gist above).
I'm not sure what the desired behavior here is; maybe the gas not being deducted is a feature to protect senders from this kind of attack? Will this terminate eventually when some max recursion limit is hit? I left it running on my local test net for about 5 minutes with no end in sight.
The text was updated successfully, but these errors were encountered:
Will be looking over this over the next week; what you've reported definitely seems to be unintended behavior (the gas should be counted, and sender should be deducted PERLs as gas fees).
I modified the recursive invocation example so that instead of starting the bomb by explicitly calling the
bomb
function on the contract, it's kicked off inon_money_received
. To set up the bomb firstset_own_id
is called to allow the contract to store the id for recursive invocation.gist Here
I expected this to behave like the example, expending all of the senders account PERLS in gas fees; though this would be even more nefarious because it's kicked off from a simple
pay [address] [ammount]
call.Actual behavior: The contract is recursively invoked as expected but the gas is never deducted from the caller (see the logs in the gist above).
I'm not sure what the desired behavior here is; maybe the gas not being deducted is a feature to protect senders from this kind of attack? Will this terminate eventually when some max recursion limit is hit? I left it running on my local test net for about 5 minutes with no end in sight.
The text was updated successfully, but these errors were encountered: