Hi All,

Do you know a use case which needs Single Onion Services and NAT punching?

We’re wondering if there are mobile or desktop applications / services that would use a single onion service for the performance benefits, but still need NAT punching. (And don’t need the anonymity of a hidden service.)

Single Onion Services:

* can’t do NAT punching, (they need an ORPort on a publicly accessible IP address),

* locations are easier to discover, and

* have lower latency.

Hidden Services:

* can do NAT punching,

* locations are hard to discover, and

* have higher latency.

Are there any use cases that:

* need NAT punching, 

* don’t need service location anonymity, and

* would benefit from lower latency?

Thanks

Tim