A new phase in the #indranet project began today.

A second active contributor has started creating a list of relay patterns and will be putting together a discussion of each of them, and he's especially focusing on what the protocol enables, given the modularity of the packet assembly system. We plan to make it easy for app developers to build bespoke designs for their application's use case.

I have now set up a kanban board for internal operations at this early stage, that any new contributors will be able to access and add to for their ideas and work towards the project.

I have now got the initial gossip of peer metadata fully working, thanks to a new dht broadcast pattern available in the libp2p kademlia dht that I can only surmise at the depth I have looked is derived from or inspired by dusk.network 's kadcast, a partition resistant reliable broadcast algorithm.

Just a few more bits to finish the thing so expired or changed data triggers updates and broadcasts, and I can finally start on the delay message implementation and disk/network load calculation.

Ah yeah. Forgot. I need to first extend the libp2p peerstore persistence layer, which is backed by the Badger key value store. Maybe that will take a day. I just need to add an iterator to the database accessors because currently I can't even count records and the test I'm working on needs to check the gossip reached all test nodes to fully pass.