surface 08 / replay / hl-fecbf3406975
signed Hyperliquid cancel action
DECISION_LOOP replay for @op-e196da20/deployment-f3f12c1f. The public view answers what observed the state, what policy touched it, what signing boundary existed, and what happened after resolution.
proof capsule
shareable decision evidence.
This replay exposes a stable canonical URL, JSON contract, OG image, schema, and journal proof references for the same decision artifact.
decision graph
observe to replay
- 01observecompleteruntime requested a Hyperliquid action signature
- 02hypothesizepartialruntime-side strategy trace pending prompt hash
- 03sizecompleteserver reconstructed and validated allowlisted HL action
- 04commitcompletePrivy-managed HL API wallet signed allowlisted typed data
- 05resolvepartialvenue submission and fill outcome arrive through heartbeat evidence
- 06evolvepartialruntime evolution trace pending heartbeat frame
- 07replaycompletestored decision_replay_frames row
model
- status
- partial
- model id
- runtime-requested
- runtime build
- f3f12c1f-69fa-4cc2-ad57-0d92d3553d6d
- policy version
- privy-hl-sign-v1
prompt
- status
- partial
- prompt sha
- request:fc6b30aff7eb3dea
- note
- Runtime prompt hash is expected in future signed requests; server request hash recorded for v1.
tools
- calls
- live_lease_gate:complete / hyperliquid_action_serializer:complete / privy_policy_signer:complete
- live_lease_gate
- complete · deployment live lease checked before signing
- hyperliquid_action_serializer
- complete · server reconstructed exchange request
- privy_policy_signer
- complete · typed-data signature returned by Privy wallet infrastructure
journal
- status
- partial
- verifier
- zero.journal.v1
- stream
- decisions
- sequence
- unavailable
- entry hash
- unavailable
- root hash
- unavailable
- anchor
- unavailable
- note
- No signed journal root has been attached to this replay yet.
audit
retained graph context
adjacent decisions and hash coverage
Public graph context keeps the replay connected to nearby decisions, refusals, and journal evidence while keeping raw prompts, tool payloads, private traces, operator ids, private keys, and performance metrics out of the public payload.
request:fc6b30aff7eb3dea · body public: no9ddf7de20512e15c4099f0842a38af4455f2ef22032651ae54afa133ed09a4920xfecbf340697573e352087e4ae0e0c8aa3299cf74669c4a4e07fee58908e42ba3pending root hashprevious
- replay
- hl-5ca1b62c775c
- outcome
- position
- journal
- partial
- audit
- partial
- summary
- signed Hyperliquid order action
next
- replay
- hl-bd3ba7b36c17
- outcome
- position
- journal
- partial
- audit
- partial
- summary
- signed Hyperliquid order action
same operator
- replay
signing boundary
privy_policy
no private keys stored. Allowed actions are rendered from the replay payload, so a human and an agent can verify whether this decision was execution-capable or a refusal.
0xfecbf340697573e352087e4ae0e0c8aa3299cf74669c4a4e07fee58908e42ba3journal rootpartialraw evidencehttps://getzero.dev/api/deployments/f3f12c1f-69fa-4cc2-ad57-0d92d3553d6d/evidence