on master help sign in
changing ethereum address as a breach
commit24c6c20d36ba12101356f77c0c573c971615e61b authorJONATHAN PAPROCKI <jon@tlon.io> dateWed 16 Sep 2020, 13:44 (6 years ago) parente74339e
1 file changed+32−7
tutorials/guide-to-breaches.md+32−7
tutorials/guide-to-breaches.md+32−7
@@ -14,18 +14,42 @@ Ships on the Ames network sometimes need to reset their continuity. A personal b
1414
1515Personal 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.
1616
17−To perform a personal breach, follow the steps below.
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.
21+
22+If you will be keeping the same Ethereum ownership address and would like to perform a
23+personal breach, follow the steps below.
1824
1925- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
2026- Click on `OS: Urbit OS Settings` at the bottom, then click `Reset Networking Keys`.
2127- 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`.
23−- Delete or archive your old pier.
24−- Create a new pier by booting your ship with your new keyfile.
28+- Download your new keyfile following these instructions: [Generate your
29+ keyfile](@/using/operations/using-bridge.md#generate-your-keyfile).
30+- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
31+- Delete your keyfile after successfully booting.
2532- Rejoin your favorite chat channels and subscriptions.
2633
27−There are two types of personal breaches: changing private keys, and changing
28−the Ethereum address that holds the Urbit ID.
34+If you are switching to a new Ethereum ownerhsip address, you will necessarily be
35+performing a personal breach as well - there is no way to change the ownership
36+address without also breaching. The process here is slightly different.
37+
38+- Go to [bridge.urbit.org](https://bridge.urbit.org) and log into your identity.
39+- Click on `ID: Identity and security settings` at the bottom, then click
40+ `Transfer this point`.
41+- Enter the new Ethereum address you would like to transfer ownership to.
42+ Click `Generate & Sign Transaction`, then click `Send Transaction` and wait
43+ for the progress bar to complete.
44+- Logout of your current session in Bridge by clicking `Logout` at the top, and
45+ then login to your new ownership address.
46+- From here, following the directions on how to [Accept your
47+ transfer](@/using/operations/using-bridge.md#accept-your-transfer), [Set your
48+ networking keys](@/using/operations/using-bridge.md#set-your-networking-keys),
49+ and [Generate your keyfile](@/using/operations/using-bridge.md#generate-your-keyfile).
50+- Proceed to [boot your ship](@/using/install.md#boot-your-planet) with the new keyfile.
51+- Delete your keyfile after successfully booting.
52+- Rejoin your favorite chat channels and subscriptions.
2953
3054Performing a personal breach on your ship increments an integer value called
3155your ship's _life_ by one, which refers to your ship's [Azimuth](@/docs/tutorials/concepts/azimuth.md) _key
@@ -34,7 +58,8 @@ Ames and Jael to ensure that you are
3458communicating with a ship created using its most recent set of keys. Your
3559ship's life is written at the end of the name of its keyfile, e.g.
3660`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.
61+called _reticketing_, increments a number called the ship's _rift_ by one in
62+addition to incrementing your ship's life.
3863Rift refers to your ship's Azimuth _continuity number_.
3964
4065You can check your current life and rift number by running the