Event JSON
{
"id": "cab9c450d341a55a52ed31ee435e01271d74dc901df0f7e2b1facc26c5dbb7e2",
"pubkey": "576d23dc3db2056d208849462fee358cf9f0f3310a2c63cb6c267a4b9f5848f9",
"created_at": 1746069148,
"kind": 1,
"tags": [
[
"e",
"e769553791abb162c0b686a03387c208e1927bea9053ae517bdd8e5eb6f8b2de",
"wss://bostr.bitcointxoko.com",
"root"
],
[
"p",
"ee11a5dff40c19a555f41fe42b48f00e618c91225622ae37b6c2bb67b76c4e49"
],
[
"r",
"wss://nos.lol/"
],
[
"r",
"wss://nostr.land/"
],
[
"r",
"wss://nostr.wine/"
],
[
"r",
"wss://relay.getalby.com/v1"
],
[
"r",
"wss://theforest.nostr1.com/"
],
[
"r",
"wss://wot.utxo.one/"
],
[
"r",
"wss://relay.snort.social/"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://relay.primal.net/"
]
],
"content": "I don't think DHTs are the right direction for small data. You're better off spraying the same records across many databases, like nostr relays. This gives you more redundancy, and the implementation is simpler. I think you could even use nostr events by first signing the message with the stronger algorithm, including this in an attribute, then signing the usual way. Even if it becomes possible to forge the outer signature, you can use the old algorithm to find potential events and then filter out those that don't have valid new signatures.\n\nI'm also not concerned about quantum cryptography. So far it seems to be a great way to attract funding and scare cryptologists, but practical advances have been limited. It may be more useful as a tactic to scare people into using unproven, less secure alternatives rather than those that are actually secure today.",
"sig": "97bca52d903cf09f0226847bb6378814831243a34cb64b46f6c6e6a51070366f6cdb11593a92e45776dd1aea6574bc4a3659a2fd0a56e16f8152622be347e4ab"
}