git.iko.soy/urbit.org
on master help sign in
Apply suggestions from code review

Co-authored-by: tinnus-napbus <77721746+tinnus-napbus@users.noreply.github.com>

commitd58b4428a238a2f53d43e60495b4c6735140320c authorpoprox <51337059+drbeefsupreme@users.noreply.github.com> dateWed 3 Nov 2021, 12:38 (5 years ago) parent583e22c
5 files changed+8−8
compare with master
unifiedsplit
content/docs/azimuth/azimuth-eth.md+3−3 content/docs/azimuth/flow.md+2−2 content/docs/azimuth/l2/layer2-api.md+1−1 content/docs/azimuth/l2/roller.md+1−1 content/docs/glossary/rollups.md+1−1
content/docs/azimuth/azimuth-eth.md+3−3
@@ -16,7 +16,7 @@ only eligible to modify the Ecliptic.
1616
1717The global state of Azimuth is given as follows.
1818
19−```
19+```solidity
2020 // points: per point, general network-relevant point state
2121 //
2222 mapping(uint32 => Point) public points;
@@ -47,7 +47,7 @@ between `0` and `2^32-1`, or `uint32`. There are two data structures associated
4747A `Point` contains data about networking keys
4848and sponsorship status, arranged in the following `struct`:
4949
50−```
50+```solidity
5151 struct Point
5252 {
5353 // encryptionKey: (curve25519) encryption public key, or 0 for none
@@ -106,7 +106,7 @@ and sponsorship status, arranged in the following `struct`:
106106The owner of an Urbit ID may also set several [proxies](/docs/using/id/proxies)
107107by modifying their `Deed`:
108108
109−```
109+```solidity
110110struct Deed
111111 {
112112 // owner: address that owns this point
content/docs/azimuth/flow.md+2−2
@@ -10,7 +10,7 @@ how Urbit implements the data flow of naive rollups.
1010
1111The following diagram illustrates the high-level structure of Azimuth.
1212
13−![High level overview](https://media.urbit.org/docs/layer2/l2-high.png)
13+[![High level overview](https://media.urbit.org/docs/layer2/l2-high.png)](https://media.urbit.org/docs/layer2/l2-high.png)
1414
1515## Bridge
1616
@@ -108,7 +108,7 @@ Ethereum address, and when the next batch of transactions will be sent. See also
108108The relationship between the roller and other agents is outlined in the
109109following diagram.
110110
111−![Roller](https://media.urbit.org/docs/layer2/roller-agents.png)
111+[![Roller](https://media.urbit.org/docs/layer2/roller-agents.png)](https://media.urbit.org/docs/layer2/roller-agents.png)
112112
113113`%roller` has a number of scries available, intended primarily to
114114display data to the end user in Bridge. They can be inferred from the `+on-peek`
content/docs/azimuth/l2/layer2-api.md+1−1
@@ -10,5 +10,5 @@ documented how to perform these API calls yourself if you are so inclined. These
1010
1111The set of API calls available is summarized in the following diagram.
1212
13−![JSON RPC-API](https://media.urbit.org/docs/layer2/l2-json-rpc.svg)
13+[![JSON RPC-API](https://media.urbit.org/docs/layer2/l2-json-rpc.svg)](https://media.urbit.org/docs/layer2/l2-json-rpc.svg)
1414
content/docs/azimuth/l2/roller.md+1−1
@@ -14,7 +14,7 @@ summary [here](/docs/azimuth/l2/layer2-api).
1414The following diagram illustrates the most important parts of the plumbing
1515present in the roller.
1616
17−![Roller internals](https://media.urbit.org/docs/layer2/roller-internal.png)
17+[![Roller internals](https://media.urbit.org/docs/layer2/roller-internal.png)](https://media.urbit.org/docs/layer2/roller-internal.png)
1818
1919We elaborate on the components of this diagram below.
2020
content/docs/glossary/rollups.md+1−1
@@ -5,7 +5,7 @@ template = "doc.html"
55category = "azimuth"
66+++
77
8−**Naive rollups**, also referred to as **layer 2**, is an upgrade to the
8+**Naive rollups**, also referred to as **layer 2**, is an upgrade to
99[Azimuth](/docs/glossary/azimuth) implemented in 2021 that reduces Ethereum gas
1010costs associated with Urbit ID transactions and friction associated with using
1111cryptocurrency in general.