@@ -135,7 +135,7 @@ If either the sponsor or sponsee are on layer 2, then sponsorship actions must
135occur on layer 2. The only exception to this is detaching. A sponsor on layer 1
135occur on layer 2. The only exception to this is detaching. A sponsor on layer 1
136may perform a layer 1 detach action on a layer 2 sponsee, and this will result
136may perform a layer 1 detach action on a layer 2 sponsee, and this will result
137in the sponsee having no sponsor on layer 1, and layer 2 as well if they were
137in the sponsee having no sponsor on layer 1, and layer 2 as well if they were
138−the sponsor on layer 2. This is necessary for logical reasons, but it also
138+the sponsor on layer 2. This is necessary to simplify the logic, but it also
139guarantees that there is no hard requirement to ever utilize layer 2. Without
139guarantees that there is no hard requirement to ever utilize layer 2. Without
140this exception, sponsors with sponsees that move to layer 2 would be forced to
140this exception, sponsors with sponsees that move to layer 2 would be forced to
141detach them as a layer 2 action if they wanted to cease sponsorship.
141detach them as a layer 2 action if they wanted to cease sponsorship.
@@ -254,10 +254,6 @@ L2-detach A1 | * | * | * | A2 | -> | * | * | * | A2
254L2-detach A1 | * | * | * | ~ | -> | * | * | * | ~
254L2-detach A1 | * | * | * | ~ | -> | * | * | * | ~
257−## Processing L1 transactions
259−## Processing L2 batches
261## Aggregators
257## Aggregators
263An "aggregator" or "roller" is any Urbit node that collects signed layer 2
259An "aggregator" or "roller" is any Urbit node that collects signed layer 2