aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorpukkamustard <pukkamustard@posteo.net>2020-11-27 13:00:43 +0100
committerpukkamustard <pukkamustard@posteo.net>2020-11-27 13:00:43 +0100
commita2866d438f77600e789c765593800f387703bf60 (patch)
tree44796569edcb5407b5e62968e5debcfd6b711d57 /doc
parent59e1becdb12f629debd284cc9bd3551553c5a10f (diff)
(eris): encode string, bytevector or content from port
Diffstat (limited to 'doc')
-rw-r--r--doc/eris.adoc2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/eris.adoc b/doc/eris.adoc
index 441da3a..1056fb5 100644
--- a/doc/eris.adoc
+++ b/doc/eris.adoc
@@ -378,7 +378,7 @@ Transport mechanisms include:
- HTTP: A simple HTTP endpoint can be used to dereference blocks
- Sneakernet: Blocks can be transported on a physical medium such as a USB stick
-More interesting transport and storage layers use the fact that blocks are content-addressed. For example the peer-to-peer network https://ipfs.io/[IPFS] can be used to store and transport blocks (see the https://gitlab.com/openengiadina/eris/-/blob/main/eris/block-storage/ipfs.scm[example] using the reference Guile implementation). The major advantages over using IPFS directly include:
+More interesting transport and storage layers use the fact that blocks are content-addressed. For example the peer-to-peer network https://ipfs.io/[IPFS] can be used to store and transport blocks (see the https://gitlab.com/openengiadina/eris/-/blob/main/examples/ipfs.scm[example] using the reference Guile implementation). The major advantages over using IPFS directly include:
- Content is encrypted and not readable to IPFS peers without the read capability.
- Identifier of blocks and encoded content is not tied to the IPFS network. Applications can transparently use IPFS or any other storage/transport mechanism.