git.iko.soy/urbit.org
on master help sign in
move flow
eec7df7drbeefsupreme
content/docs/azimuth/_index.md+5
compare with master
unifiedsplit
@@ -11,6 +11,11 @@ insert_anchor_links = "right"
11
11
12An overview of the Ethereum-based public key infrastructure utilized by Urbit.
12An overview of the Ethereum-based public key infrastructure utilized by Urbit.
13
13
14+### [Data Flow](/docs/azimuth/flow)
15+
16+Diagrams and explanations of how data flows between Bridge and the various
17+components inside Urbit involved with layer 2.
18+
14### [Urbit HD Wallet](/docs/azimuth/hdwallet)
19### [Urbit HD Wallet](/docs/azimuth/hdwallet)
15
20
16Azimuth has its own optional hierarchical deterministic wallet system, sometimes
21Azimuth has its own optional hierarchical deterministic wallet system, sometimes
content/docs/azimuth/azimuth-eth.md+1−1
@@ -149,7 +149,7 @@ able to set its own domain name and so we do not expect this to remain the case
149forever.
149forever.
150
150
151All data in this ledger is stored and processed locally on your ship by the
151All data in this ledger is stored and processed locally on your ship by the
152−[`%azimuth` Gall agent](/docs/azimuth/l2/l2-flow#azimuth), including [layer
152+[`%azimuth` Gall agent](/docs/azimuth/flow#azimuth), including [layer
1532](/docs/azimuth/l2/layer2) data. Because state transitions resulting from layer 2
1532](/docs/azimuth/l2/layer2) data. Because state transitions resulting from layer 2
154transactions are not included in this ledger, in general the local store will
154transactions are not included in this ledger, in general the local store will
155differ from what is kept in Azimuth.eth.
155differ from what is kept in Azimuth.eth.
content/docs/azimuth/azimuth.md+6−1
@@ -30,7 +30,7 @@ with a system of scarce and immutable identities.
30**Azimuth** is the public-key infrastructure built to be a system of scarce and
30**Azimuth** is the public-key infrastructure built to be a system of scarce and
31immutable identities. It consists of a suite of [smart contracts on the Ethereum
31immutable identities. It consists of a suite of [smart contracts on the Ethereum
32blockchain](https://github.com/urbit/azimuth) as well as [several
32blockchain](https://github.com/urbit/azimuth) as well as [several
33−apps](/docs/azimuth/l2/l2-flow) run locally on your urbit. Togeter, they determine
33+apps](/docs/azimuth/flow) run locally on your urbit. Togeter, they determine
34which Ethereum addresses own which Urbit ID's as well as the public keys needed
34which Ethereum addresses own which Urbit ID's as well as the public keys needed
35to communicate with those ID's. All identity-related operations, such as
35to communicate with those ID's. All identity-related operations, such as
36transfers, are governed by Azimuth. Azimuth isn't built strictly for Arvo -- the
36transfers, are governed by Azimuth. Azimuth isn't built strictly for Arvo -- the
@@ -117,6 +117,11 @@ Azimuth.
117A description of the `ecliptic.eth` smart contract, which is the business logic
117A description of the `ecliptic.eth` smart contract, which is the business logic
118for `azimuth.eth`. This includes an overview of all function calls available.
118for `azimuth.eth`. This includes an overview of all function calls available.
119
119
120+### [Data Flow](/docs/azimuth/flow)
121+
122+Diagrams and explanations of how data flows between Bridge and the various
123+components inside Urbit involved with layer 2.
124+
120### [Urbit HD Wallet](/docs/azimuth/hd-wallet)
125### [Urbit HD Wallet](/docs/azimuth/hd-wallet)
121
126
122Azimuth has its own optional hierarchical deterministic wallet system, often
127Azimuth has its own optional hierarchical deterministic wallet system, often
content/docs/azimuth/l2/l2-flow.md → content/docs/azimuth/flow.mdrenamed+7−4
@@ -14,7 +14,7 @@ The following diagram illustrates the high-level structure of Azimuth.
14
14
15## Bridge
15## Bridge
16
16
17−The primary way in which users interact with Layer 2 is via Bridge. Bridge is
17+The primary way in which users interact with Azimuth is via Bridge. Bridge is
18responsible for collecting transactions from users, signing them, and forwarding
18responsible for collecting transactions from users, signing them, and forwarding
19them to a roller via an HTTP API.
19them to a roller via an HTTP API.
20
20
@@ -102,7 +102,8 @@ collecting and submitting batches of layer 2 transactions to the Ethereum
102blockchain. Among other things, it keeps
102blockchain. Among other things, it keeps
103track of a list of pending transactions to be sent, transactions it has sent
103track of a list of pending transactions to be sent, transactions it has sent
104that are awaiting confirmation, history of transactions sent organized by
104that are awaiting confirmation, history of transactions sent organized by
105−Ethereum address, and when the next batch of transactions will be sent.
105+Ethereum address, and when the next batch of transactions will be sent. See also
106+[Rollers](/docs/azimuth/l2/roller) for more information on the roller.
106
107
107The relationship between the roller and other agents is outlined in the
108The relationship between the roller and other agents is outlined in the
108following diagram.
109following diagram.
@@ -170,7 +171,9 @@ tuple, according to the format for signed transactions outlined in the
170`chain-id` is the ID used by the Ethereum blockchain, which is `1337`. See [bytestring
171`chain-id` is the ID used by the Ethereum blockchain, which is `1337`. See [bytestring
171format](/docs/azimuth/l2/bytestring) for more information.
172format](/docs/azimuth/l2/bytestring) for more information.
172
173
173−`state` is the current state of the PKI:
174+`state` is the current state of the PKI. This is structured similarly to the
175+state held in [Azimuth.eth](/docs/azimuth/azimuth-eth), but will differ in
176+general since `state` takes into account layer 2 transactions as well.
174
177
175```hoon
178```hoon
176+$ state
179+$ state
@@ -207,7 +210,7 @@ format](/docs/azimuth/l2/bytestring) for more information.
207+$ operators (jug address address)
210+$ operators (jug address address)
208```
211```
209`points` should be self-explanatory if you are already familiar with the
212`points` should be self-explanatory if you are already familiar with the
210−structure of Urbit ID. The only new addition is `dominion`, which is a record of
213+structure of [Azimuth.eth](/docs/azimuth/azimuth-eth). The only new addition is `dominion`, which is a record of
211whether a ship is on layer 1, layer 2, or layer 1 with a layer 2 spawn proxy.
214whether a ship is on layer 1, layer 2, or layer 1 with a layer 2 spawn proxy.
212See [Layer 2 actions](/docs/azimuth/l2/l2-actions) for an overview of how
215See [Layer 2 actions](/docs/azimuth/l2/l2-actions) for an overview of how
213`dominion` determines the actions available to a ship.
216`dominion` determines the actions available to a ship.
content/docs/azimuth/l2/_index.md+1−1
@@ -20,7 +20,7 @@ A high-level technical description of the functionality of the naive rollups
20An exhaustive list of what Azimuth actions can be performed for any given tuple
20An exhaustive list of what Azimuth actions can be performed for any given tuple
21`(ship rank, layer 2 status)`.
21`(ship rank, layer 2 status)`.
22
22
23−### [Data Flow](/docs/azimuth/l2/l2-flow)
23+### [Data Flow](/docs/azimuth/flow)
24
24
25Diagrams and explanations of how data flows between Bridge and the various
25Diagrams and explanations of how data flows between Bridge and the various
26components inside Urbit involved with layer 2.
26components inside Urbit involved with layer 2.
content/docs/azimuth/l2/layer2.md+2−2
@@ -18,7 +18,7 @@ to either transfer their ship to layer 2 or perform layer 2 actions. For that,
18see ((bridge documentation yet to be written)). For a casual overview of the
18see ((bridge documentation yet to be written)). For a casual overview of the
19rationale and functionality of layer 2, please see this [blog
19rationale and functionality of layer 2, please see this [blog
20post](/blog/rollups). For more information on how Azimuth works more generally,
20post](/blog/rollups). For more information on how Azimuth works more generally,
21−including interactions with Bridge and Ethereum, see the page on [Azimuth data flow](/docs/azimuth/l2/l2-flow).
21+including interactions with Bridge and Ethereum, see the page on [Azimuth data flow](/docs/azimuth/flow).
22
22
23This page is also not where to find instruction on how to run your own "aggregator"/"roller".
23This page is also not where to find instruction on how to run your own "aggregator"/"roller".
24Documentation for this process is forthcoming. However, this page does contain
24Documentation for this process is forthcoming. However, this page does contain
@@ -207,7 +207,7 @@ sponsor of `~sampel-palnet` was `~marzod` before `~sampel-palnet` was deposited
207to layer 2, and thus the Azimuth PKI on Ethereum will forever reflect this.
207to layer 2, and thus the Azimuth PKI on Ethereum will forever reflect this.
208
208
209For more information on how Azimuth state is handled, including how this
209For more information on how Azimuth state is handled, including how this
210−integrates with Bridge and Ethereum, see [Azimuth data flow](/docs/azimuth/l2/l2-flow).
210+integrates with Bridge and Ethereum, see [Azimuth data flow](/docs/azimuth/flow).
211
211
212### Sponsorship state transitions
212### Sponsorship state transitions
213
213