# ERIS over CapTP

**URL:** <https://community.spritely.institute/t/eris-over-captp/829>\
**Category:** OCapN Protocol\
**Created:** [May 26, 2026, 10:59pm UTC](https://community.spritely.institute/t/eris-over-captp/829 "2026-05-26T22:59:23Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pukkamustard](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spritely.institute/pukkamustard/32/264_2.png) [@pukkamustard](https://community.spritely.institute/u/pukkamustard)\
**Post date:** [May 26, 2026, 10:59pm UTC](https://community.spritely.institute/t/eris-over-captp/829/1 "2026-05-26T22:59:23Z")

</div>

I’ve been working on some ERIS/Goblins integrations and am happy to announce a small step forward: how to transport blocks of ERIS encoded content via CapTP.

[ERIS](https://eris.codeberg.page) is a way of making content more robustly available over computer networks. It does so by breaking up content into small uniformly sized and encrypted blocks that can be transported over various networks. The content can be re-assembled using a short identifier, called the _read capability_.

[Previously](https://lists.sr.ht/~pukkamustard/eris/%3C87pl5vbigt.fsf@posteo.net%3E) we released initial integrations for using ERIS from Goblins (using the guile-eris library) including actors for encoding and decoding content. Now we can transport blocks using Goblins native transport: CapTP. The latest release of [goblins-eris](https://codeberg.org/eris/goblins-eris) contains a little tool called [eris-captp](https://codeberg.org/eris/goblins-eris/src/branch/main/bin/eris-captp.scm), that can be used to launch block stores that can be reached via CapTP. See the [example](https://codeberg.org/eris/goblins-eris#running-a-store-and-encoding-content) in the Readme.

Furthermore, the tool can act as a proxy between CoAP block stores and stores on CapTP. [The Constrained Application Protocol (CoAP)](https://datatracker.ietf.org/doc/html/rfc7252) is a protocol with HTTP similar semantics that was originally developed for embeded devices, but proves to be very useful for peer-to-peer applications. ERIS uses CoAP as a [primary protocol](https://eris.codeberg.page/eer/coap.xml) for getting blocks of encoded content over networks. There are a number of applications ([kapla](https://codeberg.org/eris/kapla) or [erishell](https://codeberg.org/eris/eris-go)) and even more ERIS libraries (e.g. [Python](https://codeberg.org/eris/python-eris), [Guile](https://codeberg.org/eris/guile-eris)) that speak the CoAP protocol. Using the proxy, we can use existing tools and libraries to transport ERIS blocks over CapTP and also the other way around: we can use existing tools and stores from CapTP and Goblins and all that stuff. See the [example](https://codeberg.org/eris/goblins-eris#running-a-coap-to-captp-proxy) in the readme and also the [announcement to the ERIS mailing list](https://lists.sr.ht/~pukkamustard/eris/%3C87zf1l5rvx.fsf@rdix.inqlab.net%3E).

---

<div class="post-metadata">

**Author:** ![dthompson](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.spritely.institute/dthompson/32/95_2.png) [@dthompson](https://community.spritely.institute/u/dthompson)\
**Post date:** [May 27, 2026, 2:51pm UTC](https://community.spritely.institute/t/eris-over-captp/829/2 "2026-05-27T14:51:13Z")

</div>

This is really neat! Thanks for the update! I will need to actually try this out for myself soon.
