-
Notifications
You must be signed in to change notification settings - Fork 107
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DRAFT: One Off Transactions/Requests Specification #783
base: main
Are you sure you want to change the base?
Conversation
Idea:what if we instead made this a "one off request" feature where any normally privileged request can be sent to wallet? something like this:
|
That would work, but it comes at the cost of expanding the protocol syntax by theoretically expanding the shape of the JSON payload for any request. An alternative approach: a new |
yeah I like that, great call. |
@sdlaver I like the
The way wallets work today, this is not a problem, as they don't currently allow a user to select an account during authorization; they always use the account that is currently set within the wallet. But with improved wallet UX this get messy from a UX standpoint.
|
I presume we'd use a well-known address (perhaps all
I don't think so; it would affect the state of the connection, but does not provide any auth token to manage or recover that state later. |
Summary
"One Off" transactions are transactions that do not require a previous authorization to complete. This is effectively a combination of
authorize
+sign_and_send_transactions
into a single request. Wallet endpoints supporting this feature should show a single UI modal to sign the rquested transactions.User stories
These user stories outline the goals and user experiences that this feature aims to enable.