@@ -5,15 +5,15 @@ template = "page_indiced.html"
8−*Last updated ~2020.12.9*
8+*Last updated ~2021.1.14*
10−A network reset happened on ~2020.12.8 — you may need to take action. We call an event like this a 'breach' since we breach the continuity of Urbit's network protocol. This isn't a security incident.
10+A network reset happened on ~2020.12.8 — you may need to take action.
12−Unlike past breaches, this one comes with a tool to export and reimport all of your data so that you don't lose anything; we call it `flagday`. Details on its usage can be found below.
12+Unlike past resets, this one comes with a tool to export and reimport all of your data so that you don't lose anything; we call it `flagday`. Details on its usage can be found below.
14*If you are self-hosting your ship, following these instructions is mandatory in order to communicate with the rest of the network.*
14*If you are self-hosting your ship, following these instructions is mandatory in order to communicate with the rest of the network.*
16−## When was the last network breach?
16+## When was the last network reset?
18On Tuesday, ~2020.12.8.
18On Tuesday, ~2020.12.8.
@@ -21,30 +21,30 @@ On Tuesday, ~2020.12.8.
22We'll be adding new information to this document as soon as there's anything to share. Updates will be broadcasted via Twitter [here](https://twitter.com/zodisok/) as well.
22We'll be adding new information to this document as soon as there's anything to share. Updates will be broadcasted via Twitter [here](https://twitter.com/zodisok/) as well.
24−## What is a “network breach”?
24+## What is a "network reset"?
26−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.
26+A network reset 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 change in continuity is why we refer to it as a "reset". In the past, this has required users to take some action in order to get on the new network, but this time we've provided tooling to make it seamless.
28−## Why does the network need to breach?
28+## Why does the network need to reset?
30−A network breach occurs when:
30+A network reset occurs when:
31- A change must be made to all ships on the network simultaneously
31- A change must be made to all ships on the network simultaneously
32- A change must be made to the Ames networking protocol
32- A change must be made to the Ames networking protocol
33- Substantial changes must be made to Arvo and Vere simultaneously
33- Substantial changes must be made to Arvo and Vere simultaneously
35−In this breach, we are including changes that will allow us to make these changes in the future without breaching the network.
35+In this reset, we are including changes that will allow us to make these changes in the future without resetting the network.
37## Do I need to perform a personal breach?
37## Do I need to perform a personal breach?
39−No. A network breach subsumes all personal breaches, so please don’t also perform a personal breach.
39+No. A network reset subsumes all personal breaches, so please don’t also perform a personal breach.
41## What can I expect?
41## What can I expect?
43−If you are using a self-hosted ship, you need to affirmatively perform the breach using the instructions below. If you are using hosting, your ship will process the breach automatically.
43+If you are using a self-hosted ship, you need to affirmatively perform the reset using the instructions below. If you are using hosting, your ship will process the reset automatically.
45## Do I need to do anything with Bridge/Ethereum?
45## Do I need to do anything with Bridge/Ethereum?
47−There are no Ethereum transactions necessary for this breach.
47+There are no Ethereum transactions necessary for this reset.
49## I’m self-hosted—what do I need to do?
49## I’m self-hosted—what do I need to do?
@@ -88,18 +88,22 @@ Users hosted by Tlon will not need to take any action. We’re handling everythi
89We’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.
89We’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.
91−## What is unique about this breach?
91+## What is unique about this reset?
93−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.
93+This reset 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.
95−## Will there be more network breaches?
95+## Will there be more network resets?
97−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.
97+We are optimistic that this will be our last reset, 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.
99−## What happens if I don’t breach?
99+## What happens if I don’t follow these instructions?
101−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 you won’t be able to communicate with anyone else on the network.
101+Your Urbit will fall out of communication with the rest of the Urbit network which has performed the reset. This means that updates (OTAs) will no longer process and you won’t be able to communicate with anyone else on the network.
103## How do I get help if I need it?
103## How do I get help if I need it?
105If you're in a tight spot or confused, reach out to us at support@urbit.org.
105If you're in a tight spot or confused, reach out to us at support@urbit.org.
107+## What's a 'breach'?
109+We often call events like this a 'breach' since we "breach" the continuity of Urbit's network protocol. This language has no relationship to security. If anything, it's more like a "hard fork" of the network.