Publisher
Publishing data to a Stork Aggregator via WebSocket.
Base Endpoint
The standard endpoint for interacting with Stork via websocket is:
Authentication
All websocket connection requests must include an Authorization
header with the value set as Basic <token>
. For example:
Endpoints
/evm/publish
Publish signed data updates using EVM-compatible signatures.
Example:
/stark/publish
Publish signed data updates using Stark-compatible signatures
Example:
Messages
Publish Message
Description:
Publish signed price updates for one or more assets.
Fields:
"type"
: Type of the message. Always"signed_prices"
."trace_id"
: A unique identifier for debugging purposes."data"
: An object containing updates for each asset. Each key represents an asset ID, and the value is the signed price update:"oracle_id"
: ID of the oracle."asset_id"
: The asset being updated."trigger"
: The event triggering this update."signed_price"
:"publisher_key"
: The public key of the publisher."external_asset_id"
: The external representation of the asset ID."signature_type"
: Signature type (e.g.,evm
orstark
)."price"
: The updated price."timestamped_signature"
:"signature"
: The cryptographic signature of the update."r"
: R-component of the signature."s"
: S-component of the signature."v"
: V-component of the signature (only for EVM signatures).
"timestamp"
: Timestamp of the signed update."msg_hash"
: The hash of the message being signed.
"metadata"
: Any additional information related to the update. Optional.
Example:
Last updated