Leakiness of hidden service presence due to startup circuits
In path-spec.txt we have:
Specifically, on startup Tor tries to maintain one clean fast exit circuit that allows connections to port 80, and at least two fast clean stable internal circuits in case we get a resolve request or hidden service request (at least three if we run a hidden service).
Doesn't this mean our guard can see if we run a hidden service? But is that true anyway? Do we care? (Is this in fact true of the C implementation? What should we do in Arti?)
@nickm says the guard will probably be able to figure out if we are running an onion service anyway, based on timing and suggested @mikeperry would have good insight on this issue.