From EVE University Wiki
Jump to: navigation, search
This page should be updated due to game changes.
Reason: Requires update for Equinox expansion(11 June 2024), removal of TCU and replacing Infrastructure Hub with Sovereignty Hub (Expansion notes)
On Equinox release day, 11 June, all existing infrastructure hubs will automatically convert to sovereignty hubs in legacy IHub mode. Note that if a system has a synchronous TCU and IHub ownership, it will be the IHub that converts to the sovereignty hub.

Sovereignty Hub Transition (Planned for 20 June 2024 27 June 2024) Delay reason

The transfer period will end with the next expansion, when any sovereignty hub operating in legacy IHub mode will be automatically transitioned into Sov Hub mode.

For an in-depth explanation of the SovHub transition, you can visit the Sovereignty, Structures & Transition devblog. More info: Sovereignty Updates: Transition & Upgrades

The Sovereignty Hub's capabilities grow as upgrades are added for coordinating defense, industry, resources, and logistics. Each dedicated upgrade requires a mix of colony resources in the form of workforce, power, and reagents, and apart from the base power generated from the stellar flux, these must be provided by planetary exploitation through the new Orbital Skyhooks.

  • The Sovereignty Hub will generate some amount of energy for the system. The amount of energy generated by this structure is determined by an attribute on the star.
  • When a SovHub registers the claim (either a new one, or due to transition) any TCU in the system will be destroyed.

Upgrades (Planned for 20 June 2024 27 June 2024)

  • Once an alliance has deployed a new Sov Hub in Sov Hub mode or chosen to transition their Sov Hub from IHub Mode to Sov Hub Mode, they are then able to install the new upgrades.
  • Upgrades cannot be installed if the energy cost of installed upgrades (regardless of state) would exceed the potential energy which the system could produce (assuming all planets had skyhooks installed).
  • Upgrades cannot be uninstalled once installed, they can be turned offline, but the only way to remove them is to have them self-destruct which capsuleers with the appropriate roles are able to do.
  • Upgrades can be prioritized, capsuleers with the appropriate roles can do this. Higher priority upgrades are served first for available colony resources (energy, population and consumables). This gives the player control over which upgrades go offline first in case of resource shortfall where all installed upgrades do not have the necessary resources to run. An example of where a shortfall could happen would be a skyhook being destroyed.

New Eden is divided by System Security into: high security, low security, null security, and wormhole space. High and low security space are also referred to as "empire space", because every system is claimed by either Amarr, Caldari, Gallente or Minmatar.

Null security (or nullsec) space is not claimed by the empires, and can be split into:

  • NPC nullsec regions (Curse, Great Wildlands, Outer Ring, Stain, Syndicate and Venal) are claimed by a number of different NPC factions, either pirate or corporation. These factions allow capsuleers to dock at their stations in the same way as low or highsec stations.
  • Sovereign Nullsec - the subject of this article - comprises the rest of the nullsec regions, which can be claimed by any capsuleer (player) alliance. Stations in these areas will be owned by a player alliance, and will usually only allow the owning alliance (and perhaps their allies) to dock.

All nullsec areas are essentially lawless: neither CONCORD nor the empire navies respond to aggression, there are no gate or station guns, and aggression will not result in the loss of security status.

The sovereignty system described on this page is often referred to as "Fozzie Sov", being named after a CCP employee that worked on the system and presented relevant dev blogs.

Sovereignty Structures

Each system in Sov Null can potentially have one of each of the following structures associated with it.

  • Territorial Claim Unit (TCU)
  • Infrastructure Hub (I-Hub)

Each of these structures provide benefits to the owner.

TCU and I-Hub can be destroyed by their owner. Any director of their owner corporation can warp to them, right click the sovereignty structure, and select "Self-Destruct". If it is not canceled, it will explode and disappear, allowing players to place a new sovereignty structure in a different location than they want. Any director of their owner corporation can warp to them to cancel Self-Destruct by right clicking it and selecting "Abort self-destruct sequence".

Initiating and canceling Self-Destruct on a sovereignty structure will cause alliance members to receive a mail for it immediately.

Territorial Claim Unit

Main article: Territorial Claim Unit

Territorial Claim Units or TCUs are essentially flags put up by an alliance. Whoever owns the TCU in a system will be listed on the starmap as the owner of the system.

