nostr/nips
1
0
Fork 0
mirror of https://github.com/nostr-protocol/nips.git synced 2024-12-22 08:25:53 -05:00
Code Issues Actions Packages Projects Releases Wiki Activity

chore: use comma to separate payment channels

Browse Source
This commit is contained in:
Nicolas Burtey 2023-04-08 06:21:58 +02:00
parent 8713cf25e7
commit 8250274a22
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
31001.md
View File

@ -61,7 +61,7 @@ E: Expiration date in Unix format
e: Referring to a previous order. the client SHOULD remove the previous order from the list of order currently displayed.
c: Trading channels in use. Separate multiple channels with spaces, e.g., "IBAN Revolut." For specifying channels for both left and right currencies, use a "/", e.g., "Onchain Lightning/IBAN Revolut"
c: Trading channels in use. Separate multiple channels with comma, e.g., "IBAN,Revolut,US Amazon Gift Card,UK Faster Payments" For specifying channels for both left and right currencies, use a "/", e.g., "Onchain,Lightning/IBAN,Revolut,US Amazon Gift Card,UK Faster Payments"
### replace and delete
@ -73,7 +73,7 @@ tag-e can be used to replace an offer, for example, when the price changes.
Although it's possible to build this on top of the draft marketplace, there are several reasons to create a dedicated NIP:
- Initially, P2P tradin clients will probably dedicated to this application. By using a specific kind instead of the generic {kind: 1}, it improves discoverability.
- Initially, P2P trading clients will probably dedicated to this application. By using a specific kind instead of the generic {kind: 1}, it improves discoverability.
- The data structure employs tags, allowing for native filtering across currencies, amounts, and expiration dates on existing relays.