<blockquote>
<p>Bolt12 seems to me like a clean solution without necessitating an intermediary web server. What needs to be done in order to get Nostr tipping using Bolt12? Another NIP?</p>
</blockquote>
<p>Yes it is.</p>
<blockquote>
<p>I see that NIP-57 references / depends on the LNURL specification, which references LUD-06 and LUD-16.</p>
</blockquote>
<p>I am not following the nostr protocol but I think it is possible to make an alternative version. I am not sure if it is possible to alternate the NIP a little bit to support bolt12 in it.</p>
<p>Happy to see something around</p>

CC BY-SA 4.0
2023-10-06T19:08:55.203Z
2023-10-06T19:08:55.203Z
vincenzopalazzo
<p>I see that <a href="https://github.com/nostr-protocol/nips/blob/master/57.md" rel="nofollow noreferrer">NIP-57</a> references / depends on the LNURL specification, which references <a href="https://github.com/lnurl/luds/blob/luds/06.md" rel="nofollow noreferrer">LUD-06</a> and <a href="https://github.com/lnurl/luds/blob/luds/16.md" rel="nofollow noreferrer">LUD-16</a>.</p>
<p>As someone still rather new to all the various specifications, can somebody explain to me in simple terms if it is possible to integrate a Bolt12 invoice with LUD-06 or LUD-16 identifiers, and consequently, Nostr tipping?</p>
<p>Bolt12 seems to me like a clean solution without necessitating an intermediary web server. What needs to be done in order to get Nostr tipping using Bolt12? Another NIP?</p>
<p>Thanks in advance for any help putting these pieces of understanding together.</p>

CC BY-SA 4.0
2023-12-22T12:30:42.177Z
What would be the use case? You can already have user-defined amounts with NIP-57 and bolt11. What would a Bolt12 offer add here?
Rainer Feike
CC BY-SA 4.0
2023-12-23T13:53:41.937Z
@RainerFeike As stated, I would like to see p2p tipping over NOSTR without the need for an intermediary web server required by LNURL. There should be more Bolt12 standardization across lightning network implementations in general, but I think NOSTR tipping is a great use case for moving in that direction.
Aaron
<lightning-network><core-lightning><bolt12-offers>
Is it possible to setup Lightning Network Nostr tipping using Bolt12 offers?
Aaron
# Is it possible to setup Lightning Network Nostr tipping using Bolt12 offers?

(Asked by: username_0 on 2023-10-06)

I see that [NIP-57](https://github.com/nostr-protocol/nips/blob/master/57.md) references / depends on the LNURL specification, which references [LUD-06](https://github.com/lnurl/luds/blob/luds/06.md) and [LUD-16](https://github.com/lnurl/luds/blob/luds/16.md).

As someone still rather new to all the various specifications, can somebody explain to me in simple terms if it is possible to integrate a Bolt12 invoice with LUD-06 or LUD-16 identifiers, and consequently, Nostr tipping?

Bolt12 seems to me like a clean solution without necessitating an intermediary web server. What needs to be done in order to get Nostr tipping using Bolt12? Another NIP?

Thanks in advance for any help putting these pieces of understanding together.

**Tags:** lightning-network, core-lightning, bolt12-offers

> **Comments:**
> **username_1**: What would be the use case? You can already have user-defined amounts with NIP-57 and bolt11. What would a Bolt12 offer add here?  
> **username_0**: @username_1 As stated, I would like to see p2p tipping over NOSTR without the need for an intermediary web server required by LNURL. There should be more Bolt12 standardization across lightning network implementations in general, but I think NOSTR tipping is a great use case for moving in that direction.  

---

## 1 answers

### Answer by username_2 on 2023-10-06. Score: 0

> Bolt12 seems to me like a clean solution without necessitating an intermediary web server. What needs to be done in order to get Nostr tipping using Bolt12? Another NIP?

Yes it is.

> I see that NIP-57 references / depends on the LNURL specification, which references LUD-06 and LUD-16.

I am not following the nostr protocol but I think it is possible to make an alternative version. I am not sure if it is possible to alternate the NIP a little bit to support bolt12 in it.

Happy to see something around


---

