@@ -0,0 +1,68 @@
2+title = "~2020.12 Network Breach"
3+template = "page_indiced.html"
6+## When is the next breach?
8+The next breach is scheduled for early December.
10+## What is a “network breach”?
12+A network breach occurs when we need to change the Ames networking protocol number in order to reset the network’s state. When we change the protocol number, it will essentially create a new network. This rupture in continuity is why we refer to it as a “breach”. In the past, this has required users to take some action in order to get on the new network, but we are striving to make this as painless and loss-free as possible.
14+## Why does the network need to breach?
16+A network breach occurs when:
17+- A change must be made to all ships on the network simultaneously
18+- A change must be made to the Ames networking protocol
19+- Substantial changes must be made to Arvo and Vere simultaneously
21+In this breach, we are including changes that will allow us to make these changes in the future without breaching the network.
23+## Do I need to perform a personal breach?
25+No. A network breach subsumes all personal breaches, so please don’t also perform a personal breach.
29+If you are using hosting, your ship will process the breach automatically. If you are using a self-hosted ship, you need to affirmatively perform the breach using the instructions below.
31+In either case, the breach will render your ship unavailable for roughly one hour.
33+## Do I need to do anything with Bridge/Ethereum?
35+There are no Ethereum transactions necessary for this breach.
37+## I’m hosted by Tlon, or someone else—what do I need to do?
39+Users hosted by Tlon will not need to take any action. We’re handling everything on our end. If you’re hosted by another provider, you should contact that provider for instructions.
41+## I’m self-hosted—what do I need to do?
44+1. Download your [keyfile from Bridge](https://urbit.org/using/install/#keyfile).
45+2. Shut down your ship
46+3. [Archive and move your old pier](https://urbit.org/using/operations/using-your-ship/#moving-your-pier) (this is the directory that contains your urbit event log)
47+4. [Download the latest version](@/using/install.md#macos-and-linux) of the urbit binary
48+5. [Boot your ship with the new keyfile](https://urbit.org/using/install/#boot-your-planet)
50+If you are using the flagday tool that we will provide, it will perform all of these actions on your behalf, as well as exporting and reimporting your data.
52+## What happens to my data?
54+We’ve written a tool called flagday that will allow you to easily export your ship’s Landscape data. This includes your subscriptions and any content such as Collections, Notebooks and Chats that are on your ship. This data can then be seamlessly imported into a new ship.
56+## What is unique about this breach?
58+This breach will include Arvo/Vere Version Negotiation. This will allow us to ship updates to Vere and Arvo separately without worrying about an incompatibility on ships. For example, if you are running Vere 1.0 and an OTA of Arvo goes out that requires Vere 2.0, your ship will simply drop the update and notify you that you need to update your binary in order to receive the next update. When you update your binary is up to you.
60+## Will there be more network breaches?
62+We are optimistic that this will be our last breach, as all future updates to the network can be distributed as OTA (over-the-air) updates, possibly accompanied by a notification to update a binary version.
64+## What happens if I don’t breach?
66+Your Urbit will fall out of communication with the rest of the Urbit network which has performed the breach. This means that updates (OTAs) will no longer process and won’t be able to communicate with the rest of the network.