Cherry Ripe

This is from an earlier revision, I don't think I'm going to use it. It's highly subject to DDOS attacks.

Takes it's name from the Number Station.

Group Broadcast

The purpose of Cherry Ripe is for peers to be able to broadcast signals.

Cherry Ripe does not need to use Beeds to communicate, messages can be sent directly, since messages are public anyway.

Nodes are arranged in a circle with each node referencing the node across, left and right. When it receives a message from one, it will forward to the other 2. If there is an odd number of nodes, one node will have an asymmetric "across". So if it receives a that one, it forwards to all 3. It adds the message ID (hash) and expire to it's log. The message is only forwarded until it's TTL.

A message is generally a signal and a return route. But it can be anything that fits in one packet and allows enough room for the Cherry Ripe header. The header is the hash of the message, the first node that received the message and a TTL time-stamp, and a signature of the origin node.

Eventually, we will be able to identify bad actors with the header data.

Example Use

Alice and Bob have previously exchanged signals, a 32 byte sequence that indicates they are seeking each other out. They have also exchanged "channel codes".

When Alice connects to Waxnet, she wants to find Bob. To do this, she takes Bob's channel code and find the Cherry Ripe channel closest to it. Alice then broadcasts the signal Bob gave her on that channel along with a return route. If Bob is online, he will be listening on that channel and will receive the message. He can then use that return route to connect with Alice.