Getting geared up for a network breach very very soon! Some exciting stuff on the testnet...
Show this thread
-
A "breach" is short hand for "network continuity breach." In order to introduce large changes we sometimes reset the network state. We do this by incrementing the Ames protocol number. All Urbit ID/Azimuth data are totally unaffected by this.
Show this thread
Ideally, all of urbit is upgraded over the air, but in order to write and deploy an over the air (OTA) update, developers must write not only new code but code that translates the old state into the new state. For code that involves networking, this is ... complex.
-
-
We've been front-loading these "breaching" changes so that we can get to stability and continuity faster. Updating and rationalizing the networking is a good example of this kind of thing.
Show this thread -
When the breach happens, your ship will still run, but it won't be able to access the rest of the network. When this occurs, youll be able to rename your pier dir, DL the newest binary from http://urbit.org and boot your ship with your same keyfile, no need to change keys.
Show this thread
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.