diff options
| author | Chris Ball <chris@printf.net> | 2015-05-27 14:43:01 -0400 |
|---|---|---|
| committer | Chris Ball <chris@printf.net> | 2015-05-27 14:43:01 -0400 |
| commit | 59635ae30cb7982fbfad78aabe3f637b9e8adcae (patch) | |
| tree | 924b3ae9ed49433480a4e85de0de6f68d64ab2e1 | |
| parent | f85f2237afc49c301dad0c01a1620ec53098d063 (diff) | |
README: Updates for Bitcoin scanning
| -rw-r--r-- | README.md | 4 |
1 files changed, 4 insertions, 0 deletions
@@ -84,6 +84,10 @@ e.g. Note that OP_RETURN transactions are limited to 80 bytes, which limits usernames in this scheme to 29 bytes. +As a convenience, this repository will include a database of registered usernames that is updated regularly. This doesn't make GitSwarm any more centralized -- you can run the same scripts yourself on a downloaded blockchain to make sure that this repository does not lie. This is just to save everyone from downloading tens of gigabytes of blockchain to process. + +By the way, storing full Bitcoin history is not necessary. We just need to scan every transaction once, and can discard each transaction after we've scanned it once and determined whether it contained a valid username registration that we record. We just need to scan through all unprocessed blockchain transactions once, and record where we got up to so that we don't have to look at them again after that. + ## Contributing Please send pull requests! Even changes to the design of GitSwarm are welcome and encouraged; nothing is set in stone. |