@@ -61,30 +61,15 @@ you are transferring to another address you own. The process here is slightly di
6161- Delete your keyfile after successfully booting.
6262- Rejoin your favorite chat channels and subscriptions.
6363
64−Performing a personal breach on your ship increments an integer value called
65−your ship's _life_ by one, which refers to your ship's [Azimuth](@/docs/azimuth/azimuth.md) _key
66−revision number_. This value is utilized by
67−Ames and Jael to ensure that you are
68−communicating with a ship created using its most recent set of keys. Your
69−ship's life is written at the end of the name of its keyfile, e.g.
70−`sampel-palnet-4.key`. Changing the Etherum address that holds the Urbit ID,
71−called _reticketing_, increments a number called the ship's _rift_ by one in
72−addition to incrementing your ship's life.
73−Rift refers to your ship's Azimuth _continuity number_.
74−
75−You can check your current life and rift number by running the
76−`+keys our` generator in Dojo. You can inspect another ship's life and rift can be checked by
77−running `+keys ~sampel-palnet`.
78−
79−
8064## Network Breaches
8165
82−A network breach is an event where all ships on the network are required to update to a new continuity era. Network breaches happen when an Arvo update is released that is too large to release over the air. The current continuity era is given by a value in Ames, our networking vane, that is incremented when a network breaches; only ships with the same such value are able to communicate with one another.
66+A network breach is an event where all ships on the network are required to
67+update to a new continuity era. Network breaches happen when an Arvo update is
68+released that is too large to release over the air. The current continuity era
69+is given by an integer in Ames, our networking vane, that is incremented when a
70+network breaches; only ships with the same such value are able to communicate
71+with one another. The most recent network breach occurred in December 2020, and
72+we expect it to be the final one.
8373
84−If a network breach is happening, follow the steps below.
85−
86−- Delete your old Urbit binary.
87−- Delete or archive your old pier.
88−- Download the new Urbit binary by following the instructions in the [Install page](@/getting-started/_index.md).
89−- Create a new pier by booting your ship with your key, according to the instructions on the install page. (Note: You do _not_ need to use a new key to boot into a new continuity era.)
90−- Rejoin your favorite chat channels and subscriptions.
74+If another network breach does occur, we will provide accompanying documentation
75+on what to do to transfer your ship and all of its data to the new era.