diff options
| author | bnewbold <bnewbold@robocracy.org> | 2018-03-28 15:16:10 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-03-28 15:16:10 -0700 |
| commit | 893e94b0fd0a990c2589ca5ca4dd5a395a59451a (patch) | |
| tree | 6ce136ddf2d9916e5fb77b3879498c88f794ce66 /proposals/0002-hypercore.md | |
| parent | 0723ee3bc70067190cbe97d7d4d686b4bba651a1 (diff) | |
| parent | 9b60e7f06c3ae2f7d409c6caa6908ff3589411bf (diff) | |
| download | dat-deps-893e94b0fd0a990c2589ca5ca4dd5a395a59451a.tar.gz dat-deps-893e94b0fd0a990c2589ca5ca4dd5a395a59451a.zip | |
Merge pull request #17 from bcomnes/patch-2
Fix hash link
Diffstat (limited to 'proposals/0002-hypercore.md')
| -rw-r--r-- | proposals/0002-hypercore.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/proposals/0002-hypercore.md b/proposals/0002-hypercore.md index b01ea0d..a6a560e 100644 --- a/proposals/0002-hypercore.md +++ b/proposals/0002-hypercore.md @@ -321,7 +321,7 @@ IPFS is designed for immutable hash-addressed content, but it provides a mechani # Unresolved questions [unresolved]: #unresolved-questions -- Is there a potential "branch resolution" protocol which could remove the [linear history requirement](#linear-history-requirement) and therefore enable users to share private keys freely between their devices? Explaining the risks of branches to users is difficult. (This is being explored.) +- Is there a potential "branch resolution" protocol which could remove the [linear history requirement](#the-linear-history-requirement) and therefore enable users to share private keys freely between their devices? Explaining the risks of branches to users is difficult. (This is being explored.) # Changelog |