Permit all invocations of this type on this contract

Describe the solution you’d like and the expected behavior

When a user is prompted to permit an invocation, provide a checkbox to “always permit this action for this contract”. If the user ticks the checkbox before approving the modal, then future invocations that will have prompt should instead be automatically approved.

Is your feature request related to a problem? Please describe.

There are some types of invocations that a user might always trust. An example would be invoking a “sendMessage” transaction in a chat app. Having to approve every single message being delivered via nOS would make this cumbersome.

Possible implementation / References

User setting should be saved in local storage.

The option to always approve invocations should be for a specific command on a specific smart contract (hash) on a specific network (e.g.: TestNet). If any of these three items does not match on a subsequent invocation request, then the user should still be prompted (and in turn given the option to auto-approve that invocation command as well).

Invocation occurs via the components under src/renderer/browser/components/RequestsProcessor/Invoke. The index.js container will need to be modified to automatically approve via onConfirm and render immediately (to prevent chaining children in the HOC). That logic will need to appear before the withPrompt HOC is called.

Additional context

nOS should be secure, but also convenient.

[deanpress]

1. There should be a way so that a developer can update the info on the UI when the transaction is confirmed on blockchain. Not sure how this can be done - maybe websockets. This will prevent the multiple testinvocation calls to query whether the state has been updated.

We’re planning to integrate new block events into the API, see #54

[shashank-ezdiagno]

I would like to suggest an improvement for the way invocations are done. Invocations usually cost gas and the user might not be aware that it takes some time between invocation and the reflection of results. So, the user might try to make the same invocation multiple times. In order to save gas and possibly prevent bots:

1. There should be a rate-limit on the number of invocations that can be made per unit time.
2. Prevent multiple successive invocations of the smart contract with same parameters.
3. There should be a way so that a developer can update the info on the UI when the transaction is confirmed on blockchain. Not sure how this can be done - maybe websockets. This will prevent the multiple testinvocation calls to query whether the state has been updated.