git.iko.soy/urbit.org
on master help sign in
information about life and rift number (#807)

* 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

commitd36b101709e15e66c2eec010c79d9c9e898280c5 authorpoprox <51337059+syzygyzer@users.noreply.github.com> dateTue 18 Feb 2020, 18:11 (7 years ago) parent0ee6f11
3 files changed+54−3
compare with master
unifiedsplit
glossary/ames.md+4−1 glossary/breach.md+32 tutorials/guide-to-breaches.md+18−2
glossary/ames.md+4−1
@@ -8,7 +8,10 @@ category = "arvo"
88**Ames** is the name of the Urbit network and the [vane](../vane) that communicates over it. It's an encrypted peer-to-peer network composed of instances of the [Arvo](../arvo) operating system. Each [galaxy](../galaxy), [star](../star), [planet](../planet), [moon](../moon), and [comet](../comet) communicates over the network utilizing the Ames protocol.
99
1010Your ship upgrades itself with [OTA updates](../ota-updates) via communication over Ames. The web interface, [Landscape](../landscape), of ships can be accessed by typing `sampel-palnet.arvo.network` into a browser, where `sampel-palnet` is the name of your ship.
11−
11+
12+Network continuity occasionally needs to be broken, either at an individual
13+level to fix networking issues or at a network-wide level to update Arvo beyond
14+what OTA updates are capable of doing. These events are called [breaches](../breach).
1215### Further Reading
1316
1417- [The Ames tutorial](@/docs/tutorials/arvo/ames.md): An in-depth technical guide to the Ames protocol.
glossary/breach.mdnew file+32
@@ -0,0 +1,32 @@
1++++
2+title = "Breach"
3+template = "doc.html"
4+category = "arvo"
5++++
6+
7+Continuity on the [Ames](../ames) network occasionally needs to be broken at
8+this early stage in order to correct a networking error or make major changes to
9+Arvo. These infrequent events are known as
10+**breaches** which either cause an individual ship to forget its network message
11+history, called a **personal breach**, or cause the entire network to forget its
12+history, called a **network breach**.
13+
14+Personal 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
16+an integer that represents how many personal breaches have been performed on
17+that ship.
18+
19+Network breaches happen when a major Arvo revision that cannot be implemented
20+via 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+
28+### Further Reading
29+
30+- [Guide to breaches](@/docs/tutorials/guide-to-breaches.md): A more in-depth
31+ explanation of breaches, including how to perform a personal breach.
32+- [Ship Troubleshooting](@/docs/tutorials/ship-troubleshooting.md): General instructions on getting your ship to work, which includes network connectivity issues.
tutorials/guide-to-breaches.md+18−2
@@ -4,13 +4,13 @@ weight = 10
44template = "doc.html"
55+++
66
7−An important concept on the Arvo network is that of continuity. Continuity refers to how ships remember the order of their own network messages and the network messages of others -- these messages are numbered, starting from zero. A _breach_ is when ships on the network agree to forget about this sequence and treat one or more ships like they are brand new.
7+An important concept on the [Ames](@/docs/tutorials/arvo/ames.md) network is that of continuity. Continuity refers to how ships remember the order of their own network messages and the network messages of others -- these messages are numbered, starting from zero. A _breach_ is when ships on the network agree to forget about this sequence and treat one or more ships like they are brand new.
88
99There are two kinds of breaches: **personal breaches** and **network breaches**.
1010
1111## Personal Breaches
1212
13−Ships on the Arvo network sometimes need to reset their continuity. A personal breach is when an individual ship announces to the network: "I forgot who I am, let's start over from scratch." That is, it clears its own event log and sends an announcement to the network, asking all ships that have communicated with it to reset its networking information in their state. This makes it as though the ship was just started for the first time again, since everyone has network has forgotten about it.
13+Ships on the Ames network sometimes need to reset their continuity. A personal breach is when an individual ship announces to the network: "I forgot who I am, let's start over from scratch." That is, it clears its own event log and sends an announcement to the network, asking all ships that have communicated with it to reset its networking information in their state. This makes it as though the ship was just started for the first time again, since everyone has network has forgotten about it.
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
@@ -24,6 +24,16 @@ 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+Performing a personal breach on your ship increments an integer value called
28+your ship's _life_ by one, which refers to your ship's [Azimuth](@/docs/tutorials/concepts/azimuth.md) _key
29+revision number_. This value is utilized by
30+Ames and Jael to ensure that you are
31+communicating with a ship created using its most recent set of keys. Your
32+ship'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.
35+
36+
2737## Network Breaches
2838
2939A network breach is an event where all ships on the network are required to update to a new continuity era. Network breaches happen when an Arvo update is released that is too large to release over the air. The current continuity era is given by a value in Ames, our networking vane, that is incremented when a network breaches; only ships with the same such value are able to communicate with one another.
@@ -35,3 +45,9 @@ If a network breach is happening, follow the steps below.
3545- Download the new Urbit binary by following the instructions in the [Install page](https://urbit.org/using/install/).
3646- 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.)
3747- Rejoin your favorite chat channels and subscriptions.
48+
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.