@@ -6,41 +6,25 @@ template = "page_indiced.html"
6aliases = ["/docs/getting-started/"]
6aliases = ["/docs/getting-started/"]
9−Urbit is not yet ready for everyday users — but if you're technically inclined or generally intrepid, feel free to try it out. It's a good place to explore.
9+Urbit is not for everyday users yet — but if you're technically inclined or generally intrepid, feel free to try it out. It's a good place to explore.
11## Overview
11## Overview
13There are two major components of the Urbit ecosystem: **Urbit OS** and **Urbit ID**.
13There are two major components of the Urbit ecosystem: **Urbit OS** and **Urbit ID**.
15−The the Urbit peer-to-peer (p2p) network is composed of instances of Urbit OS -- called **ships** -- that are virtual machines that run on any Unix platform.
15+The Urbit peer-to-peer (P2P) network is composed of instances of Urbit OS — also called **ships** — that run as virtual machines on any Unix platform. The Urbit ID registry is deployed on the Ethereum blockchain, and individual IDs exist as non-fungible ([ERC-721](https://eips.ethereum.org/EIPS/eip-721)) tokens. On the network, Urbit IDs function as network addresses, represented by pronounceable names like `~padmyn-pasnux`.
17−Urbit works as a p2p network where others fail because ships are associated with persistent and scarce identities that we refer to as Urbit IDs. The Urbit ID registry is deployed on the Ethereum blockchain, and individual IDs exist as non-fungible ([ERC-721](https://eips.ethereum.org/EIPS/eip-721)) tokens.
17+As we'll explain, there are a few types of Urbit ID, but everyday users tend to use **planets**, as full citizens of the network.
19−On the network, Urbit IDs function as network addresses, represented by pronounceable names like `~padmyn-pasnux`. There are a few kinds of Urbit ID, but ones meant for typical users are called **planets**. Anyone who has a planet can be thought of as a full "citizen" of the Urbit network. But to run your ship on the network, you need to start it with a piece of cryptographic information from its Urbit ID. This guide walk you through getting onto Urbit with an ID.
19+Two other types of ships are **stars** and **galaxies**. Together these perform essential infrastructural roles for the Urbit network. Each galaxy can distribute 256 stars, and each star can distribute 65,536 planets. So any given planet ultimately came from a specific star, which itself came from a specific galaxy. On the Urbit OS side, stars help route packets; galaxies are more like DNS root servers or ICANN members. The difference with Urbit in the analogy is that Urbit IDs are owned cryptographically by many different people and accrue reputation independently.
21−There are also free IDs called **comets**. They are good for bots and people who are new to Urbit and want to check out the network, but they aren't good for building a reputation as a friendly and responsible peer. Their long names make them difficult to remember and some communities ban comets to prevent spam, but they're still a good way to see what Urbit is about before buying your own planet.
21+If you just want to try Urbit out, there are also free IDs called **comets**. They are good for bots and people who are new to Urbit and want to check out the network, but they aren't good for building a reputation as a friendly and responsible peer. Their long names make them difficult to remember—and some communities ban comets to prevent spam—but they're still a good way to see what Urbit is about before buying your own planet.
23−### Stars and Galaxies
23+To start with a comet, continue below. For planet instructions, see [further below](#booting-your-planet). For star or galaxy instructions, see [this section](#star-setup-and-install).
25−In addition to comets and planets, two other types of ships are **stars** and **galaxies**. Together these perform essential infrastructural roles for Urbit OS network and for Urbit ID.
27−On the Urbit ID side, galaxies are at the top of the ID hierarchy with 256 in existence. Each galaxy can distribute 256 stars, and each star can distribute 65,536 planets. So any given planet ultimately came from a specific star, which itself came from a specific galaxy.
29−On the Urbit OS side, stars help route packets, kind of like an ISP. And galaxies are like DNS root servers or ICANN members. The difference is that Urbit IDs are owned cryptographically by many different people and accrue reputation independently.
31−If you're trying to get your star or galaxy set up, skip to [this section](#supernode).
33## Installing Urbit
25## Installing Urbit
35−The Urbit binary runs on a Unix-like operating system – Ubuntu, Fedora, or macOS, for example.
27+Regardless of your Urbit ID, you'll want the Urbit binary installed first. The Urbit binary runs on a Unix-like operating system – Ubuntu, Fedora, or macOS, for example.
37−We have different installation instructions for different platforms. To install and run Urbit OS, and its binary, run the commands that are listed for your operating system.
39−Once you've followed the appropriate install instructions, you can check if everything went right by running the `./urbit` command. Installation was successful if you get a block of output that begins with the line below:
42−Urbit: a personal server operating function
45### macOS and Linux
29### macOS and Linux
@@ -60,6 +44,12 @@ tar xzf urbit-v0.10.8-linux64.tgz
60./urbit-v0.10.8-linux64/urbit
44./urbit-v0.10.8-linux64/urbit
47+Once you've followed the appropriate install instructions, you can check if everything went right by running the `./urbit` command. Installation was successful if you get a block of output that begins with the line below:
50+Urbit: a personal server operating function
63To access your Urbit via HTTP on port 80 on Ubuntu, you may need to run the following:
53To access your Urbit via HTTP on port 80 on Ubuntu, you may need to run the following:
65sudo apt-get install libcap2-bin
55sudo apt-get install libcap2-bin
@@ -69,29 +59,15 @@ sudo setcap 'cap_net_bind_service=+ep' /path/to/urbit
70### Windows
60### Windows
72−> Please note that this method of installing Urbit is experimental, and we may not be able to assist you if you encounter issues related to WSL 2.
62+> Please note that this method of installing Urbit is experimental, and we may not be able to assist you if you encounter issues related to WSL 2.
74These instructions have been tested and verified for WSL 2 + Ubuntu 18.04 LTS.
64These instructions have been tested and verified for WSL 2 + Ubuntu 18.04 LTS.
76−Urbit cannot run on Windows itself, but there is a convenient way to run a Linux distro using the [Windows Subsystem for Linux 2](https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux) on Windows 10.
66+Urbit cannot run on Windows itself, but there is a convenient way to run a Linux distro using the [Windows Subsystem for Linux 2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-install) on Windows 10. Install the Windows Subsystem for Linux 2 and open a Linux terminal in Windows, following the Linux installation instructions above.
78−For Urbit to work, it is necessary to [install WSL 2](https://docs.microsoft.com/en-us/windows/wsl/wsl2-install) and not just WSL.
80−Once WSL 2 is installed, open a Linux terminal in Windows and then follow the Linux installation instructions above.
82For performance reasons, do not install Urbit in the mounted Windows volume, but install it in the Linux file system. For example, in your home directory, by typing `cd ~`.
68For performance reasons, do not install Urbit in the mounted Windows volume, but install it in the Linux file system. For example, in your home directory, by typing `cd ~`.
84−## Launching Urbit
70+## Setting up a comet {#comet}
86−Now that you have Urbit installed you can start it up with an ID.
88−You should have an `urbit` directory with two files in it: the `urbit-v0.XX.X-<OS>` directory, and the .tgz of that directory. The .tgz file can now be safely deleted.
90−If this is your first time using Urbit, it'll be easiest to start with a comet in order to get on the network.
92−### Comet: Install and Setup {#comet}
94−If you don't have your own Planet ID, but still want to try out the Urbit network you can launch a comet.
96**Comets** are 128-bit or 16 syllable Urbit IDs, that look like:
72**Comets** are 128-bit or 16 syllable Urbit IDs, that look like:
@@ -101,7 +77,7 @@ Comets are disposable, free identities that can be used to quickly join the netw
102### Booting a comet
78### Booting a comet
104−To boot a comet, go into the command line and run the following command from the `urbit` directory you created during Urbit installation:
80+To boot a comet, go into the command line and run the following command from the `urbit` directory you created during [Urbit installation](#installing-urbit):
@@ -111,23 +87,22 @@ To boot a comet, go into the command line and run the following command from the
111./urbit-v0.10.8-linux64/urbit -c mycomet
87./urbit-v0.10.8-linux64/urbit -c mycomet
114−This will take up to an hour, and will spin out a bunch of boot messages. It will also create a directory called `mycomet` in the Unix directory that you ran the command from (which should be your `urbit` directory).
90+Since your identity on the network is not verified, it may take up to an hour to generate your comet. As it boots, will spin out a bunch of boot messages and create a directory called `mycomet`. Toward the end of the boot process, you'll see something like:
116−Toward the end of the boot process, you'll see something like:
119ames: on localhost, UDP 31337.
93ames: on localhost, UDP 31337.
120http: live (insecure, public) on 8080
94http: live (insecure, public) on 8080
121http: live ("secure", public) on 8443
95http: live ("secure", public) on 8443
122http: live (insecure, loopback) on 12321
96http: live (insecure, loopback) on 12321
123−~sampel_commet:dojo>
97+~sampel_marzod:dojo>
126−When your ship is finished booting, you will see either the `~sampel_commet:dojo>` or `~sampel_commet:chat-cli/` prompt. If you're seeing `:chat-cli` press `Ctrl-X` to switch into Dojo.
100+When your ship is finished booting, you will see either the `~sampel_marzod:dojo>` or `~sampel_marzod:chat-cli/` prompt. If you see `:chat-cli`, press `Ctrl-X` to switch into Dojo.
128To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
102To exit Urbit, use `Ctrl-D` or enter `|exit` into Dojo.
130To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):
104To start your ship up again, run the following from your `urbit` directory (note the lack of `-c` argument):
133./urbit-v0.10.8-darwin/urbit mycomet
108./urbit-v0.10.8-darwin/urbit mycomet
@@ -143,7 +118,7 @@ Let's try our first command in the Dojo, the Urbit OS command line and Hoon REPL
143Type `(add 2 2)` into the Dojo. You should see the following:
118Type `(add 2 2)` into the Dojo. You should see the following:
146−~sampel_commet:dojo> (add 2 2)
121+~sampel_marzod:dojo> (add 2 2)
149When you press Enter, you should see this:
124When you press Enter, you should see this:
@@ -164,39 +139,37 @@ The `>=` output means that a command was successful. Now you can see your ship's
165### Using Landscape
140### Using Landscape
167−Landscape is the Urbit web interface, and it's the best way to interact with your ship. Chrome, Firefox, and Brave are the recommended browsers for using Landscape. To get onto Landscape:
142+Landscape is the Urbit web interface, and it's the best way to interact with your ship. To access Landscape:
1691. Start your ship. In the boot messages, look for a line that says something like `http: live (insecure, public) on 80`. The number given is the port that your ship is using.
1441. Start your ship. In the boot messages, look for a line that says something like `http: live (insecure, public) on 80`. The number given is the port that your ship is using.
1702. If the port given is 80, simply type `localhost` into your browser's address bar. If the given port is a different number, such as `8080`, you would type `localhost:8080`. You'll be met with a login prompt.
1452. If the port given is 80, simply type `localhost` into your browser's address bar. If the given port is a different number, such as `8080`, you would type `localhost:8080`. You'll be met with a login prompt.
1713. Type `+code` into your comet's Dojo. Copy-paste the returned code into the field asking for it in the browser page.
1463. Type `+code` into your comet's Dojo. Copy-paste the returned code into the field asking for it in the browser page.
172−4. You're in! Now you can explore apps such as Chat for messages, Publish for blogging, and Weather.
147+4. You're in! Now you can explore apps such as Chat, Publish, and more.
174−### Join a Chat
149+### Join a group
176−Now that you're on landscape, let's join the Urbit Community chat, a great place for newcomers to ask questions.
151+Now that you're on Landscape, join the Urbit Community, a great place for newcomers to ask questions.
178−Click that `Chat` type on your Landscape home page, and then click the `Join Chat` column. Then, enter `~bitbet-bolbel/urbit-community` into the field and press the `Join Chat` button.
153+Click the 'Groups' button on your Landscape home page, and then click the `Join Group` column. Then, enter `~bitbet-bolbel/urbit-community` into the field and press the `Join Group` button.
180−You can send and receive messages here, just like any other chatroom.
155+From the Urbit Community group you can join a variety of chatrooms, notebooks, and collections.
182−## Getting an Urbit ID (Planet or Star)
157+## Setting up a planet {#id}
159+If you have an Urbit ID, you'll use the [Bridge](https://bridge.urbit.org) client to get your ship's *keyfile* before you can [boot your ship](#booting-your-ship). Your keyfile is a cryptographic secret that allows your Urbit instance to authenticate itself on the network, so you can't boot your planet without it. Your keyfile is deterministically derived from your other cryptographic secrets.
161+### Purchase an Urbit ID
184Tlon doesn't currently sell or distribute Urbit IDs, but there are a few ways to get your own:
163Tlon doesn't currently sell or distribute Urbit IDs, but there are a few ways to get your own:
186- Getting an invitation from a friend
165- Getting an invitation from a friend
187- Purchasing an Urbit ID from a third party, such as [urbit.live](https://urbit.live), [OpenSea](https://opensea.io), [planet.market](https://planet.market/), or [Urbit Marketplace](https://urbitmarketplace.com/).
166- Purchasing an Urbit ID from a third party, such as [urbit.live](https://urbit.live), [OpenSea](https://opensea.io), [planet.market](https://planet.market/), or [Urbit Marketplace](https://urbitmarketplace.com/).
189−Note that when you buy a planet you may have to escape its star if the star your planet is linked to isn't operating. Ask around in the `urbit-community` chat as a comet first for help before purchasing.
191−If you already have a planet and need to escape its star, see [Escaping A Sponsor](@/using/operations/using-your-ship.md#escape).
168+Note that when you buy a planet, you should ensure with the provider that the star is operating. If you already have a planet and need to escape a non-operational star, see [Escaping A Sponsor](@/using/operations/using-your-ship.md#escape).
193Tlon occasionally selects candidates to distribute invitations, and users operating galaxies and stars can spawn and distribute a finite number of stars and planets, respectively.
170Tlon occasionally selects candidates to distribute invitations, and users operating galaxies and stars can spawn and distribute a finite number of stars and planets, respectively.
195−### Using your Urbit ID (Planet or Star) {#id}
172+### About your Urbit ID wallet
197−If you have an Urbit ID, you'll use the [Bridge](https://bridge.urbit.org) client to get your ship's *keyfile* before you can [boot your ship](#booting-your-ship). Your keyfile is a cryptographic secret that allows your Urbit instance to authenticate itself on the network, so you can't boot your planet without it. Your keyfile is deterministically derived from your other cryptographic secrets.
199−### The Urbit ID Wallet
201Your Urbit ID is actually yours. As long as you control its cryptographic secrets, nobody can take it away from you. That's why it's important to know a little bit about the cryptographic architecture of Urbit secrets.
174Your Urbit ID is actually yours. As long as you control its cryptographic secrets, nobody can take it away from you. That's why it's important to know a little bit about the cryptographic architecture of Urbit secrets.
@@ -208,36 +181,30 @@ Urbit ID secrets operate as a system of separate but hierarchically related Ethe
209- **Keyfile**: Derived from the management proxy. Used as cryptographic proof that your Urbit ship is who it says it is. You use it to start up your ship for the first time.
182- **Keyfile**: Derived from the management proxy. Used as cryptographic proof that your Urbit ship is who it says it is. You use it to start up your ship for the first time.
211−### Getting Your Keyfile {#keyfile}
184+### Get your keyfile {#keyfile}
213As mentioned previously, there are a few ways to acquire a planet. All methods, however, should result in you receiving at least one secret, such as a **master ticket**. If you received an email invite to Urbit, the master ticket should a `.pdf` the passport folder that you downloaded.
186As mentioned previously, there are a few ways to acquire a planet. All methods, however, should result in you receiving at least one secret, such as a **master ticket**. If you received an email invite to Urbit, the master ticket should a `.pdf` the passport folder that you downloaded.
215−1. To connect to Bridge, go to https://bridge.urbit.org.
188+1. Connect to [Bridge](https://bridge.urbit.org).
216−2. Enter the name of your planet and the associated master ticket in the appropriate fields. If you received your secret is in another form, such as a dictionary mnemonic, click the `Metamask, Mnemonic, Hardware Wallet...` button for alternate login methods.
189+2. Enter the name of your planet and the associated master ticket in the appropriate fields. Click the "Metamask, Mnemonic, Hardware Wallet..." button for alternate login methods if you don't have a master ticket.
217−3. Once you're logged in, click the `OS` option.
190+3. Once you're logged in, click the "OS" option.
218−4. In resulting page, click the `Download Arvo Keyfile` button. You should receive a `.key` file that contains the secret needed to boot your ship. Hold on to this file.
191+4. In resulting page, click the "Download Arvo Keyfile" button. You should receive a `.key` file that contains the secret needed to boot your ship. Hold onto this file.
220−## Hosting
193+### Choose to host or run your ship locally
222There are two supported ways of running an Urbit ship: using a cloud service, or running it locally on your own machine. Most users run things locally at first, but we recommend eventually using a cloud service for Urbit because it allows your ship to be accessed from anywhere on multiple devices. Hosting your ship in the cloud also allows it to always be online and ready for OTA updates. It's technically possible to run your Urbit ship on a home server, but ISPs often restrict this to business plans and opening up your home network to the internet can be unsafe if done improperly.
195There are two supported ways of running an Urbit ship: using a cloud service, or running it locally on your own machine. Most users run things locally at first, but we recommend eventually using a cloud service for Urbit because it allows your ship to be accessed from anywhere on multiple devices. Hosting your ship in the cloud also allows it to always be online and ready for OTA updates. It's technically possible to run your Urbit ship on a home server, but ISPs often restrict this to business plans and opening up your home network to the internet can be unsafe if done improperly.
224We have a guide for [hosting your ship on DigitalOcean](@/using/operations/hosting.md) which we've found works well, but any cloud hosting service should work.
197We have a guide for [hosting your ship on DigitalOcean](@/using/operations/hosting.md) which we've found works well, but any cloud hosting service should work.
226−### Booting Your Planet
199+### Boot your planet
228−You'll be booting your ship with the keyfile that you downloaded from Bridge [earlier in this document](#id).
230−Note that this section is only for booting a ship that uses the live Urbit network.
232−#### Step 1: Find Your Urbit ID
201+You'll be booting your ship with the keyfile that you downloaded from Bridge.
234−This will look something like `~lodleb-ritrul`. You can see the name of your Urbit ID when you log into your wallet using the [Bridge client](#id).
236−#### Step 2: Find the path to your keyfile
203+#### Step 1: Find the path to your keyfile
238Find the absolute path to the keyfile that you downloaded from Bridge. Copy it.
205Find the absolute path to the keyfile that you downloaded from Bridge. Copy it.
240−#### Step 3: Run the boot command
207+#### Step 2: Run the boot command
242Enter your `urbit` directory.
209Enter your `urbit` directory.
@@ -280,11 +247,7 @@ Note that `sampel-palnet/` is the path of a folder, which we just created in you
281Never boot multiple instances of your ship at the same time. You can prevent this from happening on accident by only ever keeping a single copy of your pier.
248Never boot multiple instances of your ship at the same time. You can prevent this from happening on accident by only ever keeping a single copy of your pier.
283−**Important:** once a key has been used to boot a ship onto the network, it cannot be used to boot that ship again later - doing so will cause communication problems with other ships.
250+**Important:** once a key has been used to boot a ship onto the network, it cannot be used to boot that ship again later - doing so will cause communication problems with other ships. For this reason you should **delete the keyfile from your machine once your ship has booted successfully**. If you do use the same key twice, you'll need to conduct a [personal breach](#breaches) to restore your ship to full functionality).
285−For this reason you should **delete the keyfile from your machine once your ship has booted successfully**.
287−If you do use the same key twice, you'll need to conduct a [personal breach](#breaches) to restore your ship to full functionality).
289Delete the keyfile with the command below:
252Delete the keyfile with the command below:
@@ -294,7 +257,7 @@ rm path/to/my-planet.key
295### Updating to the latest binary
258### Updating to the latest binary
297−Most updates to Urbit are downloaded and applied automatically as OTA (Over the Air) updates. Occasionally it would be infeasible to distribute an update this way, and a new `urbit` binary is released. This is announced in the [urbit-dev](https://groups.google.com/a/urbit.org/forum/#!forum/dev) Google Group when it occurs (as are all OTA updates).
260+Most updates to Urbit are downloaded and applied automatically as OTA (Over the Air) updates. Occasionally it would be infeasible to distribute an update this way, and a new `urbit` binary is released. This is announced in the [urbit-dev](https://groups.google.com/a/urbit.org/forum/#!forum/dev) Google Group when it occurs (as are all OTA updates).
299To update to the latest binary, download and extract it to replace your existing one. Then run it as before.
262To update to the latest binary, download and extract it to replace your existing one. Then run it as before.
@@ -341,7 +304,7 @@ Then you're good to go, in the future you'll just modify the version numbers in
342### Breaches {#breaches}
305### Breaches {#breaches}
344−An important concept on the Urbit 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.
307+An important concept on the Urbit 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.
346There are two kinds of breaches: personal breaches and network breaches.
309There are two kinds of breaches: personal breaches and network breaches.
@@ -349,15 +312,11 @@ A personal breach can fix many problems with your ship, but should be used as a
350For details on breaching, please read the [Guide to Breaches](@/docs/tutorials/guide-to-breaches.md) documentation.
313For details on breaching, please read the [Guide to Breaches](@/docs/tutorials/guide-to-breaches.md) documentation.
354−If you find a bug, please report it as an Issue at https://github.com/urbit/urbit/issues/new/choose. Give as much detail as possible with your bug report so the engineer team can fix it.
356−## Running a Star or Galaxy {#supernode}
315+## Running a star or galaxy {#supernode}
358Setting up and running a star or galaxy is a little bit different from setting up and running a planet.
317Setting up and running a star or galaxy is a little bit different from setting up and running a planet.
360−### Getting a Star or Galaxy
319+### Getting a star or galaxy
362Stars are valuable cryptographic assets. They can be bought in one of two ways.
321Stars are valuable cryptographic assets. They can be bought in one of two ways.
@@ -366,7 +325,7 @@ Stars are valuable cryptographic assets. They can be bought in one of two ways.
367Galaxies are rare and extremely valuable, meaning that there is no liquid market for them. If you want to buy a galaxy, you'll have to find an individual galaxy owner and transact with them.
326Galaxies are rare and extremely valuable, meaning that there is no liquid market for them. If you want to buy a galaxy, you'll have to find an individual galaxy owner and transact with them.
369−### A Note Regarding Security
328+### A note on security
371As mentioned before, stars are valuable. You are solely responsible for safeguarding your seeds and secret keys, and arming yourself with the computer-security knowledge that is attendant upon that safeguarding. You act at your own risk in reliance upon the contents of the manual. In no way is the Tlon Corporation responsible for the actions, decisions, or other behavior taken or not taken by you in reliance upon this manual.
330As mentioned before, stars are valuable. You are solely responsible for safeguarding your seeds and secret keys, and arming yourself with the computer-security knowledge that is attendant upon that safeguarding. You act at your own risk in reliance upon the contents of the manual. In no way is the Tlon Corporation responsible for the actions, decisions, or other behavior taken or not taken by you in reliance upon this manual.
@@ -375,20 +334,16 @@ It’s a good idea to store your keys redundantly in case one method fails. If y
375- Storing the secret on a hardware wallet that is never connected to a networked machine.
334- Storing the secret on a hardware wallet that is never connected to a networked machine.
376- There are products that let you store the key on steel. This medium is resistant to both water damage and fire damage.
335- There are products that let you store the key on steel. This medium is resistant to both water damage and fire damage.
378−### Getting a Star's Keyfile
337+### Getting a star's keyfile
380−1. To connect to Bridge, go to https://bridge.urbit.org.
381−2. Enter the name of your star and the associated master ticket in the appropriate fields. If you received your secret is in another form, such as a dictionary mnemonic, click the `Metamask, Mnemonic, Hardware Wallet...` button for alternate login methods.
382−3. Once you're logged in, click the `OS` option.
383−4. In resulting page, click the `Download Arvo Keyfile` button. You should receive a `.key` file that contains the secret needed to boot your ship. Hold on to this file.
385−### Star: Setup And Install
387−Because of their need for near-perfect uptime Stars should be hosted on cloud services.
339+1. Connect to [Bridge](https://bridge.urbit.org).
340+2. Enter the name of your star and the associated master ticket in the appropriate fields. Click the "Metamask, Mnemonic, Hardware Wallet..." button for alternate login methods if you don't have a master ticket.
341+3. Once you're logged in, click the "OS" option.
342+4. In resulting page, click the "Download Arvo Keyfile" button. You should receive a `.key` file that contains the secret needed to boot your ship. Hold onto this file.
389−We have a guide for [hosting on DigitalOcean](@/using/operations/hosting.md), but any cloud provider should work.
344+### Boot your star
391−#### Maintaining a Star
346+Because of their need for near-perfect uptime Stars should be hosted on cloud services. We have a guide for [hosting on DigitalOcean](@/using/operations/hosting.md), but any cloud provider should work.
393Being an infrastructure node, a star has certain responsibilities to the Urbit network.
348Being an infrastructure node, a star has certain responsibilities to the Urbit network.
@@ -400,6 +355,6 @@ Network-wide breaches are distinct from personal breaches, wherein an individual
401See our [Guide to Breaches](@/docs/tutorials/guide-to-breaches.md) for more information and for instructions on breaching.
356See our [Guide to Breaches](@/docs/tutorials/guide-to-breaches.md) for more information and for instructions on breaching.
403−### Running a Galaxy
358+### Running a galaxy
405A galaxy is at the top of the hierarchy in terms of importance. Thus, if you're interested in running one, please contact support@urbit.org, and we will give you personalized assistance in getting set up.
360A galaxy is at the top of the hierarchy in terms of importance. Thus, if you're interested in running one, please contact support@urbit.org, and we will give you personalized assistance in getting set up.