The node operator can see where the HTLC(s) end up, that is all as far as I know.
But that is actually obsucated since the mint sends multiple HTLC's and returns the necessary change to ecash user. So its still hard to identify imo
Just a user trying to learn how to dev on #ecash hope this helps
SUPERMAX
npub14c…hqjhl
2024-03-18 22:02:02 UTC
in reply to nevent1q…rnq2
Author Public Key
npub14cgq353exzmhdsvqjtmw4dq7fvyleuls8umyrvd5umhr4gtx6asq7hqjhlPublished at
2024-03-18 22:02:02 UTCEvent JSON
{
"id": "78aef0066b1c996753a78eccb8d0e07bc603395c1d02b621cfe779c16dfab5d4",
"pubkey": "ae1008d23930b776c18092f6eab41e4b09fcf3f03f3641b1b4e6ee3aa166d760",
"created_at": 1710799322,
"kind": 1,
"tags": [
[
"e",
"fa42f5e1d8da760884acf95560bb9743ec3ae75217bb29abaa1230a8cdf05ae0",
"",
"root"
],
[
"p",
"90590edc247b100f23879a412b6616c65e874ac790610a15e6b3257a18d9ae43"
],
[
"t",
"ecash"
],
[
"t",
"ecash"
]
],
"content": "The node operator can see where the HTLC(s) end up, that is all as far as I know. \n\nBut that is actually obsucated since the mint sends multiple HTLC's and returns the necessary change to ecash user. So its still hard to identify imo\n\n\nJust a user trying to learn how to dev on #ecash hope this helps",
"sig": "ca0498545b6ebea54ac41835167d66e52b5dc6b888d11617345b0d13897cf415f503c913f23a7b04c1ece93aa02745bcd1903e7c68c167c212460f0b2f95de86"
}