@@ -14,18 +14,47 @@ Ships on the Ames network sometimes need to reset their continuity. A personal b
15Personal breaches often fix connectivity issues, but should only be used as a last resort. Before performing a personal breach, look at alternative fixes in the [Ship Troubleshooting](../ship-troubleshooting) guide. Also reach out for help in `~/~dopzod/urbit-help`, or, failing that, in the `#ship-starting-support` channel in our [Discord server](https://discord.gg/n9xhMdz) to see if there is another option.
15Personal breaches often fix connectivity issues, but should only be used as a last resort. Before performing a personal breach, look at alternative fixes in the [Ship Troubleshooting](../ship-troubleshooting) guide. Also reach out for help in `~/~dopzod/urbit-help`, or, failing that, in the `#ship-starting-support` channel in our [Discord server](https://discord.gg/n9xhMdz) to see if there is another option.
17+There are two types of personal breaches - one where your Ethereum ownership address
18+remains the same, and one where you are switching to a new Ethereum ownership
19+address. We make the emphasis about the Ethereum _ownership_ address as
20+changing your [proxies](@/glossary/proxies.md) does not require a breach.
22+If you will be keeping the same Ethereum ownership address and would like to perform a
17−To perform a personal breach, follow the steps below.
23+personal breach, follow the steps below.
19- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
25- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
20- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
26- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
21- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then click `Send Transaction` and wait for the progress bar to appear.
27- Check the `Breach Continuity` box. Click `Reset Networking Keys`, and then click `Send Transaction` and wait for the progress bar to appear.
22−- Click `Download Arvo Keyfile`.
28+- Download your new keyfile following these instructions: [Generate your
29+ keyfile](@/using/operations/using-bridge.md#generate-your-keyfile).
23−- Delete or archive your old pier.
30+- Delete or archive your old [pier](@/glossary/pier).
24−- Create a new pier by booting your ship with your new keyfile.
31+- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
32+- Delete your keyfile after successfully booting.
25- Rejoin your favorite chat channels and subscriptions.
33- Rejoin your favorite chat channels and subscriptions.
27−There are two types of personal breaches: changing private keys, and changing
35+If you are switching to a new Ethereum ownerhsip address, you will necessarily be
28−the Ethereum address that holds the Urbit ID.
36+performing a personal breach as well - there is no way to change the ownership
37+address without also breaching. The process here is slightly different.
39+- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
40+- Click on `ID: Identity and security settings` at the bottom, then click
41+ `Transfer this point`.
42+- Enter the new Ethereum address you would like to transfer ownership to.
43+ Click `Generate & Sign Transaction`, then click `Send Transaction` and wait
44+ for the progress bar to complete.
45+- Logout of your current session in Bridge by clicking `Logout` at the top, and
46+ then login to your new ownership address.
47+- From here, following the directions on how to [Accept your
48+ transfer](@/using/operations/using-bridge.md#accept-your-transfer), [Set your
49+ networking keys](@/using/operations/using-bridge.md#set-your-networking-keys),
51+ keyfile](@/using/operations/using-bridge.md#generate-your-keyfile). The main
52+ difference with the above method is that you do not check the `Breach
54+- Delete or archive your old [pier](@/glossary/pier).
55+- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
56+- Delete your keyfile after successfully booting.
57+- Rejoin your favorite chat channels and subscriptions.
30Performing a personal breach on your ship increments an integer value called
59Performing a personal breach on your ship increments an integer value called
31your ship's _life_ by one, which refers to your ship's [Azimuth](@/docs/tutorials/concepts/azimuth.md) _key
60your ship's _life_ by one, which refers to your ship's [Azimuth](@/docs/tutorials/concepts/azimuth.md) _key
@@ -34,7 +63,8 @@ Ames and Jael to ensure that you are
34communicating with a ship created using its most recent set of keys. Your
63communicating with a ship created using its most recent set of keys. Your
35ship's life is written at the end of the name of its keyfile, e.g.
64ship's life is written at the end of the name of its keyfile, e.g.
36`sampel-palnet-4.key`. Changing the Etherum address that holds the Urbit ID,
65`sampel-palnet-4.key`. Changing the Etherum address that holds the Urbit ID,
37−called _reticketing_, also increments a number called the ship's _rift_ by one.
66+called _reticketing_, increments a number called the ship's _rift_ by one in
67+addition to incrementing your ship's life.
38Rift refers to your ship's Azimuth _continuity number_.
68Rift refers to your ship's Azimuth _continuity number_.
40You can check your current life and rift number by running the
70You can check your current life and rift number by running the