Is this still a thing?
Hey @mekongmonkey it looks like Amboss communities requires 2 total approvals, it does look like we have the Umbrel one it, and 2 more community members must approve!
I have a request too and we may look into this further, we could create a duplicate community (but apparently Amboss governance is difficult and then there would always be two groups) or see if this spurs interest we need more ppl currently in it to approve our requests if we are able to make contact with 2 more other than Umbrelâs on this group that got created let me know!
Hi @usernameisJim, thank you for your response. I will monitor Amboss for nodes labeled with the Umbrel tag to secure additional approvals. If I am understanding correctly, if we both obtain approval, we will be granted the tag and will be able to approve new members. This should help us revive the Amboss Umbrel community.
Sorry for the late reply, thatâs right, Umbrelâs official one, and we need two more to assist approval,
So three must approve a new member to the Amboss community to receive the tag,
Once approved we can then approve another Umbrel employee possibly to help grow this and expedite the process too, let me know if you heard anything!
Hi
I have an issue with amboss.
I made a ghost address on Amboss in my umbrel lightning node, but now I donât know how can I delete itđ
đ¤Śââ
Can you help me to delete the address?
Grok explains better even if gets more verbose than me:
A Ghost Address on Amboss (format like yourname@ghst.to) is a special type of Lightning Address that lets any Lightning node (including your Umbrel one) receive payments using an easy, email-style address â without needing to run your own full Lightning Address server or rely on a custodial wallet service (like Wallet of Satoshi or Phoenix, which hold your keys).
How it works technically
⢠Normal Lightning Addresses require a publicly reachable web server to handle requests and generate invoices pointing to your real node.
⢠Ghost Addresses use a clever trick called Phantom Payments:
⢠When someone pays your Ghost Address, their wallet queries [ghst.to](http://ghst.to) (Ambossâ server).
⢠Amboss generates a BOLT11 invoice where the destination looks like a fake (âphantomâ) node that doesnât exist.
⢠But the invoice includes **route hints** (extra routing info) from Ambossâ API that secretly point to **your real nodeâs pubkey**.
⢠Your node sees the incoming HTLC (payment attempt) via those hints, âinterceptsâ it, and settles it â so the funds arrive directly in your self-custodial node.
⢠Result: You get the convenience of a static, shareable Lightning Address, but everything stays non-custodial and lightweight. No extra server needed on your end.
This was launched by Amboss Technologies in late 2023 specifically to fight reliance on centralized/custodial Lightning wallets.
Why is it tied to your nodeâs identity (pubkey) and not just a node alias?
⢠Itâs fundamentally linked to your nodeâs public key, because the routing magic relies on Amboss including your specific nodeâs pubkey in the route hints for every invoice generated for that Ghost Address.
⢠Ambossâ backend (ghst.to + their API) maps the chosen username (e.g., yourname@ghst.to) directly to your nodeâs pubkey. Thatâs how they know which node should intercept the phantom-routed payment.
⢠A node alias (the friendly name shown in Lightning explorers like 1ML or Amboss.space) is just a gossiped label anyone can set via their node software â itâs not used for payment routing. Aliases can change easily and arenât unique or enforced.
⢠Ghost Address username is unique (first-come, first-served for random ones; custom ones may require subscription), registered via Amboss, and permanently associated with one pubkey to prevent conflicts or hijacking. Changing your nodeâs pubkey (e.g., by wiping LND data) would break the mapping, as the address is tied to that specific identity/key.
Itâs specific to Amboss â not a standard Lightning feature. Other Lightning Address providers (like lightningaddress.com or individual node-hosted ones) work differently and usually require you to run your own endpoint or use their custodial service. Amboss invented this âghost/phantomâ method to make it work for any node with zero extra setup beyond claiming it (often via Thunderhubâs Amboss tab on Umbrel).
About deleting it
From whatâs out there (including Umbrel forums and Thunderhub updates), it seems Ghost Addresses are persistent once claimed â no built-in self-service delete/unclaim in the UI or API (at least as of older docs and user reports). Thunderhub even deprecated Ghost Address support in later versions (around 0.14.x), so if youâre on a newer Thunderhub, the tab might be gone or read-only.
Best next step remains contacting Amboss support directly:
⢠Check https://amboss.space or https://amboss.tech for a contact form / support.
⢠They have community channels (often Discord or Telegram linked from their site/X account @ambosstechambosstech).
⢠Ask them to release/unlink the username from your pubkey â explain you set it up via Umbrel/Thunderhub and no longer need/want it. Since they control the mapping, they can usually do this manually if you prove ownership (e.g., via node signature or account link).
If you share your Ghost Address (without doxxing yourself) or more details from where you see it now, I can try to narrow it down further. Hang in there 
End of grok response
Anyone who may stumble upon,
To summarize these are only the lightning explorerâs (like 1ML.com and more) but this is for just https://Amboss.space features specifically there for Amboss only⌠but this second question relates to their ability to give your node a lightning address easily user generated, but they didnât mean to last reply there and didnât want to be stuck with that lightning address example: mulligan@ghst.io that gets tied to their lightning node
the original question was for the feature (maybe still a niche feature only so far) in amboss to make community explorer tags within their explorer
From the ghost addresses itâs not like a gossip manual broadcast to name your node on the internet with a node alias
Itâs your lightning address you can send and receive bitcoin via lightning from, set by and provided to you by Amboss
It looks like as described above you can unlink it in the settings of your node manager app possibly where linked or contact amboss if you want
If you donât want to wait and publicize that ghost address you made with your node, the final option would be (after following built in recovery or optimally closing channels making sure all funds are safe you used for liquidity and preparing for this well) just set up a new node and either do or donât just spin up another instance of your Lightning Node app and that new one of course wonât be associated with that Lightning address as in example:
mulligan@ghst.io lays dormant old node offline, you set up a new node with a different aezeed seed phrase on LND that old one then is just not associated with anything active anymoreâŚ.
Furthermore connection differences (see more info or be sure to look up core lightning backup feature if you use core lightning app and this implementation of course since itâs different with hsm secret not the aezeed phrase)
Grok gen again:
⢠LND (what most Umbrel nodes run, via apps like Thunderhub):
Yes, it works out of the box if you claimed it through Thunderhubâs Amboss tab (as you did). Thunderhub added specific support for intercepting those âphantomâ payments routed via Ambossâ route hints. This was the main/only ready-made client when Ghost Addresses launched in late 2023.
â Your existing one is tied to your LND node and should continue receiving payments normally (as long as your node is online, funded channels, etc.).
⢠Core-Lightning (CLN):
Technically possible, because the mechanism relies on standard Lightning features:
⢠Invoices with a fake destination + route hints pointing to your real pubkey/channel.
⢠Your node just needs to âseeâ and accept the incoming HTLC via those hints (no special permissions or extra software required beyond normal routing).
Amboss themselves state on ghst.to and in their blog: âGhost Addresses are possible using any lightning implementation and an integration with the Amboss API.â
â However, there is no built-in/off-the-shelf client or app (like Thunderhub for LND) that handles the claim + payment interception for CLN. Youâd need custom code or a tool to query Ambossâ API, generate/handle the mapping, and ensure your CLN node properly intercepts the payments. As of now (early 2026), no popular CLN managers (Ride The Lightning, etc.) or Umbrel/Start9 apps have added native Ghost Address support for CLN. So itâs doable in principle but requires development effort.
Bottom line
⢠If youâre on Umbrel with LND (most common setup): It works great, and thatâs exactly what Amboss built it for initially via Thunderhub.
⢠If you switch to or run Core-Lightning: The address could receive payments to your CLN node if someone re-maps it (via Amboss support/API) to your CLN pubkey and you implement the interception logic (similar to what Thunderhub does). But without a ready tool, itâs not plug-and-play like on LND.
End second Grok gen
I do like some of these features though think they help with the community to scale and connect like easy lightning addresses that are present many ways to set that up historically⌠or community features, or even later any more easy lightning liquidity that was easy as Thor/bitefill, lots of possibilities⌠cheers