@totalis/hip4-client 0.0.0-stage → 0.73.0

package/CHANGELOG.md

@@ -0,0 +1,1903 @@
+# Changelog
+
+`@totalis/hip4-client` follows [semantic versioning](https://semver.org).
+The contract version the generated types come from is `sdkVersion` in `./version`.
+
+## 0.73.0
+
+A follower's copied trades, what copying each trader came to, and which of
+their fills copies made (TT-2486); the chain-agent registry's `SET_AGENT`
+Combo copy agents and the Combo copy budget (TT-2487).
+Generated from contract `201.0.0-copy-budget`. Additive.
+
+### Added
+
+- `listCopyTrades` (`GET /v1/me/copy-trades`): your copy journal, newest
+  first, optionally for one `leader`. Each row is a followed trader's trade
+  and what became of your copy: `PENDING`, `COPIED`, `PARTIAL`, `SKIPPED`
+  with a `reason`, or `FAILED`.
+- `getCopySummary` (`GET /v1/me/copy-summary`): per trader, copies filled,
+  skipped and failed, USDC `bought` and `sold`, copied shares still `held`,
+  and whether those give the P&L (`complete`).
+- `listCopiedFills` (`GET /v1/me/copy-fills?tids=&from=&through=`): which
+  of up to 100 of your fills, by Hyperliquid trade ID, in a span of at most
+  31 days, copies made, with the copied trade and its `leader`.
+- `HyperevmKeeperOperationKind` (internal registry): `SET_AGENT`, a relayed
+  vault agent grant or revoke.
+- Combo copy agents: `requestComboCopyAgent`, `grantComboCopyAgent`,
+  `confirmComboCopyAgent`, `revokeComboCopyAgent` and
+  `switchOffComboCopyAgent` (`/v1/me/copy-agents/combo*`). The key Combo
+  auto-copy signs with, the account's vault `AgentGrant` for it relayed to
+  `setAgent`, its confirmation once on chain, an on-chain revoke, and
+  switching it off. `getCopyAgents` adds `combo`.
+- `getCopyBudget` and `setCopyAllocation` (`/v1/me/copy-budget`): the Combo
+  copy allocation and the budget the sweeper leaves in the vault for Combo
+  copying.
+
+## 0.72.0
+
+Emoji reactions on market comments (TT-2399), and a named refusal for a
+core copy key on another account (TT-2485).
+Generated from contract `196.0.0-copy-engine`. Additive.
+
+### Added
+
+- Comment reactions: `reactComment` and `unreactComment`
+  (`PUT` and `DELETE /v1/comments/{comment_id}/reactions/{reaction}`) give and
+  take back one of `fire`, `laugh`, `mind_blown`, `cry`, `rocket` and `skull`.
+  Every comment gains `reactions`: each reaction it has, with its `count` and
+  whether you gave it (`reacted`).
+
+### Changed
+
+- `requestCoreCopyAgent` (`POST /v1/me/copy-agents/core`) can answer
+  409 `STATE_CONFLICT` while a key is active on another account: switch it
+  off first, or renew for the active key's account.
+
+## 0.71.0
+
+Server-held copy agents for core auto-copy (TT-2484), users, cash-outs and
+open positions in partner reports (TT-2541), and public trader profiles that
+start on (TT-2539).
+Generated from contract `194.0.0-partner-users`. Additive, except that public
+profiles now start on.
+
+### Added
+
+- Partner reports (TT-2541): `report()` (`GET /v1/partner/report`) adds
+  `users` (wallets you admitted and the accounts they created, all time),
+  `open_tickets` (your users' open positions and their stake), and per day
+  and in total `cashouts`, `cashout_volume`, `active_traders` and
+  `new_accounts`. In `totals`, `active_traders` counts each account once over
+  the range.
+
+- Copy agents (TT-2484): `requestCoreCopyAgent`
+  (`POST /v1/me/copy-agents/core`) makes the key core auto-copy signs with,
+  which the account approves with `approveAgent` in the named slot
+  `TotalisCopy`; `confirmCoreCopyAgent` (`POST .../core/confirm`) activates it
+  once Hyperliquid lists it; `getCopyAgents` (`GET /v1/me/copy-agents`) reads
+  the active key and any replacement waiting for approval; and
+  `switchOffCoreCopyAgent` (`DELETE /v1/me/copy-agents/core`) stops copying at
+  once. New schemas `CopyAgent` and `CopyAgents`.
+
+### Changed
+
+- Public trader profiles start on (TT-2539). A new account's profile is public
+  as soon as it exists, and every existing profile that never used the switch
+  was turned on, so `getIdentity` (`GET /v1/me`) reports `public_profile: true` for them, including
+  accounts without a username. `setPublicProfile` (`PUT /v1/me/public-profile`)
+  still turns it off, now also before the account has a username, and turning
+  it on still needs one. While on, a profile links the account wallet to its
+  username in `GET /v1/traders/{username}` and the leaderboards.
+
+## 0.70.0
+
+A named refusal for a sign-in without Google, email or X (TT-2519, TT-2537).
+Generated from contract `192.0.0-sign-in-required`. Additive.
+
+### Added
+
+- `bindEmbeddedWallet` refuses a new account whose Privy user has no Google,
+  email or X login linked, such as one signed in only with an external
+  wallet, with the new error code
+  `SIGN_IN_REQUIRED` (403) instead of `ACCESS_REQUIRED` (TT-2519). An X
+  login now opens an account like Google or email (TT-2537).
+  On `bindEmbeddedWallet`, `ACCESS_REQUIRED` now means only that no invite has
+  been redeemed; wallet sign-in keeps its meaning.
+
+## 0.69.0
+
+Vault run-off (TT-2260), X pictures on the leaderboard (TT-2318), a gas
+ceiling on sponsored work (TT-2338), no generated usernames (TT-2299),
+perp marks for price charts (TT-2335), live
+games on sports cards and detail (TT-2306), Combos of at most 5 legs, and
+games in play on browse, live scores over the market stream and score
+timelines (TT-2371), market comments (TT-2297), their moderation (TT-2410),
+holder badges and the holders filter (TT-2411), up to three suggested Combos,
+held chances (TT-2366), partner reports (TT-2420), market list cursors
+that continue across catalog generations (TT-2425), a named refusal for an
+accept beside another in flight (TT-2259), the account's X picture from the
+server (TT-2443), sponsored deposits from 0.10 USDC (TT-2444), the
+funded-accept wording that gives a transfer sent before `fund_by` two more
+seconds to land (TT-2259), the net stake on entry RFQs (TT-2419) and the
+discovery cards of suggested Combo legs (TT-2475), opt-in public
+trader profiles (TT-2481) and follows with copy settings (TT-2482).
+Generated from contract `191.0.0-follows`.
+Breaking only for callers of the removed operation and RFQs of more than 5
+legs.
+
+### Added
+
+- Follows and copy settings (TT-2482): `followTrader` and `unfollowTrader`
+  (`PUT` and `DELETE /v1/me/follows/{username}`) follow a public trader and
+  set the follow's core and Combo copy settings, `listFollows`
+  (`GET /v1/me/follows`) lists them, and `getCopySettings` and
+  `setCopySettings` (`/v1/me/copy-settings`) read and set the pause and daily
+  caps across every follow. `getTrader` gains `followers` and `following`, and
+  the new error codes `FOLLOW_SELF` and `FOLLOW_LIMIT_REACHED` refuse following
+  oneself or more than 100 traders.
+- Public trader profiles (TT-2481): `setPublicProfile`
+  (`PUT /v1/me/public-profile`) turns the account's profile on or off, and
+  `getTrader`, `listTraderTrades`, `listTraderPositions` and `getTraderPnl`
+  (`GET /v1/traders/{username}` and its `trades`, `positions` and `pnl`) read
+  an opted-in trader. `VenueIdentity` and both leaderboards' traders gain
+  `public_profile`, and the new error code `USERNAME_REQUIRED` refuses turning
+  a profile on without a username.
+- `SuggestedCombo` (`GET /v1/suggested-combo`) requires `cards`: the browse
+  contract 4 discovery card each leg was picked from, in leg order, as read
+  when it was quoted, so a client can draw a leg that is not on its own page
+  (TT-2475).
+- `EntryRfq` (`GET /v1/rfqs`, `GET /v1/rfqs/{rfq_id}`, snapshot `open_rfqs`)
+  and the entry `RFQ_CREATED` payload carry `net_stake`, what the vault backs
+  if a quote is accepted: `stake - floor(stake * taker_fee_bps / 10000)` with
+  the vault's current taker fee, the one every quote must carry. `stake` stays
+  gross and quotes still sign it. Absent while the server does not know the
+  taker fee (TT-2419).
+- `DashboardQuotes` (`GET /v1/makers/{maker_id}/quotes`) requires `net_stake`
+  on each quote: its stake less its own taker fee (TT-2419).
+- `VenueIdentity` (`GET /v1/me`) and comment authors carry `picture_url`, the
+  profile picture of the X account linked to the account's Privy login, the
+  same one the leaderboards show; absent when the server has none.
+  `POST /v1/me/picture` (`refreshPicture`) reads it from Privy now; call it
+  right after the user links or unlinks X.
+- `ErrorCode` adds `ACCEPTANCE_IN_FLIGHT` (409, `REFRESH`), and Accept quote
+  lists it: an account has one entry acceptance in flight at a time, so
+  accepting an entry quote while another awaits its maker or its trade is
+  refused with it instead of `STATE_CONFLICT`. Nothing was created; accept a
+  fresh quote once that acceptance's operation ends.
+- Wallet challenges accept the exact bundled iOS origin `capacitor://localhost`
+  when it is registered in the service allowlist. Existing HTTPS origins and
+  wallet-signature requirements are unchanged.
+- Partner reports (TT-2420): `createPartnerServer(...).report({ from, to })`
+  (`GET /v1/partner/report`) returns your partner's fees per UTC day, your
+  terms and, all time, what you earned, were paid and are owed, with every
+  payout and its transfers. It takes your server key; omit the range for the
+  30 days through today.
+- `signInWithWallet({ serverKey })`: a partner signing its users in from its
+  own servers passes its `tpk_v1_` server key, and the sign-in is rate limited per
+  partner instead of per source address (TT-2424). The origin must be one the
+  partner owns; the wallet still signs. Server-side only.
+- Vault v1.1 maker withdrawals: `controllerTransactions(...).withdraw(amount,
+  to)` builds `withdrawMaker`, which pays at once. `requestWithdraw`,
+  `executeWithdraw` and `cancelWithdraw` stay for a vault v1 maker.
+- Market comments (TT-2297): `GET /v1/comments` lists a question's or
+  standalone outcome's top-level comments, most liked or newest first;
+  `GET /v1/comments/{comment_id}/replies` lists a comment's replies. A
+  signed-in session posts, edits, deletes, likes and unlikes with
+  `POST /v1/comments`, `PUT` and `DELETE /v1/comments/{comment_id}` and
+  `PUT` and `DELETE /v1/comments/{comment_id}/like`.
+- Comment moderation (TT-2410): a comment carries `removed` when a moderator
+  deleted it, and a comment page carries `pinned`, the comment a moderator
+  pinned to lead the thread, on a thread's first page only. A muted account's
+  posts and edits are 403 `FORBIDDEN`.
+- Comment holders (TT-2411): a comment carries `holder` when its author holds
+  an open Combo on its market now, null when that is not known.
+  `GET /v1/comments?filter=holders` lists only holders' comments.
+- `GET /v1/suggested-combo` carries `combos`, up to three suggested Combos
+  that share no outcome. `combo`, the first of `combos` or null, is
+  deprecated and goes in the next release.
+- `signRunOffClaim({ vaultAddress })` signs an Exit of the account's free cash
+  in a vault running off to the account's own wallet; send it with
+  `sendRunOffClaim` (`POST /v1/me/run-off-claims`) and follow its operation
+  with `waitForOperation`.
+- Balances carry `run_off`: cash per vault running off, never part of
+  `amount`, with any claim still in flight as `claim`. A position carries
+  `vault_address` and `cashout_available`; a core exit carries
+  `vault_address`.
+- A cash-out of a position on a vault running off returns `STATE_CONFLICT`.
+- Both leaderboards' traders carry `picture_url`, the profile picture of the X
+  account linked to the trader's Privy login, which clients show in place of
+  the generated avatar.
+- `ErrorCode` adds `GAS_PRICE_ABOVE_CEILING` (503, `BACKOFF`): creating a
+  Combo RFQ or a cash-out is refused while HyperEVM gas is above the venue's
+  sponsorship ceiling. Retry after `Retry-After`.
+- An RFQ's `status` adds `DECLINED` and the stream adds `RFQ_DECLINED`, for
+  RFQs makers declined before declines were removed (TT-2431); no RFQ ends
+  `DECLINED` now. `watchQuotes` empties and `onRfq` drops the RFQ on it, as on
+  `RFQ_CANCELLED`.
+- Types for `GET /v1/perp-marks`, a perp's mark price on a fixed step recorded
+  from Totalis's own Hyperliquid node, and for the market stream's opt-in
+  `publication` frame (`publication_freshness`), which proves how far a
+  socket is current.
+- Browse and search cards carry `estimated_live_until` (TT-2306): for a
+  scheduled single sports contest, its start plus its league's reviewed usual
+  game length, so `[date_at, estimated_live_until)` is when it is in play. A
+  live game feed holds it open while the game runs long and closes it when
+  the game ends. Null otherwise; never a trading cutoff. Every default browse
+  page, All included, lists cards inside that window first.
+- `Question` carries the same `estimated_live_until` for its markets, and
+  `MarketDetail` read with `contract=4` carries its matchup's: its question's,
+  else its game's, else its own.
+- Both also carry `scoreboard`: the matchup's game as the live game feed last
+  read it (`status`, `period`, `clock`, `outs`, both `competitors` with
+  `score` in the matchup's own order, `last_play`, `refreshed_at`), or null
+  when the feed does not cover the game or its reading is stale. Display only,
+  never a result.
+- Browse queries take `live: true` (TT-2371): only the cards in play at
+  publication, for All or one `category`, in either browse sort; a
+  subcategory, frequency or date window beside it returns `INVALID_QUERY`.
+  Results echo it as `filters.live`. Every browse and search result carries
+  `live`: the publication's count of cards in play, `total` and per
+  configured category (`categories`, `{ value, count }`), each equal to that
+  live page's total, or `UNAVAILABLE` when the result's other counts are.
+- The market stream's opt-in `scoreboards` frame (TT-2371): a subscription
+  that sets `scoreboards` gets every selected game's `scoreboard`, complete
+  after each snapshot and then on every change.
+- Types for `GET /v1/markets/{outcome_id}/score-timeline` and
+  `GET /v1/questions/{question_id}/score-timeline` (TT-2371): the matchup's
+  score after each scoring play at the feed's wall-clock time, for a game
+  chart, or a null `timeline`.
+
+### Changed
+
+- `openPosition` (`POST /v1/rfqs`) takes 1 to 5 legs, down from 50; more
+  return `400 INVALID_REQUEST`.
+- A reference's `chance` holds the newest evidence, an execution or a book
+  midpoint at most 0.10 wide, kept inside the live book (TT-2366): on a book
+  at most 0.50 wide at any age, and on a wider, one-sided or empty book for
+  20 minutes. `chance_basis` adds `HELD` for a chance that is neither the
+  current midpoint nor the unclamped last trade. A one-sided or empty book is
+  published `AVAILABLE` while it has a `mark` (a chance, else the best bid,
+  else 0 with asks only), with the missing side null and `value` equal to
+  `mark`. Reference closes record the shown chance of
+  any basis, not only midpoints.
+- `GET /v1/markets` no longer returns `409 STALE_CURSOR`: its cursor continues
+  by native ID when a new catalog generation is published, so pages can name
+  different `catalog_generation` values (TT-2425).
+- `createDeposit` (`POST /v1/me/deposits`) admits deposits from 0.10 USDC
+  (`100000`) from a Totalis embedded wallet, down from 1 USDC (TT-2444). Any
+  other wallet still moves at least 1 USDC, its floor for every sponsored way
+  out.
+
+### Removed
+
+- `generateUsername` (`POST /v1/me/username`) and its `GeneratedUsername`
+  schema. An app picks the username and sets it with `setUsername`
+  (`PUT /v1/me/username`).
+
+### Fixed
+
+- `sendAcceptance` no longer discards a bridge because a resent accept was
+  refused (TT-2259). When the first send's answer was lost and the SDK's resend
+  under the same `Idempotency-Key` met a 401 (the session lapsed), the bridge
+  was recorded `DISCARDED` and never sent, even though the venue held the first
+  send's acceptance. A resend's refusal now ends the attempt only if the venue
+  checks it after replaying a stored acceptance (a gone price, a bad
+  signature). A resend's 401, 403 or 429, which the venue checks before the
+  replay, and a 5xx or an answer cut off mid-body, no longer discard the
+  bridge: the SDK reads the acceptance and moves the bridge from what it finds. If that read fails too, the bridge stays unsent
+  and the error reports `mayStillRun: true`, with `resend()`, so recovery
+  decides after re-authenticating.
+- `recoverAcceptance` works without a signer: it checks the record's account
+  against the session's wallet (`GET /v1/me`), since recovery signs nothing.
+
+## 0.68.0
+
+Every expired operation names why (TT-2315). Generated from contract
+`165.0.0-expiry-reasons`; an older venue simply sends fewer reasons.
+
+### Changed
+
+- `OperationFailureReason` adds `DEADLINE_BEFORE_CLAIM`,
+  `AUTHORIZATION_TOO_CLOSE`, `SIGNER_QUOTE_LIFE`, `SIMULATION_REVERTED`,
+  `QUARANTINE_EXPIRED` and `ATTESTATION_EXPIRED`. An operation's
+  `failure_reason`, and `OPERATION_UPDATED`'s, can carry any of them on
+  `EXPIRED_UNEXECUTED`.
+- `entryFailure` returns the operation's own reason for every reason but
+  `INSUFFICIENT_CASH`, which it still words as `INSUFFICIENT_CASH` or
+  `CORE_MOVE_MISSED`. `EntryFailure` widens to match: code that handles it
+  exhaustively needs a case for each new reason.
+
+## 0.67.0
+
+Taker flow fixes (TT-2268). Additive: 0.66 code runs unchanged.
+
+### Added
+
+- `bestBid(minLifeSeconds, minPrice)`: an optional price floor in USDC base
+  units; no bid below it is chosen.
+- `RetryPolicy.maxRetryAfterMs` (default 30 s). A BACKOFF answer whose
+  Retry-After is longer is no longer waited out: the call throws at once, for
+  example `RATE_LIMITED`, with `retryAfterMs` set.
+- `StreamClosedError.commandSent` and `TotalisStream.closeError()`.
+
+### Changed
+
+- A follow cut off by a stream closed for good rejects with the server's
+  close reason (for example `STREAM_REPLACED`), not a generic `closed`. When
+  it follows a command already sent (`waitForOperation`, `waitForCoreExit`,
+  `sendWithdrawal`, `waitForWithdrawal`), the error has `commandSent` and
+  `normalizeError` reports `mayStillRun: true`.
+- An `AcceptanceResult`'s `bridged` reads the bridge as it stands now, so it
+  turns `landed: "yes"` once Hyperliquid answers `ok`, and reads undefined
+  once a bridge is refused or discarded unsent.
+- `openPosition` takes and signs a fresh quote once when the accept is
+  refused with `QUOTE_EXPIRED` or `QUOTE_REPLACED`; `onSigned` gets the new
+  record. A second refusal, or no fresh quote within `quoteTimeoutMs`, throws
+  the refusal.
+- Deposit, withdrawal and exit signing windows are set on the venue clock the
+  stream tracks once it has synced. Signing never waits for the stream, so a
+  window signed on a fresh instance before its first sync uses the device
+  clock; start the stream first on devices whose clock may be off.
+- Documented that an acceptance read after the trade settled, for example by
+  `recoverAcceptance`, can be `FILLED` or `FAILED`, both with `operationId`.
+
+## 0.66.1
+
+Combos close at a market's admission cutoff (TT-2271). No type changes.
+
+### Changed
+
+- `combo` is `CLOSED` with `OUTSIDE_WINDOW` and a null `opens_at` once a
+  market's result can be known: a price market from its observation time, a
+  policy rate from its scheduled decision. A sports game stays open in play
+  until its resolution backstop. RFQs refuse such legs as before.
+
+## 0.66.0
+
+A lighter HyperCore read for Cash (TT-2277). Additive: 0.65 code runs unchanged.
+
+### Added
+
+- `GET /v1/hypercore/balance` returns the session account's HyperCore spot
+  USDC, perps cash, account mode and HIP-4 positions in one read, on mainnet
+  and testnet. It reads no orders or fill history, so it answers even when
+  the portfolio's fill history is unavailable.
+- HyperCore funding (`/v1/hypercore/portfolio` and the new route) carries
+  `spot_usdc_total` and `spot_usdc_hold`; `spot_usdc` stays total minus hold.
+## 0.65.2
+
+The package is now `@totalis/hip4-client`, published to public npm. Install
+it under the new name and change your imports from
+`@totalistrading/hip4-client` to `@totalis/hip4-client`; nothing else
+changes. 0.65.1 was tagged under the old name but never published.
+
+## 0.65.1
+
+The first release on public npm (`registry.npmjs.org`), under Apache-2.0, with
+no registry configuration or token needed. Remove any
+`@totalistrading:registry=https://npm.pkg.github.com` line from your `.npmrc`.
+The code is the same as 0.65.0; 0.65.0 and earlier stay on GitHub Packages.
+The README is now a short overview; the full guide is at
+[docs.totalis.trade/hyperliquid/sdk](https://docs.totalis.trade/hyperliquid/sdk).
+
+## 0.65.0
+
+A failed operation says why (TT-2261). Additive: 0.64 code runs unchanged.
+
+### Added
+
+- `Operation` and the `OPERATION_UPDATED` payload carry an optional
+  `failure_reason`: `INSUFFICIENT_CASH` when an accept ended
+  `EXPIRED_UNEXECUTED` because the taker's Cash did not cover the stake, and
+  absent otherwise. `waitForOperation` resolves with it, so you no longer need
+  the RFQ's `terminal_reason`.
+- `entryFailure(record, operation)` names why an entry did not trade, for the
+  message to show: `INSUFFICIENT_CASH` (not enough Cash, including when the
+  planned Core cash landed) or `CORE_MOVE_MISSED` (the record planned Core
+  cash that Hyperliquid never confirmed moving before `fund_by`, so the user
+  may still have enough on HyperCore). It is `undefined` for any other
+  outcome. Pass the latest record, as `onRecord` last handed it back.
+- `openPosition` returns the entry `record`, which follows each bridge update
+  `onSigned` gets.
+- The `createRfq` error list includes `RFQ_GENERATION_STALE`,
+  `RFQ_GENERATION_IN_FLIGHT` and `COMBO_AUTOMATIC_DISABLED`, which the route
+  already returned.
+
+```ts
+const opened = await totalis.openPosition({ legs, stake, core });
+if (opened.operationId) {
+  const operation = await totalis.waitForOperation(opened.operationId);
+  if (operation.status !== "COMMITTED") {
+    const failure = entryFailure(opened.record, operation); // "INSUFFICIENT_CASH" | "CORE_MOVE_MISSED" | undefined
+  }
+}
+```
+
+Needs a venue with contract `163.0.0-operation-failure-reason`; against an
+older venue `failure_reason` is absent and `entryFailure` returns `undefined`.
+
+## 0.64.0
+
+A Combo entry posts its accept at once and moves Core cash only after the
+maker takes it (TT-2125). The accept no longer waits up to 1.5 s for
+Hyperliquid's answer to the bridge, and a declined, timed-out or not-admitted
+entry never sends its bridge. Needs a venue that publishes `accept_before` on entry
+quotes and `fund_by` and `server_time` on acceptances.
+
+### Changed
+
+- `sendAcceptance` posts the accept first. The Core to HyperEVM bridge goes
+  only when the acceptance is `ACCEPTED` with a `fund_by` still ahead, and is
+  resent while unanswered until `fund_by`; an accept answered any other way
+  discards it. The result does not wait for Hyperliquid: its new `bridging`
+  promise carries the answer, and `bridge` (the answer) is gone.
+- `signEntry` asks the signer for the quote, the bridge and the wallet
+  authorization at once. Pass `cash` (the `{ vault, wallet }` of a
+  `spendableCash` read) to plan without a balances read on the press; a plan
+  that fails then throws before the wallet is asked for anything. Without
+  `cash` it still reads the balances. `openPosition` takes `cash` too, and
+  otherwise reads the balances while the quotes arrive.
+- `recoverAcceptance` now finishes the bridge: it sends a never-sent bridge
+  if the acceptance is `ACCEPTED` before its `fund_by` and discards it
+  otherwise, and resends a sent but unanswered one, the same bytes, within
+  that window. It takes `transport` and `onRecord`. A bridge moves only for
+  the record's own acceptance: when another record's acceptance took the
+  quote, the result reports it and this record's bridge is discarded.
+  While a never-sent bridge waits on a `PENDING_CONFIRM` acceptance, it and
+  a lost accept answer are read every 250 ms until 2 s past the maker's
+  deadline, so an early `ACCEPTED` still moves cash before `fund_by`.
+- `fund_by` is judged by the latest the venue clock can read: a response's
+  new `server_time`, read from the database clock that sets `fund_by`, plus
+  the time since its request left. A skewed local clock or a delayed
+  response never sends late, and a bridge with no stamp to judge by is
+  discarded. An entry with a bridge reads its RFQ's quotes alongside the
+  accept for a tight stamp, since the held accept's own runs late by the
+  maker's wait. A first send whose `fund_by` passed while
+  `onRecord` saved `SENT` is not sent and records `DISCARDED`.
+- Entry records carry `version: 2` and a `bridgeState` (`SENT`, `LANDED`,
+  `PROCESSED`, `REFUSED`, `DISCARDED`). `onRecord` on `sendAcceptance` and
+  `recoverAcceptance` (and `openPosition`'s `onSigned`) is awaited with the
+  record before the first send and gets it again with each new state:
+  persist it over the stored one. A record without `version`
+  (`LegacySignedEntry`, from 0.63 or older) is only read by
+  `recoverAcceptance`; `sendAcceptance` refuses it.
+- `bridged` is set only once a bridge was sent: never for one never sent,
+  discarded or refused. A refused bridge after `ACCEPTED` leaves the result
+  `ACCEPTED`.
+- `settleHypercore` checks its `deadline` before every send, not only by
+  timer, on its new `now` clock (epoch ms by default).
+- `bestQuote()` and the quote book cut entry quotes off at their
+  `accept_before` instead of fixed margins; `bestQuote` takes no argument,
+  and the UI adapter's `minLifeSeconds` applies to cash-out quotes only. An
+  entry quote without `accept_before` is never offered.
+
+### Removed
+
+- `EntryError` codes `QUOTE_SHORT`, `BRIDGE_LATE` and `BRIDGE_REFUSED`, with
+  its `hyperliquidError` and `bridged`, and `bridged` on `ApiError` and
+  `normalizeError`'s result: nothing is bridged before the accept any more.
+
+## 0.63.0
+
+Fixes from a partner integration (TT-2258).
+
+### Changed
+
+- `openPosition` and `cashOut` take `collectMs` (default 1,000): once `choose`
+  would take a quote, more quotes may arrive for that long, and `choose` picks
+  when the window ends, whether or not any did. The window ends sooner when
+  waiting would leave `choose` nothing. `collectMs: 0` takes the first quote
+  as before. A `Chooser` may be asked about a later time, so it must
+  depend only on its arguments.
+- `signEntry` and `openPosition` without `core` throw `EntryError`
+  `INSUFFICIENT_FUNDS`, naming the shortfall, when the wallet is known to fall
+  short, instead of signing an entry the venue refuses.
+- `issueApiKey` refuses a challenge whose `urn:totalis:scope:` resources differ
+  from the requested scopes. Key challenges now list the scopes they grant and
+  `urn:totalis:expires-in-days:<days>`.
+- A transfer bid its buyer's free vault balance cannot pay is refused at
+  publish (`INVALID_REQUEST`, `transfer.price`) instead of timing out after the
+  owner accepts it.
+
+## 0.62.0
+
+Hourly reference closes, so charts can show a market's trend past one day
+(TT-2230). Generated from contract 161.
+
+### Added
+
+- `GET /v1/markets/{outcome_id}/reference-closes` takes `bucket=HOUR`: each
+  UTC hour carries the close of its last observed minute, over a window of up
+  to 90 days (the default with no `from`/`to`), `limit` up to 2,184. Every
+  response now carries `bucket_seconds` (60 or 3600), and runs read
+  `[bucket, close, buckets]`. Minute closes are unchanged.
+
+## 0.61.0
+
+Makers onboard and run headless (TT-2257): the /mm dashboard becomes read-only,
+so every maker write goes through the SDK or the API. No API change.
+
+### Added
+
+- `listApiKeys(client, { maker? })` reads every page of an account's or a
+  maker's keys; `revokeApiKey(client, keyId, { maker? })` revokes one and throws
+  the venue's `ApiError` otherwise.
+- `QUOTING_BOT_SCOPES` (the maker scopes for a quoting bot, none of which move
+  vault money) and `COLLATERAL_SCOPES` (for `reduceCollateral`), with the
+  `KeyScope` and `KeyMetadata` types.
+- `examples/onboard.mjs`: headless maker onboarding from the exported Totalis
+  wallet key: sign in, open and admit the maker, issue the quoting bot's key,
+  make the first deposit into the maker vault (only while it is empty on
+  chain) and start quoting. A rerun resumes and never deposits twice.
+
+### Changed
+
+- `signInWithWallet`'s `origin` documentation: outside a browser a maker passes
+  the Totalis app's origin (`https://hip4.totalis.trade`, or
+  `https://hip4-staging.totalis.trade` on staging) and sends it as the Origin
+  header with every request on the session.
+
+## 0.60.1
+
+The venue now refuses, with 409 `STATE_CONFLICT`, to replace or cancel a quote
+while a taker's acceptance of it awaits the maker's answer, instead of
+withdrawing the acceptance (TT-2254). That closes the window 0.60.0 left: an
+acceptance recorded while a replacing quote was on its way. Generated from the
+contract with the new 409 descriptions; no API change.
+
+### Changed
+
+- `quote`, `bid` and `cancelQuote` can answer `ApiError` `STATE_CONFLICT`
+  (`retry: "REFRESH"`) when an acceptance of the quote awaits this maker's
+  answer: answer it (`confirm`, or `onAcceptance`) first. The documentation of
+  `AcceptancePendingError` and `cancelQuote` says so.
+
+## 0.60.0
+
+A maker no longer withdraws the acceptances it knows of by quoting again
+(TT-2253). An acceptance the venue records while a quote is already on its way
+can still be withdrawn by it: the SDK checks what the stream and the
+acceptances read have delivered, not the venue's state at publication.
+Generated from contract 160; no API change.
+
+### Changed
+
+- Maker (`createMaker`): replacing or cancelling a quote while a taker's
+  acceptance of it awaits the maker's answer makes the venue withdraw that
+  acceptance. `quote` and `bid` now throw `AcceptancePendingError` (`code`
+  `ACCEPTANCE_PENDING`, with `rfqId`, `quoteId` and `deadline`), publishing
+  nothing, on an RFQ where this maker holds an unanswered acceptance, and
+  `onRfq` holds such an RFQ back until the acceptance is answered or its
+  deadline passes. A restarted maker that quotes every RFQ `onRfq` hands it no
+  longer withdraws the acceptances its snapshot carries.
+- `quote` and `bid` start the maker stream if needed and wait until it is live,
+  so the pending acceptances are known, and check again just before publishing.
+  After a snapshot that truncated `acceptances`, or a stream resumed from a
+  cursor (its replay has no end marker, and an acceptance delivered before the
+  saved cursor is not replayed), they and `onRfq` also wait until
+  `GET /v1/makers/{maker_id}/acceptances` has been read in full. While that
+  read fails, `quote` and `bid` throw its error and `onRfq` offers nothing,
+  retrying every second. That read needs `quote:read`, one of the maker
+  scopes. Acceptance deadlines are compared on the venue clock.
+- `cancelQuote`: `ACCEPTED` means this maker already confirmed the quote.
+  Cancelling a quote whose acceptance awaits an answer withdraws the
+  acceptance; prefer `confirm(acceptance, "DECLINE")`.
+### Added
+
+- `reduceCollateral` returns the job's `idempotencyKey`. Without
+  `signTransaction`, sign the returned `transaction` yourself and submit it to
+  `POST /v1/makers/{maker_id}/operations/{operation_id}/self-funded-transaction`
+  under that same `Idempotency-Key`, the only one the route admits for the job.
+  Before, a job returned without `signTransaction` could not be finished.
+
+### Changed (example)
+
+- `examples/node-bot.mjs` bids on cash-outs only to buy back its own positions
+  (a transfer is paid from the maker wallet's own account balance, which it
+  does not fund) and confirms only while its `willing(acceptance)` check holds.
+
+## 0.59.0
+
+Say where the cash is after a bridged entry that did not trade (TT-2219).
+Generated from contract 160; no API change.
+
+### Added
+
+- `AcceptanceResult.bridged` (`BridgedCash`: `{ amount, landed }`, amount in
+  USDC base units) for an entry that bridged from HyperCore, whatever its
+  status. Unless the entry's operation `COMMITTED`, that cash is in the
+  HyperEVM wallet, not on HyperCore: the next entry spends it first, or
+  `returnToCore` moves it back. `landed` is `"yes"` only on Hyperliquid's
+  `ok`; with no answer, a `processed` nonce (a lost refusal spends it too) or
+  after `recoverAcceptance` it is `"unknown"`.
+- An accept refused after the bridge (an `ApiError` that cannot still run,
+  such as `QUOTE_EXPIRED`) and a `BRIDGE_LATE` `EntryError` carry the same
+  `bridged`; `normalizeError` copies it to `NormalizedError.bridged`.
+
+## 0.58.0
+
+An opt-in maker quote lease, so takers stop spending their quote window on a
+maker that has gone quiet (TT-2229). Generated from contract 160.
+
+### Added
+
+- Maker (`createMaker`): `keepQuoteLease(leaseMs, onError?)` renews the lease
+  now and every third of `leaseMs` until the returned stop function, `close()`
+  or another `keepQuoteLease` call. `renewQuoteLease(leaseMs)`
+  (`PUT /v1/makers/{maker_id}/quote-lease`, 1000 to 60000 ms) arms or renews it
+  once and answers `{ lease_ms, expires_at }`; `releaseQuoteLease()`
+  (`DELETE`) disarms it and answers `{ released }`.
+- Once a lease lapses, the venue cancels each open quote of the maker that no
+  taker is accepting, and each one it publishes after, until it renews or
+  releases the lease. Takers see `QUOTE_REMOVED` with `CANCELLED`, which
+  `watchQuotes` and `bestQuote` already honour. An acceptance already under way
+  runs to its confirm deadline as before. A maker without a lease sees no change.
+
+## 0.57.0
+
+Partner helpers from the Liquid dogfood run (TT-2224). Generated from contract
+159; no API change.
+
+### Changed
+
+- `stream.status === "live"` after a resumed account stream means the replay
+  has been applied. With publication freshness (the account default) the
+  stream stays `connecting` through the replayed events and goes live at the
+  first publication checkpoint, which the venue sends only after them. A
+  stream without publication freshness (the maker default) has no such marker
+  and is still live once subscribed. `stream.live()` and the flows wait the
+  same way, up to one 1 s heartbeat longer on a resume.
+- A withdrawal or return to HyperCore with an unread balance throws
+  `BalanceUnknownError` (`component`: `VAULT_FREE` or `WALLET_USDC`), and a
+  deployment without exits to HyperCore (staging) throws
+  `ExitUnavailableError` from `signCoreExit`, `exitToCore`, `signReturnToCore`
+  and `returnToCore`, before anything is signed. Both used to be plain
+  `Error`s. `sendCoreExit` turns the venue's 503 `CORE_EXIT_UNAVAILABLE`,
+  which it answers only where no exit runs, into `ExitUnavailableError` (the
+  refusal as `cause`). `signReturnToCore` reads the exit route before it signs
+  the deposit leg. Entries still throw `EntryError` `BALANCE_UNKNOWN`.
+
+### Added
+
+- `spendableCash(balance)` and `totalis.spendableCash()`: `{ vault, wallet,
+  total }` from `GET /v1/me/balances`, the reservation-aware figures the SDK
+  plans with. Each is `null` while unknown, never 0.
+- `netPayout(quote)`, `netCashout(bid, position)`, `netOfProfitFee` and
+  `netStake`: what the user actually receives, by the vault's fee rules. The
+  profit fee is `floor((amount - net_stake) * fee_bps / 10000)` on a settlement
+  payout or sell-back price above the net stake; a transfer pays its price in
+  full. A quote with payout 9.18 USDC on a 3 USDC stake nets 9.118140 USDC.
+- `normalizeError(error)`: any SDK failure as `{ code, message, retryable,
+  retry, requestId, status, mayStillRun, resend, cause }`. `mayStillRun` is
+  true when the command may have reached the venue (a lost response, an abort
+  or timeout in flight, `BACKOFF` after the resends, a proxy 5xx). Also on
+  `/errors`, with the error classes.
+- `createUiAdapter(totalis, { onInvalidate, onCatalogStale })`: quotes with the
+  best one (`watchQuotes`), the venue clock (`serverNow`, `secondsLeft`),
+  `readInvalidated` revisions (and every resource each time the stream goes
+  live) for a query cache, and a catalog refresh only for a newer
+  `catalog_generation` than `catalogLoaded`. No framework dependency.
+- `/maker`: `makerReadiness(client)` reads `GET /v1/me/maker`, admits an
+  indexed or self-service `PENDING` maker with `POST /v1/me/maker`, and
+  answers `NOT_INDEXED` instead of a 404 while the open transaction is not
+  indexed yet; `waitForMaker(client)` reads again until it is.
+
+## 0.56.0
+
+An eligibility filter on the market list (TT-2226). Generated from contract
+158.
+
+### Added
+
+- `eligibility` on `GET /v1/markets` (`ENABLED` or `DISABLED`) keeps only
+  markets in that state. A page can be short or empty while `has_more` is
+  true, and the cursor is bound to the filter.
+
+## 0.55.0
+
+Cash-out RFQs carry the position's stake and payout (TT-2228). Generated from
+contract 157.
+
+### Added
+
+- `CashoutRfq` and the cash-out `RFQ_CREATED` payload require `net_stake` and
+  `payout`, atomic USDC strings: the position's `tickets(position_id).stake`
+  (after the taker fee) and `.payout`. The vault fixes both when the position
+  opens, so they hold at `decision_block`. A maker can price a transfer
+  without reading the ticket.
+
+## 0.54.0
+
+Anonymous reads refuse query parameters they do not take (TT-2223).
+Generated from contract 155. No code change for callers.
+
+### Changed
+
+- A malformed query, a repeated parameter or one the operation does not list
+  is 400 `INVALID_QUERY` on every anonymous read. `field_violations` names an
+  unlisted parameter as `UNEXPECTED`, and a repeated one or a malformed value
+  (`limit=%GG`) as `INVALID`; a key that does not decode names nothing. This
+  covers markets, questions, series, history, recurring rounds, discovery,
+  search, taxonomy, market stats, config, definitions, deployment, suggested
+  Combo, RFQs and the market stream handshake. `/v1/markets?search=BTC` used to
+  answer an unfiltered page.
+- `getDeployment`, `getSuggestedCombo`, `getMarketStats`, `getMarketDataConfig`
+  and `getMarketDefinitions` gain a 400 response; the rest list
+  `INVALID_QUERY` in `operationErrors`.
+
+## 0.53.1
+
+The package ships its examples, and the README matches what the SDK does
+(TT-2222). Generated from contract 154. No code change for callers.
+
+### Changed
+
+- `examples/` is in the package. The README keeps the partner guide; the
+  repository's development and release notes moved to `CONTRIBUTING.md`,
+  which is not published.
+- A withdrawal kept across a restart stores the whole `signWithdrawal`
+  record, `{ idempotencyKey, account, body }`; without `account`,
+  `sendWithdrawal` posts it and then throws "different terms".
+- `waitForOperation` resolves at `REVERTED` and `EXPIRED_UNEXECUTED` as well
+  as `COMMITTED`; the README checks `status`.
+- `onRfq` delivers each open RFQ once per subscription; another subscription
+  or a restart delivers the still-open ones again, and quoting again replaces
+  the earlier quote.
+- `examples/browser-wallet.html` runs from a checkout of the SDK, not from an
+  installed copy; an app imports `browser-wallet.mjs` through its bundler.
+- The `tpk_` server-key guards throw at runtime only; they cannot keep a key
+  out of a bundle.
+- The README names staging's stream host, `wss://hip4-ws-staging.totalis.trade`.
+
+## 0.53.0
+
+Markets say whether a Combo can take them and who deployed them; Esports is
+its own category (TT-2196). Generated from contract 154.
+
+- `Market.combo`: `{ state: "OPEN" }`, or `CLOSED` with `reason`
+  (`EXCLUDED`, `UNLISTED_DEPLOYER`, `OUTSIDE_WINDOW`) and `opens_at`, when an
+  `OUTSIDE_WINDOW` market joins Combos. RFQs refuse legs that are not `OPEN`.
+- `Market.deployer`: `{ name, address }`; Hyperliquid's own markets have no
+  address, deployers Totalis does not list have no name and stay out of browse.
+- `Category` adds `Esports`; `lol` moves there from Sports. Switches over
+  categories need the new case.
+
+## 0.52.0
+
+`getProfitLeaderboard` reads the top 10 traders by profit, each as their
+Portfolio Profit/Loss card shows it, with the same `range` and `kind` as
+`getVolumeLeaderboard` and the same signed-in caller (TT-2157). Each trader
+carries `profit` in atomic USDC. Generated from contract 153. Additive.
+
+## 0.51.1
+
+Staging streams connect to their own host (TT-2204). Generated from contract
+152. No code change for callers.
+
+### Changed
+
+- `publicStreamServers.staging` is `wss://hip4-ws-staging.totalis.trade`, so
+  `realtimeUrl("staging")` and `marketStreamUrl("staging")` open there. The API
+  host still serves both paths.
+
+## 0.51.0
+
+Maker withdrawals from the dashboard or a bot (TT-2189). Generated from
+contract 152. Additive.
+
+- `GET /v1/makers/{maker_id}/withdrawal` and `maker.withdrawal()`: the
+  pending vault withdrawal (`amount`, `destination`, `ready_at`), whether
+  `executeMakerWithdraw` would succeed now, and its `blockers`
+  (`WITHDRAW_NOT_READY`, `VAULT_PAUSED`, `MAKER_SHORT`, `INSUFFICIENT_FREE`).
+  `pending` is null when none is live.
+- `GET /v1/makers/{maker_id}/capital` now reports `MAKER_WITHDRAW` as
+  available: the amount a new request may ask for (`free_after_pending`), or
+  null with `MAKER_WITHDRAW_PENDING` while a request is live.
+- The maker wallet still sends `requestWithdraw`, `executeWithdraw` and
+  `cancelWithdraw` from `maker.controller()` itself and pays the gas in HYPE.
+
+## 0.50.0
+
+Breaking: `getVolumeLeaderboard` needs a signed-in participant session;
+anonymous calls and API keys are refused. It returns up to 10 traders and
+takes `kind`: `ALL` (the default), `SINGLES` for HyperCore fills alone or
+`COMBOS` for Combo stakes alone, each with its own top 10, and the answer
+names its `kind`. Each trader carries `avatar_seed`, so a client can draw the
+same generated avatar as for `GET /v1/me`. Both are optional in the answer, so
+servers before contract 151 may omit them. Generated from contract 151.
+
+## 0.49.0
+
+Maker dashboard reads (TT-2188). Generated from contract 150. Additive.
+
+### Added
+
+- `GET /v1/makers/{maker_id}/quote-history` (`listMakerQuoteHistory`): every
+  quote the maker published in `[from, through)`, newest first, with its
+  status (`OPEN`, `AWAITING_CONFIRMATION`, `ACCEPTED`, `FILLED`, `FAILED`,
+  `DECLINED`, `TIMED_OUT`, `CANCELLED`, `REPLACED`, `EXPIRED`, `NOT_SELECTED`,
+  `RFQ_CANCELLED`), stake, net stake, payout, maker risk or cash-out price,
+  submitted/accepted/resolved times and the period's `fill_rate`. Filters
+  `status` and `kind`; cursor paged.
+- `GET /v1/makers/{maker_id}/exposure` (`getMakerExposure`): the maker's open
+  book by outcome: YES/NO, gross, net and worst-case exposure, netting
+  savings, and what awaits settlement.
+- Positions carry `maker_pnl`, `maker_result` (`WON`, `LOST`, `EVEN`) and
+  `protocol_fees`; position lists filter on `maker_result`.
+- Performance carries `history_from` (the earliest complete `from`),
+  `won_ticket_count`, `lost_ticket_count`, `even_ticket_count`,
+  `gross_winning_pnl` and `gross_losing_pnl`; each `series` point carries
+  `closed_ticket_count` and `net_trading_pnl_change` since the previous point.
+
+## 0.48.0
+
+A stream closes `STREAM_REPLACED` when its owner opens a fifth live stream,
+which replaces the owner's oldest (TT-2185). `TotalisStream` does not
+reconnect; it emits a `StreamClosedError` with that reason, since reconnecting
+would replace the owner's oldest stream in turn. Generated from contract 149,
+whose error schema gains the reason.
+
+## 0.47.0
+
+A maker is one wallet, its controller and its quote signer (TT-2181).
+Breaking: `maker.controller()` / `controllerTransactions` no longer build
+`setQuoteSigner`. Open a maker with `openMakerVaultTransaction(deployment,
+wallet)` sent from that same wallet; nothing fills without its confirmation
+signature, so stop confirming to stop filling. Generated from contract 148.
+
+## 0.46.0
+
+`getMarketDefinitions` reads the native names and descriptions of every
+question and outcome in the current catalog, with the network's reviewed
+outcome templates. Generated from contract 148. Additive.
+
+## 0.45.0
+
+Fund a Combo from HyperCore and resume every money flow after a reload or a
+killed app (TT-2174). Generated from contract 147. Breaking: the native
+HyperCore withdrawal routes (`/v1/hypercore/withdrawals*`) and their types are
+gone; sign a `sendAsset` and submit it to Hyperliquid (or a relay) yourself,
+since Hyperliquid's first answer settles it.
+
+### Added
+
+- `signEntry({ quote, core?, sourceDex?, acceptanceId?, hypercoreNonce? })`:
+  signs a Combo entry as a plain JSON record. Funding is planned from current
+  balances: free vault cash, then the wallet, then a Core to HyperEVM bridge.
+  A vault balance the venue marks `STALE` or `UNKNOWN` throws `EntryError`
+  `BALANCE_UNKNOWN`; a wallet without a current read is authorized for the
+  whole shortfall and the venue checks it.
+  `core: null` means your Core read failed: an entry that needs the bridge
+  throws `EntryError` `BALANCE_UNKNOWN`. Without `core` it funds from the
+  wallet alone.
+- `signCashout({ quote, acceptanceId? })`, and `sendAcceptance(signed,
+  { transport?, signal? })` / `recoverAcceptance(signed, { wait? })` for either
+  record. A refused bridge throws `EntryError` and posts nothing. Only
+  `sendAcceptance` sends the bridge, within the quote's life; recovery never
+  sends it or signs again, and only reads and fences the acceptance. An accept answer
+  that does not echo the record's acceptance, RFQ and quote IDs throws.
+  `recoverAcceptance(signed, { wait: false })` returns a `PENDING_CONFIRM`
+  acceptance at once instead of reading it again after the maker's deadline.
+- `signCoreExit` / `sendCoreExit`, `signDeposit` / `sendDeposit` (sponsored
+  `POST /v1/me/deposits`), and `returnToCore` with `signReturnToCore` /
+  `sendReturnToCore`: deposit the wallet USDC, wait for it to commit, then exit
+  it with the free vault cash. External wallets only: an embedded wallet's
+  vault cash is already swept to HyperCore, so it throws there.
+- `wallet_kind` (`EMBEDDED` or `EXTERNAL`) on `GET /v1/me`.
+- `openPosition` takes `core`, `sourceDex`, `transport` and `onSigned`;
+  `cashOut` takes `onSigned`. Both return the record's IDs as before.
+- Hyperliquid bridge helpers: `hyperliquidNetwork`, `bridgeAction`,
+  `sendAssetTypedData`, `signSendAsset`, `hypercoreSignature`,
+  `hypercoreNonce`, `usdcText`, `hyperliquidExchange`, `submitHypercore`,
+  `settleHypercore`, `classifyHypercoreAnswer`, `hyperevmUsdcBridge`,
+  `bridgeGasBuffer`.
+
+### Fixed
+
+- A retried Core exit resends the same signed body under its exit ID. Before,
+  `exitToCore` signed again, which the venue refused as
+  `IDEMPOTENCY_KEY_REUSED`.
+
+### Changed
+
+- `openPosition` and `cashOut` cancel their RFQ when signing fails, or when an
+  entry stops before its accept is posted.
+- The lost-answer fence also holds when the cancel answers `NOT_FOUND`, and
+  holds on 409 only for `RFQ_NOT_CANCELLABLE`. After `STATE_CONFLICT` the RFQ
+  is still open, so a still-absent acceptance throws instead of ending
+  `NOT_ADMITTED`.
+
+## 0.44.0
+
+New subcategory filters: Champions League (`ucl`) and Europa League (`uel`)
+under Sports, HYPE (`hype`) under Crypto. Generated from contract 146.
+Additive.
+
+## 0.43.0
+
+High-frequency template rounds, like BTC every 15 minutes, read as recurring
+rounds. Generated from contract 145. Additive.
+
+### Added
+
+- `RecurringSeries.stream`: the deployer template stream (`stream_id`, `venue`,
+  `template`, `price_description`, `seconds`) behind a recurring round, or
+  `null` for a native recurring series.
+
+### Changed
+
+- `recurring_round` on market detail, and the market recurring-round route,
+  also describe a qualified stream round. Its `target_price` is the template
+  threshold, and it settles YES only strictly above it. Such a market has no
+  `series_id`.
+
+## 0.42.0
+
+The public volume leaderboard (TT-2157). Generated from contract 144.
+Additive.
+
+### Added
+
+- `GET /v1/leaderboard/volume` (`getVolumeLeaderboard`): up to 100 traders by
+  username and volume in 10^-8 USDC, for `range` `1W` (default) or `ALL`.
+
+## 0.41.0
+
+Streams connect to a stream host apart from the API host (TT-2113). Still
+contract 143. Additive, with one default change.
+
+### Added
+
+- `streamBaseUrl` on `createTotalis`, `createMaker` and `TotalisStream`: the
+  WebSocket origin, apart from `baseUrl` (the REST origin).
+- `publicStreamServers`, `streamServerUrl()`, `marketStreamUrl()` (joins
+  `fallback_stream` from `/v1/market-data/config` to the stream origin) and
+  `marketStreamProtocol` (`totalis.market.v2`).
+- `realtimeUrl()` takes an optional third argument, `streamBaseUrl`.
+
+### Changed
+
+- In production, streams connect to `wss://hip4-ws.totalis.trade` by default.
+  REST stays on `https://hip4-api.totalis.trade`, which still serves both stream
+  paths during the migration. A `baseUrl` without `streamBaseUrl` keeps
+  deriving the stream from `baseUrl`, as before; to go back to the API host,
+  pass `streamBaseUrl: "wss://hip4-api.totalis.trade"`.
+- A `drain` frame's `retry_after_ms` is a floor: the stream reconnects after
+  between one and two times the hint, so the sockets one drain closes do not
+  all return at once.
+
+## 0.40.0
+
+A first exit to a HyperCore account that does not exist yet can pay its
+activation fee. Generated from contract 143.
+
+### Added
+
+- `activation_fee_accepted` on the `POST /v1/core-exits` command and on every
+  `CoreExit`.
+- The `CORE_ACCOUNT_ACTIVATION_REQUIRED` error code.
+- `exitToCore({ activationFeeAccepted: true })` sends that consent.
+
+## 0.39.0
+
+The Core funding float is dropped. Generated from contract 142. Breaking.
+
+### Removed
+
+- The `PENDING_FUNDING` acceptance status. Only Core funding reached it.
+- The retired `CORE_FUNDING_UNAVAILABLE`, `CORE_FUNDING_CONFLICT` and
+  `CORE_VAULT_RESERVATION` error codes.
+
+## 0.38.0
+
+Core funding is retired. Generated from contract 141. Breaking.
+
+### Removed
+
+- `GET /v1/me/core-fundings` (`activeCoreFundings`) and
+  `GET /v1/quotes/{quote_id}/acceptance/funding` (`getCoreFunding`), with the
+  `core-funding` schemas.
+- `CORE` and `COMBINED` accept funding. `funding` on an accept is a `WALLET`
+  authorization only; any other kind is `INVALID_REQUEST`. To spend Core USDC,
+  bridge it to the wallet first.
+- The `CORE_FUNDING_UPDATED` stream event.
+
+### Changed
+
+- `CORE_FUNDING_UNAVAILABLE`, `CORE_FUNDING_CONFLICT` and
+  `CORE_VAULT_RESERVATION` stay registered but are retired; no route returns
+  them.
+
+## 0.37.0
+
+Usernames are optional, changeable, and name each account's /r/ link. Generated
+from contract 140. Additive, with one behaviour change.
+
+### Added
+
+- `POST /v1/me/username` (`generateUsername`): an account that skipped choosing
+  a username takes a generated one (`trader_` and six characters), returned as
+  `GeneratedUsername`. An account with a username gets its own back. If every
+  generated name it tries is taken, it answers `USERNAME_TAKEN`; try again.
+
+### Changed
+
+- `PUT /v1/me/username` (`setUsername`) also changes an existing username, so it
+  no longer answers `USERNAME_ALREADY_SET`. A Totalis campaign link, a reserved
+  platform name or another account's earlier link name is `USERNAME_TAKEN`.
+- `getUsernameAvailability` reports a name Totalis keeps for its own links,
+  such as `instagram`, as `TAKEN`.
+- `setUsername` and `generateUsername` answer `INVALID_REQUEST` to an
+  `Idempotency-Key` stamped more than 5 minutes ahead of server time, since the
+  keys put username changes in order.
+
+## 0.36.0
+
+Profit/Loss series for Portfolio and backend-owned Chance and Value (TT-2004).
+Generated from contract 139. Additive.
+
+### Added
+
+- Available market references carry nullable `chance`, `chance_basis`,
+  `mark`, `last_trade` and `last_trade_at`. `chance` is the crowd view (mid
+  within 10c, last trade inside a 10-50c spread, else null), and
+  `chance_basis` says which (`MID` or `LAST_TRADE`); `mark` is what a held
+  share is worth (chance, else best bid). Read them instead of deriving them
+  from the book.
+- `GET /v1/me/pnl` (`getAccountPnl`): the cumulative trading P&L of the
+  account Portfolio shows, for `range` `1D`, `1W`, `1M` (default) or `ALL`.
+  `points` are `{at, pnl}` in atomic USDC, cumulative since `tracked_since`;
+  a window's change is its last point minus its first. A `pnl` of `null` is
+  unknown, never zero.
+
+## 0.35.0
+
+Onboarding picks a username and an avatar (TT-1986). Generated from contract
+138. Additive.
+
+### Added
+
+- `getUsernameAvailability` (`GET /v1/me/username/availability?username=`)
+  answers `UsernameAvailability` `{available, reason}`, where `reason` is
+  `INVALID`, `NOT_ALLOWED`, `TAKEN` or `null`. The account's own username is
+  available.
+- `setAvatar` (`PUT /v1/me/avatar`) with `AvatarRequest` `{avatar_seed}` sets
+  the seed the account's generated avatar is drawn from.
+
+## 0.34.0
+
+Followers survive a failed recovery read (TT-1902). Additive.
+
+### Fixed
+
+- `withdraw`, `sendWithdrawal`, `waitForWithdrawal`, `waitForOperation`,
+  `waitForCoreExit`, `reduceCollateral`, and the quotes read after a truncated
+  snapshot no longer reject when a recovery read fails. Each recovery read is
+  sent once, and the follower alone decides when to read again. A lost read
+  (including a body cut off mid-response), a `BACKOFF` error, or a 500, 502,
+  503 or 504 without the venue's error envelope is read again, one read at a
+  time, after the client's `retry` backoff and jitter, or the response's
+  `Retry-After` capped at `maxDelayMs` when that is longer. A `Retry-After` of
+  zero or a past date never skips the backoff. The backoff restarts after any
+  successful read. A stream update or reconnect during the backoff, or during
+  a read that then fails, reads at once; during a `Retry-After` wait it reads
+  when the wait ends. Settling, the
+  caller's abort and `close()` stop it and abort the read in flight. A `NEVER`
+  or `REFRESH` refusal (such as 404 or 401), any other 5xx without the
+  envelope (such as 501), or an error thrown by your own code (a chooser or
+  token provider) still rejects.
+- `retry: false` turns off the request layer's resends; followers still read
+  again, with the default backoff.
+- Resent requests keep the client's `mode`, `integrity`, `referrer`,
+  `referrerPolicy` and `keepalive` instead of falling back to fetch defaults.
+
+### Added
+
+- `follow(stream, read, done, wake, signal, retry)`: `read` receives an
+  `AbortSignal` that aborts when the follow ends, and `retry` sets the
+  recovery backoff.
+
+## 0.33.0
+
+Wallet USDC deposits are back (TT-1788). Generated from contract 137. Additive.
+
+### Added
+
+- `POST /v1/me/deposits` (`createDeposit`): a browser session moves USDC
+  from its Privy embedded wallet into its Totalis balance. Send a
+  `DepositEnvelope` whose command is the wallet's signed USDC
+  `ReceiveWithAuthorization` with the vault as payee
+  (`receiveWithAuthorizationTypedData`); Totalis relays it and pays the gas.
+  The 202 `DepositAccepted` carries the queued `operation_id`. A deposit moves
+  at least 1 USDC; an account gets at most 5 an hour (`RATE_LIMITED` with
+  `Retry-After`). API keys cannot call it.
+
+## 0.32.1
+
+Market stats cache lifetime (TT-1993). Generated from contract 136. No code
+change for callers.
+
+### Changed
+
+- `GET /v1/market-stats` `Cache-Control` is `public, max-age=N` with N at most
+  30 and never past the snapshot's `valid_until`, or `no-store` within a second
+  of expiry. Its generated header type is `string`.
+
+## 0.32.0
+
+Vault v1 (TT-1959). Generated from contract 135. **Breaking** for makers that
+open or fund a vault with the SDK.
+
+### Changed
+
+- `openMakerVaultTransaction(deployment, quoteSigner)`: the controller argument
+  is gone. The sending wallet becomes the controller, a controller opens one
+  maker, and the vault's `makerOf(controller)` returns its maker ID.
+- `controllerTransactions(deployment, makerId, controller)`: `deposit` encodes
+  `depositMaker(makerId, controller, amount)`, which the vault refuses unless
+  `controller` is the maker's current controller. `maker.controller()` reads
+  it from `GET /v1/makers/{maker_id}/capital`.
+- `GET /v1/makers/{maker_id}/funding-transaction` returns the three-argument
+  `depositMaker` call bound to the projected controller, or 404 for a maker
+  the projection has not seen.
+- Position and cash-out RFQ legs allow up to 100 (`maxItems`), the vault's leg
+  limit. Entry RFQs and quotes keep their 50-leg request limit.
+- `AWAITING_SETTLEMENT` also covers a position whose payout, with every
+  unresolved leg counted as a win, already rounds down to zero.
+- New error code `COLLATERAL_REDUCTION_UNAVAILABLE` (503, `BACKOFF`):
+  `POST /v1/makers/{maker_id}/collateral-reductions` refuses it, without
+  queueing a job, while the vault has no attestor. Vault v1 starts that way.
+
+## 0.31.0
+
+Every account has a generated avatar (TT-1975). Generated from contract 134.
+Additive.
+
+### Added
+
+- `VenueIdentity.avatar_seed`: a random UUID fixed when the account is created,
+  for drawing the account's avatar. Optional, so servers before contract 134
+  may omit it.
+
+## 0.30.0
+
+Partner admission needs the wallet's consent (TT-1688). Generated from contract
+133. **Breaking** for partner servers.
+
+### Changed
+
+- `createPartnerServer(...).admitWallet(address, consent)`: the consent is
+  required. A consent for another partner, wallet, environment or chain, or an
+  expired one, is `INVALID_SIGNATURE`.
+
+### Added
+
+- `signAdmissionConsent({ signer, partner, environment, chainId })`: in the
+  partner's frontend, the wallet signs that the partner may open its account.
+  `admissionConsentMessage` is the exact message.
+
+## 0.29.0
+
+Funding helpers for external wallets (TT-1685). Still contract 132. Additive.
+
+### Added
+
+- `exitToCore({ amount, purpose? })`: the wallet signs an Exit to the CoreExit
+  router and the exit is sent once under its exit ID. `waitForCoreExit(exitId)`
+  follows it on the stream until it is credited on HyperCore, and rejects
+  `RECOVERED`, `FAILED` or `ABANDONED`. External wallets have no background
+  sweep, so this is how their cash reaches HyperCore before a native order.
+- `directDepositCalls(amount)`: the approve and `depositUser(account, amount)`
+  transactions for a self-paid HyperEVM deposit.
+
+## 0.28.0
+
+Wallet sign-in and partner credentials for external wallets (TT-1685). Still
+contract 132. Additive.
+
+### Added
+
+- `./wallet-session`: `signInWithWallet` asks for a challenge, checks it is
+  the Totalis sign-in for this origin, wallet and request, has the wallet sign
+  it, and returns the session. `signOutWallet` ends it.
+  `checkSignInChallenge` is the check on its own.
+- `./partner`: `createPartnerServer({ serverKey }).admitWallet(address)`, for a
+  partner's server. It refuses to run in a browser.
+- `partnerKey` on every client: the publishable `tpb_` key, sent as
+  `X-Totalis-Partner`. A `tpk_` server key is refused.
+- `examples/partner-frontend.mjs` and `examples/partner-server.mjs`.
+
+## 0.27.0
+
+Partners admit wallets (TT-1678). Generated from contract 132. Additive.
+
+### Added
+
+- `admitPartnerWallet` (`POST /v1/partner/wallet-admissions`): a partner's
+  server, with its secret `tpk_` key, admits a wallet so the wallet's next
+  `createWalletSession` creates its account. Server-side only; never put the
+  key in a browser.
+
+## 0.26.0
+
+Browse contract 4 groups IPO market-cap ladders and sports games (TT-1853).
+Generated from contract 131. Additive for contracts 2 and 3.
+
+### Added
+
+- `./browse`: contract `"4"` (query parameter, header, `totalis.market.browse.v4`
+  stream). Contract 4 cards add `DiscoveryGameItem` (`kind: "GAME"`, `game:<key>`
+  ID, `game` with `sport`, `scheduled_start`, `participants` and the
+  `winner_outcome_ids`, `spread_outcome_ids`, `total_outcome_ids` that partition
+  its markets) and SERIES cards whose `series` is an `IpoMarketCapSeries`
+  (`template: "COMPANY_IPO_MARKET_CAP"`, `company`, `listing_deadline`).
+- `getMarket`: optional `contract` query parameter. With `"4"` the detail adds
+  `game` (`MarketGame` or null) and sets `series_id` for IPO ladder members.
+
+### Changed
+
+- `Series.series` and `DiscoverySeriesItem.series` are `SeriesDescriptor`, a
+  union discriminated by `template`: `PriceSeries` or `IpoMarketCapSeries`.
+  Contracts 2 and 3 never return an `IpoMarketCapSeries`; narrow on
+  `template` before reading `underlying`.
+
+## 0.25.0
+
+Externally owned wallets can sign in (TT-1676). Generated from contract 130.
+Additive.
+
+### Added
+
+- `createWalletChallenge` (`POST /v1/auth/wallet-challenges`) returns the
+  EIP-4361 message for a wallet to sign with `personal_sign`. It answers
+  `WALLET_CONTRACT_UNSUPPORTED` for an address with contract code.
+- `createWalletSession` (`POST /v1/auth/wallet-sessions`) exchanges the
+  signature for a `Bearer` session for the wallet's existing account. The
+  session lasts at most 30 days and ends after 7 days without an API request.
+  A wallet that is not an account's own wallet gets `ACCESS_REQUIRED`.
+- `endWalletSession` (`DELETE /v1/auth/wallet-sessions/current`) logs that
+  session out.
+- Error code `WALLET_CONTRACT_UNSUPPORTED`.
+
+## 0.24.0
+
+Accounts have a public username, set once (TT-1953). Generated from contract
+129. Additive.
+
+### Added
+
+- `setUsername` (`PUT /v1/me/username`) with `UsernameRequest`, and the errors
+  `USERNAME_NOT_ALLOWED`, `USERNAME_TAKEN` and `USERNAME_ALREADY_SET`.
+- `VenueIdentity.username`: the account's username, or `null` until it is set.
+  Optional, so servers before contract 129 may omit it.
+
+## 0.23.0
+
+A price series links its sibling expiries (TT-1907). Generated from contract
+128. Additive.
+
+### Added
+
+- `Series.siblings`: the other current series on the same network, template and
+  underlying, as `SeriesSibling` (`series_id`, `expiry`) by expiry ascending, up
+  to 64. Optional, so servers before contract 128 may omit it.
+
+## 0.22.0
+
+Settlement credits have their own read, and no read writes. Needs contract 127.
+Additive.
+
+### Added
+
+- `getHypercoreSettlementCredits` (`GET /v1/hypercore/settlement-credits`,
+  browser session only): the account's retained USDC settlement credits from
+  storage, with no Hyperliquid read. Same mainnet and linked-account checks as
+  `getHypercorePortfolio`.
+
+### Changed
+
+- `getAcceptance` only reads. An unanswered acceptance that has lapsed reads as
+  `TIMED_OUT` or `CANCELLED` before the venue stores it.
+- `getHypercorePortfolio` and `getHypercoreWithdrawal` only read. Settlement
+  credits come from the background observer, so a new settlement appears once
+  the observer has passed it; a withdrawal advances when the background
+  reconciler resolves it.
+
+## 0.21.1
+Settlement credits name the market they settled (TT-1929). Generated from
+contract 126; the types are unchanged.
+### Changed
+- `Activity.fill` is set on `CREDIT` rows: the outcome and side that settled,
+  `direction` `SELL`, `size` the shares settled and `price` what one share of
+  that side paid (`1` for a win, `0` for a loss, in between for a fractional
+  settlement). `size` times `price` is the payout before the fee effect.
+## 0.21.0
+
+A session admits its maker from its linked wallet, with no signature. Needs
+contract 125, which drops the signed registration. Breaking only for callers of
+the removed operations.
+
+### Added
+
+- `admitOwnMaker` (`POST /v1/me/maker`, browser session only): admits the
+  lowest maker whose controller and quote signer are both the account's
+  qualified linked wallet and returns the `GET /v1/me/maker` body (`OwnMaker`).
+  No body and no `Idempotency-Key`; a repeat returns the current ownership.
+  `404 NOT_FOUND` until such a maker is indexed, `409 STATE_CONFLICT` when the
+  wallet already has a profile for a different maker.
+
+### Removed
+
+- `createMakerOnboardingChallenge`, `registerMaker` and `getMakerRegistration`
+  (`POST /v1/maker-onboarding/challenges`, `POST
+  /v1/maker-onboarding/registrations` and `GET
+  /v1/maker-onboarding/registrations/{maker_id}`), with the `ChallengeEnvelope`,
+  `Challenge`, `ProofEnvelope` and `Profile` maker-access schemas. `OwnerProof`
+  stays: API key issuance uses it.
+- `MakerAccess.expires_at`, which was always `null`: owner access does not
+  expire.
+
+## 0.20.0
+
+Maker dashboard access comes only from owning the maker. Needs contract 124,
+which drops the legacy dashboard grants. Breaking only for callers of the
+removed operations.
+
+### Removed
+
+- `createMakerAccessChallenge`, `consumeMakerAccessProof`,
+  `grantMakerMembership` and `revokeMakerMembership` (`POST
+  /v1/makers/{maker_id}/access/challenges`, `POST .../access/proofs`, `PUT` and
+  `DELETE /v1/makers/{maker_id}/members/{participant_id}`), with their
+  `MembershipRequest` and `AccessChallenge` schemas and the unused `MakerList`.
+- `MANAGE_ACCESS` from `Permission`.
+
+### Changed
+
+- `MakerAccess.expires_at` is always `null`: owner access does not expire.
+- The README and `examples/node-bot.mjs` sign with your exported Totalis
+  wallet key, `TOTALIS_WALLET_KEY` (was `QUOTE_SIGNER_KEY`).
+
+## 0.19.0
+
+Activity effects carry their asset, fills carry their trade and positions
+carry what the owner paid (TT-1875, TT-1862). Needs contract 123.
+
+### Added
+
+- `Effect.asset` (`Asset`: `asset_id`, `symbol`, `decimals`). `delta` is in
+  that asset's atomic units: HyperEVM USDC has 6 decimals, HyperCore USDC and
+  HYPE have 8. Never assume 6.
+- `Activity.fill`: outcome, side, direction, size, price, oid and tid on
+  `FILL` and `CONVERSION` rows; null on every other kind.
+- `Position.acquisition_cost`: the gross stake with the entry fee for the
+  opener, or the latest transfer price for a buyer; null when the chain
+  history can't establish it.
+
+### Changed
+
+- Workflow activities (a pending or failed Combo, cash-out or withdrawal) set
+  `occurred_at` to the time the request was made, which later revisions keep.
+- A HyperCore send with a HYPE fee and a spot to perp transfer without a nonce
+  now appear instead of being held back.
+
+## 0.18.0
+
+A quote's `kind` names its terms (TT-1916): `ENTRY`, `SELL_BACK` or
+`TRANSFER`, replacing `CASHOUT`. Needs contract 122, which serves only the new
+shape. Breaking. Terms and signed EIP-712 structs are unchanged.
+
+### Changed
+
+- `Quote` (list quotes, the account snapshot's `quotes`, `QUOTE_CREATED`) is
+  the union of `EntryQuote`, `SellBackQuote` and `TransferQuote`; each carries
+  exactly its own terms (`entry`, `sell_back` or `transfer`), so narrowing on
+  `kind` types the terms.
+- `MakerAcceptance` (`QUOTE_ACCEPTED`, the maker snapshot's `acceptances`,
+  `GET /v1/makers/{maker_id}/acceptances`) is the same three-way union.
+- `CashoutBid` is `SellBackQuote | TransferQuote`; `SellBackQuote` and
+  `TransferQuote` are exported from the root.
+- An RFQ's `kind` stays `ENTRY` or `CASHOUT`.
+
+## 0.17.0
+
+Compact chart closes and a preflight-free browse contract. Needs contract 121.
+
+### Added
+
+- `GET /v1/markets/{outcome_id}/reference-closes`
+  (`getMarketReferenceCloses`): `REFERENCE_PRICE_OHLC` history reduced to
+  closes. `runs` holds `CloseRun` tuples `[minute, close, minutes]`, with
+  `minute` in Unix seconds; `anchor` is `{ minute, close }`. The parameters,
+  source, scale, `closed_before` and cursor match history, and `limit`
+  counts minutes, not runs.
+- `./browse`: a `contract` query parameter (`"2"` or `"3"`) on discovery,
+  search and taxonomy. It negotiates like `X-Totalis-Browse-Contract` but adds
+  no custom header, so browsers skip the CORS preflight.
+
+### Changed
+
+- `./browse`: `contract` is required and `X-Totalis-Browse-Contract` is
+  optional, so every typed request negotiates and matches its typed response.
+  A header-only caller adds `query: { contract }`; the header may stay if it
+  matches. The server still negotiates on the header alone.
+
+## 0.16.0
+
+Everything the caller owns lives under `/v1/me` (TT-1786). Needs contract
+120, which serves only the new paths. Breaking. Signed EIP-712 structs are
+unchanged.
+
+### Changed
+
+- `POST /v1/positions/{position_id}/cashout` is now
+  `POST /v1/me/positions/{position_id}/cashout` (`createCashout`), which
+  `cashOut` calls.
+- `GET /v1/operations/{operation_id}` is now
+  `GET /v1/me/operations/{operation_id}` (`getOperation`), which
+  `waitForOperation` rereads, for personal and maker keys alike.
+- `POST /v1/withdrawals` is now `POST /v1/me/withdrawals` (`createWithdrawal`),
+  which `sendWithdrawal` and `withdraw` call.
+- `GET /v1/withdrawals/{withdrawal_id}` is now
+  `GET /v1/me/withdrawals/{withdrawal_id}` (`getWithdrawal`), the recovery read
+  behind `withdraw` and `waitForWithdrawal`.
+- The `Operation` and `Withdrawal` types are unchanged; only the paths they
+  are keyed on moved.
+
+## 0.15.0
+
+Browse contract 3 groups standalone price-threshold markets into price series
+(TT-1905). Needs contract 119.
+
+### Added
+
+- `./browse`: `X-Totalis-Browse-Contract: "3"`, the `DiscoverySeriesItem`
+  card (`kind: "SERIES"`, `series: {template, underlying, expiry}`, two or more
+  member `markets`) and `series:` item IDs in cards and browse updates.
+  Contract 2 never returns them.
+- `GET /v1/series/{series_id}` (`getSeries`): one price series with every
+  active member plus the most recently listed inactive members, up to 256.
+  Members are `SeriesMarket`s, whose `native_question_id` is always `null`.
+- `series_id` on `MarketDetail`: the series key of a standalone binaryPrice or
+  priceTouch market, else `null`.
+- `totalis.market.browse.v3` stream updates carry contract `"3"` and may name
+  `series:` cards.
+
+## 0.14.0
+
+The API speaks prediction-market vocabulary (TT-1904): quotes, acceptances
+and positions, keyed by `quote_id` and `position_id`, and a v2 stream. Needs
+contract 118, which serves only the new surface. Breaking.
+
+### Changed
+
+- Taker (`createTotalis`): `placeBet` is `openPosition`, `watchBook` is
+  `watchQuotes`, and `release()` is `deployment()` (`GET /v1/deployment`).
+  `openPosition` returns `{ rfqId, acceptanceId, quoteId, positionId, entry,
+  status, operationId, outcome }`; an entry position is named by its quote, so
+  `positionId` is `quoteId`. `cashOut({ positionId })` creates the cash-out RFQ
+  with `POST /v1/positions/{position_id}/cashout` (`POST /v1/rfqs` is
+  entry-only) and returns `{ rfqId, acceptanceId, quoteId, positionId, status,
+  operationId, outcome }`.
+- Accepting is `POST /v1/quotes/{quote_id}/accept` with `{ taker_signature,
+  funding? }`. Its required `Idempotency-Key` is the acceptance ID, a UUIDv7
+  made before the first send and reused for every resend. A lost accept is
+  recovered from `GET /v1/quotes/{quote_id}/acceptance`; `NotAdmitted` is
+  `{ status: "NOT_ADMITTED", quote_id, rfq_id }`.
+- Acceptance status: `PENDING_CONFIRM`, `PENDING_FUNDING` (was `CONFIRMED`),
+  `ACCEPTED` (was `COMMITTED`), `FILLED` and `FAILED` (from the operation),
+  `DECLINED`, `TIMED_OUT`, and `CANCELLED` (was `WITHDRAWN`).
+- Maker (`createMaker`): `withdraw(rfqId, digest)` is `cancelQuote(quoteId)`
+  (`DELETE /v1/quotes/{quote_id}`, answering `{ status }`), `onConfirmation` is
+  `onAcceptance`, and `release()` is `deployment()`. `quote()` posts
+  `{ quote_id, entry }` and `bid()` `{ quote_id, sell_back | transfer }` to
+  `POST /v1/rfqs/{rfq_id}/quotes`; both return `quoteId`. The answer is
+  `POST /v1/quotes/{quote_id}/confirm` with a `decision` and no
+  Idempotency-Key: the quote keys it. Truncated acceptances are paged from
+  `GET /v1/makers/{maker_id}/acceptances`.
+- Legs are `{ outcome_id: "<decimal>", side: "YES" | "NO" }` everywhere, as
+  markets and positions name them. The typed-data builders encode them as the
+  signed `uint32`/`uint8`, and read `position_id` into the signed `ticketId`;
+  digests and signatures are unchanged.
+- Entry RFQs carry `taker` and `stake` (were `taker_address` and
+  `stake_amount`); cash-out RFQs and cash-out terms carry `position_id` (was
+  `ticket_id`). A quote's entry terms are `entry` (was `quote`).
+- Lifecycle fields are `status` (were `state`) on RFQs, operations,
+  withdrawals, collateral reductions (`operation_status`) and stream payloads.
+  RFQs are `OPEN`, `ACCEPTED` (was `SELECTED`), `EXPIRED`, `CANCELLED` (the
+  stream's `EXPIRED` and REST's `CANCELLED` now agree) or `FAILED` (was
+  `CLOSED`); an operation's `DURABLE` is `QUEUED`.
+- The stream is `totalis.realtime.v2`. `StreamOptions.topic` is `subscription`:
+  `{ type: "account", open_rfqs? }` or `{ type: "maker", maker_id }`. The client
+  sends `{ method: "subscribe", subscription }` and every server frame is
+  `{ channel, data }`; `RealtimeHello` and `RealtimeReady` are
+  `RealtimeSubscribe` and `RealtimeSubscriptionResponse`. An event carries
+  `cursor` (was `stream`); a snapshot carries `truncated` (was
+  `continuations`) and the account's `quotes` (was `book_quotes`) and
+  `acceptances`.
+- Event names: `QUOTE_CREATED` / `QUOTE_REMOVED` (were `BOOK_QUOTE_*`),
+  `QUOTE_ACCEPTED` (was `CONFIRMATION_REQUESTED`), `RFQ_CREATED` (was
+  `ENTRY_RFQ_OPENED` and `CASHOUT_RFQ_OPENED`), `RFQ_ACCEPTED` (was
+  `RFQ_SELECTION_DURABLE`), `RFQ_FAILED` (was `RFQ_CLOSED`),
+  `OPERATION_UPDATED` (was `EXECUTION_REPORT` and `WITHDRAWAL_REPORT`),
+  `VAULT_BALANCE_CHANGED` (was `BALANCE_CHANGED`), `WALLET_FUNDING_UPDATED`,
+  `POSITION_*` (were `TICKET_*`, now `{ position_id, block_number, log_index }`
+  without the stored ticket status) and `MAKER_CAPITAL_UPDATED`.
+- A wallet funding carries `kind: "WALLET"`.
+- Types: `BookQuote`, `Confirmation` and `Release` are `Quote`, `Acceptance`
+  and `Deployment`; `MakerConfirmationRequest` and `MakerConfirmation` are
+  `MakerAcceptance` and `Acceptance`; `TotalisRelease` and `UsdcRelease` are
+  `TotalisDeployment` and `UsdcDeployment`.
+- API key scopes `ticket:accept` and `ticket:cashout` are `quote:accept` and
+  `position:cashout`.
+
+### Removed
+
+- `clientInstanceId` on the stream, and the v1 `session.hello` protocol.
+
+## 0.13.0
+
+`GET /v1/vault` no longer reports whether financial actions are enabled
+(TT-1900). Needs contract 117. Breaking.
+
+### Removed
+
+- `financial_actions_enabled` on `Release`. The venue still refuses
+  balance-affecting commands while a release is disabled; the command fails
+  with `FINANCIAL_ACTIONS_DISABLED`, so read that error rather than the release.
+
+## 0.12.0
+
+Commands, the stream and identity carry only what a reader uses (TT-1866).
+Needs contract 116. Breaking.
+
+### Changed
+
+- A command body is the command itself: the five POST commands
+  (`createRfq`, `publishBookQuote`, `beginConfirmation`, `finishConfirmation`,
+  `createWithdrawal`) no longer wrap it in `{schema_version, request_id,
+  sent_at, command}`; `envelope()` now wraps only the commands that still carry
+  it (core exits, HyperCore withdrawals and maker onboarding).
+  `error.request_id` is the response's `X-Request-ID`. The body types are `CreateRfqCommand`, `BookQuoteCommand`,
+  `ConfirmationAcceptanceCommand`, `MakerConfirmationCommand` and
+  `WithdrawalCommand` (were the `…Envelope` types).
+- The venue fills the addresses the credential implies from its one embedded
+  wallet, and the signed typed data still names that wallet: `createRfq` sends
+  no `taker_address`, a wallet funding (`WalletFunding`, was the collateral
+  envelope's `command`) no `account` or `from`, and `createWithdrawal` no
+  `account` and a `vault_withdrawal` without `account` and `to`.
+  `signWithdrawal` returns `{ idempotencyKey, account, body }`.
+- A stream event is `{stream, event_id, event_type, occurred_at, payload}`.
+  `ENTRY_RFQ_OPENED` carries the whole open entry RFQ; `onRfq` delivers it, and
+  a cash-out RFQ, as an `Rfq` with `state: "OPEN"` and reads nothing. A
+  replayed opening is skipped once its collection has ended, and otherwise
+  re-read and delivered only while the RFQ is still open.
+- `GET /v1/me` returns `{ account_id, status, wallet }`.
+- The attempt routes' `Idempotency-Key` header is optional; `attempt_id` is
+  the key. The SDK still sends it.
+
+### Removed
+
+- `quote_digest` and `taker_signature` inside a wallet funding (copies of the
+  accept's own).
+- `chain_id` and `vault_address` on book offers (the list, the snapshot's
+  `book_quotes` and `BOOK_QUOTE_PUBLISHED`), on the publication checkpoint,
+  and `max_frame_bytes` on `session.ready`: read the deployment from
+  `/v1/vault`.
+- `schema_version`, `resource_kind` and `resource_id` on stream events; the
+  `rfqDetails` stream option and the event frame's `rfq`.
+- `state` and `terminal_reason` on `ENTRY_RFQ_OPENED` and `CASHOUT_RFQ_OPENED`
+  payloads (the event type says it is OPEN).
+- The retired `ENTRY_QUOTE_DISPLAYED`, `CASHOUT_BID_DISPLAYED` and
+  `*_REMOVED_FROM_DISPLAY` events and their payload types.
+- `state` and `operation_id` on `MakerConfirmationRequest`.
+- `LegacyTerminalCashoutRfq`.
+- `wallets`, `owner`, `signer` and `privy_did` on `GET /v1/me`.
+
+## 0.11.0
+
+Account and maker reads carry amounts, not envelopes (TT-1866). Needs contract
+115. Breaking.
+
+### Changed
+
+- Every account-read amount (`Metric`, `UnsignedMetric`) is an atomic USDC
+  string, or `null` when unavailable. One `context: { as_of, status }` per
+  response replaces each amount's asset, authority, sources, method, time,
+  status and reason.
+- `context` is `{ as_of, status }`. Paging binds to one snapshot through the
+  opaque `next_cursor`; there is no `snapshot_id` to compare.
+- An activity lists `transaction_hashes` (was `evidence`), and each effect is
+  `{ bucket, delta, classification }`.
+- `GET /v1/me/balances` returns the one balance at the top level (was
+  `balances[0]`), without `product` or `unit`. A `Checkpoint` has no
+  `chain_id`. The `ProductBalanceList` type is `Balance`.
+- The activity, position and list types are shared by account and maker
+  reads: `ActivityList`, `ActivityDetail` and `PositionList` (were the
+  `Account…` and `Maker…` variants).
+
+### Removed
+
+- `contract_version` and `scope` on account and maker reads.
+- `funding_id` and `transfer_id` on an activity, and the `asset` activity
+  filter.
+- `initial_exposure` (it is `signed_payout - net_stake`) and
+  `claim_evidence_ids` on a position; `total_net_stake`,
+  `total_initial_exposure` and `activity_url` on position reads.
+- `allocated_wallet_cash` on maker capital; `asset`, `bucket`, `funding_id`,
+  `expires_at` and evidence IDs on its reservations.
+- `unrealized_pnl`, `return_on_capital` and `gas_by_asset` on maker
+  performance, which were never available.
+- `lens_address` on `Release`.
+
+## 0.10.0
+
+Market data carries only what a reader uses (TT-1866). Needs contract 114.
+Breaking.
+
+### Changed
+
+- `Market.dates` is always present, and also carries `scheduled_event_at`,
+  `observation_ends_at` and `market_class`. It is null only when the market has
+  neither reviewed timing nor a market class.
+- `Question` and `MarketDetail` carry `catalog_generation`; a `MarketDetail`'s
+  `question.markets` omits the requested market, which is `market`.
+- `MarketHistory` carries `side`, `scale` and `volume_scale` once; each bar is
+  `{minute, open, high, low, close, volume, trade_count}`. A scale change starts
+  a new page. `include_gaps` defaults to `false`.
+- `MarketDetail.stats` is `{volume_24h, open_interest}` in atomic USDC.
+- `MarketDetail.metadata` is `{content: {title, rules}, parent, sides: [{side,
+  label}]}`.
+
+### Removed
+
+- From `Market`: `deadline`, `quote_asset`, `catalog_generation`, `source`,
+  `taxonomy_state`, `taxonomy_source` and `taxonomy_version`. From its sides:
+  `asset_id`, and the reference's `source`, `feed_generation` and
+  `source_time`; `quality` names the feed class.
+- The same provenance fields from `Question` and discovery items, and the
+  `CatalogSource`, `TaxonomySource`, `TaxonomyState` and `TaxonomyVersion`
+  types.
+- `MarketDetail.feed_generation`, and `price_semantics`, `volume_semantics`,
+  `interval` and `fill_policy` from `MarketHistory`, which follow from
+  `series_type`.
+
+The market stream's catalog entries and references keep their shape
+(`FeedReference`).
+
+## 0.9.0
+
+Partners call only what trading needs (TT-1841). Needs contract 112. Breaking.
+
+### Changed
+
+- `withdraw`, `signWithdrawal` and `sendWithdrawal` send
+  `POST /v1/withdrawals` (was `/v1/totalis-withdrawals`), and follow
+  `WITHDRAWAL_UPDATED` on a `WITHDRAWAL` (was
+  `TOTALIS_WITHDRAWAL_CONTINUATION_UPDATED` on a `CONTINUATION`), reading
+  `GET /v1/withdrawals/{withdrawal_id}` only after a reconnect.
+- A withdrawal is the `Withdrawal` type (was `TotalisWithdrawal`) and its ID is
+  `withdrawal_id` (was `continuation_id`); `onStarted` and `waitForWithdrawal`
+  take that ID.
+
+### Removed
+
+- `deposit` and `POST /v1/deposits`: `placeBet` already funds a vault
+  shortfall from the wallet in the accept. The `DepositAccepted` type.
+- `withdrawFromVault` and the vault-only `POST /v1/withdrawals`: `withdraw`
+  moves any vault shortfall on its way out. The `OperationAccepted` type.
+- `settleTicket`, `claimTicket` and the ticket routes (`/claims`,
+  `/settlements`, `/transfers`): Totalis settles and claims every decided
+  ticket itself. `transferTypedData` and the plain `Transfer` type.
+- `POST /v1/operations/{operation_id}/self-funded-transaction`; a maker's
+  `reduceCollateral` keeps its own route.
+- The `ticket:settle` and `ticket:transfer` key scopes, and `operations:submit`
+  for personal keys.
+
+## 0.8.0
+
+A maker key reads its own account through `/v1/me`, and the maker stream is its
+only replay (TT-1841). Needs contract 111. Breaking.
+
+### Changed
+
+- `TotalisStream` resumes a persisted `cursor` on the stream itself: the hello
+  carries it and the venue replays the retained events after it, or resets to
+  a snapshot. `createMaker` no longer reads events over HTTP first. Every
+  `event` listener now receives the frame.
+- The maker snapshot has no `quotes` class, and its `operations` continuation is
+  `GET /v1/me/operations`.
+- A maker key reads `GET /v1/me/positions[/{ticket_id}]`,
+  `GET /v1/me/activity[/{activity_id}]`, `GET /v1/me/operations` and
+  `GET /v1/operations/{operation_id}` for its maker.
+
+### Removed
+
+- The `replay` stream option and `replayPages`.
+- Calls to `GET /v1/makers/{maker_id}/events`, `/snapshot`, `/offers`,
+  `/operations[/{operation_id}]`, `GET /v1/me/makers` and
+  `GET /v1/hypercore/history`, which are gone from the venue.
+- Issuing the `maker:access:read` key scope (its reads are app-session only).
+
+## 0.7.0
+
+Market data is list, detail and history (TT-1841). Needs contract 110. Breaking.
+
+### Changed
+
+- `GET /v1/markets/{outcome_id}` (`MarketDetail`) also carries `metadata`
+  (the product metadata at the market's catalog generation),
+  `recurring_round` (null outside a recurring series) and `stats` (the
+  market's 24h volume and open interest, null before a snapshot).
+
+### Removed
+
+- `GET /v1/markets/{outcome_id}/metadata` (read `metadata` on the market
+  detail) and `GET /v1/questions` (read `question` on the market detail),
+  with the `STALE_CATALOG` error code.
+
+## 0.6.0
+
+An external withdrawal is one request (TT-1775). Needs contract 109. Breaking.
+
+### Changed
+
+- `withdraw` signs the Exit for any wallet shortfall and the USDC
+  `TransferWithAuthorization` payout up front and sends them in one
+  `POST /v1/totalis-withdrawals` (`payout_authorization`). The payout's nonce is
+  `payoutNonce(release, account, idempotencyKey)`, so the signature is bound to
+  that request. It resolves at `PAYOUT_COMMITTED` from
+  `TOTALIS_WITHDRAWAL_CONTINUATION_UPDATED`, which now carries the whole
+  withdrawal, and reads `GET /v1/totalis-withdrawals/{id}` only after a
+  reconnect. `FAILED` throws; the USDC is then still in the vault or the
+  wallet.
+- `transferWithAuthorizationTypedData(release, payout)` takes
+  `{ from, to, value, valid_after, valid_before, nonce }`.
+- A withdrawal is `VAULT_WITHDRAWAL_QUEUED`, `PAYOUT_SUBMITTED`,
+  `PAYOUT_COMMITTED` or `FAILED`, and carries `payout_operation_id`,
+  `payout_transaction_hash` and `updated_at`.
+
+### Added
+
+- `signWithdrawal` and `sendWithdrawal`, to store a signed withdrawal before
+  sending it, and `waitForWithdrawal` to follow one after a restart.
+- `payoutNonce` and the `PayoutAuthorization` type in `./typed-data`.
+
+### Removed
+
+- `resumeWithdrawal` (use `waitForWithdrawal`), the `WalletTransfer` type, and
+  calls to `/payout-claim` and `/payout-submission`.
+
+## 0.5.0
+
+A maker that starts or reconnects with more than 100 pending confirmation
+requests now sees all of them (TT-1838). Needs contract 107.
+
+### Changed
+
+- `onConfirmation` pages `GET /v1/makers/{maker_id}/confirmations` when the
+  snapshot names it as the `confirmations` continuation, and handles every
+  request it returns once, like the snapshot's and the stream's. A failed read
+  reaches `onError` without a request, so its `request` parameter is now
+  optional.
+
+## 0.4.0
+
+Fewer RFQ routes: the taker keeps the book from the account stream, and entry
+and cash-out share one accept (TT-1835). Needs contract 106. Breaking.
+
+### Changed
+
+- The taker's book comes from the account stream: the snapshot's
+  `book_quotes`, then `BOOK_QUOTE_PUBLISHED` and `BOOK_QUOTE_REMOVED`.
+  `GET /v1/rfqs/{rfq_id}/book-quotes` is read only for an RFQ followed after a
+  snapshot that truncated `book_quotes`. `BookQuote` is the one offer shape
+  for both kinds; choosers take `Chooser<EntryQuote>` (`bestQuote`) or
+  `Chooser<CashoutBid>` (`bestBid`) with the venue clock. Expiry sends no
+  event, so an offer leaves the book (and `watchBook` re-renders) once it has
+  no more signed life than the venue needs to begin on it: 2 s for a quote,
+  22 s for a bid.
+- `placeBet` and `cashOut` use one accept,
+  `POST /v1/rfqs/{rfq_id}/attempts/{attempt_id}`. `cashOut` has the owner sign
+  the bid's `SellBack` or `CashoutTransfer` before the accept and returns
+  `{ rfqId, attemptId, quoteDigest, state, operationId, outcome }`: `COMMITTED`
+  with `operationId` means the sell-back or transfer is queued. `bid_digest` is
+  now `quote_digest`.
+- A lost accept the venue never received is recovered by reading the attempt,
+  cancelling the RFQ (204 or 409) and reading again; still absent is
+  `{ state: "NOT_ADMITTED" }`. `ABANDONED` is gone.
+- `createMaker`: `bid` publishes on `POST /v1/rfqs/{rfq_id}/book-quotes` with
+  `{ quote_digest, sell_back | transfer }` and returns `quoteDigest`.
+  `onConfirmation` answers `CONFIRMATION_REQUESTED` (live, or replayed from
+  `GET /v1/makers/{maker_id}/events` on resume) and the snapshot's
+  `confirmations`, including requests delivered before it was attached; its
+  `onError` always receives the request. `MakerConfirmationRequest` is the
+  event's payload type.
+
+### Removed
+
+- `watchCashoutBook` (`watchBook` renders quotes and bids) and the
+  `CashoutConfirmation` type.
+- Calls to `/cashout-book`, `/cashout-attempts`, `/attempts/{id}/abandon`,
+  `/tickets/{ticket_id}/sell-back` and `GET /v1/makers/{maker_id}/confirmations`.
+
+### Added
+
+- `stream.serverNow()`: the venue clock from `session.ready` and publication
+  checkpoints.
+- `EntryQuote` and `NotAdmitted` types.
+
+## 0.3.1
+
+### Fixed
+
+- `withdraw` / `resumeWithdrawal` no longer wait forever after the vault
+  top-up or the payout commits. The venue advances a withdrawal only when it is
+  read, so the flow now also re-reads on the `WITHDRAWAL_REPORT` or
+  `EXECUTION_REPORT` of the withdrawal's own operation, and on
+  `WALLET_BALANCE_CHANGED` for its wallet (found by TT-1778).
+
+## 0.3.0
+
+Helpers for the flows the SDK-first docs could only show as raw API calls, and
+fees and USDC read from `GET /v1/vault` (TT-1832). Needs contract 105.
+
+### Added
+
+- `createTotalis`: `withdrawFromVault` (direct `POST /v1/withdrawals` with a
+  signed Exit), `settleTicket` and `claimTicket`.
+- `createMaker`: `controller()` builds the maker's vault transactions
+  (`setQuoteSigner`, `approveUsdc`, `deposit`, `requestWithdraw`,
+  `executeWithdraw`, `cancelWithdraw`, `resetDiscount`) from the canonical ABI
+  for the controller wallet to send; `reduceCollateral` follows a collateral
+  reduction and can submit its attestation through the self-funded route.
+- `/maker` also exports `controllerTransactions`,
+  `openMakerVaultTransaction`, `encodeCall` and `TransactionCall`.
+
+### Changed
+
+- `createMaker` no longer takes `fees`: quotes carry the vault's current
+  `fee_bps` and `taker_fee_bps`, read from `GET /v1/vault` for every quote so a
+  governance change applies at once, and `quote` throws until the venue
+  publishes them.
+- `usdcDomain(release)`, `receiveWithAuthorizationTypedData(release, …)` and
+  `transferWithAuthorizationTypedData(release, transfer, window)` take USDC and
+  its signing domain from the release; `usdcTokens` is removed.
+
+## 0.2.0
+
+The SDK core on the current API (TT-1784).
+
+### Added
+
+- `createTotalis`: `placeBet` (RFQ, book from the stream, one synchronous
+  accept, wallet funding of a vault shortfall), `cashOut`, `deposit`,
+  `withdraw` / `resumeWithdrawal` (sponsored Totalis withdrawal),
+  `waitForOperation`, `watchBook` / `watchCashoutBook`, `issueApiKey` /
+  `rotateApiKey`.
+- `createMaker` (`/maker`): `quote`, `bid`, `withdraw`, `confirm`,
+  `onConfirmation`, `onRfq`, with HTTP replay from a persisted cursor.
+- `TotalisStream` (`/realtime`): snapshot, replay, deduplication, reconnect
+  with backoff, close-reason retry handling and stale-socket detection.
+- A request layer: every client resends the same bytes and `Idempotency-Key`
+  after network failures and `BACKOFF` errors, honouring `Retry-After`;
+  `unwrap` throws `ApiError`; `NetworkError` (with `resend()` for flow commands); `sendOnce`; `uuidv7`; `envelope`.
+- `pages`, `items` and `replayPages` over the TT-1771 list shape.
+- `toTotalisSigner` (`/signer`) for viem accounts and wallet clients,
+  EIP-1193 providers and ethers signers.
+- Typed data: `hashTypedData`, `hashDomain`, `receiveWithAuthorizationTypedData`,
+  `depositNonce`, `transferWithAuthorizationTypedData`, `usdcDomain`,
+  `canonicalSignature`, `issueKeyMessage`, `parseIssueKeyMessage`.
+- `ApiClientOptions`: `baseUrl`, `retry`, and `accessToken` as a function.
+- Node bot and browser-wallet examples.
+
+### Changed
+
+- `signTotalis` returns a canonical signature (v in {27, 28}).
+- `./errors` also exports `ApiError` and `NetworkError`.
+
+## 0.1.0
+
+Generated client, maker, operator, realtime, browse and account-read types;
+API-key client; typed data for vault signatures.