@pulsepairs/sdk 0.9.1 → 0.9.2

package/DOCUMENTATION.md

@@ -1,6 +1,6 @@
 # `@pulsepairs/sdk` — Reference Documentation
 
-**Version:** 0.7.0 · **License:** UNLICENSED · **Runtime:** Node ≥ 18 or a modern browser
+**Version:** 0.9.2 · **License:** UNLICENSED · **Runtime:** Node ≥ 18 or a modern browser
 
 Complete reference for the UpDown TypeScript SDK: every export, its
 units, its failure modes, and the protocol it speaks.
@@ -43,10 +43,14 @@ returns, what unit a number is in, or why a signature is being rejected.
 ## 1. What this SDK is
 
 UpDown is a binary prediction market: *will BTC-USD (or ETH-USD) be UP or DOWN at
-the end of this 5-minute / 15-minute / 1-hour cycle?* Trading is an **off-chain
+the end of this 5-minute or 15-minute cycle?* Trading is an **off-chain
 central limit order book** (the "matcher"); settlement is **on-chain** on
 Arbitrum.
 
+60-minute cycles were retired on 2026-08-18 and no new ones are created. The
+`3600` timeframe is still accepted and still returns the historical rounds — see
+`getMarkets` under [§5 `UpDownHttpClient`](#5-updownhttpclient--rest-client).
+
 The SDK gives you three layers, usable independently:
 
 | Layer | Modules | What it does |

package/README.md

@@ -1,7 +1,7 @@
 # @pulsepairs/sdk
 
 Standalone SDK for the **UpDown** up/down prediction markets —
-BTC-USD / ETH-USD, UP or DOWN, on 5-minute / 15-minute / 1-hour cycles.
+BTC-USD / ETH-USD, UP or DOWN, on 5-minute and 15-minute cycles.
 
 > **On the name:** the product is **UpDown**. "PulsePairs" is a retired name that
 > survives in two places for compatibility reasons only — this npm package's name
@@ -456,6 +456,32 @@ for (const f of bulkFailures(res)) {
 
 `index` is the position in the array you sent — results are positional.
 
+**On success the order is NESTED, and the single routes spread it.** This is
+the one asymmetry that bites, because nothing about the call site hints at it:
+
+```ts
+const single = await api.amendOrder({ cancelOrderId, order });
+single.id;                       // flat — the replacement's id
+
+const bulk = await api.amendOrdersBulk({ amends });
+for (const r of bulk.results) {
+  if (!r.ok) continue;           // narrow first; failures have no `order`
+  r.order.id;                    // NESTED — `r.id` is undefined
+  r.replaced;                    // the id that was retired
+  r.priorityKept;                // false when queue position was forfeited
+  r.remaining;                   // atomic USDT carried to the replacement
+}
+```
+
+`postOrdersBulk` nests the same way: `results[i].order`, never `results[i].id`.
+
+Reading `results[i].id` yields `undefined` rather than throwing, so the mistake
+survives to wherever that id is used — usually a later cancel that silently
+matches nothing. SDK **0.9.0 typed the bulk result flat** and shipped that
+mistake into the types themselves; 0.9.1 corrected them. The wire shape never
+changed, so no server behaviour depends on which version you are on — but on
+0.9.0 the compiler will agree with you while you read the wrong field.
+
 Two behavioural differences worth knowing, because they change how latency
 scales:
 

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@pulsepairs/sdk",
-  "version": "0.9.1",
-  "description": "Standalone SDK for the UpDown (PulsePairs) up/down prediction markets \u2014 matcher REST/WS client, EIP-712 order signing, trade-math, and Alchemy Account Kit (smart-account) order signing for rain.trade integration.",
+  "version": "0.9.2",
+  "description": "Standalone SDK for the UpDown (PulsePairs) up/down prediction markets — matcher REST/WS client, EIP-712 order signing, trade-math, and Alchemy Account Kit (smart-account) order signing for rain.trade integration.",
   "license": "UNLICENSED",
   "type": "module",
   "main": "dist/index.js",