TCUs do have one tangible benefit, though, by way of a 25% reduction in fuel consumption to any Player-owned starbase owned by the same alliance in that system.

Infrastructure Hub

Infrastructure Hubs or I-Hubs are used to upgrade a variety of aspects of the system. These upgrade can be divded into three categories: Strategic Upgrades, Industrial Upgrades and Military Upgrades. Upgrades, which are actual items that must be produced and delivered to the I-Hub for installation, are unlocked by achieving specific System Index Levels.

Strategic Upgrades

Strategic System Upgrades enable a variety of logistical options for the system, allowing the owner to set up more advanced flex structures such as Jump Bridges or system-wide Cynosural Field Jammers.
This comes at the cost of increased upkeep fees while the upgrade is active. The required additional fee per day is listed within the upgrade's information, and the difference for the remaining days of the upkeep cycle will have to be paid upon activation of the upgrade. From then on, the additional cost will be included in the weekly upkeep payments for the system. Deactivating a strategic upgrade will not refund any fees but will remove the upgrades upkeep cost from future upkeep bills for as long as the upgrade remains inactive.

Strategic upgrades rely on the Strategic Index, which is dependent on how long the alliances claim on the system has been unbroken.

Available upgrades:

  • Advanced Logistics Network: This upgrade allows the onlining of a Standup Conduit Generator at one Ansiblex Jump Gate structure in the same solar system.
  • Cynosural Navigation :This upgrade allows the onlining of a Standup Cynosural Field Generator at one Pharolux Cyno Beacon structure in the same solar system.
  • Cynosural Suppression: This upgrade allows the onlining of a Standup Cynosural System Jammer at one Tenebrex Cyno Jammer structure in the same solar system.
  • Supercapital Construction Facilities: This upgrade allows the onlining of a "Standup Supercapital Shipyards" service module at any Sotiyo-class Engineering Complexes in the solar system.

Industrial Upgrades

These upgrades provide industrial oriented anomalies, such as guaranteed Ore sites or an increased chance for Data Sites. They rely on the Industrial Development Index, which can be increased by mining ores in the system. The Industrial Development Index will degrade if no mining takes place. Alliance members are advised that it will continue to degrade over downtime and thus they should ensure they have mined enough to cover any degradation when aiming to reach the next index level.

Available Upgrades:

  • Ore Prospecting Array 1 - 5: Creates Ore Anomalies in the system. Each level creates one specific belt that's always the same (e.g. Ore Prospecting Array I creates a Small Asteroid Cluster, which always spawns with the same number and type of asteroids). All five contain all ores up to and including Arkonor, and levels 3 and above also contain Mercoxit. If one belt is completely mined out, an identical one will respawn in the same system within a few minutes.
  • Survey Networks 1 - 5: Increases the chance of data or relic sites spawning in the system.

Bug icon red.png Bug: This is thought to not work, or at least provide a statistical increase so small as to not be measurable

Military Upgrades

These upgrades confer bonuses to the presence of combat-oriented sites as well as the chance of wormholes appearing within the system. They rely on the Military Development Index, which can be increased by destroying NPC ships within the system. The Military Development Index will degrade if no NPCs are being destroyed. Alliance members are advised that it will continue to degrade over downtime and thus they should ensure they have destroyed enough pirate NPCs to cover any degradation when aiming to reach the next index level.

Available Upgrades:

  • Pirate Detection Array 1 - 5: This upgrade increases the number of active combat sites in the system (specifically, each level creates at least four additional sites). The term "active" means that if one site is completed, a replacement spawns immediately. Note that this is affected by the truesec level of the system, so a -0.1 system will still never have Sanctums. However, the higher-level upgrades will tend to produce higher-level sites within the constraints of truesec.
  • Entrapment Array 1 - 5: This upgrade increases the chances of DED complexes spawning in the system. (Along with the Military Index requirement, the Entrapment Array I also requires a Pirate Detection Array III installed.)

Bug icon red.png Bug: This is thought to not work, or at least provide a statistical increase so small as to not be measurable

  • Quantum Flux Generator 1 - 5: This upgrade increases the chance of a wormhole being present in the upgraded solar system.

Bug icon red.png Bug: This is thought to not work, or at least provide a statistical increase so small as to not be measurable

