diff --git a/_sass/minima/_article.scss b/_sass/minima/_article.scss index 0a46be9b1..fd7fa70d6 100644 --- a/_sass/minima/_article.scss +++ b/_sass/minima/_article.scss @@ -224,6 +224,16 @@ article.guide { } } + span { + &.-blue { + color: $blue; + } + + &.-green { + color: $green; + } + } + > iframe { display: block; } diff --git a/assets/images/guide/how-it-works/human-readable-addresses/clipboard-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/clipboard-mobile.png new file mode 100644 index 000000000..85ceae9df Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/clipboard-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/clipboard-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/clipboard-mobile@2x.png new file mode 100644 index 000000000..d0aec08cc Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/clipboard-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/clipboard.png b/assets/images/guide/how-it-works/human-readable-addresses/clipboard.png new file mode 100644 index 000000000..7dbeb4429 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/clipboard.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/clipboard@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/clipboard@2x.png new file mode 100644 index 000000000..9319000c8 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/clipboard@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/contact-card-mobile.jpg b/assets/images/guide/how-it-works/human-readable-addresses/contact-card-mobile.jpg new file mode 100644 index 000000000..a2e0d7f3f Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/contact-card-mobile.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/contact-card-mobile@2x.jpg b/assets/images/guide/how-it-works/human-readable-addresses/contact-card-mobile@2x.jpg new file mode 100644 index 000000000..97b0d6814 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/contact-card-mobile@2x.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/contact-card.jpg b/assets/images/guide/how-it-works/human-readable-addresses/contact-card.jpg new file mode 100644 index 000000000..509142d92 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/contact-card.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/contact-card@2x.jpg b/assets/images/guide/how-it-works/human-readable-addresses/contact-card@2x.jpg new file mode 100644 index 000000000..878e2aa9a Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/contact-card@2x.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries-mobile.png new file mode 100644 index 000000000..3fb4bf707 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries-mobile@2x.png new file mode 100644 index 000000000..3a2d97c47 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries.png new file mode 100644 index 000000000..47e35ad06 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries@2x.png new file mode 100644 index 000000000..7e898d1ce Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping-mobile.png new file mode 100644 index 000000000..750dc654e Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping-mobile@2x.png new file mode 100644 index 000000000..7ada95412 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping.png new file mode 100644 index 000000000..eae7ee782 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping@2x.png new file mode 100644 index 000000000..57bf75184 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-mobile.png new file mode 100644 index 000000000..2ab7275c8 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-mobile@2x.png new file mode 100644 index 000000000..687b90759 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service-mobile.png new file mode 100644 index 000000000..3f6993f85 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service-mobile@2x.png new file mode 100644 index 000000000..39a588138 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service.png new file mode 100644 index 000000000..d4b532415 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service@2x.png new file mode 100644 index 000000000..e90c17c18 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust.png new file mode 100644 index 000000000..7f423fd0e Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust@2x.png new file mode 100644 index 000000000..20a5321df Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/education-mobile.jpg b/assets/images/guide/how-it-works/human-readable-addresses/education-mobile.jpg new file mode 100644 index 000000000..a9336706b Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/education-mobile.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/education-mobile@2x.jpg b/assets/images/guide/how-it-works/human-readable-addresses/education-mobile@2x.jpg new file mode 100644 index 000000000..b5d7b3f27 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/education-mobile@2x.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/education.jpg b/assets/images/guide/how-it-works/human-readable-addresses/education.jpg new file mode 100644 index 000000000..bb3ce65f6 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/education.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/education@2x.jpg b/assets/images/guide/how-it-works/human-readable-addresses/education@2x.jpg new file mode 100644 index 000000000..e40e5b5b0 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/education@2x.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-mobile.jpg b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-mobile.jpg new file mode 100644 index 000000000..ff5eb7868 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-mobile.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-mobile@2x.jpg b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-mobile@2x.jpg new file mode 100644 index 000000000..e80f0991e Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-mobile@2x.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-preview.jpg b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-preview.jpg new file mode 100644 index 000000000..2fb73d7cf Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-preview.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses.jpg b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses.jpg new file mode 100644 index 000000000..7e054e889 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses@2x.jpg b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses@2x.jpg new file mode 100644 index 000000000..e43f7ab48 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses@2x.jpg differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/input-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/input-mobile.png new file mode 100644 index 000000000..f2f3374fe Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/input-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/input-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/input-mobile@2x.png new file mode 100644 index 000000000..714ba1f1c Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/input-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/input.png b/assets/images/guide/how-it-works/human-readable-addresses/input.png new file mode 100644 index 000000000..39c9510f2 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/input.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/input@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/input@2x.png new file mode 100644 index 000000000..ce48c9931 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/input@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries-mobile.png new file mode 100644 index 000000000..a4fe7bfb7 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries-mobile@2x.png new file mode 100644 index 000000000..f3af4ebfe Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries.png b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries.png new file mode 100644 index 000000000..0194989e6 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries@2x.png new file mode 100644 index 000000000..398de3d50 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping-mobile.png new file mode 100644 index 000000000..844167312 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping-mobile@2x.png new file mode 100644 index 000000000..da4612362 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping.png b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping.png new file mode 100644 index 000000000..39a3804c1 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping@2x.png new file mode 100644 index 000000000..de49191de Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/mapping-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/mapping-mobile.png new file mode 100644 index 000000000..2900c8e1a Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/mapping-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/mapping-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/mapping-mobile@2x.png new file mode 100644 index 000000000..29df1ca85 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/mapping-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/mapping.png b/assets/images/guide/how-it-works/human-readable-addresses/mapping.png new file mode 100644 index 000000000..619d7884d Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/mapping.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/mapping@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/mapping@2x.png new file mode 100644 index 000000000..5ee8ebe1c Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/mapping@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings-filled-full.png b/assets/images/guide/how-it-works/human-readable-addresses/settings-filled-full.png new file mode 100644 index 000000000..013d5da24 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings-filled-full.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings-filled.png b/assets/images/guide/how-it-works/human-readable-addresses/settings-filled.png new file mode 100644 index 000000000..a9a564271 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings-filled.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings-filled@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/settings-filled@2x.png new file mode 100644 index 000000000..f74c17217 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings-filled@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings-full.png b/assets/images/guide/how-it-works/human-readable-addresses/settings-full.png new file mode 100644 index 000000000..82deb051b Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings-full.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings-select-full.png b/assets/images/guide/how-it-works/human-readable-addresses/settings-select-full.png new file mode 100644 index 000000000..297c44e4f Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings-select-full.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings-select.png b/assets/images/guide/how-it-works/human-readable-addresses/settings-select.png new file mode 100644 index 000000000..24ebf58a1 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings-select.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings-select@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/settings-select@2x.png new file mode 100644 index 000000000..6e69d292f Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings-select@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings.png b/assets/images/guide/how-it-works/human-readable-addresses/settings.png new file mode 100644 index 000000000..fd69ef8ed Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/settings@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/settings@2x.png new file mode 100644 index 000000000..9b69ad1bc Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/settings@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-done-full.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-done-full.png new file mode 100644 index 000000000..2efaa5fe0 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-done-full.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-done.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-done.png new file mode 100644 index 000000000..22f64e515 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-done.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-done@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-done@2x.png new file mode 100644 index 000000000..1597ca9a0 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-done@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled-full.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled-full.png new file mode 100644 index 000000000..0d0c6a06e Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled-full.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled.png new file mode 100644 index 000000000..84d24c0cb Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled@2x.png new file mode 100644 index 000000000..57d0c1e3f Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-username-filled@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-username-full.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-username-full.png new file mode 100644 index 000000000..876e7b4bd Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-username-full.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-username.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-username.png new file mode 100644 index 000000000..6912c7691 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-username.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/setup-username@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/setup-username@2x.png new file mode 100644 index 000000000..3931f9832 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/setup-username@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/update-mobile.png b/assets/images/guide/how-it-works/human-readable-addresses/update-mobile.png new file mode 100644 index 000000000..335006f42 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/update-mobile.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/update-mobile@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/update-mobile@2x.png new file mode 100644 index 000000000..15c63aa28 Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/update-mobile@2x.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/update.png b/assets/images/guide/how-it-works/human-readable-addresses/update.png new file mode 100644 index 000000000..ad239791a Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/update.png differ diff --git a/assets/images/guide/how-it-works/human-readable-addresses/update@2x.png b/assets/images/guide/how-it-works/human-readable-addresses/update@2x.png new file mode 100644 index 000000000..e7619340c Binary files /dev/null and b/assets/images/guide/how-it-works/human-readable-addresses/update@2x.png differ diff --git a/guide/how-it-works/human-readable-addresses.md b/guide/how-it-works/human-readable-addresses.md new file mode 100644 index 000000000..f4524cd97 --- /dev/null +++ b/guide/how-it-works/human-readable-addresses.md @@ -0,0 +1,348 @@ +--- +layout: guide +title: Human readable addresses +description: Easy-to-use bitcoin addresses via DNS payment instructions and the lightning address protocol. +nav_order: 1 +parent: Payment request formats +grand_parent: How it works +permalink: /guide/how-it-works/human-readable-addresses/ +main_classes: -no-top-padding +image: /assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-preview.jpg +image_base: /assets/images/guide/how-it-works/human-readable-addresses/ +images_setup: + - file: setup-username + modalImage: setup-username-full + alt: Empty username selection screen with placeholder text 'Enter a name...' showing how the address will appear as 'Busername@bubble.com'. The 'Next' button is grayed out. + caption: The user is asked to choose a name unique to this specific service. + - file: setup-username-filled + modalImage: setup-username-filled-full + alt: Username selection screen showing 'charles' entered as the username, which would create the address 'Bcharles@bubble.com'. A green checkmark indicates the username is available. An orange 'Next' button appears at the bottom. + caption: Once a unique name is found, the user can finalize it. + - file: setup-done + modalImage: setup-done-full + alt: Success screen with a green checkmark saying 'You are all set' with a message explaining the address will be available in a few minutes. Contains a privacy warning about not posting the address online and notes this is an experimental feature. + caption: The confirmation provides additional tips to keep in mind and access to additional configuration. +images_settings: + - file: settings + modalImage: settings-full + alt: Address settings screen showing a Bubble email address 'Bcharles@bubble.com', with empty fields for backup Bitcoin address and personal message. The primary Bitcoin address shows 'Default' with a dropdown menu. + caption: By default, this address is configured with the wallet's own BOLT 12 lightning offer. + - file: settings-select + modalImage: settings-select-full + alt: Bubble app settings screen showing address configuration options. Main email address 'bcharles@bubble.com' is displayed, followed by payment options including 'Re-usable lightning address (BOLT12 offer)', 'Re-usable bitcoin address (Silent payments)', and 'Enter a new address'. + caption: The default bitcoin address linked to the Bubble address can easily be changed. + - file: settings-filled + modalImage: settings-filled-full + alt: Address settings screen showing a Bubble email address 'Bcharles@bubble.com', a default Bitcoin lightning address, a long backup Bitcoin address starting with 'sp1q', and a personal message saying 'Thanks for all the sats. - Charles' + caption: Here the user has added a silent payments address as a fallback, as well as a personal note. + +--- + + + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses.jpg" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses@2x.jpg" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-mobile.jpg" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/human-readable-addresses-mobile@2x.jpg" + alt-text = "The word bitcoin address written in binary and plain text" + width = 1600 + height = 400 + layout = "full-width" +%} + +# Human readable addresses +{:.no_toc} +--- + +
+* Table of contents +{:toc} +
+ +--- + +[Bitcoin addresses]({{'/guide/glossary/address/' | relative_url}}) and [payment requests]({{'/guide/how-it-works/payment-request-formats/' | relative_url}}) are long and cryptic, practically impossible to read, memorize, pronounce, understand, or type. We are used to being able to communicate our social media handles and email addresses easily. That expectation has also extended to transacting with neo-banking and payment applications. There have been multiple attempts at making human-readable addresses a reality in bitcoin. + +The benefits to the user experience include: + +- Familiarity: A format that feels more human and familiar to users +- Ease of sharing: A format that is easier to remember, recall, and share + +**Important:** Human-readable addresses should only be used for direct communication. Whenever payment information is communicated digitally (copy & paste, links, QR codes, messaging, etc), cryptographic formats should be used for the best security and privacy. + +On this page, we focus primarily on the [BIP-353 for DNS Payment Instructions](https://github.com/bitcoin/bips/blob/master/bip-0353.mediawiki), with some information about [Lightning Addresses](https://lightningaddress.com). They pursue similar goals, but in very different ways. + +### The basic idea + +Bitcoin transactions always rely on long and cryptic addresses and payment formats, consisting of numbers and letters. Human-readable addresses are a means for wallets to retrieve these regular addresses. In other words, they act as pointers. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/mapping.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/mapping@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/mapping-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/mapping-mobile@2x.png" + alt-text = "Diagram showing an email address pointing to a bitcoin address" + width = 800 + height = 159 +%} + +There are various technical approaches to resolve addresses. We’ll learn more about the different benefits and drawbacks below. + +### Security & privacy + +Every approach requires at least one intermediary that is being contacted to serve the payment information. This creates potential privacy and security risks that users need to understand. + +Key considerations: + +- Intermediaries can track requests and metadata to build profiles of users and payment patterns +- DNS queries may leak information about payment relationships +- Services can potentially serve different payment information than specified + +If the domain (website) where the payment information is stored, is not controlled by the user, we will refer to the address as "_managed_". To be clear, intermediaries cannot move funds at the user-provided address. They can only prevent payment information retrieval, or re-route funds by returning different payment information. + +### Address format basics + +From email and social media, we are familiar with addresses consisting of a local and a global part. The local part is typically a username, and the global part identifies a domain or service. + +- *“My email is alice@domain.com.”* +- *“I am alice on [social media service].”* +- *“Pay me at alice on [payment service].”* + +For social media, users know to navigate to the respective website or app and look up the username there. Applications rely on domains (via the [Domain Name System](https://en.wikipedia.org/wiki/Domain_Name_System), or DNS) to resolve the global part. In physical addresses, we have more hierarchical parts - country, state, city, street, house number and apartment. It is a familiar system. + +## BIP-353: DNS Payment Instructions + +This [proposal](https://github.com/bitcoin/bips/blob/master/bip-0353.mediawiki) only relies on the Domain Name System (DNS) to retrieve payment information. DNS is a decentralized hierarchical naming system used to translate human-friendly domain names (like *www.example.com*) into IP addresses (like *192.0.2.1*) that computers use to identify each other on the network. Anytime we type in a domain into a browser, we rely on this system. This use case is very similar to what human-readable addresses try to achieve, making DNS a good fit. + +{% include tip/open.html color="blue" label="Note" icon="info" %} + +This is a new proposal. It is still being discussed, and not widely implemented. + +{% include tip/close.html %} + +### Address format + +This proposal uses the formats *“username@domain.com”* and *“₿username@domain.com”*. It is similar to the email address format, which makes it familiar and easy to use. The *₿* prefix is an important addition for display purposes, to make it distinctly a bitcoin payment address. This provides clarity and trust to users, which is important when it comes to financial transactions. + +### How it works + +Users create DNS entries with payment information, which can be one or more addresses of different formats, combined to a [BIP 21 URI](https://github.com/bitcoin/bips/blob/master/bip-0021.mediawiki). Since address reuse is best avoided for privacy reasons, the included addresses should be reusable (like [silent payments]({{ '/guide/how-it-works/silent-payments/' | relative_url }}) and [BOLT12](https://bolt12.org/) offers). Single-use addresses can be used if needed, but a mechanism to rotate them should be in place. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-mapping-mobile@2x.png" + alt-text = "Diagram showing how a bitcoin address is resolved to a payment URL" + width = 800 + height = 328 +%} + +Wallets look up the payment information when first exposed to a human-readable address. To ensure this information is up-to-date, wallets regularly check for updates, based on the expiration provided by the DNS resolver. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-intermediaries-mobile@2x.png" + alt-text = "Diagram showing how the involved parties interact with each other" + width = 800 + height = 445 +%} + +### Trust + +Setting this up in a trust-minimised manner requires a user to own a domain, and trust the domain provider and DNS system to truthfully communicate their payment information. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-mobile@2x.png" + alt-text = "Diagram showing who the user trusts when owning a domain." + width = 800 + height = 192 +%} + +If the user does not own the domain but uses a third-party service instead, then another intermediary is in play. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/dns-payment-instructions-trust-service-mobile@2x.png" + alt-text = "Diagram showing who the user trusts when hosting their address with a third party." + width = 800 + height = 192 +%} + +### Design patterns + +#### Educating users + +Framing the correct use of the address should be done right away and as early in the user flow as possible. This allows user to make informed decisions as to how and when to use the address. The information should include: + +- The purpose of the address is for verbally sharing their bitcoin address in a social setting. +- That the address is public, which carries a clear directional understanding about privacy. + +{% include tip/open.html label="Bubble Wallet" %} + +The mock-ups below show an imaginary application called "Bubble Wallet". Its naming conventions are based on the idea that _Human-readable address_ is an appropriate descriptive term for technical proposal and discussion, but not necessarily practical for end-users. Due to the similarities to the familiar email format and social media practices, it borrows from those standards. + +- A human-readable address is referred to generally as (a new type of) _bitcoin address_ +- More specifically, it is referred to as _Bubble address_ or _Bubble bitcoin address_, because it is managed by the wallet (provider) +- The first part of the address is referred to as _username_ +- Other address types are first referred to by their primary properties, and secondly by their technical names + +You may choose different naming conventions based on your audience, feature set, and adoption outlook. + +{% include tip/close.html %} + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/education.jpg" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/education@2x.jpg" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/education-mobile.jpg" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/education-mobile@2x.jpg" + alt-text = "UI mock-up of a feature intro screen presenting bitcoin addresses for verbal communication" + caption = "Introduction to the feature in an imaginary application called Bubble Wallet." + width = 800 + height = 608 +%} + +#### Managed address setup + +It is important to provide users with a simple setup experience for human-readable addresses. They are likely to use them for a long time, and need to be able to trust that everything is set up and working correctly. + +Below is a sample flow, in which a user can define their unique username, which is then combined with the wallet providers domain to form their human-readable address. + +{% include image-gallery.html pages = page.images_setup %} + +Address settings allow users to adjust the payment information associated with the human-readable address. + +{% include image-gallery.html pages = page.images_settings %} + +Wallets should also verify any addresses the user defines. For example, a user who tries to add a regular onchain address can be informed that this is a bad practice due to the privacy implications. + +The additional configuration is important, to account for the diversity of features that different wallets offer. There are likely to be situations where the user wants to bundle payment information from several wallets. The best candidates for address types to use (due to their re-usability) are BOLT12 offers and silent payment addresses. Those are not broadly established, so a user may rely on different wallets for each type. + +#### Sharing + +Users should have quick access to their payment addresses. However, since they should not be shared electronically, the options to copy or share should directly use the underlying payment information that is connected to the human-readable address. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/contact-card.jpg" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/contact-card@2x.jpg" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/contact-card-mobile.jpg" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/contact-card-mobile@2x.jpg" + alt-text = "A visual contact card showing a bitcoin address and a separate button for sharing payment information" + width = 800 + height = 427 +%} + +#### Address input + +Input fields for addresses typically need to accommodate various address types (see the [contacts page]({{ '/guide/daily-spending-wallet/contacts/#adding-a-contact' | relative_url }})). Whenever possible, addresses should be pre-filled from the clipboard, contacts, or previously clicked links. This is more convenient for users and reduces manual input errors. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/clipboard.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/clipboard@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/clipboard-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/clipboard-mobile@2x.png" + alt-text = "A modal notifying the user of a bitcoin address on their clipboard and offering appropriate options" + width = 800 + height = 334 +%} + +While it is unlikely that users will type in the more complex address types, an address input field should not be restricted to only accepting a single address type. In this example, a single input field is capable of accepting a variety of different formats, and it provides feedback to the user about what they entered. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/input.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/input@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/input-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/input-mobile@2x.png" + alt-text = "Several states of an address input field showing how a user might enter bitcoin addresses" + caption = "Various interactive states of an address input field." + width = 800 + height = 536 +%} + +Wallets that host many addresses may also match entered usernames against their database and highlight matches. For example, if both sender and receiver user the same wallet, it suffices for the sender to enter the receivers username, and the wallet can auto-complete the remainder of the address. + +#### Keeping users informed + +The payment information associated with addresses in contacts may change or even become invalid. Wallets should ensure to inform the user of updates to review or act on. This is best done at the time the user wants to initiate a payment to a contact. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/update.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/update@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/update-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/update-mobile@2x.png" + alt-text = "Two modals notifying the user of changed and disabled bitcoin addresses" + width = 800 + height = 277 +%} + +Wallets should gracefully handle various failure modes, and provide clear error messages that help users understand and resolve issues. For example: + +- DNS resolution failures +- Invalid or missing payment information +- Expired payment information +- Network connectivity issues + +## Lightning Address + +Compared to DNS Payment Instructions, [Lightning Addresses](http://lightningaddress.com) are focused on the lightning network only. They bring another intermediary into play, and allow for much more dynamic functionality. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-mapping-mobile@2x.png" + alt-text = "Diagram showing how a lightning address is transformed to a URL" + width = 800 + height = 114 +%} + +### How it works + +Lightning addresses look like traditional emails. Under the hood, a wallet that uses a lightning address reformats it to a URL. It then looks for information about a [LNURL](https://github.com/lnurl/luds) web-server at that location (more on that [here](https://github.com/lnurl/luds/blob/luds/16.md)). That server handles the communication with the lightning node and passes messages back and forth. This allows for complex interactions (like authentication and withdrawals), but also requires trusting the web server. + +{% include picture.html + image = "/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries.png" + retina = "/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries@2x.png" + mobile = "/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries-mobile.png" + mobileRetina = "/assets/images/guide/how-it-works/human-readable-addresses/lightning-address-intermediaries-mobile@2x.png" + alt-text = "Diagram showing the parties involved in communicating payment information" + width = 800 + height = 159 +%} + +In a similar vein, [UMA](https://www.uma.me) is based on LNURL and Lightning Address, with modified functionality and the *"$alice@domain.com"* address format. The *$* prefix was chosen to represent both fiat and crypto currencies. + +## [Paynyms](http://paynym.is) + +This approach relies on a single directory provider, which maps a human readable name with a [BIP-47](https://github.com/bitcoin/bips/blob/master/bip-0047.mediawiki) payment code. Having a single provider allows for the omission of the global part, in this case *"my.paynym.is/username"* and users can simply be referred to by their usernames. The directory code is not open-source. + +--- + +Next, we will learn about the different [private key schemes]({{ '/guide/how-it-works/private-key-management/introduction/' | relative_url }}) used to secure your bitcoin. + +{% include next-previous.html + previousUrl = "/guide/how-it-works/payment-request-formats/" + previousName = "Payment request formats" + nextUrl = "/guide/how-it-works/private-key-management/introduction/" + nextName = "Private key management" +%} diff --git a/guide/how-it-works/introduction.md b/guide/how-it-works/introduction.md index 223c17301..b830d1756 100644 --- a/guide/how-it-works/introduction.md +++ b/guide/how-it-works/introduction.md @@ -58,7 +58,7 @@ Learn about how nodes help keep bitcoin decentralized and enforce its rules. ### [Payment request formats]({{ '/guide/how-it-works/payment-request-formats/' | relative_url }}) -Learn about the different types of payment request formats, from a standard on-chain address to a lightning address, that exist in bitcoin. +Learn about the different formats for payment information that exist in bitcoin, from standard on-chain to lightning, and [human readable addresses]({{ '/guide/how-it-works/human-readable-addresses/' | relative_url }}). --- diff --git a/guide/how-it-works/payment-request-formats.md b/guide/how-it-works/payment-request-formats.md index 4be6b5eec..0936d90f0 100644 --- a/guide/how-it-works/payment-request-formats.md +++ b/guide/how-it-works/payment-request-formats.md @@ -4,6 +4,7 @@ title: Payment request formats description: An introduction to the different bitcoin payment request formats. nav_order: 6 parent: How it works +has_children: true permalink: /guide/how-it-works/payment-request-formats/ redirect_from: - /guide/payments/send/payment-request-formats/ @@ -138,7 +139,7 @@ LNURL-Pay allows senders to dynamically request an invoice from the receiver to ##### Lightning address -[Lightning addresses](https://lightningaddress.com) build on top of LNURL-Pay and give users a more human-readable payment address. They use the very familiar email format (user@bitcoin.design) to request payments. +[Lightning addresses](https://lightningaddress.com) build on top of LNURL-Pay and give users a more [human readable payment address]({{ '/guide/how-it-works/human-readable-addresses/' | relative_url }}). They use the very familiar email format (_username@domain.com_) to request payments. ##### Withdraw @@ -235,7 +236,7 @@ Payment codes have been popularised in wallets such as [Samourai](https://samour A downside to payment codes is that they require an additional on-chain transaction each time two users want to connect and use them. [Silent payments](https://gist.github.com/RubenSomsen/c43b79517e7cb701ebf77eec6dbb46b8?permalink_comment_id=4113680) are a new experimental proposal that prevents the need for this additional on-chain transaction at the cost of extra bandwidth for receivers. -Some wallets use what is called a [PayNym](https://paynym.is/) to abstract payment codes into more human readable payment request formats. However, this is not standardized, directories are not open-source, and currently Samourai is the only operator running a directory. +Static payment codes are great for use with [DNS-based human readable addresses]({{ '/guide/how-it-works/human-readable-addresses/#dns-payment-instructions' | relative_url }}). @@ -262,11 +263,11 @@ You can learn more about unified payment requests [here](https://bitcoinqr.dev/) --- -Next, we will learn about [ecash]({{ '/guide/how-it-works/ecash/introduction/' | relative_url }}). +As you noticed, these formats are impossible to memorize and pronounce. That is what [human readable addresses]({{ '/guide/how-it-works/human-readable-addresses/' | relative_url }}) aim to solve. {% include next-previous.html previousUrl = "/guide/how-it-works/nodes/" previousName = "Nodes" - nextUrl = "/guide/how-it-works/ecash/introduction/" - nextName = "Ecash" + nextUrl = "/guide/how-it-works/human-readable-addresses/" + nextName = "Human readable addresses" %} diff --git a/guide/how-it-works/private-key-management/introduction.md b/guide/how-it-works/private-key-management/introduction.md index 1747f1cb9..73fd70f0e 100644 --- a/guide/how-it-works/private-key-management/introduction.md +++ b/guide/how-it-works/private-key-management/introduction.md @@ -76,8 +76,8 @@ A wallet that is managed by multiple independent keys, of which at least one is --- {% include next-previous.html - previousUrl = "/guide/how-it-works/payment-request-formats/" - previousName = "Payment request formats" + previousUrl = "/guide/how-it-works/human-readable-addresses/" + previousName = "Human readable addresses" nextUrl = "/guide/how-it-works/private-key-management/overview/" nextName = "Overview" %}