Skip to content

Commit 2240226

Browse files
committed
Add mention of the spec
1 parent fc1a180 commit 2240226

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

docs/concepts/ipns.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -136,6 +136,8 @@ It should be noted that there's an upper limit to the number of unique IPNS name
136136

137137
Steps 5 and 6 describe from a high level how IPNS record persistence is layered over PubSub by ensuring continuous propagation of the IPNS record in the face of node churn (nodes dropping in and out of the network).
138138

139+
> Further details about the IPNS over PubSub protocol can be found in the [IPNS over PubSub Spec](https://github.com/ipfs/specs/blob/main/naming/pubsub.md#protocol)
140+
139141
### Tradeoffs between consistency vs. availability
140142

141143
The self-certifying nature of IPNS comes with an inherent tradeoff between **consistency** and **availability**.

0 commit comments

Comments
 (0)