Every Lane Hacker knows the bitter history of our alliance with the Hellfire Legion, their betrayal and how we lost Fu Manchu, our Spyglass Battleship, during the Vespucci Exodus. Every Lane Hacker knows that before this catastrophe we managed to secure Spyglass sensor array blueprints and then reverse engineer them to work properly on our retrofitted L3GS-1 Interrogator gunship. Every Lane Hacker knows that the Spyglass scanner array requires a powerful data processing unit to perform massive iterative recalculations of the raw signal data which is impossible for small vessels. However, not every Lane Hacker knows that for some time now we have been designing a solution to this problem.
Spyglass Network Architecture is a three tier system based on the idea of distributed network of processing units that in the case of insufficient performance falls back on decentralized network of processing hubs. While a typical very heavy fighter can mount at least a rudimentary array of Spyglass antennas and sensors it cannot host a processing unit powerful enough to accommodate the raw signal and translate it into useful data in real time. The solution to this problem is to simply share the raw signal data with other processing units to make it possible.
Tier I
A wing of three or four small vessels can connect to each other directly creating a small distributed network of processing units. One of the ships with installed Spyglass scanner shares raw signal data with all its peers in the network and together they simultaneously compute and render the scanning results. A latency of this solution will be minimal.
Tier II
If a there are not enough vessels in range to create a fully autonomous distributed processing network, a Lane Hacker ship can connect directly to the closest processing hub. Mactan, Cochrane, Leiden and Airdire will compose a decentralized network capable of near instant compilation of compressed raw signal data and returning fully processed results to a lone Lane Hacker vessel in range. Latency of this solution will be negligible.
Tier III
Finally, if a lone Lane Hacker ship is not in range of any of our processing hubs it can still use a nearby lane network to reach it through Neural Net. This solution will be the most risky and erroneous due to typical security measures of the lane network, possibility of detection and finally limited bandwidth. However, maintaining low profile and performing only short scanning bursts should minimize those risk to acceptable levels.
We have already started working on new software for the Spyglass Network. In terms of hardware we do need to build four processing hubs on each of our stations, which will require amongst others a significant amount of bio-neural processors and superconductors. Professor Scorpius will coordinate acquisition of all necessary resources, while I will focus on the software part of this project.
I think I do not need to stress that this matter has now the highest priority.
![[Image: 1a.png]](http://lh.discoverygc.com/image/portraits/square/1a.png)
![[Image: 7.png]](http://lh.discoverygc.com/image/ranks/7.png)
![[Image: 34.png]](http://lh.discoverygc.com/media/34.png)