Event JSON
{
"id": "f83e98aa2788144064ed1f890d63a8cc9a05b4097b1d59879aa425a6ca986277",
"pubkey": "8cda1daafb2df8daf4500533cba69b645afa0caf7136e341be1b66a2e9e5bdd8",
"created_at": 1745326226,
"kind": 1,
"tags": [
[
"p",
"eba7c2b111a28fa8e7cb07f1ae0feef490d49d897bd7b1fb5ce5d3f0d6739e8f",
"",
"mention"
],
[
"p",
"8cda1daafb2df8daf4500533cba69b645afa0caf7136e341be1b66a2e9e5bdd8",
"",
"mention"
],
[
"p",
"5ebe60a6f2ac6af3a8e13774f7f187ba83332f5d034211f50c3938f1dc4e7bb6",
"",
"mention"
],
[
"p",
"e0e92e542d79b28e79c6efe95891d38f49636e48560a8e618b953bded630dfaa",
"",
"mention"
],
[
"p",
"b90c3cb71d66343e01104d5c9adf7db05d36653b17601ff9b2eebaa81be67823",
"",
"mention"
],
[
"p",
"f7d1876032e99fb04ec7a674bc2273af725a2f5c620ef7719241417589dcaf0c",
"",
"mention"
],
[
"e",
"123c09215ee87377e18915da455770a247624221f0e3e93949d5a10c9d6d8596",
"",
"root"
],
[
"e",
"14278648db8c2d270dde94523c6059f7035554e513367bb7a3e58e74439aabe9",
"",
"reply"
]
],
"content": "Not in any terribly useful way, but yes? The problem is that Nostr uses an incompatible elliptic curve for the DHT. \n\nSo, you could technically use the same seed to generate a Nostr key and also a Pubky, and then you could use whatever discovery system in each to list the key of the other (put your Nostr key in your Pubky data, and vv).\n\nOtherwise, these are two separate networks with separate URLs, separate data methods, etc, so bridging them isn't super-practical.\n\nNostr could change this, and start using our PKDNS method, but it would be a breaking change. (They should though, it's a strict upgrade.) ",
"sig": "9b7db896fc0c63f5895c64f519a4d05e2de7edecd43abede4e469adbe4d37a2b60096c5f20b89c9c6a2fb99c8cdb835355f59a2a50ed25196674c5aec6792b0d"
}