Quote from: franky1 on Today at 02:05:37 PM

hmm really?

Yes. Again, "hop_data", "onion_packet" and "hop_payloads" are not 2 byte big-endian values. They do not match the criteria specified in the message structure.

If "onion_packet" is a valid type for a bolt01 message then why "channel_update"' type is 258 and not just "channel_update"? It should be a simple question for you to answer.

Quote from: franky1 on Today at 02:05:37 PM

if you really want to play games that a node never sends onion routing messages or routing gossip messages without being encapsulated in a channel HTLC commit, you can play those games for decades. but you will just be playing with your group

I have never said anything like that about gossip messages. They can be formatted as bolt01 messages as all of them have a valid type.

Quote from: Rath_ on Today at 12:16:23 AM

bolt07 messages: announcement_signatures, channel_announcement, node_announcement, query_short_channel_ids/reply_short_channel_ids_end, channel_update, query_channel_range/reply_channel_range

Their types are: 259, 256, 257, 261, 258, 263, 264 respectively.

Quote from: franky1 on Today at 02:05:37 PM

find route(node gossip), access fee's accept particular route(channel gossip). have destination accept. hops response back down the path... then commit

You can remove "find route(node gossip), access fee's accept particular route(channel gossip)" as Lightning nodes constantly send/receive gossip and build a local map of the whole network. They use it to calculate payment paths.

Another simple question for you. How do they response back then? What's the message they use? You used to say "funding_locked", but you now know that it's sent only to signalise that the funding transaction has reached enough confirmations.

Quote from: franky1 on Today at 02:05:37 PM

but here is the thing. alice has to try a route to first know if one can be found, whether hops have liquidity to forward, and find out the total the fees actually are to then commit to bob

Why would she need to learn the total fees? Each "channel_update" message contains "fee_base_msat" and "fee_proportional_millionths". Every node in the network listens for these changes and adjusts their local map of the network. Alice already knows how much she is going to pay before she actually tries to send the transaction. How do hops reply that they have enough liquidity in your opinion?