Merge branch 'andytudhope-main' into main

docs/index.mdx

@@ -15,9 +15,9 @@ import GridBlock from "@site/src/components/GridBlock/GridBlock.tsx";
 
 If MEV remains centralized, we cannot realise the promises that crypto offers.
 
-SUAVE unifies coordination in a decentralized way. SUAVE does not compete with other blockchains: it is intended to aggregate bundles of transactions and coordinate the building of blocks that ultimately change the state of other chains.
+SUAVE unifies how we coordinate without forcing any one mechanism onto everyone. SUAVE does not compete with other blockchains: it is intended to aggregate and coordinate all the things that ultimately change the state of other chains.
 
-SUAVE is a permissionless and open marketplace for mechanisms. SUAVE enables anyone to innovate on auctions and other mechanisms for managing orderflow or filling blockspace, which enables us to (among other things) _decentralize block building_ for all blockchains. Such "MEV applications" can provide a sustainable [defender's advantage](https://vitalik.ca/general/2016/12/29/pos_design.html) against centralizing economic forces both within and beyond crypto. 
+SUAVE is a permissionless and open marketplace for many different mechanisms. SUAVE enables anyone to innovate, design, and deploy new mechanisms, which enables us to (among other things) _decentralize block building_ for all blockchains. Such "MEV applications" can provide a sustainable [defender's advantage](https://vitalik.ca/general/2016/12/29/pos_design.html) against centralizing economic forces both within and beyond crypto.  
 
 Reducing the economic centralization pressure on other networks enables:
 

docs/reference/builder-solidity/index.mdx

@@ -14,7 +14,7 @@ import AlignItems from "@site/src/components/AlignItems/AlignItems.tsx";
 
 Builder solidity is solidity with some additional precompiles intended to support MEV applications. Using these precompiles, builder solidity contracts can define how SUAVE nodes run computation, without that computation being done on chain. That is, SUAVE nodes can accept encrypted data from users, do stuff with it privately and only reveal the results, not the inputs.
 
-## Why is this cool?
+## Verifiable logic, private data
 
 Builders have no incentive to share the algorithms by which they currently build blocks, so it is hard for searchers to know whether their bundles will be built in the order they submit them, or manipulated. This means that searchers are more likely to send their bundles to the few builders they trust, or only those who consistently build winning blocks (in order to avoid leaking alpha to everyone). This results in block builder centralization over time.
 

docs/reference/builder-solidity/worked-examples/mev-share.mdx

@@ -20,7 +20,6 @@ What do I need to do, and what happens next? We'll describe the steps first in n
 
 1. I take my signed ETH L1 Uniswap tx, and encrypt it using the public key of a specific SUAVE node.
     1. I decide whether I want all my transaction information in there, or just - for instance - the address of the pool contract I am trading on, but not the direction of the trade. 
-        1. We call this Ethereum L1 transaction a "hint", because it need not reveal _everything_ an ordinary L1 transaction would.
     3. I wrap my L1 transaction in another transaction to the MEVShare.sol on SUAVE.
 2. I send the transaction in (1.ii) to the SUAVE node I encrypted it for.
 3. The SUAVE node sees this transaction, sees that it contains additional data (the encrypted L1 transaction), and passes it to the MEVM running in that node to process confidentially.

docs/reference/index.mdx

@@ -29,7 +29,15 @@ The high level plan is:
 3. **Decentralized execution**
     - geographically and administratively, using threshold MPC, FHE etc as they become viable
 
-Technically, we will achieve this with the "MEVM": our adaption of the EVM with a new runtime and APIs. These APIs enable you to leverage new precompiles in what we call "builder solidity", which is solidity as you know and love it, but extended so that you can create MEV applications. 
+There are many reasons why we think the market will evolve toward many chains sharing a unified sequencing layer which is specifically intended to keep power meaningfully decentralized in each specific chain:
+
+1. Block builders who only operate on a single domain will find themselves increasingly disadvantaged due to cross-domain MEV.
+2. There are efficiency gains for users from aggregating and clearing their preferences inside the same auction.
+3. The credible neutrality of an open marketplace in which many parties share their views, strategies, and opinions gives SUAVE an information advantage on centralized builders.
+4. Enabling computation on sensitive data (user orderflow) in a permissionless setting is hard. By solving it once, we can amortize the cost across the ecosystem and provide better solutions more cheaply than any individual participant could.
+5. Because of how fundamental transaction sequencing is in blockchains, only another decentralized system can provide the necessary security and credible neutrality.
+
+Building unified infrastructure for expressing diverse values is the best way to give domains control over their own validation guarantees and to ensure smaller domains stay decentralized in the face of centralizing economic forces outside their control.
 
 ## *Refers to notes
 

docs/sidebars.js

@@ -58,7 +58,7 @@ module.exports = {
       link: {type: 'doc', id: 'understand/index'},
       items: [
         'understand/meaning',
-        'understand/fairness',
+        'understand/welfare',
         'understand/power'
       ],
     },