What do you think about integrating into a bridge server so that me@me.com would first access the lnproxy api to hide the @me.com public key? Then the owner of me.com could trust the bridge server code they're running to make sure that the payment hashes always match and the "max fees" don't change.
me@me.comwould first access the lnproxy api to hide the@me.compublic key? Then the owner ofme.comcould trust the bridge server code they're running to make sure that the payment hashes always match and the "max fees" don't change.