Claiming Sovereignty

The mechanics of capturing and defending structures are based around the use of an Entosis Link.

Placing structures

If a system does not currently have an I-Hub, or TCU a player may place one. Deploying an I-Hub or TCU involves buying or making one, and then launching it in to space (right-click and "launch" or dragging the structure to space). Once this is done the structure is in a neutral state and owned by the SCC. To gain ownership of the structure, a player must activate an entosis link on the structure to capture it. Other alliances are free to attempt to capture the structure while it is in this state.

Capturing existing structures

To capture or disable a structure, attackers must first use an entosis link on the structure during its Vulnerability window. Once the link has completed its first cycle, the capture process begins and the alliance owning the structure is notified of the attack. Once the entosis link has been active and uncontested for a certain amount of time, the structure enters reinforce mode and a reinforce timer begins. The duration of this timer depends on the type of structure attacked and the Activity Defense Multiplier (ADM) of the system. These timers are all affected by Time Dilation.

The base timer for each type of structure is:

  • Structure (I-Hub, TCU): 10 minutes
  • Command Node: 4 minutes

ADM is explained below.

There is no speed benefit to having more than one entosis link active on a structure, the time to capture a structure is the same whether the attacker has 1 or 100 links active. If both the defender and attacker have an entosis link active on the structure, all capture progress is paused. If only the defender has an entosis link active, the timer counts up towards its starting value. A structure that was attacked but not fully captured will slowly regen; eventually the timer will return to full.

The reinforce timer will end at a randomly determined point during the structure vulnerability timer two days later. Once the timer expires, command nodes will begin to spawn in the same constellation as the contested structure.

Command node

Command nodes are objects that appear in space. They are shown on the overview and it is possible to warp to them directly. These nodes can spawn in any system within the constellation, regardless of the owner of that system. Their name in the overview identifies the system they are connected to as well as the structure in that system. They also have a unique ID to help identify which node in a system players are referring to. For example, a command node for the TCU in O1Y-ED may spawn in X36Y-G with the name "O1Y-ED Territorial Claim Unit Command Node NK17".

Command node control

  • Once the reinforce timer for a structure hits 0, command nodes spawn randomly within the constellation. Initially 5 of these spawn, with more spawning as time goes one. Once a node is captured, a new node spawns.
  • As the command nodes spawn, a progress bar for the structure appears. It starts at 60%. If it reaches 100%, the defenders have won. If it reaches 0%, the attackers have won.
  • Capturing a command node moves the progress bar by 7%. This means that attackers need to capture at least 9 command nodes. The defenders need to capture at least 6.
  • If an attacking force does not attempt to capture the command nodes, they will automatically regen for the defending team. An unattended capture node event will self-complete in < 196 minutes.
  • Any entosis link activated by a player not in the defending alliance is counted as attacking. This means that an alliance can not enlist other entities to defend their structures with entosis links.
  • If the structure currently has an owner, the capture timer for attacking forces on nodes related to that structure is modified by ADM. The level of ADM bonus is determined by the indices of the system containing the reinforced structure (at the time of initial reinforcement).
  • Once one side has won the event, all other nodes related to that structure will self-destruct.

After the event

If the defender wins the command node event, the structure being fought for becomes invulnerable and will remain that way until the next vulnerability window occurs. If the attacker wins, the next steps depend on the type of structure being attacked. For I-Hubs and TCUs, the existing structure explodes. This allows anyone to anchor their own structure in space to replace the old one.


Structures that have been attacked but not reinforced and command nodes all have defensive regeneration. This means that if the structure is left uncontested, eventually the defending side will win. The maximum regeneration times are as follows:

Structure Regeneration time (min)
I-Hub 50
TCU 50
Command node 98

Note: It takes 196 minutes for an uncontested command node event to end as initially only 5 nodes spawn. This is not enough for the defenders to regain control, so they must wait for 3 of the second set of spawned nodes to regenerate to win the event.

The full flow of structure contesting is shown here:


Activity Defense Multiplier

The length of time it takes to reinforce a structure or capture a command node depends on the Activity Defense Multiplier (ADM) for the system. This rewards an alliance for holding and being active in the system, making it easier for them to defend.

The base timer for the structure is multiplied by the ADM to give the total amount of (uncontested) time required for an attacker to reinforce a structure or capture a command node. The time taken for a defender to regen a structure or capture a command node is unaffected by the ADM.

