bitshares / beet

Beet is a stand-alone key/identity-manager and signing app for BitShares, heavily influenced by Scatter.
MIT License
27 stars 32 forks source link

Deeplink prompt responses #253

Closed grctest closed 1 year ago

grctest commented 1 year ago

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

When using socketio connect/link route, we're able to provide 3rd party apps full responses to queries.

When a 3rd party app interacts with the BEET wallet via totp/raw/qr/local deeplinks, these offer solely broadcast-only functionality, so the 3rd party app either needs to assume the user has approved the prompt, or verify subsequent account histories to get the same outcome as the above.

Describe the solution you'd like

Possibly offer a box of text for the user to copy/paste into a 3rd party app, enabling the external app to access broadcast responses as well as parse requested information.

Alternatively, we could offer a deeplink to the external application, however this could introduce a clickjacking / redirect attack vector for users.

Describe alternatives you've considered

Reserve such functionality to beet linked dapps.

Additional context

Some users can't use the linked dapp functionality, so they're limited to broadcast-only blockchain operations with the Beet multiwallet.

grctest commented 1 year ago

With the optional prompt receipt PR merged into develop, the user can now copy the output for 3rd party apps if so inclined.