Reject spend tx immediately if the recipient contract is not payable about aeternity HOT 5 CLOSED

Is there a hypotheses when an account can become payable ? 🤔

from aeternity.

@dincho An address/account is by default payable (i.e. any account that isn't in the state tree (yet) is considered payable). When a contract is created, the associated account is set to either payable or not payable depending on the contract (default is not payable). After the contract creation there is no way to change the payable status.

@davidyuk in this case the cost for checking is small enough that I think we can add it as the default - doing HTTP is as you suggest worse 😅 - though the client could cache this...

Let's add it to the mempool-checks!

from aeternity.

Keyword here is we can, I guess. I don't think we lookup the recipient account when checking a SpendTx, so it would be an additional cost, if the recipient is a name it would be even more costly.

Maybe some of the tools along the way could warn that spending to this account is perhaps not a great idea 😅

from aeternity.

Isn't it costly to keep such transaction in mempool?

Maybe some of the tools along the way could warn that spending to this account is perhaps not a great idea

Checking this on sdk side also would be an additional cost. Even more expensive because of extra http requests.

from aeternity.

After the contract creation there is no way to change the payable status.

That was my mine question, and by account, I meant contract account/address.

from aeternity.