GrypsAgentic

AVDS conformance

1 met · 3 partial · 2 not met

Self-assessment of Gryps v2 (SEI) against the Agent-Native Venue Design Standards foundational sections. Honest reading: no level claimed yet.

Statement

Pre-Level-1. Gryps v2 in its Polygon test phase meets §4.6 and partially meets §4.3–§4.5. Reaching L1 (Foundational) requires the identity and sub-account primitives plus idempotent submission semantics — the same six [Gryps-coord] items the Loadout tech spec routes to the protocol team.

§4.1Identity layer

Not Met

Accounts are bare EOAs; no queryable on-chain agent identity, operator link, or status field.

GapNeeds an agent registration primitive (did-style or key-hash) — Loadout [Gryps-coord] question #5.

§4.2Sub-account architecture

Not Met

One margin account per address; per-symbol leverage preferences exist but no isolated sub-accounts, tiers, or per-sub-account signing authority.

Gappaper / restricted / full tiering absent; agents and human capital share one envelope.

§4.3Action submission semantics

Partially Met

Nonce-ordered submission; deterministic state reads (balance, positions, pendingOrders) exposed per wallet; pending state is explicit.

GapNo client idempotency keys and no explicit ambiguous-outcome status on the write path — the v1 Hopf race is the cautionary case.

§4.4Risk control (killswitch)

Partially Met

Venue-wide rollup pause flag exists and is queryable; liquidation prices per position are exposed.

GapNo per-account or per-agent killswitch with drawdown / action-rate / time-window / manual triggers. Dashboard evaluates these monitor-side as a stopgap.

§4.5Forensics & attribution

Partially Met

Complete per-wallet fill history with ids, fees, timestamps; rollup seq/root history supports state-at-time queries.

GapNo sub-account tagging or logical-action boundary events; reconstruction is done off-venue (this dashboard, per ADR-007).

§4.6Venue Quirks Registry

Met

This registry entry (gryps-v2-perpsrollup-polygon-v0), maintained from live scheduled observation with dated changelog.

Open questions for the protocol team

  1. Confirmed v2 contract addresses per environment (proxy verified on Polygon; future deployments?)
  2. Hedger activity API surface
  3. Solver depth real-time access
  4. Killswitch contract integration
  5. Identity registration mechanism
  6. Event emission completeness for forensics

These are the six [Gryps-coord] items from the Loadout Operator Console tech spec — answering them is the path from pre-L1 to Level 1 (Foundational).

Conformance · Gryps v2