@@ -57,9 +57,10 @@ For planets, stars, and galaxies, your networking public key is configured on
57the Ethereum blockchain using one of your Azimuth private keys - either the one
57the Ethereum blockchain using one of your Azimuth private keys - either the one
58associated to the wallet which owns the ship, or the one which holds the
58associated to the wallet which owns the ship, or the one which holds the
59[management proxy](@/docs/glossary/proxies.md). This is typically accomplished
59[management proxy](@/docs/glossary/proxies.md). This is typically accomplished
60−with Bridge. Your networking private key is a necessary input (the
60+with Bridge. Your networking private key (in the
61−[keyfile](@/docs/glossary/keyfile.md)) for the initial boot sequence of your
61+[keyfile](@/docs/glossary/keyfile.md)) is a necessary input for the initial boot
62−ship (sometime called its `%dawn`), and this is also provided by Bridge.
62+sequence of your ship (sometime called its `%dawn`), and this is also provided
64Public keys for moons are not tracked on the blockchain; instead they are
65Public keys for moons are not tracked on the blockchain; instead they are
65tracked by their parent ship. The networking private key is generated by the
66tracked by their parent ship. The networking private key is generated by the
@@ -67,7 +68,7 @@ parent ship and injected into the `%dawn` sequence for the moon, and its public
67key is stored by the parent in its Jael vane. Networking keys for moons may be
68key is stored by the parent in its Jael vane. Networking keys for moons may be
68changed by the parent ship, but not by the moon itself.
69changed by the parent ship, but not by the moon itself.
70−For comets, their 128-bit `@p` name is actually their networking public key, and
71+For comets, their 128-bit `@p` name is the hash of their networking public key, and
71the "mining" process to generate a comet consists of guessing a private key for
72the "mining" process to generate a comet consists of guessing a private key for
72which the associated public key for which the last two bytes of their `@p`
73which the associated public key for which the last two bytes of their `@p`
73matches one of the stars on the comet sponsors list downloaded during boot.
74matches one of the stars on the comet sponsors list downloaded during boot.
@@ -104,8 +105,8 @@ are utilized by Ames. All cryptographic primitives are
104cryptographic libraries.
105cryptographic libraries.
106[Vere](@/docs/vere/_index.md) is Urbit's Nock runtime system, written in C. All
107[Vere](@/docs/vere/_index.md) is Urbit's Nock runtime system, written in C. All
107−cryptographic functions implemented in Hoon are hinted to the interpreter use
108+cryptographic functions implemented in Hoon are hinted to the interpreter,
108−the [jet system](@/docs/vere/jetting.md) to run standard vetted cryptographic
109+causing it to utilize the [jet system](@/docs/vere/jetting.md) to run standard vetted cryptographic
109libraries.
110libraries.
111[Azimuth](@/docs/azimuth/_index.md) is an Ethereum-based public key
112[Azimuth](@/docs/azimuth/_index.md) is an Ethereum-based public key