Skip to content

Commit

Permalink
Update recommendations section
Browse files Browse the repository at this point in the history
  • Loading branch information
philipliu committed Aug 17, 2023
1 parent 58cef2b commit 92baa73
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions ecosystem/sep-0006.md
Original file line number Diff line number Diff line change
Expand Up @@ -270,7 +270,7 @@ SEP-6 lays out many options for how deposit and withdrawal can work. These are r
* Determine which anchor endpoints will require authentication
* Fetch the asset's deposit & withdrawal fee structure: if `fee_fixed` and `fee_percent` are provided, show this to the user early in the process so they're fully informed.
* If the `/fee` endpoint is enabled, use it for computing fees when you need to show them to the user.
* While `/info` allows an anchor to communicate non-standard fields that are needed for `/deposit` or `/withdraw`, it's easier for a basic wallet implementation to hard-code extra fields that are needed on a per-anchor basis, and ensure those fields are passed in properly.
* While `/info` allows an anchor to communicate fields that are needed for `/deposit` or `/withdraw`, Anchors are recommended not to collect these through request parameters, but rather through [SEP-12](sep-0012.md) to avoid leaking sensitive information through URLs. If the anchor requires fields to be provided through request parameters, the wallet can hard-code any extra fields on a per-anchor basis to ensure those fields are passed in correctly.
* **Authentication**
* If needed, perform [authentication](#authentication) via SEP-10 before hitting those endpoints
* **Make a request to `/deposit` or `/withdraw`.**
Expand All @@ -288,7 +288,7 @@ SEP-6 lays out many options for how deposit and withdrawal can work. These are r

### Basic Anchor Implementation

* Provide a full-featured implementation of [`/info`](#info).
* Provide a full-featured implementation of [`/info`](#info) using SEP-12 to collect any KYC or financial account information from the user.
* Decide which endpoints, if any, need to be [authenticated](#authentication), and declare that properly in the `/info` endpoint.
* Pick your approach to [fees](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md#fee). We recommend using `/info` to express fees as it provides a better user experience (the user can see the fee structure in the wallet early in the process).
* **For both deposit and withdrawal**:
Expand Down

0 comments on commit 92baa73

Please sign in to comment.