Yep, the recipient will need to redeem the ecash with the mint in order to receive them. Probably an http call but any medium will work. It doesn't need to happen synchronously. This seems like a big improvement over lightning zaps. More private, more async, can all be done in the client.

The token can be issued with a commitment to the pubkey of the receiver that is enforced by the mint and that commitment can be verified by every reader, that's what nostr:npub12rv5lskctqxxs2c8rf2zlzc7xx3qpvzs3w4etgemauy9thegr43sf485vg told me. This is very necessary for the protocol to work in a public environment.

We probably also have to check if the tokens are issued by the set of mints specified as trusted by the receiver.

?cid=586b07f0oanux45k4mphhm2nsn0izf17c70exrkdqzm1x71u&ep=v1_gifs_search&rid=200w.gif&ct=g And if the federated mint is a network of relay operators?