Hmm I've not set one up yet. Do most clients report it as routing fees?
I must say, nostr:npub19tcpurtt6xulhw0r6sc404j9jraj0h8me2lzs7z2tqewz7l0hpas59nlea's ghost addresses are REALLY slick and easy to set up!
Now we just need to be able to see the deposits in our wallet, rather than just the balance changing without an indication of why. I think that requires LND to update something so they show up in the transaction history, though.
Oh, and NIP-57 support would be fantastic, since my main use-case would be receiving zaps straight to self-custody, and I am sure I am not alone in that.
Either way, GREAT WORK!
Discussion
No. It doesn't appear that your node knows what it is at all, so it doesn't show up in your transaction history whatsoever, as fees paid or otherwise.
From what I understand, when your node sees the payment, it acts as if it is just one hop along the way to route the payment to another destination until it is told by Amboss, "Yeah, about that.. You are actually the destination. Go ahead and keep those sats without forwarding them." That's in the least technical terms possible, mostly because I don't know the technical terms. 🤣
A bit more context on what is happening. The ghost address generates an invoice that tells the sender to route the payment to a fake node that doesn't exist, with your node as the last hop along the way. When your node gets the HTLC instructing it to forward the payment to a node that it has no channels with, it reaches out to Amboss to see if they have a preimage to unlock the HTLC so your node can keep the sats.
Since your node did not appear to be the destination in the HTLC, the payment is not recorded in your transaction history whatsoever, but your available balance increases.