You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The visualize function shows a summary of an incoming transaction, but you can't dig into the full JSON nor rapidly verify that the entire intended JSON snippet is fully uncompromised.
Describe the solution you'd like
In a prompt, include accordion component segments which include:
An identicon of the JSON.stringified(QRContents) which can be shown in 3rd party app and in prompt to verify that the prompt you're seeing is the one you intended to create.
The full beautified JSON of the inbound request
Describe alternatives you've considered
console.log the request
Improve maintainability of the visualize function
Improve verification of inbound BTS TX for broadcast
Additional context
Similar to investigating the advanced info behind and inbound email, enabling additional due diligence when faced with potential spear phishing.
We have not yet implemented a quick visual aid like the identicon of the request JSON, however the entire request JSON is viewable in a scrollbox accordion segment in prompts now 👍
Is your feature request related to a problem? Please describe.
The visualize function shows a summary of an incoming transaction, but you can't dig into the full JSON nor rapidly verify that the entire intended JSON snippet is fully uncompromised.
Describe the solution you'd like
In a prompt, include accordion component segments which include:
JSON.stringified(QRContents)
which can be shown in 3rd party app and in prompt to verify that the prompt you're seeing is the one you intended to create.Describe alternatives you've considered
Additional context
Similar to investigating the advanced info behind and inbound email, enabling additional due diligence when faced with potential spear phishing.
#213 (comment)
The text was updated successfully, but these errors were encountered: