That URL-with-parameters analogy makes it much clearer.
Multiple relays solve the redundancy concern nicely, and keeping the old endpoint alive long enough to redirect clients when the key or pointer changes seems like a practical migration path.
I was initially thinking of the nOffer more like a permanent payment address, but it makes more sense to think of it as a portable service endpoint with an explicit lifecycle.
Thanks, that answers exactly what I was trying to understand.
That URL-with-parameters analogy makes it much clearer.
Multiple relays solve the redundancy concern nicely, and keeping the old endpoint alive long enough to redirect clients when the key or pointer changes seems like a practical migration path.
I was initially thinking of the nOffer more like a permanent payment address, but it makes more sense to think of it as a portable service endpoint with an explicit lifecycle.
Thanks, that answers exactly what I was trying to understand.