@@ -5,31 +5,31 @@ template = "doc.html"
55+++
66
77[Ecliptic.eth](https://etherscan.io/address/ecliptic.eth) holds the business
8−logic for the ledger kept by Azimuth.eth. It may be modified by [galaxy
8+logic for the ledger kept by `Azimuth.eth`. It may be modified by [galaxy
99vote](/docs/glossary/upgrade). This determines things such as what the various
1010proxies are capable of, how keys are changed, or verifying that a request is
1111valid.
1212
13−Ecliptic uses external contracts such as
13+`Ecliptic.eth` uses external contracts such as
1414[Azimuth.eth](/docs/azimuth/azimuth-eth) and
1515[Polls](https://github.com/urbit/azimuth/blob/master/contracts/Polls.sol) for
1616data storage so that it can easily be replaced in case the logic needs to be
17−changed without affecting the data. These data contracts are owned by the
18−Ecliptic contract, and this ownership is passed to the new Ecliptic contract
17+changed without affecting the data. These data contracts are owned by
18+`Ecliptic.eth`, and this ownership is passed to the new Ecliptic contract
1919whenever it is replaced. Thus it is advised for clients to not store Ecliptic's
20−contract address directly, but instead ask the Azimuth.eth contract for its
20+contract address directly, but instead ask the `Azimuth.eth` contract for its
2121`owner` attribute to ensure that transactions are sent to the latest Ecliptic
22−contract. Alternatively, the ENS name `ecliptic.eth` will always resolve to the
23−latest Ecliptic.
22+contract. Alternatively, the [ENS](https://ens.domains/) name `Ecliptic.eth`
23+will always resolve to the latest Ecliptic.
2424
2525You can read about [Urbit's first
2626upgrade](https://github.com/urbit/azimuth/pull/35) to Ecliptic, which occurred
2727in the summer of 2021, [here](https://urbit.org/blog/first-contract). The
2828[second](https://github.com/urbit/azimuth/pull/43) occurred later in the year
2929and consisted of several small modifications to ready the PKI for the
30−introduction of naive rollups.
30+introduction of [naive rollups](/docs/azimuth/l2/layer2).
3131
32−Ecliptic implements the [ERC-721](https://eips.ethereum.org/EIPS/eip-721)
32+`Ecliptic.eth` implements the [ERC-721](https://eips.ethereum.org/EIPS/eip-721)
3333interface for non-fungible tokens, as well as the
3434[ERC-165](https://eips.ethereum.org/EIPS/eip-165) standard for interface
3535detection.
@@ -42,12 +42,12 @@ applicable.
4242
4343## Write functions {#write}
4444
45−Here we briefly describe each function in the Ecliptic which allows one to write
45+Here we briefly describe each function in `Ecliptic.eth` which allows one to write
4646data to Ethereum. These can be called using
4747[Etherscan](https://etherscan.io/address/ecliptic.eth#writeContract), but
4848the most common functions may be called from within Bridge.
4949
50−We only document here the write functions specific to Ecliptic and not the
50+We only document here the write functions specific to `Ecliptic.eth` and not the
5151standard functions that are part of the ERC-721 or ERC-165 interfaces.
5252
5353### `Point`s interface
@@ -66,9 +66,11 @@ to its [proxies](#proxies). All of these actions may be performed from Bridge.
6666 bool _discontinuous)
6767```
6868
69−Configure `_point` with network public keys `_encryptionKey`, `_authenticationKey`,
70−and corresponding `_cryptoSuiteVersion`, incrementing the `Point`'s continuity
71−number if needed.
69+Configure `_point` with network public keys `_encryptionKey`,
70+`_authenticationKey`, and corresponding `_cryptoSuiteVersion`, incrementing the
71+`Point`'s [`keyRevisionNumber`](/docs/azimuth/azimuth-eth#points) if the keys
72+have changed and `continuityNumber` number if `_discontinuous` is set to true
73+(see [Life and Rift](/docs/azimuth/life-and-rift)).
7274
7375Corresponds to the layer 2 `%configure-keys` action.
7476
@@ -97,15 +99,17 @@ Corresponds to the layer 2 `%spawn` action.
9799 function transferPoint(uint32 _point, address _target, bool _reset)
98100```
99101
100−Transfer `_point` to `_target`, clearing all permissions
101−data and keys if `_reset` is true
102−
103−Note: the `_reset` flag is useful when transferring the point to
104−a recipient who doesn't trust the previous owner.
102+Transfer `_point` to `_target`, clearing all permissions data and keys if
103+`_reset` is true. `_reset` set to makes this transaction a
104+[breach](/using/id/guide-to-breaches), and thus this action increments the
105+[`continuityNumber`](/docs/azimuth/azimuth-eth#points) of `_point`, and usually
106+the `keyRevisionNumber` as well (see [Life and
107+Rift](/docs/azimuth/life-and-rift)).
105108
106109Requirements:
107110 - `:msg.sender` must be either `_point`'s current owner, authorized to transfer
108− `_point`, or authorized to transfer the current owner's points (as in ERC721's operator)
111+ `_point`, or authorized to transfer the current owner's points (i.e. is
112+ listed as an ERC-721 operator in [`operators`](/docs/azimuth/azimuth-eth#other)).
109113 - `_target` must not be the zero address.
110114
111115Corresponds to the layer 2 `%transfer-point` action.
@@ -179,8 +183,10 @@ Requirements:
179183Corresponds to the layer 2 `%detach` action.
180184
181185Unlike all other layer 1 actions, layer 1 sponsors may use a layer 1 `detach` on
182−a layer 2 sponsee. See the [Layer 2](/docs/azimuth/l2/layer2#sponsorship) section
183−for more detail.
186+a layer 2 sponsee. See the [Layer 2](/docs/azimuth/l2/layer2#sponsorship)
187+section for more detail. The detach action available in Bridge is a layer 2
188+action, so a layer 1 detach must be done
189+[manually](https://etherscan.io/address/ecliptic.eth#writeContract).
184190
185191### Proxy management {#proxies}
186192
@@ -337,6 +343,9 @@ performed manually. It is not available in Bridge.
337343Check whether the `_proposal` has achieved majority. Any Ethereum address may
338344call this function.
339345
346+This action eiher occurs as part of a vote that achieves a majority, or must be
347+performed manually. It is not available in Bridge.
348+
340349### Contract owner operations
341350
342351The following functions may only be performed by the owner of the contract.
@@ -363,9 +372,6 @@ this function has no valid arguments.
363372Sets 3 DNS domains by which galaxy IP addresses may be looked up as part of the
364373bootstrap process to get on the network. Currently, all three domains are `urbit.org`.
365374
366−In the future, this function should probably be parameterized as a per-galaxy
367−setting, so that each galaxy may set its own domain.
368−
369375## Read functions {#read}
370376
371377Here we briefly describe each function in the Ecliptic which allows one to read
@@ -424,7 +430,7 @@ Release](https://etherscan.io/address/0x86cd9cd0992f04231751e3761de45cecea5d1801
424430and [Conditional Star
425431Release](https://etherscan.io/address/0x8c241098c3d3498fe1261421633fd57986d74aea).
426432
427−Beginning in 2019, stars may spawn at most 1024 planets. This limit doubles for
428−every subsequent year. However, this limit is not currently implemented on
429−[Layer 2](/docs/azimuth/l2/layer2).
433+Beginning in 2019, stars may spawn at most 1024 planets. This limit doubles
434+every subsequent year until the maximum is reached. However, this limit is not
435+currently implemented on [Layer 2](/docs/azimuth/l2/layer2).
430436