If I'm not mistaken, Bolt12's blinded paths, when adopted widely, should replace the hold invoice approach. If Bob is provably the introduction point to a blinded path in an amount-less bolt12 offer that pays Carol, then Bob can enforce that he'll be paid when Alice pays Carol. Using this approach, it might be possible for several Bobs to be predictably paid when Carol does, assuming blinded paths can contain other blinded paths. This isn't my exact dream of a single payment being split along independent routes, to different receivers, with codependent settlement at the protocol layer, but maybe novel forms of decentralized coordination can wait for bolt13.

Think about the revolutionary technologies of recent decades: the television, the PC, the internet, the smartphone, Facebook, AI. They all took root in the same demographic: people with disposable income in developed countries. Facebook took this approach to the extreme by first opening only to students attending elite Western universities. And now it’s your aunt’s favorite technology. Another lesson.

Source: medium.com

I think the danger here is that if we as a developer community fail to realize the limitations of nostr and try to adapt the protocol to fit every possible use case, on an ad-hoc basis, we're going to end up with a tragedy of the commons, where no developer can comprehend what must be done to get his work done, and all kinds of weird artifacts appear for end users that no one can explain.