PABLOF7z on Nostr: it was very likely from a failed migration from the old NIP-60 format to the new one; ...
it was very likely from a failed migration from the old NIP-60 format to the new one; there used to be different keys involved, now its always the same key that doesn't change
going forward having the invalid p2pk should not be possible since your public key won't be changing
Published at
2025-02-14 16:02:36Event JSON
{
"id": "0398461ca24d7a37346441c8ed496e90044c034da5986730c9af0f990f42b774",
"pubkey": "fa984bd7dbb282f07e16e7ae87b26a2a7b9b90b7246a44771f0cf5ae58018f52",
"created_at": 1739548956,
"kind": 1,
"tags": [
[
"e",
"73179d42a9ea7df0478c86706dfb1b71a11b19f630c0cfecfc63ff874bc00067",
"wss://e.nos.lol",
"root"
],
[
"p",
"4ce66109a2ebabd7ca84551d2e5b6eff409ceaf9e213e3dc061c15cf84d1590c"
],
[
"r",
"wss://f7z.io/"
],
[
"r",
"wss://pyramid.fiatjaf.com/",
"write"
],
[
"r",
"wss://relay.damus.io/"
],
[
"r",
"wss://relay.primal.net/"
]
],
"content": "it was very likely from a failed migration from the old NIP-60 format to the new one; there used to be different keys involved, now its always the same key that doesn't change\n\ngoing forward having the invalid p2pk should not be possible since your public key won't be changing",
"sig": "147d3cf926096a6a084f1e4904801201254bd12f6cde3f6882a399f4d5221ffb17b25167061ae8f1bd932a6b422de61390c1676549f8b7bf3b6567f1360103c7"
}