proxmox/docs/04-configuration/GRU_NATIVE_PROTOCOL_ONLY_POLICY.md

GRU Native Protocol Only Policy

Purpose

This policy makes one rule explicit for GRU public venue coverage, gas-family mirrors, and MEV/public routing claims:

• A protocol lane counts as live, routingVisible, or publicRoutingEnabled only when it points at a native, discoverable protocol contract on the target network.
• Placeholder, scaffold, synthetic, or documentation-only addresses must never be represented as live protocol support.

Applies To

• cross-chain-pmm-lps/config/deployment-status.json
• public protocol coverage docs and status tables
• MEV route / venue inventory derived from those surfaces
• operator rollout checklists that reference protocol readiness

Required Behavior

Live lane requirements

A protocol lane marked live must have all of the following:

1. A real on-chain address for the native protocol contract family
2. Contract discovery or provenance that ties it back to the intended upstream protocol
3. Matching route / planner / indexer visibility where the surface claims it is routable

Not allowed as live support

These must not be counted as live protocol coverage:

• scaffold addresses
• synthetic addresses used only for planning
• placeholder addresses shaped from chain IDs or protocol markers
• inventory rows that exist only to reserve a future slot

Current Implication

If a venue family is still using scaffold addresses, its status must be represented as one of:

• planned
• scaffolded
• not yet native
• out of scope

but not:

• live
• routingVisible
• publicRoutingEnabled

Enforcement

The deployment-status validator now rejects obvious placeholder addresses for:

• gasPmmPools[*].poolAddress when publicRoutingEnabled=true
• gasReferenceVenues[*].venueAddress when live=true or routingVisible=true

This is a guardrail, not a full provenance proof. Operator review still needs to confirm the upstream-native protocol family is correct.