submit_observation_wormhole

Submits a Wormhole Guardian-verified observation for a configured registered position.

Accounts

Account	Role	Description
glam_state	read-only	`glam_state` account required by the `submit_observation_wormhole` instruction (see program source for the full constraint).
glam_signer	signer, writable	`glam_signer` account required by the `submit_observation_wormhole` instruction (see program source for the full constraint).
observation_state	writable	`observation_state` account required by the `submit_observation_wormhole` instruction (see program source for the full constraint).
wormhole_config	writable	`wormhole_config` account required by the `submit_observation_wormhole` instruction (see program source for the full constraint).
guardian_set	read-only	`guardian_set` account required by the `submit_observation_wormhole` instruction (see program source for the full constraint).
guardian_signatures	read-only	`guardian_signatures` account required by the `submit_observation_wormhole` instruction (see program source for the full constraint).
wormhole_verify_vaa_shim	read-only	`wormhole_verify_vaa_shim` account required by the `submit_observation_wormhole` instruction (see program source for the full constraint).

RPI role access is not required for this submit path; the signer relays a Wormhole VAA body whose signatures have already been posted to the Wormhole Verification Shim.
Position must be enabled, configured as a USD-valued Wormhole position, and match the stored Wormhole and Hyperliquid payload constraints.
Accepted payloads become pending USD observations; validate_observation still performs GLAM oracle normalization before pricing.