The ADM is calculated based on the value of 3 defensive indices:

  • Strategic Index: Automatically increases as you hold control of the I-Hub over a continuous period.
  • Military Index: Increases in proportion to the number of NPC ships killed in the system.
  • Industrial Index: Increases in proportion to the volume of ore mined in the system.

In terms of the Industry index: mining waste is NOT[1] going to be part of the ADM calculation.

Each of these indices has a level between 0 and 5. To determine the current ADM of a system, find the corresponding modifier for each of the system's indices in the table, then add them all to the base value of 1. For example, a system with Military Index 3 (+1.7), Industrial Index 1 (+0.6) and Strategic Index 5 (+1.0) would have an ADM of 1.0 + 1.7 + 0.6 + 1.0 = 4.3. The maximum value for ADM is 6, which would extend the time taken to reinforce a structure to 60 minutes, or capture a command node to 24 minutes for an attacker. As 6 is the maximum ADM, if the calculation produces a value above 6, the ADM for the system will be 6.

Index Level 0 1 2 3 4 5
Military 0 0.6 1.2 1.7 2.1 2.5
Industrial 0 0.6 1.2 1.7 2.1 2.5
Strategic 0 0.4 0.6 0.8 0.9 1

Below is a partial list of possible total multipliers based on different combinations of system indices:

Military Index Level Industrial Index Level Strategic Index Level Total Activity Multiplier Time to reinforce a structure Time to capture a command node
0 0 0 1x 10 minutes 4 minutes
0 0 5 2x 20 minutes 8 minutes
5 0 0 3.5x 35 minutes 14 minutes
0 5 5 4.5x 45 minutes 18 minutes
4 2 2 4.9x 49 minutes 19.6 minutes
3 3 5 5.4x 54 minutes 21.6 minutes
4 4 4 6x 60 minutes 24 minutes
5 3 5 6x 60 minutes 24 minutes
5 5 5 6x 60 minutes 24 minutes

Capital systems

Major staging systems aren't necessarily a safe place for activities that boost Military or Industrial indices, which can have a negative effect on the ADM for those systems. This could make it more difficult for an alliance to defend their home system. To counter this, each alliance is able to designate one system as its Capital system. The alliance must own the TCU in the system it chooses. The system set as the Capital system will have a +2 bonus to the ADM. The maximum ADM is still 6x, the capital boost acts purely as a mechanism to make it easier to reach ADM 6. Changing the capital system of an alliance takes several days to take effect.

Raising indices

In 2009, CCP posted this chart indicating the time required to raise strategic index levels.[2] The exact formula for raising of the other indices is unknown.

Index Level Time
1 7 days
2 21 days
3 35 days
4 65 days
5 100 days

Vulnerability window

Structures are not vulnerable to attack 24 hours a day. Each alliance has a window of time set during which their structures are vulnerable to attack. This is usually their "prime time" where they are best able to fend off any attacks. Newly deployed or captured structures will inherit this setting from the alliance that controls it. However, the alliance can choose to change the window of any structure the default setting to a custom value. If a structure is partially captured at the end of a vulnerability window, it will remain vulnerable until it is either reinforced or successfully defended.

Changing the vulnerability window

To stop an alliance shifting vulnerability timers at short notice in an attempt to avoid an impending attack, it takes 96 hours for a change in the vulnerability window to take effect. At the end of this 96 hour waiting period, the structure will be vulnerable twice within the same 24 hour period, during both the old window and the new one. From then on, the new vulnerability window setting takes effect.

ADM scaling

The default length of the vulnerability window is 18 hours, but this can be reduced by increasing the ADM of the system. The length of the window is 18 hours divided by the ADM. This gives a window ranging from 18 hours for ADM 1, to 3 hours for ADM 6. The length of each day's vulnerability window is locked in at the midpoint of the vulnerability window the day before. This is to ensure that players are not surprised by last minute changes to the window.


  1. ^ EVE forum: From Extraction To Production: Update By CCP Psych 2021-11-10. Accessed 2023-06-30.
  2. ^ Devblog: Upgrading And Upkeep Of Sovereign Solar Systems In Dominion By CCP Chronotis 2009-11-07. Accessed 2023-06-30.