@@ -1,16 +1,19 @@
11+++
2−title = "Guide to Breaches"
2+title = "Guide to Factory Resets"
33weight = 40
44template = "doc.html"
55+++
66
7−An important concept on the [Ames](/docs/arvo/ames/ames) 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.
7+An important concept on the [Ames](/docs/arvo/ames/ames) network is that of
8+continuity. Continuity refers to how ships remember the order of their own
9+network messages and the network messages of others -- these messages are
10+numbered, starting from zero. A _factory reset_ is when ships on the network agree to
11+forget about this sequence and treat one or more ships like they are brand new.
812
9−There are two kinds of breaches: (personal) **breaches** and **network breaches**.
13+## Factory Resets
1014
11−## Breaches
12−
13−Ships on the Ames network sometimes need to reset their continuity. A breach is
15+Ships on the Ames network sometimes need to reset their continuity. A factory
16+reset (hereafter just called a _reset_) is
1417when an individual ship announces to the network: "I forgot who I am, let's
1518start over from scratch." That is, it clears its own event log and sends an
1619announcement to the network, asking all ships that have communicated with it to
@@ -18,36 +21,40 @@ reset its networking information in their state. This makes it as though the
1821ship was just started for the first time again, since everyone on the network
1922has forgotten about it.
2023
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](/using/os/ship-troubleshooting) guide. Also reach out for help in the
24−Help channel in the Urbit Community group `~bitbet-bolbel/urbit-community` to see if there is another option.
25−Connectivity issues are typically related to a bug, and you may be able to help
26−us fix it by emailing us at `support@urbit.org`.
24+Resets often fix connectivity issues, but should only be used as a last
25+resort. Before performing a reset, look at alternative fixes in the [Ship
26+Troubleshooting](/using/os/ship-troubleshooting) guide. Also reach out for help
27+in the Help channel in the Urbit Community group
28+`~bitbet-bolbel/urbit-community` to see if there is another option. Connectivity
29+issues are typically related to a bug, and you may be able to help us fix it by
30+emailing us at `support@urbit.org`.
2731
28−There are two separate sequences of actions you need to take in order to breach.
32+There are two separate sequences of actions you need to take in order to reset.
2933One flow is for when you wish to keep Ethereum ownership address of the ship the
3034same, and the other is for when you are transferring the ship to a new Ethereum
3135ownership address. We make the emphasis about the Ethereum _ownership_ address
32−as changing your [proxies](/docs/glossary/proxies) does not require a
33−breach.
36+as changing your [proxies](/docs/glossary/proxies) does not require a reset.
3437
3538If you will be keeping your ship at the same Ethereum ownership address and
36−would like to perform a breach, follow the steps below.
39+would like to perform a reset, follow the steps below.
3740
3841- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
39−- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
40−- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then click `Send Transaction` and wait for the progress bar to appear.
42+- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking
43+ Keys`.
44+- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then
45+ click `Send Transaction` and wait for the progress bar to appear.
4146- Download your new keyfile following these instructions: [Generate your
4247 keyfile](/using/id/using-bridge#generate-your-keyfile).
4348- Delete or archive your old [pier](/docs/glossary/pier).
44−- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the new keyfile.
49+- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the
50+ new keyfile.
4551- Delete your keyfile after successfully booting.
4652- Rejoin your favorite chat channels and subscriptions.
4753
48−If you are transferring a ship to a new Ethereum ownership address you will have the
49−choice as to whether or not you want to breach. This is to cover the case when
50−you are transferring to another address you own. The process here is slightly different.
54+If you are transferring a ship to a new Ethereum ownership address you will have
55+the choice as to whether or not you want to reset. This is to cover the case
56+when you are transferring to another address you own. The process here is
57+slightly different.
5158
5259- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
5360- Click on `ID: Identity and security settings` at the bottom, then click
@@ -58,25 +65,30 @@ you are transferring to another address you own. The process here is slightly di
5865- Logout of your current session in Bridge by clicking `Logout` at the top, and
5966 then login to your new ownership address.
6067- From here, following the directions on how to [Accept your
61− transfer](/using/id/using-bridge#accept-your-transfer), [Set your
62− networking keys](/using/id/using-bridge#set-your-networking-keys),
63− and [Generate your
64− keyfile](/using/id/using-bridge#generate-your-keyfile). The option
65− whether or not to breach is in the Accept your Transfer step.
68+ transfer](/using/id/using-bridge#accept-your-transfer), [Set your networking
69+ keys](/using/id/using-bridge#set-your-networking-keys), and [Generate your
70+ keyfile](/using/id/using-bridge#generate-your-keyfile). The option whether or
71+ not to reset is in the Accept your Transfer step.
6672- Delete or archive your old [pier](/docs/glossary/pier).
67−- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the new keyfile.
73+- Proceed to [boot your ship](/getting-started/cli#boot-your-planet) with the
74+ new keyfile.
6875- Delete your keyfile after successfully booting.
6976- Rejoin your favorite chat channels and subscriptions.
7077
71−## Network Breaches
78+## Network Resets
7279
73−Network breaches were events where all ships on the network were required to
74−update to a new continuity era. Network breaches happened when an Arvo update
80+Network resets were events where all ships on the network were required to
81+update to a new continuity era. Network resets happened when an Arvo update
7582was released that could not be implemented via an [OTA
76−update](/docs/glossary/ota-updates). The continuity era is given by an
77−integer in Ames that is incremented when the network breaches. Only ships with
78−the same such value are able to communicate with one another. The most recent
79−network breach occurred in December 2020, and we expect it to have been the final one.
83+update](/docs/glossary/ota-updates). The continuity era is given by an integer
84+in Ames that is incremented when the network resets. Only ships with the same
85+such value are able to communicate with one another. The most recent network
86+reset occurred in December 2020, and we expect it to have been the final one.
8087
81−If another network breach does occur, we will provide accompanying documentation
88+If another network reset does occur, we will provide accompanying documentation
8289on what to do to transfer your ship and all of its data to the new era.
90+
91+## Breaches
92+
93+Factory resets used to be called _breaches_, and you may find this terminology
94+still used in some places. This is an identical concept - only the name differs.