Open K0IN opened 1 year ago
First, I'd say don't worry about your own DHT network, you don't need that for what you're describing. Data of the Hyperdrive is not stored in the DHT, so the setup will be the same with or without your own DHT. Although, you're welcome to experiment and/or spin up a node in the main DHT network :)
Hyperdrives are private by default. If you're seeding the drive, that's only advertising the discovery key
(hash of the public key) in the DHT network and this is safe, so no one can read your drive unless someone has the public key
You can use the drive's public key yourself to replicate it several times as form of backups
Discovery key = discovery purposes Public key = read capabilities (starts as private but you can share it) Secret key = write capabilities (don't share it or else haha)
If happens that you actually need the --bootstrap
option let me know, we can add it
Thanks for the quick reply. I think a bootstrap option would be great for (like in my case) offline/private networks with no access to the internet - but access to the nodes.
:) i couldn't find any guide on how to host a drive/dht (in a production scenario), is there any documentation on how to do so?
First just to clarify, if I create a new drive it will be advertised in the public holpunch DHT?
I see correctly that i could host this dht myself?
Like this: hyperdht --bootstrap --host (server-ip)
So how do i advertise a drive in my private DHT?
Im asking for a private network, where I want my own data to be seeded as backups on multiple devices.