What would be needed in order to make zaps work with bolt12-supporting wallets like Phoenix?
Discussion
I can have understood something wrong but I see a flaw in bolt12.
It is ofted praised as a complete advancement over bolt11 but it comes with a fondamental problem: part of the routing, an arbitrarly long path, of the payment is decided by receiver, but payed by sender.
Bolt12 needs first a standardized incentive-compatibles way to deal with that; or am I missing something?
I don't believe that is true. I think you are referring to the routing hints, where I can encode in my invoice the last few hops. Great for when your node is using a private channel as you can only get paid if you provide details on how to get from a public channel to your node.