@@ -24,14 +24,18 @@ Troubleshooting](../ship-troubleshooting) guide. Also reach out for help in the
24Help channel in the Urbit Community group `~bitbet-bolbel/urbit-community`, or,
24Help channel in the Urbit Community group `~bitbet-bolbel/urbit-community`, or,
25failing that, in the `#ship-starting-support` channel in our [Discord
25failing that, in the `#ship-starting-support` channel in our [Discord
26server](https://discord.gg/n9xhMdz) to see if there is another option.
26server](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`.
28−There are two types of breaches - one where your Ethereum ownership address
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
29−remains the same, and one where you are switching to a new Ethereum ownership
32+same, and the other is for when you are transferring the ship to a new Ethereum
30−address. We make the emphasis about the Ethereum _ownership_ address as changing
33+ownership address. We make the emphasis about the Ethereum _ownership_ address
31−your [proxies](@/docs/glossary/proxies.md) does not require a breach.
34+as changing your [proxies](@/docs/glossary/proxies.md) does not require a
33−If you will be keeping the same Ethereum ownership address and would like to perform a
37+If you will be keeping your ship at the same Ethereum ownership address and
34−breach, follow the steps below.
38+would like to perform a breach, follow the steps below.
36- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
40- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
37- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
41- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
@@ -43,7 +47,7 @@ breach, follow the steps below.
43- Delete your keyfile after successfully booting.
47- Delete your keyfile after successfully booting.
44- Rejoin your favorite chat channels and subscriptions.
48- Rejoin your favorite chat channels and subscriptions.
46−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
47choice as to whether or not you want to breach. This is to cover the case when
51choice as to whether or not you want to breach. This is to cover the case when
48you are transferring to another address you own. The process here is slightly different.
52you are transferring to another address you own. The process here is slightly different.
@@ -74,7 +78,7 @@ was released that could not be implemented via an [OTA
74update](@/docs/glossary/ota-updates.md). The continuity era is given by an
78update](@/docs/glossary/ota-updates.md). The continuity era is given by an
75integer in Ames that is incremented when the network breaches. Only ships with
79integer in Ames that is incremented when the network breaches. Only ships with
76the same such value are able to communicate with one another. The most recent
80the same such value are able to communicate with one another. The most recent
77−network breach occurred in December 2020, and we expect it to be the final one.
81+network breach occurred in December 2020, and we expect it to have been the final one.
79If another network breach does occur, we will provide accompanying documentation
83If another network breach does occur, we will provide accompanying documentation
80on what to do to transfer your ship and all of its data to the new era.
84on what to do to transfer your ship and all of its data to the new era.