@@ -6,27 +6,32 @@ template = "doc.html"
7An 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.
7An 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.
9−There are two kinds of breaches: **personal breaches** and **network breaches**.
9+There are two kinds of breaches: (personal) **breaches** and **network breaches**.
11−## Personal Breaches
11+## Breaches
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.
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.
15−Personal breaches often fix connectivity issues, but should only be used as a
21+Breaches often fix connectivity issues, but should only be used as a last
16−last resort. Before performing a personal breach, look at alternative fixes in
22+resort. Before performing a breach, look at alternative fixes in the [Ship
17−the [Ship Troubleshooting](../ship-troubleshooting) guide. Also reach out for
23+Troubleshooting](../ship-troubleshooting) guide. Also reach out for help in the
18−help in the Help channel in the Urbit Community group
24+Help channel in the Urbit Community group `~bitbet-bolbel/urbit-community`, or,
19−`~bitbet-bolbel/urbit-community`, or, failing that, in the
20−`#ship-starting-support` channel in our [Discord
25+failing that, in the `#ship-starting-support` channel in our [Discord
21server](https://discord.gg/n9xhMdz) to see if there is another option.
26server](https://discord.gg/n9xhMdz) to see if there is another option.
23−There are two types of personal breaches - one where your Ethereum ownership address
28+There are two types of breaches - one where your Ethereum ownership address
24remains the same, and one where you are switching to a new Ethereum ownership
29remains 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
30+address. We make the emphasis about the Ethereum _ownership_ address as changing
26−changing your [proxies](@/docs/glossary/proxies.md) does not require a breach.
31+your [proxies](@/docs/glossary/proxies.md) does not require a breach.
28If you will be keeping the same Ethereum ownership address and would like to perform a
33If you will be keeping the same Ethereum ownership address and would like to perform a
29−personal breach, follow the steps below.
34+breach, follow the steps below.
31- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
36- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
32- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
37- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
@@ -63,13 +68,13 @@ you are transferring to another address you own. The process here is slightly di
64## Network Breaches
69## Network Breaches
66−A network breach is an event where all ships on the network are required to
71+Network breaches were events where all ships on the network were required to
67−update to a new continuity era. Network breaches happen when an Arvo update is
72+update to a new continuity era. Network breaches happened when an Arvo update
68−released that is too large to release over the air. The current continuity era
73+was released that could not be implemented via an [OTA
74+update](@/docs/glossary/ota-updates.md). The continuity era is given by an
69−is given by an integer in Ames, our networking vane, that is incremented when a
75+integer in Ames that is incremented when the network breaches. Only ships with
70−network breaches; only ships with the same such value are able to communicate
76+the same such value are able to communicate with one another. The most recent
71−with one another. The most recent network breach occurred in December 2020, and
77+network breach occurred in December 2020, and we expect it to be the final one.
72−we expect it to be the final one.
74If another network breach does occur, we will provide accompanying documentation
79If another network breach does occur, we will provide accompanying documentation
75on what to do to transfer your ship and all of its data to the new era.
80on what to do to transfer your ship and all of its data to the new era.