wormhole node

• its actually 2 nodes
• node 1 drops messages in place X
• node 2 retrieves messages from place X
• messages are literal hive protocol messages
• X is any transport layer, literally anything
• nodes might not know each other at all as long as they know how to retrieve stuff
• the objective is hiding location
• any master that sees node 2 just thinks it is node 1!

implementations: - usenet anon message boards (read # post #)

storage node

• any node can leave a payload in a storage node + associated proof
• optionally encrypted (recommended)
• a proof is a text string + same string encrypted with "receiver pubkey"
• any node can request any (encrypted) file
• the storage node will send the encrypted proof
• the node sends the decrypted proof
• if both match the node proves it is the receiver
• the storage node sends the file

note: connections to these nodes should be ephemeral, ie, nodes disconnect once the deed is done note2: these can be public and hosted by random people, if you trust PGP

rendevouz node

a variation of the above, imagine a scenario with a very very large hive, maybe some nodes are even public or half way across the world

• node fires a "query" hive message
• message contains the address of a storage node the mind should drop the answer in
  • the response doesnt need to travel all the way back
  • optionally include node pubkey (may have been shared out of band)
• node checks the pre defined storage node every timestep until it receives an answer
  • depending on relationship with storage node it might be possible to use events instead
  • a storage node can be a http api (see http bridge TODO)
• where did the answer come from?