git.iko.soy/urbit.org
on master help sign in
Fixed life and rift number definition (#812)
a1aedefpoprox
glossary/breach.md+10−8
compare with master
unifiedsplit
@@ -12,18 +12,20 @@ history, called a **personal breach**, or cause the entire network to forget its
12history, called a **network breach**.
12history, called a **network breach**.
13
13
14Personal breaches are always initiated by the user, frequently in response to a
14Personal breaches are always initiated by the user, frequently in response to a
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
15−connectivity error. Each one increments the _life_ number of the ship by one, which is
17+the Urbit ID ownership address. Each one increments the _life_ number of the ship by one, which is
16an integer that represents how many personal breaches have been performed on
18an 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.
18
24
19Network breaches happen when a major Arvo revision that cannot be implemented
25Network breaches happen when a major Arvo revision that cannot be implemented
20via an [OTA update](../ota-updates) occurs. When this happens, a new binary
26via 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
27+will need to be downloaded, and your ship's pier needs to be moved to the
22−the network by one, which is an integer that represents how many network
28+directory containing the new binary.
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
29
28### Further Reading
30### Further Reading
29
31
tutorials/guide-to-breaches.md+10−7
@@ -24,14 +24,22 @@ To perform a personal breach, follow the steps below.
24- Create a new pier by booting your ship with your new keyfile.
24- Create a new pier by booting your ship with your new keyfile.
25- Rejoin your favorite chat channels and subscriptions.
25- Rejoin your favorite chat channels and subscriptions.
26
26
27+There are two types of personal breaches: changing private keys, and changing
28+the Ethereum address that holds the Urbit ID.
29+
27Performing a personal breach on your ship increments an integer value called
30Performing a personal breach on your ship increments an integer value called
28your ship's _life_ by one, which refers to your ship's [Azimuth](@/docs/tutorials/concepts/azimuth.md) _key
31your ship's _life_ by one, which refers to your ship's [Azimuth](@/docs/tutorials/concepts/azimuth.md) _key
29revision number_. This value is utilized by
32revision number_. This value is utilized by
30Ames and Jael to ensure that you are
33Ames and Jael to ensure that you are
31communicating with a ship created using its most recent set of keys. Your
34communicating with a ship created using its most recent set of keys. Your
32ship's life is written at the end of the name of its keyfile, e.g.
35ship's life is written at the end of the name of its keyfile, e.g.
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+
33−`sampel-palnet4.key`. You can also check your current life number by running the
40+You can check your current life and rift number by running the
34−`+keys` generator in dojo.
41+`+keys our` generator in dojo. You can inspect another ship's life and rift can be checked by
42+running `+keys ~sampel-palnet`.
35
43
36
44
37## Network Breaches
45## Network Breaches
@@ -46,8 +54,3 @@ If a network breach is happening, follow the steps below.
46- 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.)
54- 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.)
47- Rejoin your favorite chat channels and subscriptions.
55- Rejoin your favorite chat channels and subscriptions.
48
56
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.