aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorPaul Frazee <pfrazee@gmail.com>2018-07-06 10:41:31 -0500
committerPaul Frazee <pfrazee@gmail.com>2018-07-06 10:41:31 -0500
commit5569167587e95bd98f4045471dcb4594c5d2c3e6 (patch)
tree9ce67c90d3feda0c3084c516094813c4ecb0b963
parent1a22f614a22c1aaf04f1601390f54b8d1e214456 (diff)
downloaddat-deps-5569167587e95bd98f4045471dcb4594c5d2c3e6.zip
dat-deps-5569167587e95bd98f4045471dcb4594c5d2c3e6.tar.gz
hypercore-v1 -> hypercore
-rw-r--r--proposals/0000-hypercore-header.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/0000-hypercore-header.md b/proposals/0000-hypercore-header.md
index 7a65b3c..dffa8e9 100644
--- a/proposals/0000-hypercore-header.md
+++ b/proposals/0000-hypercore-header.md
@@ -23,7 +23,7 @@ The Dat protocol supports a variety of data structures on top of the hypercore a
At time of writing, Dat's standard data structures are being expanded upon (hyperdb) while existing data structures are being updated with breaking changes (hyperdrive). In order for these changes to be deployed smoothly to the network, it's important that the following needs be met:
- 1. Programs should correctly identify the data structure type and version within a hypercore. This will enable the program to use the correct handling code (eg hyperdb, hyperdrive-v1, hyperdrive-v2).
+ 1. Programs should correctly identify the data structure type and version within a hypercore. This will enable the program to use the correct handling code (eg hyperdb, hyperdrive, hyperdrive-v2).
2. Programs should abort processing a hypercore if they lack support for the type or version of the data structure.