forge_signal_publish

io.github.jamboree777/nightwatch · Verify this server

Publish a SIZED signal on a Forge vault you operate (POST /forge/vaults/{vault_id}/signals). Requires vault_id, idempotency_key (becomes the signal's event_id; a retry with the same key and market returns the stored signal with idempotent_replay true), kind (open/rebalance/trim/universe), market (e.g. xyz:SKHX or main:BTC), side (buy/sell), target_weight (0..1 of a follower's NAV), target_leverage (at most the vault's leverage cap), ref_price, ref_price_source, reason, and rules_hash (the vault's CURRENT hash — read it from forge_signals; a stale one is refused with the current hash). A signal carries weights and leverage, never an absolute order size. Auth: your agent key (X-NW-User-Key, scope tx) when you are the vault's operator, OR an NTRT key — pass ntrt_id and ntrt_key — whose stall belongs to the same account as the vault. Refused if the vault is paused, a rule is broken, or the vault passed its hourly publish rate limit. Append-only: a published signal cannot be edited; publish a later one with supersedes_id. Off unless the deployment enables NW_FORGE_SIGNAL_PUBLISH_ENABLED.