You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This required adapting `onion_utils::decode_next_hop` to work for both payments
and onion messages.
Currently we just print out the path_id of any onion messages we receive. In
the future, these received onion messages will be redirected to their
respective handlers: i.e. an invoice_request will go to an InvoiceHandler,
custom onion messages will go to a custom handler, etc.
let next_hop = match onion_utils::decode_next_hop(shared_secret,&msg.onion_routing_packet.hop_data[..], msg.onion_routing_packet.hmac, msg.payment_hash){
2142
+
let next_hop = match onion_utils::decode_next_payment_hop(shared_secret,&msg.onion_routing_packet.hop_data[..], msg.onion_routing_packet.hmac, msg.payment_hash){
0 commit comments