proxmox/docs/04-configuration/GRU_V2_PROTOCOL_COMPLETION_MATRIX.md

GRU v2 Protocol Completion Matrix

This file defines what “complete” means per protocol across the three GRU namespaces:

• c* V2 on Chain 138
• cA* on ALL Mainnet 651940
• cW* on the connected public networks

Status vocabulary:

• todo
• in_progress
• blocked
• done
• unsupported_by_protocol
• not_applicable

Implementation vocabulary:

• script-backed: this repo has a deploy/integration path for the protocol cell
• inventory-backed: this repo documents the cell, but does not yet deploy it end to end
• external-blocked: completion depends on external venue support, partner deployment, or out-of-repo contracts

1. Protocol expectations

Protocol	Liquidity / market role	Required namespace scope	Completion rule
DODO	primary PMM and single-sided mesh	138, 651940, public cW*	every required hub pair and Wave 1 pair has a PMM lane
Uniswap v3	concentrated-liquidity reference and execution	138, 651940, public cW*	primary hub pairs and gas-native hub pairs have reference lanes
Uniswap v2	fallback spot lane	138, 651940, public cW*	fallback lanes exist where v2 semantics are supported
SushiSwap	secondary AMM lane	138, 651940, public cW*	required hub families represented where deployed on the chain
Curve	stable and basket lanes	138, 651940, public cW*	stable families have Curve-compatible basket/routing coverage where supported
Balancer	weighted and stable basket lanes	138, 651940, public cW*	weighted / stable basket pools for required families where supported
1Inch	aggregator execution and routing	138, 651940, public cW*	venue surfaces are routeable and executable through the aggregator
Aave	reserve listing and flash-liquidity support	138, 651940, public cW*	reserve / flash integration or explicit unsupported_by_protocol
GMX	native market integration	138, 651940, public cW*	market support or explicit unsupported_by_protocol
dYdX	native market integration	138, 651940, public cW*	market support or explicit unsupported_by_protocol

2. Namespace-by-protocol tracker

Namespace	DODO	Uni v3	Uni v2	Sushi	Curve	Balancer	1Inch	Aave	GMX	dYdX
138 c* V2	done, script-backed	done, script-backed	todo, external-blocked	todo, external-blocked	done, script-backed	done, script-backed	done, script-backed	todo, external-blocked	todo, external-blocked	todo, external-blocked
651940 cA*	todo, inventory-backed	todo, external-blocked	todo, external-blocked	todo, external-blocked	todo, external-blocked	todo, external-blocked	todo, external-blocked	todo, external-blocked	todo, external-blocked	todo, external-blocked
public cW*	in_progress, script-backed	in_progress, inventory-backed	in_progress, inventory-backed	todo, external-blocked	todo, external-blocked	todo, external-blocked	in_progress, inventory-backed	todo, external-blocked	todo, external-blocked	todo, external-blocked

3. Completion gates

For a protocol cell to move to done, all of the following should be true:

1. deployed
2. seeded or listed
3. validated
4. live
5. MEV-ready where the protocol participates in MEV routing/execution

For Aave, GMX, and dYdX, if the protocol does not support the family or chain natively, the cell should be closed as unsupported_by_protocol rather than left ambiguous.