k98kurz / gossip Goto Github PK

Is your feature request related to a problem? Please describe.
Currently, the examples implemented have action handlers that forward messages/bulletins to all connected nodes, including the node from which the message/bulletin was received. This results in redundant messages.

Describe the solution you'd like
The node from which the message/bulletin was received should be excluded from that forwarding mechanism in the action handler. This can be done using the Neighbor class to simulate how each individual Node would act, though this requires additional O(n) memory.

Describe alternatives you've considered
Considered adding it to the base classes, but it should be implementable without any changes to interfaces or base classes.

Is your feature request related to a problem? Please describe.
The problem is that the current model uses hashcash at the Message level, making forwarding of Bulletins costly for forwarders rather than the progenitor of the Bulletin.

Describe the solution you'd like
The hashcash mechanism should be implemented at the Bulletin level rather than at the Message level. In particular, Message should retain hashcash at a lower difficulty threshold to prevent node-to-node spam, and Bulletin should implement hashcash at a higher difficulty to cost the progenitors of Bulletins proof-of-work rather than forwarders.

Is your feature request related to a problem? Please describe.
Hashcash at the Message level prevents individual nodes from spamming other individual nodes. It intentionally throttles network activity with proof-of-work. Currently, this is set globally and is not adaptive.

Describe the solution you'd like
The difficulty threshold for each Message should be tunable at the Connection level, with each Connection starting at a low global threshold. It is not necessary to add an adaptive algorithm for tuning this per-Connection Message hashcash difficulty threshold; it is only necessary to make it possible to do so.