on master help sign in
Merge pull request #421 from urbit/rob-edits

Rob edits

commitf1817cdd7d06e085dfcc87e430acb21a8f63f6d5 authorDavid Kerschner <dkerschner@hcoop.net> dateWed 6 Mar 2019, 12:01 (8 years ago) parent90cc1d2c2b311e
3 files changed+59−5
getting-started/azimuth.udon+23−3 introduction/arvo-vs-azimuth.udon+3−2 introduction/galaxies-stars-and-planets.udon+33
getting-started/azimuth.udon+23−3
@@ -1,8 +1,28 @@
1−:- :~ title/'Azimuth'
1+:- :~ title/'Bridge'
22 sort/'3'
33 ==
44;>
55
6−# Using Azimuth
6+# Bridge
77
8−The primary way to interact with Azimuth, our identity platform, is through our application [Bridge](https://github.com/urbit/bridge) and the node libraries that it depends on, azimuth-js and keygen-js. Take a look at the source and play around or see [Getting Started](/docs/getting-started).
8+[Bridge](https://github.com/urbit/bridge) is the client we built for interacting with [Azimuth](/docs/pki) and managing points.
9+
10+To install Bridge, navigate to the [release page](https://github.com/urbit/bridge/releases/) on GitHub. Download the `.zip` file at of the latest version. After you download it, follow the instructions below.
11+
12+### Verify Checksums
13+
14+You may wish to validate your downloaded file's checksum to make sure that you weren't given a different file by a malicious third party. To do this, unzip the file you download. Navigate inside the resulting folder, and compare the lines in checksum.txt to SHA-256 hashes of the `build` directory's contents. You can get such a hash by running one of the following commands.
15+
16+- On MacOS: `shasum -a 256 -c checksums.txt build` in the terminal.
17+- On Linux: `sha256sum -c checksums.txt build`
18+- On Windows: Go into the `build` directory and verify files individually with `CertUtil -hashFile [file_name] SHA256`
19+
20+### Installation
21+
22+To use Bridge:
23+
24++ Unzip the `.zip` file that you downloaded (`bridge-$version.zip`).
25++ Open up your command line interface (Terminal on OSX, Command Prompt on Windows).
26++ Navigate to the `bridge-$version` directory, where `$version` is the appropriate version number.
27++ Run this command: `python3 -m http.server 5000 --bind 127.0.0.1 --directory build`
28++ You can then use the Bridge app by navigating to `http://localhost:5000` in your internet browser.
introduction/arvo-vs-azimuth.udon+3−2
@@ -1,4 +1,5 @@
11:- :~ title/'Arvo vs. Azimuth'
2+ sort/'4'
23 ==
34;>
45
@@ -6,9 +7,9 @@
67
78Urbit is a project, not a single computer system. It has three components: Arvo, the operating system; Azimuth, the identity system; and Aegean, the pattern for creating software experiences for individual Urbit communities. This document compares the first two.
89
9−*Arvo* is an operating system that provides the software for a personal server. These personal servers together constitute the peer-to-peer Arvo network. To make this network work on the social level, Arvo is built to work with a system of scarce and immutable identities.
10+[*Arvo*](https://github.com/urbit/arvo) is an operating system that provides the software for a personal server. These personal servers together constitute the peer-to-peer Arvo network. To make this network work on the social level, Arvo is built to work with a system of scarce and immutable identities.
1011
11−*Azimuth* is the public-key infrastructure built to be such a system. A suite of smart-contracts on the Ethereum blockchain, Azimuth determines which Ethereum addresses own which Azimuth identities, called _points_. All point-related operations, such as transfers, are governed at this layer. But Azimuth isn't built strictly for Arvo -- it could be used as a generalized identity system for other projects.
12+[*Azimuth*](https://github.com/urbit/azimuth) is the public-key infrastructure built to be such a system. A suite of smart-contracts on the Ethereum blockchain, Azimuth determines which Ethereum addresses own which Azimuth identities, called _points_. All point-related operations, such as transfers, are governed at this layer. But Azimuth isn't built strictly for Arvo -- it could be used as a generalized identity system for other projects.
1213
1314These otherwise-parallel systems meet when you want to connect to the Arvo network. Your Arvo personal server, called your _ship_, needs to be able to prove cryptographically that it is who it says it is. This proof comes in the form of a keyfile, derived from your point, that you use to start your ship.
1415
introduction/galaxies-stars-and-planets.udonnew file+33
@@ -0,0 +1,33 @@
1+:- :~ title/'Galaxies, Stars, and Planets'
2+ ==
3+;>
4+
5+# Galaxies, Stars, and Planets
6+
7+The current internet has no consistent system of identity. There are only quasi-identities such as IP addresses, Google accounts and email addresses, each able to be assumed and abandoned without much trouble. The result is a hostile social experience, since bad actors -- spammers, scammers, malware-spreaders, and harassers -- have an inexhaustible supply of places to hide.
8+
9+That's why we built a system for persistent identity called [Azimuth](../arvo-vs-azimuth). Azimuth identities are called _points_, and you need one to use the Arvo network. Points are secure, since they are owned and controlled with key-pair the Ethereum blockchain, which Azimuth is built on top of.
10+
11+An Azimuth point is a pronounceable string like `~firbyr-napbes`. It means nothing, but it's easy to remember and say out loud. `~firbyr-napbes` is actually just a 32-bit number (`3.237.967.392`, to be exact) that we turn into a human-memorable string.
12+
13+Points come in three classes: *galaxies*, *stars*, and *planets*. You can tell what class a point is in by how long its name is. The address space grows like a family tree. Galaxies are 8-bit and have names like `~mul`. Galaxies can issue 16-bit stars (`~dacpyl`), which can themselves issue 32-bit planets (`~laptel-holfur`).
14+
15+Planets are intended for everyday use by an adult human, and there is a maximum of about 4.3 billion of them (2 to the 32nd power). Stars and galaxies, on the other hand, are meant to act as network infrastructure: in the Arvo network they provide P2P routing and distribute software updates.
16+
17+```
18+ Size Name Parent Object Example
19+ ----- ------ ------ ------ -------
20+ 2^8 galaxy ~ supernode ~zod
21+ 2^16 star galaxy supernode ~dozbud
22+ 2^32 planet star user ~tasfyn-partyv
23+ 2^64 moon planet device ~sigsam-nimbot-tasfyn-partyv
24+ 2^128 comet ~ bot ~racmus-mollen-fallyt-linpex--watres-sibbur-modlux-rinmex
25+```
26+
27+## Moons and Comets
28+
29+In addition to these three classes of Azimuth points, there two other kinds of Urbit identities, but they do _not_ use Azimuth.
30+
31+*Moons* are 64 bits, are issued by planets, and have names like `~doznec-salfun-naptul-habrys`. Moons are meant for connected devices: phones, smart TVs, digital thermostats. Moons are not independent, but are subordinated to their parent planet.
32+
33+*Comets* are 128-bit points with no parents that can be launched by anyone. They are meant for bots. Being disposable and essentially unlimited, they will likely not be trusted by the others on the Arvo network. They have enormous names, like `~racmus-mollen-fallyt-linpex--watres-sibbur-modlux-rinmex`.