Skip to content

Commit d007b57

Browse files
committed
rephrase sentence to avoid use of 'recently'
incorporating Christoph's feedback
1 parent e55bdb1 commit d007b57

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

guide/daily-spending-wallet/contacts.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -213,11 +213,10 @@ Whether we’re sending emails, physical mail, or following someone on social me
213213

214214
Addresses, invoices, node IDs and other transaction endpoints in bitcoin are highly unintuitive. Abstracting them via a contact list can create a much smoother user experience. There are many [payment request formats]({{ '/guide/how-it-works/payment-request-formats/' | relative_url }}), each with unique properties and varying levels of maturity and adoption, requiring unique design solutions. This page will use a more approachable "address" as an umbrella term for various types of payment information.
215215

216-
Recently, a number of safely reusable payment request formats such as [silent payments]({{ '/guide/how-it-works/silent-payments' | relative_url }}), [BOLT 12]({{ '/guide/how-it-works/payment-request-formats/#offers' | relative_url }}) and [BIP-353]({{ '/guide/how-it-works/human-readable-addresses/#bip-353-dns-payment-instructions' | relative_url }}) have emerged. This property makes them ideal for abstraction through contacts.
216+
Some payment request formats such as [silent payments]({{ '/guide/how-it-works/silent-payments' | relative_url }}), [BOLT 12]({{ '/guide/how-it-works/payment-request-formats/#offers' | relative_url }}) and [BIP-353]({{ '/guide/how-it-works/human-readable-addresses/#bip-353-dns-payment-instructions' | relative_url }}) are designed to be safely reused. This property makes them ideal for abstraction through contacts.
217217

218218
Let's go over common user interactions around managing contacts. This will illustrate how such a feature could work, and helps explain the underlying design problems and decisions.
219219

220-
221220
### Adding a contact
222221

223222
The most basic interaction is that a user manually adds a contact by entering their name and an address. This is likely not the most common user flow, as most contacts will be created with incoming payment requests, as illustrated further below. But wallets should generally support manual options, as users may not be able to avoid them.

0 commit comments

Comments
 (0)