Federated ecash based lightning address server, quite a cool idea for resilient always online LN receive while storing sats in a bearer asset.
https://github.com/Kodylow/hermes
## Hermes: A Noncustodial Lightning Address Messenger w/Fedimint
Hermes is a non-custodial, asynchronous lightning address server that uses Fedimint Ecash on the backend. The protocol flow of Hermes is as follows:
### Registration
1. Users register their Nostr public key and username with the Hermes server. This registration process creates a lightning address for the user.
2. The registration requires a small fee in ecash or lightning.
### Receiving Payments
3. Sender follows normal lnurlp protocol hitting well-known and callback endpoints.
4. Hermes server creates a Fedimint Lightning Gateway transaction based off the receiver's public key, and returns the invoice to the sender via the callback endpoint.
5. Sender pays the lightning invoice, which the lightning gateway immediately completes by locking ecash to the receiver's public key.
6. Hermes server sends a notification to the receiver that they have received a payment.
7. When the receiver's Fedimint Client next connects to their federation, they scan for the payment and reissue the pubkey locked ecash.
Max Hillebrand
npub1kl…lx3vt
2024-01-18 23:15:18
Author Public Key
npub1klkk3vrzme455yh9rl2jshq7rc8dpegj3ndf82c3ks2sk40dxt7qulx3vtPublished at
2024-01-18 23:15:18Event JSON
{
"id": "4124435742cc64095680d282da8f11671f69c9764cda15022d11c1b3e59e3ca9",
"pubkey": "b7ed68b062de6b4a12e51fd5285c1e1e0ed0e5128cda93ab11b4150b55ed32fc",
"created_at": 1705616118,
"kind": 1,
"tags": [
[
"r",
"https://github.com/Kodylow/hermes"
]
],
"content": "Federated ecash based lightning address server, quite a cool idea for resilient always online LN receive while storing sats in a bearer asset. \n\nhttps://github.com/Kodylow/hermes\n\n## Hermes: A Noncustodial Lightning Address Messenger w/Fedimint\nHermes is a non-custodial, asynchronous lightning address server that uses Fedimint Ecash on the backend. The protocol flow of Hermes is as follows:\n\n### Registration\n1. Users register their Nostr public key and username with the Hermes server. This registration process creates a lightning address for the user.\n\n2. The registration requires a small fee in ecash or lightning.\n\n### Receiving Payments\n3. Sender follows normal lnurlp protocol hitting well-known and callback endpoints.\n\n4. Hermes server creates a Fedimint Lightning Gateway transaction based off the receiver's public key, and returns the invoice to the sender via the callback endpoint.\n\n5. Sender pays the lightning invoice, which the lightning gateway immediately completes by locking ecash to the receiver's public key.\n\n6. Hermes server sends a notification to the receiver that they have received a payment.\n\n7. When the receiver's Fedimint Client next connects to their federation, they scan for the payment and reissue the pubkey locked ecash.",
"sig": "45e84a7e6a0d960d6dd19c4416372892f6da5ed6f01706538449d05fa70260180d12d69b6d1c81bae64b36684db729e59f1990a0edff31f85fd48d52fbf9ab4a"
}