@@ -6,27 +6,22 @@ category = "arvo"
8Continuity on the [Ames](../ames) network occasionally needs to be broken at
8Continuity on the [Ames](../ames) network occasionally needs to be broken at
9−this early stage in order to correct a networking error or make major changes to
9+this early stage in order to correct a networking error or to make major changes
10−Arvo. These infrequent events are known as
10+to Arvo. These infrequent events are known as **breaches** which either cause an
11−**breaches** which either cause an individual ship to forget its network message
11+individual ship to forget its network message history, called a **personal
12−history, called a **personal breach**, or cause the entire network to forget its
12+breach**, or cause the entire network to forget its history, called a **network
13−history, called a **network breach**.
13+breach**.
15Personal breaches are always initiated by the user, frequently in response to a
15Personal breaches are always initiated by the user, frequently in response to a
16connectivity error. The easiest way to do this is with [Bridge](../bridge).
16connectivity error. The easiest way to do this is with [Bridge](../bridge).
17−There are two types of personal breaches: changing private keys, and changing
17+There are two types of personal breaches: changing networking keys, and changing
18−the Urbit ID ownership address. Each one increments the _life_ number of the ship by one, which is
18+the Urbit ID ownership address.
19−an integer that represents how many personal breaches have been performed on
20−that ship. Transferring the ID to a new address will also increase the _rift_
21−number of the ship in addition to the life number.
23−You can check your life and rift number by typing `+keys our`
24−into dojo and pressing Enter.
26Network breaches happen when a major Arvo revision that cannot be implemented
20Network breaches happen when a major Arvo revision that cannot be implemented
27−via an [OTA update](../ota-updates) occurs. When this happens, a new binary
21+via an [OTA update](../ota-updates) occurs. When this happens, a new binary will
28−will need to be downloaded, and your ship's [pier](../pier) needs to be moved to the
22+need to be downloaded, and your ship's [pier](../pier) needs to be moved to the
29−directory containing the new binary.
23+directory containing the new binary. The most recent network breach occurred in
24+December 2020, and we expect it to be the final one.
31### Further Reading
26### Further Reading