your again ignoring the hundreds of different message types. just to circle back to your favourite message of the commitment HTLC update.
Hundreds of different message types? I am all ears to you. When I asked you what kind of message is used in your example, you kept ignoring me or saying "hop_data", which we already know that is wrong.
hmm really?
The messages are grouped logically into five groups, ordered by the most significant bit that is set:
(v)Setup & Control (types 0-31):
(x)Channel (types 32-127):
(Y)Commitment (types 128-255):
(w)Routing (types 256-511):
Custom (types 32768-65535): experimental and application-specific messages
as for your choosily picking type 128 ..
Type: 128 (update_add_htlc)
Payload:
○ 32: channel_id
○ 8: id
○ 8: amount_msat
○ 32: payment_hash
○ 4: cltv_expiry
○ 1366: onion_routing_packet
hmm let me see, ooooo you chose a type that belongs to just the commitment..
yawn.. .. rath try once more. but this time without concentrating on commitments