git.iko.soy/urbit.org
on master help sign in
Fixed life and rift number definition (#812)

* info about life and rift number, arvo -> ames * dojo command to check life and rift * initial breach entry * further reading and typo * rift definition * breach link in ames * add category = arvo * revised life and rift description * revised life and rift number defintion * +keys our * +keys our and +keys ~ship for tutorial

commita1aedef591fd1a3544edd4c02dc555a170f9b39a authorpoprox <51337059+syzygyzer@users.noreply.github.com> dateWed 26 Feb 2020, 17:08 (7 years ago) parent2107406
2 files changed+20−15
compare with master
unifiedsplit
glossary/breach.md+10−8 tutorials/guide-to-breaches.md+10−7
glossary/breach.md+10−8
@@ -12,18 +12,20 @@ history, called a **personal breach**, or cause the entire network to forget its
1212history, called a **network breach**.
1313
1414Personal breaches are always initiated by the user, frequently in response to a
15−connectivity error. Each one increments the _life_ number of the ship by one, which is
15+connectivity error. The easiest way to do this is with [Bridge](../bridge).
16+There are two types of personal breaches: changing private keys, and changing
17+the Urbit ID ownership address. Each one increments the _life_ number of the ship by one, which is
1618an integer that represents how many personal breaches have been performed on
17−that ship.
19+that ship. Transferring the ID to a new address will also increase the _rift_
20+number of the ship in addition to the life number.
21+
22+You can check your life and rift number by typing `+keys our`
23+into dojo and pressing Enter.
1824
1925Network breaches happen when a major Arvo revision that cannot be implemented
2026via an [OTA update](../ota-updates) occurs. When this happens, a new binary
21−will need to be downloaded. Each network breach increments the _rift_ number of
22−the network by one, which is an integer that represents how many network
23−breaches have been performed.
24−
25−You can check your life number and the current rift number by typing `+keys`
26−into dojo and pressing Enter.
27+will need to be downloaded, and your ship's pier needs to be moved to the
28+directory containing the new binary.
2729
2830### Further Reading
2931
tutorials/guide-to-breaches.md+10−7
@@ -24,14 +24,22 @@ To perform a personal breach, follow the steps below.
2424- Create a new pier by booting your ship with your new keyfile.
2525- Rejoin your favorite chat channels and subscriptions.
2626
27+There are two types of personal breaches: changing private keys, and changing
28+the Ethereum address that holds the Urbit ID.
29+
2730Performing a personal breach on your ship increments an integer value called
2831your ship's _life_ by one, which refers to your ship's [Azimuth](@/docs/tutorials/concepts/azimuth.md) _key
2932revision number_. This value is utilized by
3033Ames and Jael to ensure that you are
3134communicating with a ship created using its most recent set of keys. Your
3235ship's life is written at the end of the name of its keyfile, e.g.
33−`sampel-palnet4.key`. You can also check your current life number by running the
34−`+keys` generator in dojo.
36+`sampel-palnet4.key`. Changing the Etherum address that holds the Urbit ID,
37+called _reticketing_, also increments a number called the ship's _rift_ by one.
38+Rift refers to your ship's Azimuth _continuity number_.
39+
40+You can check your current life and rift number by running the
41+`+keys our` generator in dojo. You can inspect another ship's life and rift can be checked by
42+running `+keys ~sampel-palnet`.
3543
3644
3745## Network Breaches
@@ -46,8 +54,3 @@ If a network breach is happening, follow the steps below.
4654- Create a new pier by booting your ship with your key, according to the instructions on the install page. (Note: You do _not_ need to use a new key to boot into a new continuity era.)
4755- Rejoin your favorite chat channels and subscriptions.
4856
49−Each network breach increments an integer value called the _rift_ of the network
50−by one, which is recorded by each ship and refers to the current Azimuth
51−_continuity number_. Only ships with the same rift number can
52−communicate over Ames. You can check the current rift number by running the
53−`+keys` generator in dojo.