Skip to content

Commit

Permalink
fix broken table
Browse files Browse the repository at this point in the history
  • Loading branch information
@JiahuiWho
JiahuiWho committed Sep 27, 2024
1 parent 9fe27a1 commit 46bdc2c
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions ecosystem/sep-0038.md
View file
Original file line number Diff line number Diff line change
Expand Up @@ -553,17 +553,17 @@ must also provide either `sell_delivery_method` or `buy_delivery_method`, but no
A `201 Created` status code should be returned for successful requests.

| Name | Type | Description |
| ---------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --- |
| ---------------------- | ----------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `id` | string | The unique identifier for the quote to be used in other Stellar Ecosystem Proposals (SEPs). |
| `expires_at` | [UTC ISO 8601](https://www.iso.org/iso-8601-date-and-time-format.html) string | The date and time by which the anchor must receive funds from the client. |
| `total_price` | string | The total conversion price offered by the anchor for one unit of `buy_asset` in terms of `sell_asset`, including fees. In traditional finance, `buy_asset` would be referred to as the base asset and `sell_asset` as the counter asset. |
| `price` | string | The conversion price offered by the anchor for one unit of `buy_asset` in terms of `sell_asset`, without including fees. In traditional finance, `buy_asset` would be referred to as the base asset and `sell_asset` as the counter asset. |
| `sell_asset` | string | The asset the client would like to sell. Ex. `USDC:G...`, `iso4217:ARS` |
| `sell_amount` | string | The amount of `sell_asset` to be exchanged for `buy_asset`. It could be different from the `sell_amount` provided in the request, depending on how fees are applied by the Anchor. |
| `sell_delivery_method` | string | (optional) The method by which the user plans to deliver an off-chain asset to the anchor. This will only be present if the parameter was specified in the associated `POST /quote` request. | |
| `sell_delivery_method` | string | (optional) The method by which the user plans to deliver an off-chain asset to the anchor. This will only be present if the parameter was specified in the associated `POST /quote` request. |
| `buy_asset` | string | The asset the client would like to exchange for `sell_asset`. |
| `buy_amount` | string | The amount of `buy_asset` to be exchanged for `sell_asset`. It could be different from the `buy_amount` provided in the request, depending on how fees are applied by the Anchor. `price * buy_amount = sell_amount` must be true up to the number of decimals required for `buy_asset`. |
| `buy_delivery_method` | string | (optional) The method by which the user plans to receive an off-chain asset from the anchor. This will only be present if the parameter was specified in the associated `POST /quote` request. | |
| `buy_delivery_method` | string | (optional) The method by which the user plans to receive an off-chain asset from the anchor. This will only be present if the parameter was specified in the associated `POST /quote` request. |
| `fee` | object | An object describing the fee used to calculate the conversion price. This can be used to datail the price components for the end-user. |

To better understand the relation between the `*price`, `*amount` and `fee` fields, please refer to the
Expand Down

0 comments on commit 46bdc2c

Please sign in to comment.