diff options
| author | Chris Ball <chris@printf.net> | 2015-05-31 07:45:42 -0400 |
|---|---|---|
| committer | Chris Ball <chris@printf.net> | 2015-05-31 07:45:42 -0400 |
| commit | e461589d2e1715ada3808da1cb52eaf922944587 (patch) | |
| tree | 03feca56d997785dab19fa0a05947e12cc7e29d6 /README.md | |
| parent | ec9f63e828de47aeb15c28b7a4ebacee71770276 (diff) | |
| parent | 4e440776743ac216d19a7fc53c83a0681fdbf45b (diff) | |
Merge pull request #16 from mgalgs/patch-1
README.md: Add missing word
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -35,7 +35,7 @@ When Git is asked to perform a network operation with a URL that starts with e.g In GitTorrent's case, we could be asked for three styles of URL: * `gittorrent://some.git.hosting.site/somerepo` -- we connect over `git://` to find out what the latest commit is, then perform the download using that commit's sha1. This is kind of like a [CDN](CDN) for a git server; the actual download of objects happens via peers, but the lookup of which objects to downloads happens in the normal Git way. * `gittorrent://<hex sha1>/reponame` -- the sha1 corresponds to a gittorrent user's "mutable key" (hash of their public key) on our DHT -- we look up the key, receive JSON describing the user's repositories, and then perform the download using that commit's sha1. This doesn't use any resources outside of GitTorrent's network. -* `gittorrent://<username>` -- the username is converted into a mutable key sha1 as above. The mapping from usernames to happens on Bitcoin's blockchain in OP_RETURN transaction. +* `gittorrent://<username>` -- the username is converted into a mutable key sha1 as above. The mapping from usernames to sha1s happens on Bitcoin's blockchain in OP_RETURN transaction. ## 2. Distributed hash table |