@cft

Is this a set of packets where only new packets (to be appended to the log) will be added to the set? Or could it be that the producer suddenly would have to go back in its log end swap some of the packets in the set with old packets from the log? That would rule out SSB for IoT devices which could only keep a limited window of their log in memory.

The sets should be stable enough. Let's call the nodes 1, 4, 13, 40, 120, ... the spine of the graph. The certificate pool of msg n basically connects n to the spine (path from n to the next smaller node in the spine) and travels down the the spine to the origin - this latter part is stable enough for the iot usecase. Finally, the certpool contains the path from the next larger node on the spine to n. I can't tell you whether the connections to the spine are stable enough without knowing more about the requirements.

@mix

hey @Aljoscha if you can write got for the certificate pool

got?

then I’d be happy to make a nice little interactive SVG where people could hover over different numbers and see the nodes and edges followed

That would be great. I started a similar thing at arthack that included computing the graph and how to lay it out. But just doing it for the fixed set of 40 nodes would be sufficient and far simpler.