on master help sign in
tinnus suggestions
583e22cdrbeefsupreme
content/docs/azimuth/azimuth.md+1−1
@@ -100,7 +100,7 @@ blockchains. However, anybody can run a roller, and even using your own ship as
100a roller to submit single transactions results in significant savings.
100a roller to submit single transactions results in significant savings.
101
101
102A casual overview of the naive rollups system can be found on the
102A casual overview of the naive rollups system can be found on the
103−[blog](/blog/rollups) as well as the Pilot's Manual (insert link). Developers
103+[blog](/blog/rollups). Developers
104are encouraged to read our Layer 2 documentation, starting with the [Layer 2
104are encouraged to read our Layer 2 documentation, starting with the [Layer 2
105Overview](/docs/azimuth/l2/layer2).
105Overview](/docs/azimuth/l2/layer2).
106
106
content/docs/azimuth/hd-wallet.md+1−1
@@ -28,7 +28,7 @@ their own individual Ethereum key-pairs.
28
28
29Think of your master ticket like a very high-value password. The master ticket
29Think of your master ticket like a very high-value password. The master ticket
30is the secret code from which all of your other keys are derived. Technically,
30is the secret code from which all of your other keys are derived. Technically,
31−your master ticket is seed entropy. You should never share it with anyone, and
31+your master ticket is a cryptographic seed. You should never share it with anyone, and
32store it very securely. This ticket can derive all of your other keys: your
32store it very securely. This ticket can derive all of your other keys: your
33ownership key and all of the related proxies.
33ownership key and all of the related proxies.
34
34
content/using/id/hd-wallet.md+1−1
@@ -26,7 +26,7 @@ If you're interested, you can read the spec here: [Urbit HD Wallet Spec (UP
26
26
27### What is a master ticket? {#master-ticket}
27### What is a master ticket? {#master-ticket}
28
28
29−The "master ticket" is the entropy seed from which your other Urbit ID keys are
29+The "master ticket" is the cryptographic seed from which your other Urbit ID keys are
30derived. It should be treated like a master password: **you should never share
30derived. It should be treated like a master password: **you should never share
31it with anyone, and you must store it very securely (see our practices below).**
31it with anyone, and you must store it very securely (see our practices below).**
32This ticket is used to derive the Ethereum wallet that holds your ownership
32This ticket is used to derive the Ethereum wallet that holds your ownership
content/using/id/overview.md+11−11
@@ -81,9 +81,9 @@ a message is signed after another by including the signature of the first in the
81second. This is equivalent to reading out a newspaper headline to prove a
81second. This is equivalent to reading out a newspaper headline to prove a
82message was recorded after a given day.
82message was recorded after a given day.
83
83
84−However, the problem of proving one message was sent before any later ones
84+The problem of proving that one message was sent before any later ones
85inverts the problem. You can solve this with newspapers by placing the message
85inverts the problem. You can solve this with newspapers by placing the message
86−in the text of the newspaper. However, while reading a newspaper requires no
86+in the text of the newspaper. While reading a newspaper requires no
87central party, writing one does. For a long time, this sort of message was
87central party, writing one does. For a long time, this sort of message was
88always handled by a central party. SSL revocations are managed by a few central
88always handled by a central party. SSL revocations are managed by a few central
89parties. When you buy property, it's not sufficient to have the previous owner
89parties. When you buy property, it's not sufficient to have the previous owner
@@ -92,7 +92,7 @@ the owner may sell their property to multiple people and there would be no way
92to determine who is the new owner. With the land registry, all you need to do is
92to determine who is the new owner. With the land registry, all you need to do is
93ask the registry which sale happened first, and that's the one that counts.
93ask the registry which sale happened first, and that's the one that counts.
94
94
95−However, Urbit is yours and it's forever. Trusting central registries
95+Again, Urbit is yours and it's forever. Trusting central registries
96jeopardizes both. The keen reader will notice that the problem of determining
96jeopardizes both. The keen reader will notice that the problem of determining
97which key rotation happened first is exactly the double-spend problem that
97which key rotation happened first is exactly the double-spend problem that
98Satoshi solved with his proof of work algorithm for Bitcoin. His first block
98Satoshi solved with his proof of work algorithm for Bitcoin. His first block
@@ -102,11 +102,11 @@ it after that date.[^1]
102
102
103Some argue that blockchain is only good for money. This is myopic and is
103Some argue that blockchain is only good for money. This is myopic and is
104generally based on the experience that its most valuable application so far has
104generally based on the experience that its most valuable application so far has
105−been money. However, blockchain is a cryptographic primitive to do what was
105+been money. The deeper problem that the blockchain cryptographic primitive
106−previously impossible: prove that one message was signed before another without
106+allows one to solve a previously impossible task: prove that one message was
107−a central party. Blockchain was discovered by someone trying to create digital
107+signed before another without a central party. Blockchain was discovered by
108−money, and he needed that primitive, but that doesn't mean that's all it's good
108+someone trying to create digital money, and he needed that primitive, but that
109−for.
109+doesn't mean that's all it's good for.
110
110
111Thus, we store our PKI data on a blockchain for our second kind of name:
111Thus, we store our PKI data on a blockchain for our second kind of name:
112[planets](/docs/glossary/planet). A planet is a 32-bit address which has key information stored on the
112[planets](/docs/glossary/planet). A planet is a 32-bit address which has key information stored on the
@@ -116,7 +116,7 @@ everyone on the network will listen to the blockchain for key data. Thus, we
116have global consistency, permanence, and self sovereignty. We know of no other
116have global consistency, permanence, and self sovereignty. We know of no other
117solution that can provide these properties.
117solution that can provide these properties.
118
118
119−However, while small individually, the aggregate PKI data for all nodes on the
119+While small individually, the aggregate PKI data for all nodes on the
120network may become very large. This is not an issue for comets because nobody
120network may become very large. This is not an issue for comets because nobody
121needs to store comet keys except for those which they're talking with, and even
121needs to store comet keys except for those which they're talking with, and even
122those can be garbage-collected and re-requested and verified. For planets, there
122those can be garbage-collected and re-requested and verified. For planets, there
@@ -136,7 +136,7 @@ state locally, dramatically reducing gas costs to the point that Tlon offers a
136free-to-use public "roller" which aggregates transactions and submits them as a
136free-to-use public "roller" which aggregates transactions and submits them as a
137batch.
137batch.
138
138
139−However, 4 billion is not enough addresses for every device on the planet today,
139+Of course, 4 billion is not enough addresses for every device on the planet today,
140much less in a few decades. So, we apply our maxim of re-examining our choices
140much less in a few decades. So, we apply our maxim of re-examining our choices
141at each level for each use case. Examining the idea maze above, we cannot use
141at each level for each use case. Examining the idea maze above, we cannot use
142the blockchain option for everything since the data is too big. However, it's
142the blockchain option for everything since the data is too big. However, it's
@@ -150,7 +150,7 @@ for its own moons, and anyone who needs to talk to your moons can ask you for
150the keys.
150the keys.
151
151
152This is the sense in which moons are true ships: they're permanent names and you
152This is the sense in which moons are true ships: they're permanent names and you
153−own them completely, as long as you own the planet. However, they're not
153+own them completely, as long as you own the planet. But they're not
154independent ships — their keys can always be revoked by their planet.
154independent ships — their keys can always be revoked by their planet.
155
155
156To create a sane network, we require global consistency for all our names. There
156To create a sane network, we require global consistency for all our names. There