# Expanding on BOLT12

**URL:** <https://delvingbitcoin.org/t/expanding-on-bolt12/1167>\
**Category:** Protocol Design\
**Tags:** lightning\
**Created:** [September 29, 2024, 4:13am UTC](https://delvingbitcoin.org/t/expanding-on-bolt12/1167 "2024-09-29T04:13:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![andyschroder](https://delvingbitcoin.org/letter_avatar_proxy/v4/letter/a/c57346/32.png) [@andyschroder](https://delvingbitcoin.org/u/andyschroder)\
**Post date:** [September 30, 2024, 6:32am UTC](https://delvingbitcoin.org/t/expanding-on-bolt12/1167/2 "2024-09-30T06:32:47Z")

</div>

Here’s another proposal that I missed. This one suggests it should be a bLIP, not a revision of the BOLT. That makes sense to me since this proposal is optional and BOLT12 should work normally if the user doesn’t have/want this proposed feature.

> [@Bolt 12 Trusted Contacts](https://delvingbitcoin.org/t/bolt-12-trusted-contacts/1046):
>
> Bolt 12 makes it possible for lightning wallets to provide a UX that is very close to traditional payment applications. By attaching offers to metadata describing who those offers belong to, users can manage their “contacts list” and easily pay them without any interaction (no need to manually share a Bolt 11 invoice for every payment). This is the kind of payment experience non-technical users expect. However, when sending money to their friends and family, users expect some form of mutual aut…

---

_[View the full topic](https://delvingbitcoin.org/t/expanding-on-bolt12/1167)._