The issue of payload distribution among all hops is addressed, and it is suggested that the sender and receiver should negotiate all details of payment beforehand to prevent fee-shaving. The concern of onion reuse and replay attacks is also discussed, with the suggestion that if nodes remember all r-preimages, then the first hop would immediately pull funds. It is noted that all hops receive a per-hop payload which includes details such as payment and time-lock value, making it difficult for the second-to-last hop to re-create a new onion blob. Ultimately, assuming the final receiver knows the expected value for each r-hash, the payment as a whole should not be affected.