Re: #3, the last hop doesn't know the amount being sent because of multipath, etc., and he does not know the recipient because he does not know he is the last hop. Onions are padded at each step so that they are always 1300 bytes. So the last hop thinks he might be the first hop with up to 19 more to go. Re: "by default," lightning nodes don't expose your IP address to the public by default because the only way that happens is if you (1) configure your node to route payments (it doesn't do it by default) and (2) choose clearnet instead of tor. Re: the podcast, we recorded it a few days ago and I am excited for its presumably looming release. I made this chart in part based on things I learned while preparing for the de ate, like the fact that monero does not encrypt peer to peer traffic. Dandelion++ is nice but if several of your peers are fednodes logging all of your IP traffic they can learn a lot.
Ok, onion padding I'm assuming you're talking about BOLT12? I'll take your word for it. That's cool I didn't know that. Thanks for clarification. Even if you aren't a routing node, how does the first node in a payment route not know your IP by default? I don't see how that is possible. Yea, Dandelion doesn't encrypt traffic (didn't claim it did). You just can't be sure the transaction you are receiving originated from someone or if they were just another hop. It's not perfect (neither is Tor), but Dandelion AND Tor is strictly better than just Tor. Ok cool, looking forward to listening when it drops, thanks