Wormholes

Someone spawns a wormhole a system, scans that system's static, warps to it and checks the next system, decides that that route isn't interesting or viable, goes back and collapses his connection to the system in order to roll the dice again.

Happens every day, and if that hasn't occurred to the inhabitants of the system, and providing they weren't online or paying attention when that happened, it might look to them like despite the absence of any K162 at the moment of their scanning, someone has been coming from the only place they couldn't possibly be coming: their unwarped static. And the fact that static will despawn within normal time will only serve to fuel the confusion.

Sheer observation over the years however, has wiped these speculations from the table. There's no need for an official word from CCP about it to anyone who's been doing this for a while.

I just posted something of a similiar nature in the other thread about this - tho from the other way around - we were almost jumped in site by another corp who I know of fairly well and chat to some of their members now and again in the AHARM public channel the scenario being:

Both corps had collapsed all links to their WH and left their static scanned but not warped to.
Both corps ran sites about the same time while monitoring for new sigs, etc. as usual.
The other corp once they'd run their sites then warped to their static looking for pew.
The WH then linked straight to us.
We saw the new sig and pulled out the site as their cloaky scout was narrowing down which site we were at.

After the failed gank there was some banter about it between myself and those in the corp who were in the same channel ingame - which clarified the above points including that we were the first place their static linked to - to my mind its pretty conclusive that the link to us was only spawned once they initated warp to it.

I totally agree. But still they swear blind :)

A though has just occurred to me; has anyone scanned their fresh new static just before DT, then waited till after DT to warp-to and jump?
A comparison of the K162 side's Sig ID with other Sig ID's in-system might provide a clue..

This is a fairly safe rule of thumb to be honest. I wouldn't leave a static unscanned for days because in that time you could've had an incoming that was collapsed quickly, and when that incoming existed someone could've come in and "opened" your static, leaving you in a position of believing that it hadn't spawned when it actually had.

The only way you can really know, or at least be as sure as you can be, is to collapse the static yourself at such time that you know there are no other incoming wormholes or people already inside cloaked. As soon as you see probes that aren't your own, or time has passed when noone was watching d-scan, the saffest policy is to assume it has probably already been spawned by someone else.

The Schrödinger's Cat observation is particularly astute

If you were using Staticmapper, it was never 100% accurate anyway. Many times I'd noticed that jumps I'd made with various characters weren't showing. (And yes I was well aware of the refresh times on there). I can't speak for any other websites offering the same sort of service.

Hi ...

I am in the camp that static WHs are spawned only when warped to at their initiating end. I do not know if this is true for all wormholes.

The justification is pretty simple ... static wormholes never appear as K162s. For example, a C2 with static B274 and static Z647 will always have one of each of these. Always ... in my experience after a year in a WH scanning the new exits down every day. These always existed ... never replaced by a K162. The odds of these never being scanned from the other side which could happen under the hypothesis that both ends are established when the signature is spawned ... never occurred. So, I think the hypothesis that the static WH link is only spawned when warped to is correct.

In addition, I suspect that this is true of all WH mechanics. The server spawns signatures and the WH link is only created when the initiating signature is instantiated by someone landing on grid. The exit wormhole becomes a K162. There is no way to prove this of course ... but it does avoid alot of issues (simulaneous discovery, race conditions ...) and makes the coding much simpler and requires less data base storage since any signatures that aren't warped to do not generate any overhead.