Carla Kirk-Cohen da76d05fa5

htlcswitch: add NextBlinding to ForwardingInfo and set in UpdateAddHtlc ...

When we have a HTLC that is part of a blinded route, we need to include
the next ephemeral blinding point in UpdateAddHtlc for the next hop. The
way that we handle the addition of this key is the same for introduction
nodes and relaying nodes within the route.

2024-04-03 08:38:24 -04:00

..

error_encryptor.go

multi: fix make fmt

2022-08-23 22:10:24 +08:00

forwarding_info.go

htlcswitch: add NextBlinding to ForwardingInfo and set in UpdateAddHtlc

2024-04-03 08:38:24 -04:00

fuzz_test.go

htlcswitch: update fuzzPayload for route blinding

2024-01-16 11:12:11 -06:00

iterator_test.go

htlcswitch: add NextBlinding to ForwardingInfo and set in UpdateAddHtlc

2024-04-03 08:38:24 -04:00

iterator.go

htlcswitch: add NextBlinding to ForwardingInfo and set in UpdateAddHtlc

2024-04-03 08:38:24 -04:00

log.go

htlcswitch: move hop iterator into htlcswitch/hop package

2019-09-05 15:30:31 +02:00

payload_test.go

multi: validate contents in blinded data against payload

2024-04-03 08:38:23 -04:00

payload.go

multi: validate contents in blinded data against payload

2024-04-03 08:38:23 -04:00

type.go

htlcswitch/hop: move hop.Exit and hop.Source to hop pkg

2019-09-05 01:35:23 -07:00