e1d8649 · urbit.org · git.iko.soy

content/Bitcoin-wallet.md+1−1

compare with master

unifiedsplit

@@ -18,7 +18,7 @@ If you are interested in [being a provider](https://subject.network/posts/btc-wa

18

19### Verify

20

21−You should verify your version of this Bitcoin wallet. To do so, follow the instructions in the README in our [Github](https://github.com/urbit/urbit/blob/master/pkg/btc-wallet/README.md) repo.

21+You should verify your version of this Bitcoin wallet. To do so, follow the instructions in the README in our [Github](https://github.com/urbit/urbit/blob/master/pkg/btc-wallet/README) repo.

22

23Instructions reproduced here:

24

content/blog/first-contract.md+23−23

@@ -15,9 +15,9 @@ image = "https://media.urbit.org/site/posts/essays/land3.jpg"

15<br>

16

17Recently, the [first upgrade](https://github.com/urbit/azimuth/pull/35) to the

18−[Azimuth](/docs/glossary/azimuth.md) smart contracts which make up Urbit ID was

18+[Azimuth](/docs/glossary/azimuth) smart contracts which make up Urbit ID was

19−put up to an [upgrade proposal vote](/docs/glossary/upgrade.md) by the

19+put up to an [upgrade proposal vote](/docs/glossary/upgrade) by the

20−[Galactic Senate](/docs/glossary/senate.md). This vote is still open and will

20+[Galactic Senate](/docs/glossary/senate). This vote is still open and will

21last for 30 days (June 20th) or until an absolute majority is reached. We’d like

22to take this opportunity to discuss two things. [First](#changelist), what the

23proposed changes are, and [second](#senate), a review of how Urbit governance

@@ -25,16 +25,16 @@ works and where we’re at in the decentralization process.

25

26Before we dive into what the proposed changes are, let’s review what the Senate

27is actually capable of changing. Urbit ID is really two sets of smart contracts:

28−Azimuth and [Ecliptic](/docs/glossary/ecliptic.md). Azimuth is the data of the

28+Azimuth and [Ecliptic](/docs/glossary/ecliptic). Azimuth is the data of the

29public key infrastructure - roughly, this is the list of

30−[ships](/docs/glossary/ship.md) and which Ethereum addresses own them, along

30+[ships](/docs/glossary/ship) and which Ethereum addresses own them, along

31with other data such as networking keys and sponsorship status. The Senate has

32no ability to touch this data directly. This is in direct contrast to all

33existing centralized services, where your account is always at risk of being

34taken away from you. What the Senate can change is Ecliptic, which is the

35“business logic” that decides how you can interact with the data in Azimuth.

36These are mechanisms such as what powers various

37−[proxies](/docs/glossary/proxies.md) have, how stars/planets are released over

37+[proxies](/docs/glossary/proxies) have, how stars/planets are released over

38time, and how sponsorship works. Put another way, the data and database format

39must remain the same, but the rules by which we interact with it may change

40according to the governance rules we [detail below](#senate).

@@ -119,27 +119,27 @@ current position, but still serve as useful historical markers. We hope to

119revisit and refresh these documents soon.

120

121- [2016.5.16 - Interim

122− Constitution](/blog/interim-constitution.md)

122+ Constitution](/blog/interim-constitution)

123- [2016.5.16 - The

124− Urbit Address Space](/blog/the-urbit-address-space.md)

124+ Urbit Address Space](/blog/the-urbit-address-space)

125- [2016.6.24 - The DAO as a Lesson in Decentralized

126− Governance](/blog/the-dao-as-a-lesson-in-decentralized-governance.md)

126+ Governance](/blog/the-dao-as-a-lesson-in-decentralized-governance)

127- [2019.1.11 - Governance of

128− urbit.org](/blog/governance-of-urbit.md)

128+ urbit.org](/blog/governance-of-urbit)

129

130### Galactic Senate

131

132−The Galactic Senate is composed of all [galaxy](/docs/glossary/galaxy.md)

132+The Galactic Senate is composed of all [galaxy](/docs/glossary/galaxy)

133holders, which at present consists of more than 100 individuals and a few

134organizations, including Tlon and the Urbit Foundation. Using the Azimuth

135voting contract, the Senate can present and vote on two kinds of proposals:

136−[document proposals](/docs/glossary/docvote.md) and [upgrade

136+[document proposals](/docs/glossary/docvote) and [upgrade

137−proposals](/docs/glossary/upgrade.md). Thus far, all matters which the Senate

137+proposals](/docs/glossary/upgrade). Thus far, all matters which the Senate

138has voted on have been document proposals. The [most recent

139vote](https://github.com/urbit/azimuth/pull/34) declared the Urbit network as

140(i) being secure (as confirmed by a [third party

141−audit](/blog/security-audit.md)) and (ii) having reached continuity (as in, no

141+audit](/blog/security-audit)) and (ii) having reached continuity (as in, no

142−further [network breaches](/docs/glossary/breach.md) are expected). Previous votes

142+further [network breaches](/docs/glossary/breach) are expected). Previous votes

143were to declare that [Azimuth is live](https://github.com/urbit/azimuth/pull/25)

144and that [Arvo is stable](https://github.com/urbit/azimuth/pull/24).

145

@@ -155,7 +155,7 @@ In the beginning, Urbit’s creator Curtis Yarvin was in possession of the entir

155address space - all 256 galaxies, and everything underneath it. A network of one

156is no network at all, and so over the last decade Urbit’s development has been

157primarily driven by selling or giving away these galaxies. On [June 1,

158−2016](/blog/the-urbit-address-space.md), the allocation was:

158+2016](/blog/the-urbit-address-space), the allocation was:

159

160> 95, to the Tlon Corporation. 50, to urbit.org, the future community

161> foundation. 40, to Tlon employees and their family members (24 to Curtis, who

@@ -167,9 +167,9 @@ primarily driven by selling or giving away these galaxies. On [June 1,

167Since then, Tlon has sold a number of

168its galaxies to fund development and others have changed hands to the point

169that Tlon and urbit.org no longer possess a majority share of galaxies. In

170−January 2019, [Curtis gave all of his galaxies](/blog/a-founders-farewell.md) to

170+January 2019, [Curtis gave all of his galaxies](/blog/a-founders-farewell) to

171Tlon when he left the project. In August 2020 we shared an update on the [known

172−distribution of address space](/blog/value-of-address-space-pt3.md), where

172+distribution of address space](/blog/value-of-address-space-pt3), where

173Curtis’ galaxies are marked as Tlon’s “naked galaxies”. Shortly thereafter, Tlon

174disbursed its naked galaxies among the employees that wanted one who did not

175already possess one, thus removing Tlon and urbit.org’s controlling share of the

@@ -198,13 +198,13 @@ controlled by the users is now well underway.

198

199In the past, nearly all Urbit software was written by Tlon. While Tlon is still

200the only corporation actively updating Urbit’s MIT-licensed open source

201−software, namely [Vere](/docs/glossary/vere.md) (the runtime),

201+software, namely [Vere](/docs/glossary/vere) (the runtime),

202−[Arvo](/docs/glossary/arvo.md) (the kernel),

202+[Arvo](/docs/glossary/arvo) (the kernel),

203−[Landscape](/docs/glossary/landscape.md) (the client), and

203+[Landscape](/docs/glossary/landscape) (the client), and

204−[Bridge](/docs/glossary/bridge.md) (the ID manager), unaffiliated individuals have been making enormous contributions to Urbit over the past couple of years via the [grants program](https://grants.urbit.org/history). Recent examples include the [Bitcoin node and wallet integration](https://github.com/urbit/urbit/pull/4940), [WebRTC integration](https://grants.urbit.org/proposals/21131866-webrtc-gall-agent-and-external-app), [Port, an Urbit installer and ship manager](https://github.com/arthyn/port), and [`|fuse`, an important primitive for 3rd party software distribution](https://github.com/urbit/urbit/pull/4820).

204+[Bridge](/docs/glossary/bridge) (the ID manager), unaffiliated individuals have been making enormous contributions to Urbit over the past couple of years via the [grants program](https://grants.urbit.org/history). Recent examples include the [Bitcoin node and wallet integration](https://github.com/urbit/urbit/pull/4940), [WebRTC integration](https://grants.urbit.org/proposals/21131866-webrtc-gall-agent-and-external-app), [Port, an Urbit installer and ship manager](https://github.com/arthyn/port), and [`|fuse`, an important primitive for 3rd party software distribution](https://github.com/urbit/urbit/pull/4820).

205

206The only real power Tlon holds over Urbit is the ability to push [OTA

207−updates](/docs/glossary/ota-updates.md) via `~zod`, and suggest that people

207+updates](/docs/glossary/ota-updates) via `~zod`, and suggest that people

208download our binaries. To the best of our knowledge, all extant galaxies

209retrieve their OTA updates from `~zod`, who forward it to their stars, who

210forward it to their planets. This software distribution route is merely a

content/blog/first-steps-towards-urbit-org.md+1−1

@@ -56,4 +56,4 @@ I look forward to working with you.

56

57[^2]: We’re also really into the idea of being the first builder of housing on Mars. Just saying...

58

59−[^3]: We call this project Airlock. You’ll hear more about it soon.

59+[^3]: We call this project Airlock. You’ll hear more about it soon.

content/community/governance.md+1−1

@@ -16,7 +16,7 @@ An owner of a galaxy (or a delegate) can propose a new iteration of the contract

16

17In a similar process, document hashes can be proposed. While their off-chain documents can't be "technically enforced", this mechanism is useful for the Senate to record more abstract decisions.

18

19−For off-chain process around proposals, as suggested by core developers, please see [senate.md](https://github.com/urbit/azimuth/blob/master/senate.md).

19+For off-chain process around proposals, as suggested by core developers, please see [senate.md](https://github.com/urbit/azimuth/blob/master/senate).

20

21The group of core developers manages Urbit’s [GitHub repository](https://github.com/urbit/), which controls Arvo, Urbit’s operating system. Changes and upgrades are decided upon by consensus.

22

content/docs/arvo/ames/ames.md+6−6

@@ -11,7 +11,7 @@ over it. When Unix receives a packet over the correct UDP port, it pipes

11it straight into Ames for handling. Also, all packets sent over the

12Ames network are sent by the Ames vane. Apps and vanes may use

13Ames to directly send messages to other ships. In general, apps use

14−[Gall](/docs/userspace/gall/gall.md) and [Clay](/docs/arvo/clay/clay.md)

14+[Gall](/docs/userspace/gall/gall) and [Clay](/docs/arvo/clay/clay)

15to communicate with other ships rather than using Ames

16directly, but this isn't a requirement. Of course, Gall and Clay use

17Ames behind the scenes to communicate across the network. Jael is the only other

@@ -28,7 +28,7 @@ vane or app, is defined in Ames.

28This section summarizes the design of Ames. Beyond this section are deeper

29elaborations on the concepts presented here.

30

31−Ames extends [Arvo's](/docs/arvo/overview.md) `%pass`/`%give` `move` semantics across the network.

31+Ames extends [Arvo's](/docs/arvo/overview) `%pass`/`%give` `move` semantics across the network.

32

33Ames receives packets as Arvo events and emits packets as Arvo

34effects. The runtime is responsible for transferring the bytes in

@@ -159,9 +159,9 @@ order:

159

160 `SIV` is a "synthetic initialization vector" as defined in AES-256 SIV, the encryption

161 algorithm utilized to encrypt Ames packets (see the page on [Ames

162− cryptography](/docs/arvo/ames/cryptography.md)). It is formed from the

162+ cryptography](/docs/arvo/ames/cryptography)). It is formed from the

163 following noun: `~[sender=@p receiver=@p sender-life=@ receiver-life=@]` (see

164− [Life and Rift](/docs/azimuth/life-and-rift.md) for information on what `life`

164+ [Life and Rift](/docs/azimuth/life-and-rift) for information on what `life`

165 is). As this data is in Azimuth, it is not explicitly sent over the wire. Thus

166 the mod 16 sender and receiver life in the first 8 bits are only for quick

167 filtering of honest packets sent to or from a stale life.

@@ -256,7 +256,7 @@ This means all re-sends of an ack packet will be bitwise identical to each other

256Each datum in this noun is an atom with the aura `@ud` or an aura that nests

257under `@ud`.

258

259−Here, `our-life` refers to the [`life`](/docs/glossary/breach.md), or revision

259+Here, `our-life` refers to the [`life`](/docs/glossary/breach), or revision

260number, of the acking ship's networking keys, and `her-life` is the `life` of

261the ack-receiving ship's networking keys. `bone` is an opaque number identifying

262the flow. `message-num` denotes the number of the

@@ -428,7 +428,7 @@ message.

428

429Urbit's functionality is split between the two binaries `urbit-worker` (sometimes

430called the Serf) and `urbit-king` (sometimes called the King). This division of

431−labor is currently not well-documented outside of the [Vere documents](/docs/vere/_index.md), but we summarize it here.

431+labor is currently not well-documented outside of the [Vere documents](/docs/vere/_index), but we summarize it here.

432

433In short, the Serf is the Nock runtime and so keeps track of the current state

434of Arvo as a Nock noun and updates the state by `%poke`ing it with nouns, and

content/docs/arvo/ames/cryptography.md+1−1

@@ -35,7 +35,7 @@ is used for authentication

35

36The encrypted payload of each packet is a `$shut-packet`, which is the `+jam` of

37a cell with the `bone`, message number, and message fragment or ack (see

38−[Ames](/docs/arvo/ames/ames.md) for more information on packet structure). The

38+[Ames](/docs/arvo/ames/ames) for more information on packet structure). The

39message fragment is signed using the authentication key. It is encrypted using

40[`+en:crub:crypto`](/docs/arvo/reference/cryptography.md#en) found in

41`sys/zuse.hoon`, which utilizes the 256-bit AES-SIV algorithm.

content/docs/arvo/reference/_index.md+1−1

@@ -5,7 +5,7 @@ sort_by = "weight"

5template = "sections/docs/chapters.html"

6+++

7

8−[Cryptography](/docs/arvo/reference/cryptography.md)

8+[Cryptography](/docs/arvo/reference/cryptography)

9

10An overview of where Arvo uses cryptography, what algorithms are used, and how

11they are implemented.

content/docs/arvo/reference/cryptography.md+5−5

@@ -6,12 +6,12 @@ template = "doc.html"

6

7This is a summary of the cryptography functions found in `sys/zuse.hoon`, Arvo's

8standard library. This page currently only documents cryptographic functions

9−directly utilized by [Ames](/docs/arvo/ames/ames.md). `zuse` also contains

9+directly utilized by [Ames](/docs/arvo/ames/ames). `zuse` also contains

10cryptographic functions relevant to Ethereum such as the `+keccak:crypto` core,

11but they are currently undocumented.

12

13−Documentation for [Insecure Hashing](/docs/hoon/reference/stdlib/2e.md) and the

13+Documentation for [Insecure Hashing](/docs/hoon/reference/stdlib/2e) and the

14−[SHA Hash Family](/docs/hoon/reference/stdlib/3d.md) is found in the Hoon standard

14+[SHA Hash Family](/docs/hoon/reference/stdlib/3d) is found in the Hoon standard

15library reference.

16

17## Summary

@@ -198,9 +198,9 @@ Diffie-Hellman](https://en.wikipedia.org/wiki/Elliptic-curve_Diffie%E2%80%93Hell

198key agreements as well as [Elliptic Curve Digital Signature

199Algorithm](https://en.wikipedia.org/wiki/Elliptic_Curve_Digital_Signature_Algorithm).

200These functionalities are ultimately utilized by [`+crub:crypto`](#crub), the

201−only cryptosuite which [Ames](/docs/arvo/ames/ames.md) makes use of.

201+only cryptosuite which [Ames](/docs/arvo/ames/ames) makes use of.

202

203−Most gates in `+ed:crypto` are [jetted](/docs/vere/jetting.md), meaning that an

203+Most gates in `+ed:crypto` are [jetted](/docs/vere/jetting), meaning that an

204external reference library is utilized whenever these functions are called,

205rather than running in Nock natively. See the [Vere

206documentation](/docs/vere/cryptography.md#ed) for more information about the

content/docs/arvo/reference/filesystem.md+8−8

@@ -7,13 +7,13 @@ template = "doc.html"

7Here we describe what each of the primary folders present in the `%home` `desk`

8are used for. This organization is merely a convention, and the exact location

9of any file does not affect its operation. That being said, some [Ford

10−runes](/docs/arvo/ford/ford.md) are designed with this structure in mind, and

10+runes](/docs/arvo/ford/ford) are designed with this structure in mind, and

11applications such as dojo look in specific folders for code to run. Furthermore,

12this organization is not perfectly adhered to - sometimes you may find structure

13definitions in `/lib`, for example.

14

15- `/app` contains userspace applications, i.e. [Gall

16− agents](/docs/userspace/gall/gall.md).

16+ agents](/docs/userspace/gall/gall).

17- `/gen` contains generators. Many applications make use of generators, but

18 also each generator in this folder may be run from dojo using `+`. For

19 example, `/gen/foo/hoon` is run with `+foo`.

@@ -21,7 +21,7 @@ definitions in `/lib`, for example.

21 generators, etc. However, this is not the location of the standard libraries

22 (see `/sys`). Libraries are imported from `/lib` with `/+`.

23- `/mar` contains [mark](/docs/arvo/clay/architecture.md#marks) definitions.

24−- `/sur` contains shared [structure](/docs/hoon/reference/rune/_index.md) definitions.

24+- `/sur` contains shared [structure](/docs/hoon/reference/rune/_index) definitions.

25 Whenever you expect structures to be used by code across multiple files, it

26 is recommended to place their shared structures in `/sur`. Structures are

27 imported from `/sur` with `/-`.

@@ -30,7 +30,7 @@ definitions in `/lib`, for example.

30 the exception to the rule - structures and functions that are central to

31 Hoon, Arvo, and its vanes, are all located within this folder rather than in

32 `/lib` and `/sur`. See [below](#sys) for more information on `/sys`.

33−- `/ted` contains [threads](/docs/userspace/threads/overview.md). These may be

33+- `/ted` contains [threads](/docs/userspace/threads/overview). These may be

34 run from dojo using `-`. For example, `/ted/foo/hoon` is run with `-foo`.

35- `/tests` contains unit tests intended to be run using the `test` thread. To

36 run a particular test `+test-bar` in `/tests/foo.hoon` in dojo, enter `-test %/tests/foo/test-bar ~`. If a file is specified, every test in that file will

@@ -44,13 +44,13 @@ dependencies is `hoon.hoon` -> `arvo.hoon` -> `lull.hoon` -> `zuse.hoon`. We

44give a brief description of each of them.

45

46- `hoon.hoon` contains the Hoon compiler and the [Hoon standard

47− library](/docs/hoon/reference/stdlib/table-of-contents.md). The Hoon

47+ library](/docs/hoon/reference/stdlib/table-of-contents). The Hoon

48 compiler is self-hosted. This is the first file loaded by the Nock virtual

49− machine, [Vere](/docs/vere/runtime.md), in order for it to learn how to

49+ machine, [Vere](/docs/vere/runtime), in order for it to learn how to

50 interpret Hoon. The kelvin version number is the subject of `hoon.hoon`,

51 currently at 140. One may see this from dojo by inspecting the subject with

52 `.` and noting that `%140` is the final entry of the subject.

53−- `arvo.hoon` contains the [Arvo kernel](/docs/arvo/overview.md) and

53+- `arvo.hoon` contains the [Arvo kernel](/docs/arvo/overview) and

54 additional structures and functions directly relevant to the kernel. This is

55 Urbit's "traffic cop", and as such contains the structure definitions for

56 call stacks such as `duct`s and `bone`s. Once Vere understands Hoon, it loads

@@ -64,6 +64,6 @@ give a brief description of each of them.

64 in order to prepare to create the vanes. `arvo.hoon` is the subject of `lull.hoon`.

65- `zuse.hoon` is the Arvo standard library. It consists primarily of functions

66 shared by the kernel and vanes, such as the ones related to

67− [cryptography](/docs/arvo/reference/cryptography.md). `zuse.hoon` is loaded

67+ [cryptography](/docs/arvo/reference/cryptography). `zuse.hoon` is loaded

68 by the larval kernel following `lull.hoon`. `lull.hoon` is the subject of

69 `zuse.hoon`. Then `zuse` is the subject of the vanes.

content/docs/azimuth/azimuth.md+2−2

@@ -43,7 +43,7 @@ Think of your master ticket like a very high-value password. The master ticket i

43

44### Ownership Address

45

46−An ownership address has all rights over the assets deeded to it. These rights are on-chain actions described and implemented in [Ecliptic](/docs/glossary/ecliptic.md), Azimuth's suite of governing smart-contracts.

46+An ownership address has all rights over the assets deeded to it. These rights are on-chain actions described and implemented in [Ecliptic](/docs/glossary/ecliptic), Azimuth's suite of governing smart-contracts.

47

48### Proxies

49

@@ -56,7 +56,7 @@ Proxy addresses allow you to execute non-ownership related actions like spawning

56

57- **Voting Proxy**

58

59− Galaxies only. Galaxies are the part of the [Galactic Senate](/docs/glossary/senate.md), and this means

59+ Galaxies only. Galaxies are the part of the [Galactic Senate](/docs/glossary/senate), and this means

60 they can cast votes on new proposals including changes to Ecliptic.

61

62- **Spawn Proxy**

content/docs/development/develop.md+1−1

@@ -35,7 +35,7 @@ an [interface](https://github.com/urbit/urbit/tree/master/pkg/interface) built

35with [React](https://reactjs.org).

36

37Additionally, you can [contribute to

38−Landscape](https://github.com/urbit/urbit/blob/master/pkg/interface/CONTRIBUTING.md)

38+Landscape](https://github.com/urbit/urbit/blob/master/pkg/interface/CONTRIBUTING)

39by tackling issues in its [issue

40tracker](https://github.com/urbit/landscape/issues) and/or running the

41[development stream](https://groups.google.com/a/urbit.org/g/dev/c/r2hv4ajCLwk).

content/docs/hoon/hoon-school/doors.md+1−1

@@ -408,7 +408,7 @@ In the above example we created a door `c` with sample `b=@` and found that the

408 ++ greater |=(a=@ (gth a b))

409 --

410```

411−Here the type of `b` is inferred to be `@` based on the example value `7`, similar to how we've seen casting done by example. You will learn more about how types are inferred in [Lesson 2.2](@docs/hoon/hoon-school/type-checking-and-type-inference.md).

411+Here the type of `b` is inferred to be `@` based on the example value `7`, similar to how we've seen casting done by example. You will learn more about how types are inferred in [Lesson 2.2](@docs/hoon/hoon-school/type-checking-and-type-inference).

412

413### Doors in the Hoon Standard Library

414

content/docs/hoon/reference/irregular.md+1−1

@@ -294,7 +294,7 @@ See [%sand](/docs/hoon/reference/rune/constants#warm) for other irregular defini

294

295### Wings

296

297−[docs](content/docs/hoon/reference/limbs/wing.md)

297+[docs](content/docs/hoon/reference/limbs/wing)

298`[%wing p=(list limb)]`; a limb search path.

299`a.b` finds limb `a` within limb `b` ("var" `a` within "var" `b`).

300

content/docs/system-overview/cryptography.md+3−3

@@ -119,6 +119,6 @@ Jael and utilized by Ames for end-to-end encrypted communication.

119The following pages contained more detailed information about the cryptography

120utilized by each of the system components.

121

122−- [Ames](/docs/arvo/ames/cryptography.md)

122+- [Ames](/docs/arvo/ames/cryptography)

123−- [Zuse](/docs/arvo/reference/cryptography.md)

123+- [Zuse](/docs/arvo/reference/cryptography)

124−- [Vere](/docs/vere/cryptography.md)

124+- [Vere](/docs/vere/cryptography)

content/docs/userspace/threads/basics/summary.md+1−1

@@ -11,7 +11,7 @@ Now here's a quick recap of the main points covered:

11## Spider

12

13- is the gall agent that manages threads.

14−- Details of interacting with threads via spider can be seen [here](../reference.md).

14+- Details of interacting with threads via spider can be seen [here](../reference).

15

16## Threads

17- are like transient gall agents

content/docs/vere/_index.md+1−1

@@ -37,6 +37,6 @@ A walkthrough of each of the `u3` modules.

37

38A jetting guide by for new Urbit developers.

39

40−## [Cryptography](/docs/vere/cryptography.md)

40+## [Cryptography](/docs/vere/cryptography)

41

42References on the cryptography libraries utilized by jets.

content/docs/vere/cryptography.md+2−2

@@ -5,7 +5,7 @@ template = "doc.html"

5+++

6

7All cryptographic primitives utilized by Arvo are

8−[jetted](/docs/vere/jetting.md). This is done for performance-related reasons

8+[jetted](/docs/vere/jetting). This is done for performance-related reasons

9in other parts of the system, but for cryptography this is also extremely

10important because it allows us to utilize standard reference implementations for

11the primitives written in C.

@@ -15,7 +15,7 @@ All jets related to encryption may be found in `pkg/urbit/jets/e/`.

15In this section we review what specific implementations are utilized. At the

16moment, only libraries directly related to Ames are documented here, though we

17note that there are jets for other cryptographic functions such as the [SHA

18−Hash Family](/docs/hoon/reference/stdlib/3d.md) as well.

18+Hash Family](/docs/hoon/reference/stdlib/3d) as well.

19

20### Ed25519 {#ed}

21

content/faq.md+6−6

@@ -124,15 +124,15 @@ It’s also worth noting that, while there are almost 8B people on Earth, there

124

125### How secure is Urbit right now? {#how-secure-is-urbit}

126

127−We consider some parts of Urbit to be secure, while other parts still need some work and external auditing. For technical details on Urbit's cryptosystems, see the [documentation](/docs/system-overview/cryptography.md).

127+We consider some parts of Urbit to be secure, while other parts still need some work and external auditing. For technical details on Urbit's cryptosystems, see the [documentation](/docs/system-overview/cryptography).

128

129[Urbit ID](#what-is-urbit-id) / [Azimuth](#what-is-azimuth), Urbit's identity layer, is live on the Ethereum blockchain and has been audited by Open Zeppelin, Blockchain at Berkeley, and Bloctrax.

130

131−In late 2020, Urbit's [Ames](/docs/glossary/ames.md) networking protocol was audited by [Leviathan Security](https://www.leviathansecurity.com/). You can read about this milestone [here](/blog/security-and-continuity.md).

131+In late 2020, Urbit's [Ames](/docs/glossary/ames) networking protocol was audited by [Leviathan Security](https://www.leviathansecurity.com/). You can read about this milestone [here](/blog/security-and-continuity).

132

133−The security of the runtime, [Vere](/docs/vere/_index.md), has not yet been adequately assessed or systematically hardened.

133+The security of the runtime, [Vere](/docs/vere/_index), has not yet been adequately assessed or systematically hardened.

134

135−All communication on Urbit is end-to-end encrypted. However, the [event log](/docs/glossary/eventlog.md) is not encrypted at rest but we plan to give users that option in the future.

135+All communication on Urbit is end-to-end encrypted. However, the [event log](/docs/glossary/eventlog) is not encrypted at rest but we plan to give users that option in the future.

136

137Tlon keeps a quantum computing expert on staff and understands that post-quantum cryptographic methods must be implemented sooner than later, since any data not already encrypted using these methods is at risk of being collected and decrypted once sufficiently powerful quantum computers exist. [NIST](https://www.nist.gov/) anticipates the release of their preliminary findings on [post-quantum cryptography standards](https://csrc.nist.gov/projects/post-quantum-cryptography) around the end of 2021, with full guidelines following in 2024. Tlon will develop a strategy for post-quantum encryption for Urbit following their recommendations.

138

@@ -142,7 +142,7 @@ Thus, while Urbit is probably more secure and private than most digital communic

142

143The [Urbit Hierarchical Deterministic (HD) Wallet](/docs/glossary/hdwallet) is a custom Ethereum wallet based on BIP39 and BIP44 – the same underlying technology used by wallet providers like Ledger, Trezor, Metamask, and MyEtherWallet. You can think of the Urbit HD wallet as a wallet of wallets, which lets you keep a single passphrase for all of your Urbit ID keys. Urbit ID uses multiple keys with different capabilities – a bit like permissions – so that you can keep the more valuable keys in cold storage while keeping less valuable keys, used in day-to-day operation, more easily accessible. If you're only operating a planet, you shouldn't have to worry about this: you can simply think of your "master ticket" as the password to your Urbit ID. If you're operating a star or galaxy, the Urbit HD Wallet allows you to implement a multi-tier key custody scheme.

144

145−If you're interested, you can read the spec here: [Urbit HD Wallet Spec (UP 8)](https://github.com/urbit/proposals/blob/master/008-urbit-hd-wallet.md).

145+If you're interested, you can read the spec here: [Urbit HD Wallet Spec (UP 8)](https://github.com/urbit/proposals/blob/master/008-urbit-hd-wallet).

146

147### What is a master ticket? {#master-ticket}

148

@@ -167,7 +167,7 @@ An ownership address is an Ethereum address that owns one or more of your Urbit

167

168All Ethereum key-pairs in the Urbit wallet system, including [proxies](/docs/glossary/proxies), are produced by 128-bit cryptographically random values called seeds. These seeds are the equivalent of the BIP39 mnemonic of an Ethereum wallet and are yours alone. An ownership key pair is derived from an ownership seed and, likewise, the various proxy key pairs are generated from their respective proxy seeds.

169

170−For detailed information see the [Urbit HD Wallet Spec (UP 8)](https://github.com/urbit/proposals/blob/master/008-urbit-hd-wallet.md).

170+For detailed information see the [Urbit HD Wallet Spec (UP 8)](https://github.com/urbit/proposals/blob/master/008-urbit-hd-wallet).

171

172### What does it mean to “set public keys”? {#set-public-keys}

173

content/grants/bitcoin-key-derivation.md+1−1

@@ -52,7 +52,7 @@ The worker should have a background that demonstrates proficiency with building

52

53### Resources

54

55−- [Urbit HD Wallet design](https://github.com/urbit/fora-posts/blob/master/proposals/posts/~2018.11.8..19.31.59..ba77~.md)

55+- [Urbit HD Wallet design](https://github.com/urbit/fora-posts/blob/master/proposals/posts/~2018.11.8..19.31.59..ba77~)

56- [BIP-32 re: extended public keys](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki#Extended_keys)

57

58## Milestones

content/grants/bitcoin-wallet-on-bridge.md+1−1

@@ -39,7 +39,7 @@ A completed wallet should:

39- [Bitcoin Core SPV wallet reference](https://bitcoin.org/en/operating-modes-guide#simplified-payment-verification-spv)

40- [JS Library to interact with SPV wallet](https://github.com/bitcoinjs/bitcoinjs-lib)

41- [The Bridge repository](https://github.com/urbit/bridge)

42−- [Urbit Wallet Reference](https://github.com/urbit/fora-posts/blob/master/proposals/posts/~2018.11.8..19.31.59..ba77~.md)

42+- [Urbit Wallet Reference](https://github.com/urbit/fora-posts/blob/master/proposals/posts/~2018.11.8..19.31.59..ba77~)

43- [Urbit Wallet Key Generation](https://github.com/urbit/urbit-key-generation]

44- [BIP 32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki)

45- [BIP 39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki)

content/grants/the-complete-guide-to-gall-and-landscape.md+1−1

@@ -18,7 +18,7 @@ link = ""

18

19## PoC and Prior Work

20

21−The first 5 chapters of the course are complete in late draft form and can be found [here](https://github.com/timlucmiptev/gall-guide/blob/master/guide-docs/overview.md)

21+The first 5 chapters of the course are complete in late draft form and can be found [here](https://github.com/timlucmiptev/gall-guide/blob/master/guide-docs/overview)

22

23My ["Nock for Everyday Coders" Guide](https://blog.timlucmiptev.space/part1.html) was the result of my exploring Nock on my own, and is probably the most detailed Nock reference available currently.

24

content/grants/unit-tests-for-zuse-cryptographic-functions.md+1−1

@@ -32,7 +32,7 @@ Save the test files in the `tests/sys/zuse/crypto` directory in Arvo. Use the sa

32#### Resources

33

34- Read the [guide](https://github.com/urbit/urbit/blob/master/pkg/arvo/TESTING.udon) to writing unit tests in Hoon.

35−- Read the guide to [contributing](https://github.com/urbit/urbit/blob/master/CONTRIBUTING.md).

35+- Read the guide to [contributing](https://github.com/urbit/urbit/blob/master/CONTRIBUTING).

36- [Here](https://github.com/urbit/urbit/blob/alef2/pkg/arvo/tests/sys/zuse/ordered-map.hoon) is an example test file for the new Ames. Your tests should be similar to it.

37

38#### Contribution Guidelines

content/grants/volt-lightning-on-urbit.md+2−2

@@ -110,7 +110,7 @@ Private key/hot wallet management inside Urbit. This is needed to sign commitmen

110### RFCs implemented

111

112We implement everything related to channels, HTLCs, and invoices. We leave out all the Lightning networking and routing elements.

113−[RFCs located here](https://github.com/lightningnetwork/lightning-rfc/blob/master/00-introduction.md)

113+[RFCs located here](https://github.com/lightningnetwork/lightning-rfc/blob/master/00-introduction)

114

115- RFC 02: channel opening, closing, HTLCs

116- RFC 03: commitment transactions

@@ -231,7 +231,7 @@ It is possible to re-balance channel liquidity (shifting more of the balance to

231

232- The libraries and full node interface provided by the `btc-wallet` project will be useful for parsing formats like `bech32` and for querying the state of the blockchain to monitor for cheating.

233- [Urbit Bitcoin Wallet](https://github.com/timlucmiptev/btc-agents)

234−- [Lightning RFC](https://github.com/lightningnetwork/lightning-rfc/blob/master/00-introduction.md)

234+- [Lightning RFC](https://github.com/lightningnetwork/lightning-rfc/blob/master/00-introduction)

235- [lnd RPC API](https://api.lightning.community/)

236

237## contributor requirements