More fine-grained allow/deny modes for post-conditions

[friedger]

Is your feature request related to a problem? Please describe.
Currently, users have to specify post-conditions for transactions that transfer assets from a contract. Users do not care about whether a contract is losing/transferring any assets.

Describe the solution you'd like
Only verify post-conditions that affect the tx-sender

Additional context
leather-io/extension#969

[jcnelson]

Hi @friedger, this is something the wallet should be doing for the user. I think there needs to be an API endpoint on the node that does the following:

• It lets you run any contract-call, including read/write ones (kind of like Implement #1641 rpc call public functions as read-only - take 2 #2527)
• It returns the JSON-serialized AssetMap from the contract call, which tells you which assets moved from which principals

This way, the wallet can run the contract-call, get the AssetMap, generate the post-conditions, and present them to the user to confirm that the assets that are moving are all desired.

[jcnelson]

I renamed this issue to call for a re-assessment of the post-condition allow/deny modes, so that a user can, for example, execute a deny-mode transaction only on their own tokens, but allow-mode on other principals' tokens.

[jcnelson]

Transferring this issue to @obycode for the time being. Please feel free to re-assign.