git.iko.soy/urbit.org
on master help sign in
move flow
commiteec7df749e8bdc9841dc7b368da78d5f5aa85f25 authordrbeefsupreme <drbeefsupreme@discordja.net> dateThu 7 Oct 2021, 14:02 (5 years ago) parent97e713d
6 files changed+22−9
compare with master
unifiedsplit
content/docs/azimuth/_index.md+5 content/docs/azimuth/azimuth-eth.md+1−1 content/docs/azimuth/azimuth.md+6−1 content/docs/azimuth/l2/l2-flow.md → content/docs/azimuth/flow.md+7−4 content/docs/azimuth/l2/_index.md+1−1 content/docs/azimuth/l2/layer2.md+2−2
content/docs/azimuth/_index.md+5
@@ -11,6 +11,11 @@ insert_anchor_links = "right"
1111
1212An overview of the Ethereum-based public key infrastructure utilized by Urbit.
1313
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+
1419### [Urbit HD Wallet](/docs/azimuth/hdwallet)
1520
1621Azimuth 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
149149forever.
150150
151151All 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
1531532](/docs/azimuth/l2/layer2) data. Because state transitions resulting from layer 2
154154transactions are not included in this ledger, in general the local store will
155155differ 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.
3030**Azimuth** is the public-key infrastructure built to be a system of scarce and
3131immutable identities. It consists of a suite of [smart contracts on the Ethereum
3232blockchain](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
3434which Ethereum addresses own which Urbit ID's as well as the public keys needed
3535to communicate with those ID's. All identity-related operations, such as
3636transfers, are governed by Azimuth. Azimuth isn't built strictly for Arvo -- the
@@ -117,6 +117,11 @@ Azimuth.
117117A description of the `ecliptic.eth` smart contract, which is the business logic
118118for `azimuth.eth`. This includes an overview of all function calls available.
119119
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+
120125### [Urbit HD Wallet](/docs/azimuth/hd-wallet)
121126
122127Azimuth 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.
1414
1515## Bridge
1616
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
1818responsible for collecting transactions from users, signing them, and forwarding
1919them to a roller via an HTTP API.
2020
@@ -102,7 +102,8 @@ collecting and submitting batches of layer 2 transactions to the Ethereum
102102blockchain. Among other things, it keeps
103103track of a list of pending transactions to be sent, transactions it has sent
104104that 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.
106107
107108The relationship between the roller and other agents is outlined in the
108109following diagram.
@@ -170,7 +171,9 @@ tuple, according to the format for signed transactions outlined in the
170171`chain-id` is the ID used by the Ethereum blockchain, which is `1337`. See [bytestring
171172format](/docs/azimuth/l2/bytestring) for more information.
172173
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.
174177
175178```hoon
176179+$ state
@@ -207,7 +210,7 @@ format](/docs/azimuth/l2/bytestring) for more information.
207210+$ operators (jug address address)
208211```
209212`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
211214whether a ship is on layer 1, layer 2, or layer 1 with a layer 2 spawn proxy.
212215See [Layer 2 actions](/docs/azimuth/l2/l2-actions) for an overview of how
213216`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
2020An exhaustive list of what Azimuth actions can be performed for any given tuple
2121`(ship rank, layer 2 status)`.
2222
23−### [Data Flow](/docs/azimuth/l2/l2-flow)
23+### [Data Flow](/docs/azimuth/flow)
2424
2525Diagrams and explanations of how data flows between Bridge and the various
2626components 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,
1818see ((bridge documentation yet to be written)). For a casual overview of the
1919rationale and functionality of layer 2, please see this [blog
2020post](/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).
2222
2323This page is also not where to find instruction on how to run your own "aggregator"/"roller".
2424Documentation 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
207207to layer 2, and thus the Azimuth PKI on Ethereum will forever reflect this.
208208
209209For 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).
211211
212212### Sponsorship state transitions
213213