Skip to content

Idea: Limit operation scope whilst adding a new account #26

@grctest

Description

@grctest

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

When you're going to process a deeplink, qr code or json file for a prompt you're first prompted to customize scope or allow all operations in the upcoming prompt.

Whilst you're able to limit the scope of allowed prompts from inputs, benefiting client security, you're unable to limit the scope of broadcastable operations in a wallet from the user themselves.

Scenario: User is operating a service account, their boss is expecting them to process operations, the expected/allowed operations are transfers only, but the cashier could themselves scan non-transfer operations.

Describe the solution you'd like

Whilst adding a new account to a wallet offer an optional prompt to permanently limit the permitted operations.

When the user selects "Allow all operations", they will be limited to the pre-permitted operations setup during sign up.

Describe alternatives you've considered

Wait for the next Bitshares core releases which may include more fine-tuned keys for limiting the broadcastable operations based on the keys used during the add account phase.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions