@@ -6,27 +6,36 @@ template = "doc.html"
66
77An important concept on the [Ames](@/docs/arvo/ames/ames.md) network is that of continuity. Continuity refers to how ships remember the order of their own network messages and the network messages of others -- these messages are numbered, starting from zero. A _breach_ is when ships on the network agree to forget about this sequence and treat one or more ships like they are brand new.
88
9−There are two kinds of breaches: **personal breaches** and **network breaches**.
10−
11−## Personal Breaches
12−
13−Ships on the Ames network sometimes need to reset their continuity. A personal breach is when an individual ship announces to the network: "I forgot who I am, let's start over from scratch." That is, it clears its own event log and sends an announcement to the network, asking all ships that have communicated with it to reset its networking information in their state. This makes it as though the ship was just started for the first time again, since everyone on the network has forgotten about it.
14−
15−Personal breaches often fix connectivity issues, but should only be used as a
16−last resort. Before performing a personal breach, look at alternative fixes in
17−the [Ship Troubleshooting](../ship-troubleshooting) guide. Also reach out for
18−help in the Help channel in the Urbit Community group
19−`~bitbet-bolbel/urbit-community`, or, failing that, in the
20−`#ship-starting-support` channel in our [Discord
9+There are two kinds of breaches: (personal) **breaches** and **network breaches**.
10+
11+## Breaches
12+
13+Ships on the Ames network sometimes need to reset their continuity. A breach is
14+when an individual ship announces to the network: "I forgot who I am, let's
15+start over from scratch." That is, it clears its own event log and sends an
16+announcement to the network, asking all ships that have communicated with it to
17+reset its networking information in their state. This makes it as though the
18+ship was just started for the first time again, since everyone on the network
19+has forgotten about it.
20+
21+Breaches often fix connectivity issues, but should only be used as a last
22+resort. Before performing a breach, look at alternative fixes in the [Ship
23+Troubleshooting](../ship-troubleshooting) guide. Also reach out for help in the
24+Help channel in the Urbit Community group `~bitbet-bolbel/urbit-community`, or,
25+failing that, in the `#ship-starting-support` channel in our [Discord
2126server](https://discord.gg/n9xhMdz) to see if there is another option.
27+Connectivity issues are typically related to a bug, and you may be able to help
28+us fix it by emailing us at `support@urbit.org`.
2229
23−There are two types of personal breaches - one where your Ethereum ownership address
24−remains the same, and one where you are switching to a new Ethereum ownership
25−address. We make the emphasis about the Ethereum _ownership_ address as
26−changing your [proxies](@/docs/glossary/proxies.md) does not require a breach.
30+There are two separate sequences of actions you need to take in order to breach.
31+One flow is for when you wish to keep Ethereum ownership address of the ship the
32+same, and the other is for when you are transferring the ship to a new Ethereum
33+ownership address. We make the emphasis about the Ethereum _ownership_ address
34+as changing your [proxies](@/docs/glossary/proxies.md) does not require a
35+breach.
2736
28−If you will be keeping the same Ethereum ownership address and would like to perform a
29−personal breach, follow the steps below.
37+If you will be keeping your ship at the same Ethereum ownership address and
38+would like to perform a breach, follow the steps below.
3039
3140- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
3241- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
@@ -38,7 +47,7 @@ personal breach, follow the steps below.
3847- Delete your keyfile after successfully booting.
3948- Rejoin your favorite chat channels and subscriptions.
4049
41−If you are switching to a new Ethereum ownership address you will have the
50+If you are transferring a ship to a new Ethereum ownership address you will have the
4251choice as to whether or not you want to breach. This is to cover the case when
4352you are transferring to another address you own. The process here is slightly different.
4453
@@ -61,30 +70,15 @@ you are transferring to another address you own. The process here is slightly di
6170- Delete your keyfile after successfully booting.
6271- Rejoin your favorite chat channels and subscriptions.
6372
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−
8073## Network Breaches
8174
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.
75+Network breaches were events where all ships on the network were required to
76+update to a new continuity era. Network breaches happened when an Arvo update
77+was released that could not be implemented via an [OTA
78+update](@/docs/glossary/ota-updates.md). The continuity era is given by an
79+integer in Ames that is incremented when the network breaches. Only ships with
80+the same such value are able to communicate with one another. The most recent
81+network breach occurred in December 2020, and we expect it to have been the final one.
8382
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.
83+If another network breach does occur, we will provide accompanying documentation
84+on what to do to transfer your ship and all of its data to the new era.