{"id":6184,"date":"2026-09-05T13:27:29","date_gmt":"2026-09-05T04:27:29","guid":{"rendered":"https:\/\/eternalsphere.net\/echoes\/?p=6184"},"modified":"2026-09-12T14:03:19","modified_gmt":"2026-09-12T05:03:19","slug":"p6fnqq68pslgtnb","status":"publish","type":"post","link":"https:\/\/blog.eternalsphere.net\/index.php\/2026\/09\/05\/p6fnqq68pslgtnb\/","title":{"rendered":"The Lifecycle of a New Tor Relay"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Running a Tor relay is not as simple as installing Tor, opening a port, and immediately receiving large amounts of network traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A newly launched relay enters the Tor network gradually. During its early life, it must first become known to the network, prove that it is reachable, accumulate bandwidth measurements, demonstrate stability, and eventually become eligible for more important roles.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This gradual process is intentional.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tor is an anonymity network, so allowing newly created relays to immediately receive large amounts of traffic would create serious security problems. Instead, Tor gradually increases the trust and usefulness of a relay over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The lifecycle of a new relay can therefore be understood as a process of <strong>discovery, measurement, maturation, and long-term participation<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">A Relay Is Not Trusted Immediately<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">When a Tor relay starts for the first time, it creates an identity and publishes information about itself to the Tor directory system.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This includes information such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>the relay&#8217;s identity,<\/li>\n\n\n\n<li>supported Tor protocol versions,<\/li>\n\n\n\n<li>available ports,<\/li>\n\n\n\n<li>advertised bandwidth,<\/li>\n\n\n\n<li>exit policy,<\/li>\n\n\n\n<li>and other operational characteristics.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">However, the Tor network cannot simply trust everything that a relay claims.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example, a malicious relay could theoretically claim to have an extremely large amount of bandwidth:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Advertised bandwidth: 100 Gbit\/s\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">If Tor accepted that value without independent verification, an attacker could deploy many relays that falsely advertise enormous capacity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Those relays could then attract a disproportionate amount of Tor traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That would make traffic-analysis attacks much easier.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For this reason, the Tor network does not treat a relay&#8217;s self-reported capacity as sufficient evidence.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Its bandwidth must gradually be measured and incorporated into the network&#8217;s consensus information.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">The Unmeasured Phase<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The original Tor Project article describes the first stage as the <strong>unmeasured phase<\/strong>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Historically, this period lasted approximately the first few days of a relay&#8217;s life.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">During this period, the relay may already be publicly visible and technically operational, but Tor does not yet have enough information to confidently determine how much traffic it should receive.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This creates an important distinction:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Internet connection speed\n        \u2260\nadvertised relay bandwidth\n        \u2260\nmeasured relay bandwidth\n        \u2260\ntraffic actually received\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">A relay connected to a fast server or fiber connection may therefore initially receive very little traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is normal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The available bandwidth of the machine does not automatically determine how frequently Tor clients will select it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, Tor needs time to observe and independently measure the relay.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Bandwidth Measurement Begins<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Once a new relay has been visible for some time, the network&#8217;s bandwidth measurement infrastructure begins to establish a more realistic estimate of its usable capacity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The basic idea can be simplified as follows:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>New relay\n   \u2193\nReceives limited traffic\n   \u2193\nBandwidth is measured\n   \u2193\nNetwork gains confidence in capacity\n   \u2193\nConsensus weight increases\n   \u2193\nRelay receives more traffic\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This process is gradual rather than instantaneous.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A relay operator may therefore notice that traffic increases slowly over several days.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A server capable of handling hundreds of megabits per second may initially receive only a tiny fraction of that amount.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">There is usually nothing unusual about this.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Tor network is intentionally cautious when incorporating new infrastructure.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Why a New Relay Usually Becomes a Middle Relay First<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A normal Tor circuit commonly contains three relay positions:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Client\n  \u2502\n  \u25bc\nGuard\n  \u2502\n  \u25bc\nMiddle\n  \u2502\n  \u25bc\nExit\n  \u2502\n  \u25bc\nDestination\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Each position has different security implications.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A newly created non-exit relay cannot serve as an Exit because its exit policy does not permit that role.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It also generally cannot immediately become a Guard.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As a result, its natural early role is usually:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Guard     No\nMiddle    Yes\nExit      No\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This makes the Middle position the normal starting point for many new Tor relays.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A Middle relay forwards encrypted traffic between other Tor relays.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It normally does not know both ends of the connection.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Guard sees the client&#8217;s network address but not the final destination.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Exit sees the destination but normally does not know the client&#8217;s original address.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Middle sits between them.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Why Guard Status Requires Time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Becoming a Guard is much more significant than simply being accepted as a Middle relay.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The Guard is the first relay contacted by the Tor client.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">That means it can see the client&#8217;s IP address.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For this reason, Tor must be particularly careful about which relays are allowed to occupy the Guard position.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consider what would happen if newly created relays could immediately become Guards.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">An attacker could deploy hundreds or thousands of temporary Tor relays:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Create malicious relay\n        \u2193\nImmediately become Guard\n        \u2193\nReceive client connections\n        \u2193\nObserve user IP addresses\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The cost of attacking the network would become much lower.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, a relay generally needs to demonstrate characteristics such as:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>sufficient uptime,<\/li>\n\n\n\n<li>sufficient stability,<\/li>\n\n\n\n<li>adequate bandwidth,<\/li>\n\n\n\n<li>long enough presence in the network,<\/li>\n\n\n\n<li>and reliable operation.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Only after establishing this history can it become suitable for Guard use.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This means that <strong>time itself is part of Tor&#8217;s security model<\/strong>.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Stability Is a Resource<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Relay operators naturally tend to think about hardware resources:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>CPU,<\/li>\n\n\n\n<li>memory,<\/li>\n\n\n\n<li>bandwidth,<\/li>\n\n\n\n<li>storage,<\/li>\n\n\n\n<li>network connections.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">But Tor relays have another important resource:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>operational history.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A relay that remains online continuously for months can become more valuable than a much faster server that constantly disappears from the network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">From Tor&#8217;s perspective, a useful relay is not merely fast.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It should ideally be:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>reachable\n+ stable\n+ predictable\n+ sufficiently fast\n+ continuously available\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Long-term stability allows directory authorities and clients to build confidence in the relay.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is particularly important for Guard eligibility.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Receiving the Guard Flag Does Not Mean Immediate Heavy Traffic<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">One of the most interesting observations in the original Tor Project article is that traffic can temporarily decrease after a relay becomes Guard-eligible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This may initially seem strange.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A relay has apparently been promoted to a more important role, so why would its traffic decrease?<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The reason is that Tor treats different types of relay capacity as separate resources.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Conceptually, the network has:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Guard capacity\nMiddle capacity\nExit capacity\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">These resources are not always equally abundant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If Guard capacity is scarce, Tor may try to preserve suitable Guard relays for Guard use rather than consuming all of their capacity as Middle relays.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A simplified example might look like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Before Guard eligibility\n\nMiddle traffic:\n\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\n\n\nShortly after Guard eligibility\n\nGuard:\n\u2588\u2588\n\nMiddle:\n\u2588\u2588\u2588\u2588\u2588\n\n\nLater, after clients increasingly adopt the relay\n\nGuard:\n\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\u2588\n\nMiddle:\n\u2588\u2588\u2588\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The exact behavior depends on the state of the network, but the important idea is that Tor actively balances different categories of relay capacity.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Guard Adoption Is Gradual<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Even after a relay becomes eligible to serve as a Guard, it does not instantly become the first hop for a large number of users.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tor clients deliberately maintain relatively stable Guard selections.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This is another important anonymity protection.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Imagine a Tor client that selected a completely random first relay for every new circuit.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Over time, the client would interact with a large portion of the Guard population.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">If an attacker controlled even a small percentage of those relays, the probability of eventually encountering an attacker-controlled first hop would continuously increase.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The simplified problem looks like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Circuit 1 \u2192 Guard A\nCircuit 2 \u2192 Guard B\nCircuit 3 \u2192 Guard C\nCircuit 4 \u2192 Guard D\nCircuit 5 \u2192 malicious Guard\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">Tor reduces this exposure by keeping the client&#8217;s entry-relay choices relatively stable.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of continuously trying new Guards, a client tends to maintain a limited set of trusted entry candidates.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">As a result, newly qualified Guards are adopted gradually across the client population.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This means there can be a significant delay between:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Relay becomes Guard-eligible\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">and:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Relay receives substantial Guard traffic\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">The Mature Relay<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Eventually, a relay that remains online and performs reliably becomes an established member of the Tor network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">At this stage, the network has accumulated substantial information about it.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The relay has:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>a persistent identity,<\/li>\n\n\n\n<li>long-term uptime history,<\/li>\n\n\n\n<li>bandwidth measurements,<\/li>\n\n\n\n<li>stability data,<\/li>\n\n\n\n<li>directory authority observations,<\/li>\n\n\n\n<li>and accumulated client usage.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">A mature Guard\/Middle relay may then receive a relatively stable amount of traffic according to its consensus weight and the overall needs of the network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Its lifecycle can therefore be summarized as:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>New relay\n   \u2502\n   \u25bc\nPublished to directory system\n   \u2502\n   \u25bc\nReachability confirmed\n   \u2502\n   \u25bc\nBandwidth measured\n   \u2502\n   \u25bc\nMiddle relay usage increases\n   \u2502\n   \u25bc\nStability and uptime accumulate\n   \u2502\n   \u25bc\nGuard eligibility\n   \u2502\n   \u25bc\nGradual client adoption\n   \u2502\n   \u25bc\nMature Tor relay\n<\/code><\/pre>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Restarts Are Different From Losing Identity<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">An important practical distinction is the difference between restarting a relay and replacing its identity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Routine maintenance is normal.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For example:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>systemctl restart tor\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">or even rebooting the operating system does not automatically turn an established relay into a completely new one.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The important element is the relay&#8217;s persistent cryptographic identity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Conceptually:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Restart Tor\n+ preserve relay identity keys\n= same relay\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">By contrast:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Delete relay identity\n+ generate new keys\n= new relay\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The new identity does not inherit the historical reputation of the previous relay.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For long-running Tor infrastructure, preserving the relay identity is therefore important.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Why the Lifecycle Helps Defend Tor<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The gradual relay lifecycle is not merely a performance-management mechanism.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It also raises the cost of attacking the network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Consider an attacker attempting to perform a Sybil attack by creating hundreds of malicious relays.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Without a maturation process:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>100 malicious servers\n        \u2193\nImmediately receive large traffic volumes\n        \u2193\nImmediately become sensitive circuit positions\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">With a maturation process:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>100 malicious servers\n        \u2193\nMust remain online\n        \u2193\nMust remain reachable\n        \u2193\nMust accumulate measurements\n        \u2193\nMust demonstrate stability\n        \u2193\nMust wait for eligibility\n        \u2193\nMust gradually be selected by clients\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The attacker now needs more:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>time,<\/li>\n\n\n\n<li>bandwidth,<\/li>\n\n\n\n<li>infrastructure,<\/li>\n\n\n\n<li>money,<\/li>\n\n\n\n<li>operational discipline,<\/li>\n\n\n\n<li>and persistent identities.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">This does not make malicious relays impossible.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But it significantly increases the cost of operating them at scale.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">A Distributed Trust Problem<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The lifecycle of a Tor relay also reveals something important about Tor&#8217;s architecture.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tor does not have a single central server deciding which relay should carry every user&#8217;s traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead, several systems interact.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A simplified model looks like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Tor Relay\n    \u2502\n    \u2502 publishes information\n    \u25bc\nDirectory Authorities\n    \u25b2\n    \u2502\nBandwidth Measurement\n    \u2502\n    \u25bc\nAuthority Votes\n    \u2502\n    \u25bc\nNetwork Consensus\n    \u2502\n    \u25bc\nTor Clients\n    \u2502\n    \u25bc\nIndependent Circuit Selection\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The directory authorities create a common view of the network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Clients then use that information to independently construct circuits.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">This allows Tor to coordinate thousands of independently operated relays while avoiding a single central traffic dispatcher.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Why New Relay Traffic May Look Disappointing<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">For a new operator, one of the most confusing experiences is seeing a relay with substantial available bandwidth receive very little traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Suppose a relay is running on a connection capable of:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>500 Mbit\/s\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">but Tor initially sends only:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>1\u20135 Mbit\/s\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">That does not necessarily indicate:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>broken port forwarding,<\/li>\n\n\n\n<li>incorrect bandwidth configuration,<\/li>\n\n\n\n<li>poor routing,<\/li>\n\n\n\n<li>insufficient CPU,<\/li>\n\n\n\n<li>or a malfunctioning Tor daemon.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">The relay may simply be young.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Instead of looking only at raw traffic volume, a new operator should pay attention to whether the relay:<\/p>\n\n\n\n<ul class=\"wp-block-list\">\n<li>is reachable,<\/li>\n\n\n\n<li>appears in Tor&#8217;s directory information,<\/li>\n\n\n\n<li>receives expected relay flags,<\/li>\n\n\n\n<li>obtains bandwidth measurements,<\/li>\n\n\n\n<li>remains continuously online,<\/li>\n\n\n\n<li>and preserves its identity.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Traffic often increases naturally as those conditions accumulate.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">The Original Timeline Should Be Read Historically<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The Tor Project&#8217;s original article described approximately four periods:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Days 0\u20133\nUnmeasured\n\nDays 3\u20138\nBandwidth measurement and increasing Middle traffic\n\nDays 8\u201368\nGuard adoption and increasing Guard traffic\n\nDay 68+\nSteady-state operation\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">These values reflected the Tor network and Guard algorithms of that period.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Tor has continued evolving since the article was published.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Modern Guard selection is considerably more sophisticated, and the exact timing should not be interpreted as a current guarantee.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The more useful interpretation is conceptual:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Discovery\n    \u2193\nMeasurement\n    \u2193\nMiddle maturation\n    \u2193\nGuard qualification\n    \u2193\nGuard adoption\n    \u2193\nLong-term operation\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">The architecture and security reasoning remain highly relevant even though individual thresholds and timing rules have changed.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">The Most Important Resource Is Time<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">The lifecycle of a Tor relay illustrates an unusual property of decentralized anonymity infrastructure.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A relay becomes valuable not merely because it has powerful hardware.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Its usefulness is built over time.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A reliable relay gradually develops something similar to a network history:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Identity\n+ uptime\n+ measurements\n+ stability\n+ availability\n+ long-term participation\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This history allows Tor to use the relay more confidently.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The network therefore rewards consistency.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A modest server that remains online reliably for years can make a meaningful contribution.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A very powerful server that appears only occasionally may contribute much less.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">In Tor, bandwidth matters.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">But <strong>bandwidth plus time<\/strong> matters much more.<\/p>\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\" \/>\n\n\n\n<h2 class=\"wp-block-heading\">Conclusion<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">A new Tor relay does not enter the network at full capacity.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It begins as an unfamiliar participant.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The network observes it, verifies its reachability, measures its bandwidth, watches its stability, and gradually allows it to carry more important traffic.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For many non-exit relays, the path looks roughly like this:<\/p>\n\n\n\n<pre class=\"wp-block-code\"><code>Unknown\n  \u2193\nReachable\n  \u2193\nMeasured\n  \u2193\nMiddle\n  \u2193\nStable\n  \u2193\nGuard-eligible\n  \u2193\nGradually adopted\n  \u2193\nMature relay\n<\/code><\/pre>\n\n\n\n<p class=\"wp-block-paragraph\">This slow progression is not an inefficiency.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">It is part of Tor&#8217;s defense model.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">The same mechanisms that explain why a new relay initially receives little traffic also make it harder for an attacker to deploy large numbers of malicious relays and immediately gain influential positions in the network.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">For relay operators, the practical lesson is simple:<\/p>\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Do not judge a new relay by its first few days of traffic.<\/strong><\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Keep it reachable, keep it updated, preserve its identity, provide stable bandwidth, and allow the Tor network time to learn that the relay is dependable.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\">Original Tor Project article<\/h3>\n\n\n\n<figure class=\"wp-block-embed\"><div class=\"wp-block-embed__wrapper\">\nhttps:\/\/blog.torproject.org\/lifecycle-of-a-new-relay\n<\/div><\/figure>\n","protected":false},"excerpt":{"rendered":"<p>Running a Tor relay is not as simple as installing Tor, opening a port, and immediately receiving large amounts of network traffic. A newly launched relay enters the Tor network gradually. During its early life, it must first become known to the network, prove that it is reachable, accumulate bandwidth &hellip;<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[120],"tags":[245],"class_list":["post-6184","post","type-post","status-publish","format-standard","hentry","category-1s3b6h7r2zay02x","tag-tor"],"_links":{"self":[{"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/posts\/6184","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/comments?post=6184"}],"version-history":[{"count":1,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/posts\/6184\/revisions"}],"predecessor-version":[{"id":6185,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/posts\/6184\/revisions\/6185"}],"wp:attachment":[{"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/media?parent=6184"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/categories?post=6184"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.eternalsphere.net\/index.php\/wp-json\/wp\/v2\/tags?post=6184"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}