Chiefwhite on Nostr: Coinkite im signing the configuration file to approve my bolt12 lightning withdrawl ...
Coinkite (npub12ct…c5ky) im signing the configuration file to approve my bolt12 lightning withdrawl from
OCEAN (npub1qtv…7dze) and when i sign the config file, the signature points to a different address than the one previously used and still used on ocean. since the config file sig is stating a different address (which is not visible in my sparrow wallet), i am assuming this is why it is failing on the signature check on Ocean.
Does anyone have any ideas?
#asknostr
Published at
2025-01-12 04:04:37Event JSON
{
"id": "9217af8e1ec26cb7d6ef01b9be56c5f05560788ca9c140656964e88d582d0a2f",
"pubkey": "ef9a20d782d22b929d1601ff2df44956f1c6d47b9258f7a2c2c3d58b99b5a939",
"created_at": 1736654677,
"kind": 1,
"tags": [
[
"p",
"56172b53f730750b40e63c501b16068dd96a245e7f0551675c0fec9817ee96e0",
"",
"mention"
],
[
"p",
"02d9f5676fffc339ffe94dfab38bebe21ce117c6f1509d9922a82d454f420da2",
"",
"mention"
],
[
"t",
"asknostr"
]
],
"content": "nostr:npub12ctjk5lhxp6sks8x83gpk9sx3hvk5fz70uz4ze6uplkfs9lwjmsq2rc5ky im signing the configuration file to approve my bolt12 lightning withdrawl from nostr:npub1qtvl2em0llpnnllffhat8zltugwwz97x79gfmxfz4qk52n6zpk3qq87dze and when i sign the config file, the signature points to a different address than the one previously used and still used on ocean. since the config file sig is stating a different address (which is not visible in my sparrow wallet), i am assuming this is why it is failing on the signature check on Ocean. \n\nDoes anyone have any ideas?\n\n#asknostr\n\n",
"sig": "2edc08fa50aaa88aa3602d0e22f2e6f911d34da38311681eae28667b62560710d02ceb3acc03726dfbab8c72f725f8d754f9ec3f557527e5f49adfbb2ec1b3db"
}
