SEP-6: standardize structured off-chain deposit instructions for users #1368
Assignees
Comments
|
This issue is stale because it has been open for 30 days with no activity. It will be closed in 30 days unless the stale label is removed. |
philipliu
added a commit
that referenced
this issue
Aug 30, 2023
### Proposal This adds new fields to the `transaction` object to facilitate Anchors providing deposit instructions outside of `GET /deposit` response. ### Backwards Compatability This change is backward compatible as it does not introduce new required fields if Anchors can provide deposit instructions in the `GET /deposit` response. Resolves #1372, #1368.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
What problem does your feature solve?
Today, SEP-6 uses the
howresponse attribute defined for theGET /depositendpoint, which is a short but human-readable string used to communicate off-chain payment instructions to the user. This is an insufficient solution for reasons discussed in the stellar-dev google group.What would you like to see?
We should make a change to the SEP-6 protocol that enables wallets to communicate the anchor's deposit instructions to users that doesn't rely on human-readable content provided by the anchor. This likely involves defining a structured object in the response that communicates standardized off-chain financial account data. #1367 aims to clarify which SEP-9 fields could be useful in this context.
What alternatives are there?
Members of the community as well as developers of ecosystem wallet and anchors are welcome to propose solutions. Please read the google group thread so you have full context.
The text was updated successfully, but these errors were encountered: