In this blog post, I’m reviving my series on the internals of data blobs in Cinode. Dynamic links are a cornerstone of Cinode’s design, enabling secure, updatable references to data in a decentralized network. So far, we’ve covered topics related to dynamic links, most notably: Data layout and verification of dynamic links on the public layer where I describe how the network is protected against bogus data propagation and how the forward-progress rule is applied on dynamic links Encryption of the link target where we can see how dynamic link encrypts the data and what is needed to do this safely The previous post on encryption briefly introduced a peculiar construct called the ‘key validation block.

In the previous post , we successfully set up a PostgreSQL server with all the necessary configurations for OpenStreetMap data. Now it’s time to take the next step and start building a working tile server. The base overv/openstreetmap-tile-server Docker image is designed to work with a single data source - be it a continent, country, or even a part of a country. While this works well for many use cases, I needed something different: the ability to work with multiple selected countries simultaneously.

This blog post will be about an idea I had recently - something I called “secretive folders”. It’s still fresh in my head, and I haven’t deeply analyzed it yet - that’s what this blog post is for: to take you through such an explorational journey. Idea inception I was thinking about one disadvantage of the current CinodeFS API interface - the current API does not have any method to iterate over folder entries.

In the previous post , I introduced the basic structure of the Cinode Maps Helm chart. This resulted in a simple PostgreSQL installation with default settings. Before it can support Cinode Maps, however, the setup requires slight tweaking. Let me guide you through the changes I made. The source of information The original Cinode Maps generator was built using the overv/openstreetmap-tile-server Docker image. It is a perfect solution to quickly spawn a custom map tiles server as a single “batteries-included” Docker container.

It’s been a while since I published my last post, but it’s time to start writing again. There are many topics about Cinode internals that I’d like to cover but before I do another deep-dive post about cryptography I’d like to start with another topic - Cinode maps. This post starts a series of blog posts about my recent adventures with Cinode maps. Despite some personal challenges I faced in 2024, I was still able to push this project forward a little bit.