<p>Generally speaking there are two use-cases that can be facilitated by route hints:</p>
<ul>
<li>Tell the sender about channels that they might not know about. Specifically, if the recipient doesn't announce it's channels, then the sender cannot know about those channels. Hence in order to reach the recipient they will have to share some channels completing the network view and allowing the sender to find paths from sender to recipient. The gossip network is being augmented by route hints from the invoice.</li>
<li>The recipient can hint to the sender that some channels have sufficient balance to be used for the payment described by the invoice. Assuming the recipient has many channels, some of them could be exhausted, this the recipient adds a list of channels that have balance to the invoice. This prevents failed attempts that would cost us time, since it's the last hop. This technique is sometimes referred to as route boost.</li>
</ul>

CC BY-SA 4.0
2023-08-18T22:21:52.860Z
so are the route hints added permanently to the sending node's network view or are they discarded after the payment has reached a final state?
oz21m
CC BY-SA 4.0
2023-08-21T08:40:37.130Z
They are discarded, as the information contained within is not verifiable. For example, nodes will passively prune their view of the network as they see channels closing onchain, which we can't do if the route hints uses an alias that doesn't point at a specific output (valid with option_scid_alias), and we'd have that channel forever in our view. It also is more respectful to only use the channel the one time the recipient told us about it
cdecker
CC BY-SA 4.0
2023-06-27T22:52:33.610Z
2023-06-27T22:52:33.610Z
cdecker
<p>I understand that route hints can be provided when generating an invoice, but how exactly do wallets use this information to assist in pathfinding? I imagine this can vary slightly between implementations since there doesn't seem to be any strict rules on how to use them in the BOLT specs.</p>
<p>Are there any standards for how to use route hints or might they be completely ignored by a lightning wallet?</p>

CC BY-SA 4.0
2023-06-28T06:34:50.453Z
Does this answer your question? [What exactly are route hints?](https://bitcoin.stackexchange.com/questions/108415/what-exactly-are-route-hints)
Vojtěch Strnad
CC BY-SA 4.0
2023-08-18T22:16:34.723Z
@VojtěchStrnad that answer helped a bit but I was looking for more detail on how a sending wallet uses routing hints to build the onion to attempt a payment
oz21m
<lightning-network><lightning-routing><invoices><lightning-rfc><route-hints>
How do route hints affect pathfinding?
oz21m
# How do route hints affect pathfinding?

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

I understand that route hints can be provided when generating an invoice, but how exactly do wallets use this information to assist in pathfinding? I imagine this can vary slightly between implementations since there doesn't seem to be any strict rules on how to use them in the BOLT specs.

Are there any standards for how to use route hints or might they be completely ignored by a lightning wallet?

**Tags:** lightning-network, lightning-routing, invoices, lightning-rfc, route-hints

> **Comments:**
> **username_1**: Does this answer your question? [What exactly are route hints?](https://bitcoin.stackexchange.com/questions/108415/what-exactly-are-route-hints)  
> **username_0**: @username_1 that answer helped a bit but I was looking for more detail on how a sending wallet uses routing hints to build the onion to attempt a payment  

---

## 1 answers

### Answer by username_2 on 2023-06-27. Score: 6 | Accepted answer

Generally speaking there are two use-cases that can be facilitated by route hints:

* Tell the sender about channels that they might not know about. Specifically, if the recipient doesn't announce it's channels, then the sender cannot know about those channels. Hence in order to reach the recipient they will have to share some channels completing the network view and allowing the sender to find paths from sender to recipient. The gossip network is being augmented by route hints from the invoice.
* The recipient can hint to the sender that some channels have sufficient balance to be used for the payment described by the invoice. Assuming the recipient has many channels, some of them could be exhausted, this the recipient adds a list of channels that have balance to the invoice. This prevents failed attempts that would cost us time, since it's the last hop. This technique is sometimes referred to as route boost.

> **Comments:**
> **username_0**: so are the route hints added permanently to the sending node's network view or are they discarded after the payment has reached a final state?  
> **username_2**: They are discarded, as the information contained within is not verifiable. For example, nodes will passively prune their view of the network as they see channels closing onchain, which we can't do if the route hints uses an alias that doesn't point at a specific output (valid with option_scid_alias), and we'd have that channel forever in our view. It also is more respectful to only use the channel the one time the recipient told us about it  

---

