Ecosyste.ms: Awesome

An open API service indexing awesome lists of open source software.

Awesome Lists | Featured Topics | Projects

https://github.com/alt-research/mach-avs


https://github.com/alt-research/mach-avs

machj

Last synced: 3 months ago
JSON representation

Awesome Lists containing this project

README 

        
# Mach AVS (M2)



AltLayer Mach AVS is a fast finality layer for Ethereum rollups. In Mach AVS , operators will run verifier nodes for rollups, monitor the rollup for fraudulent behavior, and submit a fraudulent alert to Mach AVS. Fraudulent alert can then be confirmed via sufficient quorum or ZK proofs.



## Use cases



1. Fast finality services for Web3 application

2. Circuit breaker for RPC nodes



## Deployments



- [Mach AVS contracts](docs/Deployments.md)



## Audits



- [PeckShield-Audit-Report-AltLayer-MACH-AVS-v1.0.pdf](audits/PeckShield-Audit-Report-AltLayer-MACH-AVS-v1.0.pdf)

- [AltLayer-Mach-AVS-M2-Final-by-n-var.pdf](audits/AltLayer-Mach-AVS-M2-Final-by-n-var.pdf)



## Components



Mach AVS consists of the following component:



- Mach AVS service manager contract

- Mach AVS aggregator (for signature aggregation version)

- Mach AVS operator

- Mach verifier



## Architecture



![Overview]()



### BLS Signature Aggregation Mode



![BLS Mode]()



```mermaid

sequenceDiagram

    participant MC as Mach Contract



    participant MA as Mach Aggregator

    participant MO as Mach Operator



    participant MV as Mach Verifier



    participant L2 as Layer2



    MV ->> L2: Fetch Layer2 Status

    MV ->> MV: Verify Layer2 Blocks by executor



    alt the block is valid

    MV ->> L2: Fetch next blocks

    else the block is invalid

    MV ->> MO: Commit alert to operator

    MV ->> MC: Commit a Earlier Alert

    MO ->> MO: Sig the alert

    MO ->> MA: Commit alert bls sig

    MA ->> MC: If collected, commit Avs confirmed Alert

    MV ->> MV: generate zk-snark-proof

    MV ->> MC: commit Zk proved Alert

    end

```



### ZK Proof Mode



![ZK Proof Mode]()



```mermaid

sequenceDiagram

    actor US as UserService

    actor UC as UserContract

    participant MC as Mach Contract

    participant MS as Mach Services

    participant L2 as Layer2



    US->>MC: A Rpc for Layer2



    MC->>L2: Map Rpc request if no alert



    UC->>MC: IsAlert



    MS->>L2: Fetch status and verify



    MS->>MC: Commit Alert for Layer2

    MS->>MC: Commit ZK proof for Alert

```



## Mach AVS service manager contract



Mach AVS service manager contracts can be found in [contracts folder](contracts/src/core/)



- [Mach AVS for all rollup stack (BLS Signature aggregation)](contracts/src/core/MachServiceManager.sol)

- [Mach AVS for OP stack based rollup (ZK proof)](contracts/src/core/MachOptimismZkServiceManager.sol)



### Dependencies



Mach AVS uses [EigenLayer Middleware v0.1.2](https://github.com/Layr-Labs/eigenlayer-middleware/releases/tag/v0.1.2-holesky-init-deployment)



### Alert submission and verification



#### BLS Signature Aggregation Mode



The aggregator service will collect BLS signatures from operators in Mach AVS. Upon reaching sufficient threshold,

the aggregator will `confirmAlert)` to submit the alert. Once verified, the alert will be confirmed.



#### ZK Proof Mode



In this mode, it does not need an aggregator to collect signatures. ZK Proof will replace the process of collecting BLS signature.



Operator can detect block or output root mismatch and submit an alert using `alertBlockMismatch()` and `alertBlockOutputOracleMismatch(`) respectively.

After the alert is submitted, operator will compute the corresponding ZK proof to prove the alert and submit the proof using `submitProve()`.



ZK Proof generation can be either done using RISC0 or GPU.



### Training wheels



Mach AVS includes operator allowlist which can be managed by contract owner.



#### Enable/Disable operator allowlist



- Enable operator allowlist: `enableAllowlist()`

- Diosable operator allowlist: `disableAllowlist()`



#### Operator allowlist management



- Add operator to whitelist: `addToAllowlist(address operator)`

- Remove operator from whitelist: `removeFromAllowlist(address operator)`



## Mach AVS Aggregator (for BLS Signature Mode)



Aggregator sample configuration file can be found at [config-files/aggregator.yaml](config-files/aggregator.yaml).



```bash

./bin/mach-aggregator --config  \

    --ecdsa-private-key  \

    --avs-deployment ./contracts/script/output/machavs_deploy_output.json

```



The `--avs-deployment` is use the `machavs_deploy_output.json` output by deploy script.



Mach AVS aggregator service can be found in [aggregator](aggregator/)



## Mach AVS Operator (for BLS Signature Aggregation Mode)



Operator sample configuration file can be found at [config-files/operator.yaml](config-files/operator.yaml).



Operator can be run using the following command:



```bash

./bin/mach-operator-signer --config 

```



Node operator client can be found in [operator](operator/). For more information on how to run operator, check out our guide at [here](scripts/README.md)



## Mach AVS Verifier



### Verifier for ZK Proof mode



The ZK Proof mode verifier codebase is found at [https://github.com/alt-research/alt-mach-verifier](https://github.com/alt-research/alt-mach-verifier)



### Verifier for BLS Signature Aggregation mode



The verifier codebase is found at [https://github.com/alt-research/mach](https://github.com/alt-research/mach)



## Deployment scripts for running within local devnet



Check out [scripts](scripts)



## Build a devnet by docker-compose



For devnet, we can use docker-compose:



```bash

docker compose build

docker compose up

```



it will boot anvil as layer1, a aggregator and a operator for test.



## Build and Run



If want to run Mach AVS by binary, can see the documentations:



- [build operator and aggregator](./docs/Build.md)

- [run operator](./docs/RunOperator.md)

- [run aggregator](./docs/RunAggregator.md)