diff options
| author | John Bampton <jbampton@users.noreply.github.com> | 2024-05-01 06:54:05 +1000 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-04-30 16:54:05 -0400 |
| commit | f61885edcf5e63ac205b1ca5f08173f1336bff74 (patch) | |
| tree | 2d577255ee2fd3c3c5743edf1c0184a67abcb7d2 /bip-0015.mediawiki | |
| parent | 2d9e431fbe654640b55bca3bf8c4b17462890109 (diff) | |
docs: fix spelling (#1117)
Co-authored-by: Mark "Murch" Erhardt <murch@murch.one>
Diffstat (limited to 'bip-0015.mediawiki')
| -rw-r--r-- | bip-0015.mediawiki | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-0015.mediawiki b/bip-0015.mediawiki index a6e4426..52a698f 100644 --- a/bip-0015.mediawiki +++ b/bip-0015.mediawiki @@ -348,7 +348,7 @@ By using DNS lookups, the MITM problem with IP transactions could be mitigated b === Namecoin ID === -This proposal uses the Namecoin blockchain to associate an alias with a bitcoin address. Bitcoin queries a namecoin node. This retreives the structured data containing the bitcoin address(es) associated with this alias. +This proposal uses the Namecoin blockchain to associate an alias with a bitcoin address. Bitcoin queries a namecoin node. This retrieves the structured data containing the bitcoin address(es) associated with this alias. Using a decentralised domain name system like Namecoin, means no external server or entity needs to be trusted unlike the other proposals listed here. This indicates a system with the advantage of having a high availability and ease of entry (no restrictions for users to create aliases). @@ -401,4 +401,4 @@ Any text can be put into the brackets, allowing merchants to adapt it to all the New features can be added later to support uncovered cases. -See the specification of [http://dot-bit.org/Namespace:Identity Namecoin ID] for more informations. +See the specification of [http://dot-bit.org/Namespace:Identity Namecoin ID] for more information. |