@cancore/contracts 0.2.0-rc.6 → 0.2.0-rc.9

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -63,6 +63,69 @@ the taker client relies on: those views and calls, the events `IntentOpened`, `F
63
63
  `Settled` and `Refunded`, and the 11-field `Order` tuple in the order of `ORDER_TYPES`, whose
64
64
  type hash is the router's `ORDER_TYPEHASH`. Router addresses are not in this package yet.
65
65
 
66
+ ### Orders, the Permit2 witness, the fee
67
+
68
+ Hashing helpers ship from the package root (sdk.md §7, decided: helpers, not data only). They
69
+ are what the backend, the filler node, the attestors and the web app use instead of their own
70
+ copies:
71
+
72
+ ```ts
73
+ import {
74
+ buildCantonSourceOrder, cantonInclusiveFeeSplit, hashOrder, hashPermitWitness, inclusiveFeeSplit,
75
+ MAX_FEE_BPS, MIN_FILL_TTL, sourceOrderHash,
76
+ } from '@cancore/contracts';
77
+
78
+ hashOrder(order, { chainId, verifyingContract: router }); // CancoreRouter.hashOrder: the orderHash
79
+ sourceOrderHash(order, sourceRouter); // what a destination keys `filled` on; a Canton origin needs no router
80
+
81
+ // the EVM-form Order of a Canton-source intent (protocol.md §3.7): refuses an inexact amount, fee or time
82
+ const { order, domain, orderHash } = buildCantonSourceOrder({
83
+ ownerPartyId, requestId, instrumentAdmin, instrumentId, amount: '1250.5',
84
+ destinationChainId: 1, wantToken, wantDecimals: 6, minReceived: '1200.25', recipient,
85
+ createdAt, fillDeadline, feeRate: '0.003', cantonOriginId: CANTON_ORIGIN_ID.devnet,
86
+ });
87
+
88
+ // what the maker signs for openFor: Permit2 PermitWitnessTransferFrom, the order as witness (PERMIT_WITNESS_TYPES for the wallet)
89
+ const digest = hashPermitWitness({ permitted: { token, amount }, spender: router, nonce, deadline, witness: order }, chainId);
90
+
91
+ inclusiveFeeSplit(105n, 500); // { payout: 100n, fee: 5n } — EVM source, CancoreRouter.settle (floor)
92
+ cantonInclusiveFeeSplit(total, 30); // Canton source, Daml inclusiveFee (half-even at 10⁻¹⁰)
93
+ ```
94
+
95
+ | Constants | Value | Held to |
96
+ | --- | --- | --- |
97
+ | `BPS`, `MAX_FEE_BPS`, `MIN_FILL_TTL`, `PROOF_KIND_ATTESTATION` | 10 000, 1 000, 60 s, 1 | `CancoreRouter.sol` via `spec/constants.json` |
98
+ | `MAX_FILL_TTL`, `MAX_SIG_TTL`, `MAX_PROOF_WINDOW`, `GRACE`, `SET_DELAY` | 24 h, 24 h, 4 h, 28 h, 72 h (seconds) | `AttestorSet.sol` via `spec/constants.json` |
99
+ | `CANTON_ORIGIN_ID`, `CANTON_SOURCE_ANCHOR`, `EIP2294_MAX_CHAIN_ID`, `OWNER_LABEL_TAG`, `INSTRUMENT_LABEL_TAG`, `DAML_NUMERIC_SCALE` | protocol.md §3.8 | `spec/vectors/canton-order.json` |
100
+
101
+ **Canton destination** (protocol.md §3.13). An EVM-source order delivered on Canton, and the
102
+ `FillProof` of the delivery, carry Canton values in EVM fields; this is the one encoder for them:
103
+
104
+ ```ts
105
+ import {
106
+ cantonNetworkOfDestination, encodeCantonAmount, encodeCantonDestination, encodeCantonOutputAsset, encodeCantonRecipient,
107
+ } from '@cancore/contracts';
108
+
109
+ const destination = encodeCantonDestination('devnet'); // keccak256(utf8("canton:devnet"))
110
+ const outputAsset = encodeCantonOutputAsset({ admin, id: 'USDCX' }); // keccak256(abi.encode("cancore:instrument:v1", admin, id))
111
+ const minReceived = encodeCantonAmount('1200.25'); // Daml Numeric 10 × 10¹⁰, exact or refused
112
+ const recipient = encodeCantonRecipient(partyId); // keccak256(utf8(partyId))
113
+ cantonNetworkOfDestination(order.destination); // 'devnet' | 'testnet' | 'mainnet' | undefined
114
+ ```
115
+
116
+ `spec/vectors/canton-destination.json` holds such an order (devnet) with its `orderHash` and the
117
+ `FillProof` of its delivery with its digest; its instrument, party and amount are those of the
118
+ Canton-destination vector of `spec/typed-data/FillProof.json` (`canton:mainnet`), which the
119
+ router test computes with `hashFillProof`.
120
+
121
+ `spec/constants.json` is written by `npm run sync` from the Solidity source of the same
122
+ evm-contracts commit as the ABIs (`CONTRACTS_RELEASE.commit`); a test holds every exported
123
+ constant to it, fails on a numeric constant the package does not export, and checks the router's
124
+ type hashes and `WITNESS_TYPE_STRING` against the package's type strings. Vectors:
125
+ `spec/vectors/evm-order.json`, `permit-witness.json` and `fee-split.json` (both rails; each EVM
126
+ case names the router test that pins it, each Canton case carries the Daml values), generated with
127
+ ethers by `scripts/gen-router-vectors.mjs`.
128
+
66
129
  ## FillProof: what attestors sign
67
130
 
68
131
  `CancoreRouter.settle(order, proof, sigs)` pays a filler out only against k attestor
@@ -84,13 +147,11 @@ const signature = await wallet.signTypedData({
84
147
 
85
148
  This repository keeps golden vectors for the schema in `spec/typed-data/FillProof.json` (shipped
86
149
  in the package since 0.2.0, under `@cancore/contracts/spec/*`), each with its `domainSeparator`,
87
- `structHash` and digest, and the file's `typeHash`. The twelve-field file is written here ahead
88
- of the router (`scripts/gen-protocol-vectors.mjs`): evm-contracts takes it byte for byte into
89
- `abi/typed-data/FillProof.json` and checks every vector against the router's own `hashFillProof`
90
- (CAN-2140); canton-contracts takes the Canton-source vector into its `FillProofVerify` vectors.
91
- From then on the schema is synced from evm-contracts like the ABIs. Until then, do not run
92
- `scripts/sync-typed-data.mjs` against an evm-contracts checkout that still has the eleven-field
93
- struct: it would overwrite this file with the old one.
150
+ `structHash` and digest, and the file's `typeHash`. The twelve-field schema and vectors are
151
+ synced from `evm-contracts/abi/typed-data/FillProof.json` at `CONTRACTS_RELEASE.commit`; the
152
+ router tests check every vector against its own `hashFillProof` (CAN-2140). Sync only from a
153
+ variant A checkout: an older eleven-field struct would overwrite this file with the old one.
154
+ The Canton-source verifier and its rollout remain a separate compatibility gate.
94
155
 
95
156
  ## Filler protocol v1 (RC)
96
157
 
@@ -100,7 +161,7 @@ breaking protocol change is `0.3`.
100
161
 
101
162
  ```ts
102
163
  import {
103
- gatewayBodyHash, hashFillerMessage, hashTicketIntent, repayToFromEvm, fillerIdHash,
164
+ cantonTicketReceipt, gatewayBodyHash, hashCantonTicketReceipt, hashFillerMessage, hashTicketIntent, repayToFromEvm, fillerIdHash,
104
165
  } from '@cancore/contracts';
105
166
 
106
167
  // what the filler's message key signs to take an offered ticket: its delivery key and payout address
@@ -118,6 +179,9 @@ const msgDigest = hashFillerMessage(message); // bodyHash = keccak256(JCS(messag
118
179
  const bodyHash = gatewayBodyHash(frame); // keccak256(JCS(frame without sig))
119
180
 
120
181
  fillerIdHash('acme'); // the on-chain fillerId of FillTicket, Filled, FillProof, Settled
182
+
183
+ // the receipt of a Canton-form ticket (no FillTicket, no ticketSig): built from ticket.issued
184
+ const receiptDigest = hashCantonTicketReceipt(cantonTicketReceipt(issued)); // orderHash, attempt, keccak256(cid), validUntil
121
185
  ```
122
186
 
123
187
  `hashTypedData` encodes flat structs (address, bool, bytes, bytesN, string, uintN) and throws on
@@ -131,10 +195,11 @@ manual key change by Cancore staff; there is no key-rotation type or message.
131
195
  | Types | Domain | Status |
132
196
  | --- | --- | --- |
133
197
  | `TicketReceipt`, `StakeBinding`, `FillerAuth`, `GatewayMessage` | `CancoreFillerProtocol` v1 | v1 RC — vectors in `spec/protocol/typed-data/` |
134
- | `FillerQuote` (`string fillerId`), `TicketIntent` (with `fillerId`, `deliveryKey`, `repayTo`), `FillerMessage`, `FillerKeyRegistration` | `CancoreFillerProtocol` v1 | settlement design (variant A), next RC — vectors in `spec/protocol/typed-data/` |
198
+ | `FillerQuote` (`string fillerId`), `TicketIntent` (with `fillerId`, `deliveryKey`, `repayTo`), `FillerMessage`, `FillerKeyRegistration` | `CancoreFillerProtocol` v1 | variant A — vectors in `spec/protocol/typed-data/` |
199
+ | `CantonTicketReceipt` (`orderHash`, `attempt`, `deliveryOrderCidHash`, `validUntil`) | `CancoreFillerProtocol` v1 | receipt of a Canton-form ticket (§10 D-O), additive — vectors in `spec/protocol/typed-data/` |
135
200
  | `Order` (11 fields, with `createdAt`), `Quote` | `CancoreRouter` v1, source router | router code; provisional copies in `spec/typed-data/` until evm-contracts publishes them |
136
- | `FillTicket` (`orderHash`, `fillerId`, `deliveryKey`, `repayTo`, `attempt`, `validFrom`, `validUntil`) | `CancoreFillTicket` v1 | variant A, written here ahead of the router (CAN-2140) |
137
- | `FillProof` (twelve fields) | `CancoreRouter` v1, source router | variant A, written here ahead of the router (above) |
201
+ | `FillTicket` (`orderHash`, `fillerId`, `deliveryKey`, `repayTo`, `attempt`, `validFrom`, `validUntil`) | `CancoreFillTicket` v1 | variant A, synced from the router (CAN-2140) |
202
+ | `FillProof` (twelve fields) | `CancoreRouter` v1, source router | variant A, synced from the router (above) |
138
203
 
139
204
  Golden vectors are generated with ethers by `scripts/gen-protocol-vectors.mjs` from the literal
140
205
  inputs in `scripts/protocol-fixtures.mjs`, and checked by this package's own encoder too. The
@@ -148,15 +213,15 @@ drand quicknet rounds.
148
213
 
149
214
  | File (`@cancore/contracts/spec/protocol/…`) | Holds |
150
215
  | --- | --- |
151
- | `messages.schema.json` | one `$def` per WebSocket frame type (23), `x-direction` S2F / F2S / both, and the primitives they share |
152
- | `rest.schema.json` | REST fallback bodies; `x-endpoints` (method, path, auth, request/response), `x-error-status` |
216
+ | `messages.schema.json` | one `$def` per frame type (23), `x-direction` S2F / F2S / both, `x-rest-only` on the two login types, and the primitives they share |
217
+ | `rest.schema.json` | REST bodies; `x-endpoints` (method, path, auth, query, request/response, `errorBody` where a refusal may be unsigned), `x-error-status` |
153
218
  | `records.schema.json` | the draw record, the epoch record, `GET /v1/gateway` |
154
- | `asyncapi.json` | AsyncAPI 3.0: channel `/v1`, the gateway's send/receive operations, examples |
219
+ | `asyncapi.json` | AsyncAPI 3.0: channel `/v1` (the upgrade's subprotocols, its HTTP refusals `x-upgrade-refusals`, the close codes `x-close-codes`), the gateway's send/receive operations, examples |
155
220
  | `vectors/messages.json`, `vectors/records.json` | valid example frames and fixture records (hashes real, `sig` a placeholder: r = s = 0, v = 27) |
156
221
  | `vectors/settle-attestations.json` | `settle.attestations` golden vectors: EVM and Canton source, real TEST-key signatures, the pushed frame and the REST body with one payload, and schema-valid payloads a filler must refuse |
157
222
 
158
- The same objects are exported as `PROTOCOL_SCHEMAS`, `ASYNCAPI`, `MESSAGE_DIRECTIONS` and
159
- `REST_ENDPOINTS`, with TypeScript shapes of every frame (`TicketOffer`, `QuoteAck`, …) and the
223
+ The same objects are exported as `PROTOCOL_SCHEMAS`, `ASYNCAPI`, `MESSAGE_DIRECTIONS`,
224
+ `REST_ONLY_TYPES` and `REST_ENDPOINTS`, with TypeScript shapes of every frame (`TicketOffer`, `QuoteAck`, …) and the
160
225
  enums (`DECLINE_REASONS`, `ERROR_CODES`, …) a test holds to the schemas.
161
226
 
162
227
  ```ts
@@ -188,6 +253,31 @@ filler's `msgSig` (`pingF2S`); the second argument of `messageSchemaRef` picks o
188
253
  `scripts/gen-protocol-docs.mjs` derives the examples, records and the AsyncAPI document from
189
254
  the schemas and the vectors.
190
255
 
256
+ ### Login and connect
257
+
258
+ A filler logs in over REST and only then opens the WebSocket:
259
+
260
+ 1. `GET /v1/filler/auth/challenge?fillerId=<fillerId>` → a signed `auth.challenge` addressed to that
261
+ `fillerId`. Check its `sig` against the published gateway key and that `fillerId` is yours.
262
+ Refusals of this anonymous route are unsigned (`unsignedErrorBody`): 400 `BAD_REQUEST`, 404
263
+ `UNKNOWN_REQUEST` (unknown or not `ACTIVE`), 429 `RATE_LIMITED` with `retryAfterMs`.
264
+ 2. `POST /v1/filler/auth` with `auth.response` (`FillerAuth` by the message key, `nonce` = the
265
+ challenge's) → `{token, expiresAt}`, bound to `(fillerId, message key)`. Refusals decided before
266
+ any signature check are unsigned too: 400 `BAD_REQUEST`, 404 `UNKNOWN_REQUEST`, 401
267
+ `UNAUTHENTICATED` (no live challenge for the fillerId: start again from step 1), 429; refusals after
268
+ the signature checks are the signed `error`.
269
+ 3. Upgrade `/v1` offering `fillerWsProtocols(token)` = `['cancore-filler.v1', 'bearer.<token>']`
270
+ (`FILLER_WS_SUBPROTOCOL`, `FILLER_WS_BEARER_PREFIX`) as `Sec-WebSocket-Protocol`; the gateway
271
+ answers `cancore-filler.v1` and sends a signed `auth.ok` first. It refuses with plain HTTP
272
+ (`FILLER_UPGRADE_REFUSALS`: 400, 401, 403, 429 with `Retry-After`, 503) and closes a session
273
+ with one of `FILLER_CLOSE_CODES` (4029: rate-limit cooldown, preceded by `error RATE_LIMITED`
274
+ whose `retryAfterMs` is the remaining cooldown).
275
+
276
+ The same token authenticates REST (`Authorization: Bearer`). `auth.challenge` and
277
+ `auth.response` never travel on the socket (`REST_ONLY_TYPES`). Over a per-fillerId rate limit
278
+ the gateway answers `error RATE_LIMITED` with `retryAfterMs` (on REST: 429, always unsigned, with
279
+ `retryAfterMs` and `Retry-After`); send nothing of that rate class before it has passed.
280
+
191
281
  ### Attestation signatures for `settle`
192
282
 
193
283
  Once filler-gateway holds at least `threshold` verified attestor signatures over a filler's
@@ -195,8 +285,8 @@ Once filler-gateway holds at least `threshold` verified attestor signatures over
195
285
  `GET /v1/filler/attestations/{orderHash}` (404 `ATTESTATIONS_NOT_READY` before that, 404
196
286
  `UNKNOWN_TICKET` when the filler holds no ticket on the order); the filler node submits `settle`
197
287
  itself (protocol §3.5, §3.6, §10 D-N). `proof` is the `FillProof` the source router hashes,
198
- field for field (`FILL_PROOF_TYPES`); variant A of protocol §3.3 (`fillerId`, `repayTo`) replaces
199
- it together with the router's struct. A signature entry follows `sourceChainId`: `{signer, signature}` with a
288
+ field for field (`FILL_PROOF_TYPES`), including variant A's `fillerId` and `repayTo`
289
+ (protocol §3.3). A signature entry follows `sourceChainId`: `{signer, signature}` with a
200
290
  65-byte signature on an EVM source, `{signer, pubKey, signature}` with the DER public key and a
201
291
  minimal DER signature on a Canton source, as `SwapIntent_SettleWithProof` takes them.
202
292
 
@@ -285,7 +375,8 @@ added.
285
375
  EVM_CONTRACTS_DIR=../evm-contracts npm run sync # then review the diff and release
286
376
  ```
287
377
 
288
- `npm run sync` is two scripts: `scripts/sync.mjs` (ABIs, error tables, release identity) and
378
+ `npm run sync` is two scripts: `scripts/sync.mjs` (ABIs, error tables, release identity, the
379
+ router and AttestorSet constants in `spec/constants.json`) and
289
380
  `scripts/sync-typed-data.mjs` (`abi/typed-data/*.json`). Until evm-contracts publishes
290
381
  `abi/typed-data/` the second one fails; run the first one alone:
291
382
 
@@ -308,7 +399,70 @@ Full documentation: <https://docs.cancore.io/sdk/contracts>
308
399
 
309
400
  ## Changes
310
401
 
311
- - Unreleased (next RC) — the settlement design of variant A (protocol.md §3.3, §3.4, §3.15,
402
+ `0.2.0-rc.9` follows `0.2.0-rc.7`: no `0.2.0-rc.8` was published. Its four entries below ship
403
+ together; the first is breaking within the RC line for a filler and for filler-gateway, the other
404
+ three are additive.
405
+
406
+ - `0.2.0-rc.9` — connect only after login, limits per fillerId (CAN-2232). **Breaking within the
407
+ RC line** for a filler and for filler-gateway:
408
+ - The login is REST only: `GET /v1/filler/auth/challenge` takes a required `fillerId` query
409
+ (`challengeQuery`), and `auth.challenge` is addressed (envelope `s2fBase`, `fillerId`
410
+ required). The refusals of the login routes decided before a signature check, and every 429,
411
+ are unsigned (`unsignedErrorBody`; `errorBody` of the two login endpoints).
412
+ `auth.challenge` and `auth.response` carry `x-rest-only` (a new annotation keyword in
413
+ `SCHEMA_VOCABULARY`; `REST_ONLY_TYPES`) and leave the AsyncAPI channel.
414
+ - The WebSocket upgrade offers `cancore-filler.v1` and `bearer.<token>`:
415
+ `FILLER_WS_SUBPROTOCOL`, `FILLER_WS_BEARER_PREFIX`, `fillerWsProtocols`; its refusals
416
+ `FILLER_UPGRADE_REFUSALS` and the session close codes `FILLER_CLOSE_CODES`, also in
417
+ `asyncapi.json` (`bindings.ws`, `x-upgrade-refusals`, `x-close-codes`).
418
+ - `error` gains optional `retryAfterMs` (an integer ≥ 1, with `RATE_LIMITED`);
419
+ `ErrorMessage.retryAfterMs`, `UnsignedErrorBody`, `ChallengeQuery`, `RestEndpoint.errorBody`.
420
+ - The `auth.challenge` example and its `GatewayMessage` vector carry `fillerId` (that vector's
421
+ digest changes); a `RATE_LIMITED` example; no other digest changes.
422
+ - `0.2.0-rc.9` — router constants and order hashing helpers (CAN-1934). Additive only:
423
+ no existing export, type or digest changes.
424
+ - Constants `BPS`, `MAX_FEE_BPS`, `MIN_FILL_TTL`, `MAX_FILL_TTL`, `MAX_SIG_TTL`,
425
+ `MAX_PROOF_WINDOW`, `GRACE`, `SET_DELAY`, `CANTON_ORIGIN_ID`, `CANTON_SOURCE_ANCHOR`,
426
+ `EIP2294_MAX_CHAIN_ID`, `OWNER_LABEL_TAG`, `INSTRUMENT_LABEL_TAG`, `DAML_NUMERIC_SCALE`;
427
+ `spec/constants.json`, synced from the Solidity source, pins them (SDK-6).
428
+ - Helpers `hashOrder`, `sourceOrderHash`, `isCantonOriginId`, `buildCantonSourceOrder` (port of
429
+ evm-contracts `test/helpers/cantonOrder.ts`, EVM destinations), `PERMIT_WITNESS_TYPES`,
430
+ `PERMIT2_WITNESS_TYPE_STRING`, `permit2Domain`, `hashPermitWitness`, `inclusiveFeeSplit` (EVM
431
+ source) and `cantonInclusiveFeeSplit` (Canton source).
432
+ - Vectors `spec/vectors/evm-order.json`, `permit-witness.json`, `fee-split.json`.
433
+ - `0.2.0-rc.9` — the Canton-destination encoder (protocol.md §3.13; CAN-1935). Additive only.
434
+ - `encodeCantonDestination(network)`, `cantonNetworkOfDestination(destination)`,
435
+ `encodeCantonOutputAsset({admin, id})`, `encodeCantonRecipient(partyId)`,
436
+ `encodeCantonAmount(amount)`, type `CantonNetwork`.
437
+ - Vector `spec/vectors/canton-destination.json`: an EVM-source order to Canton devnet and the
438
+ `FillProof` of its delivery.
439
+ - `0.2.0-rc.9` — `CantonTicketReceipt`, the receipt of a Canton-form ticket (protocol.md
440
+ §3.3, §3.5, §10 D-O; CAN-2062). Additive only (V-2): no existing type, digest or vector changes.
441
+ - Type `CantonTicketReceipt(bytes32 orderHash,uint32 attempt,bytes32 deliveryOrderCidHash,uint64 validUntil)`
442
+ in the `CancoreFillerProtocol` domain, signed by the message key; `fillerId` and `repayTo` are
443
+ not part of it (they travel in `ticket.issued`). Golden vectors in
444
+ `spec/protocol/typed-data/CantonTicketReceipt.json`.
445
+ - Helpers `CANTON_TICKET_RECEIPT_TYPES`, `hashCantonTicketReceipt`, `cantonTicketReceipt` (the
446
+ struct from a Canton-form `ticket.issued` or `ticket.receipt`) and `deliveryOrderCidHash`.
447
+ - `ticket.receipt` gains the Canton form: `form: "canton"`, `deliveryOrderCid`, `validUntil`,
448
+ `sig`; the EVM form (`form` absent or `"evm"`) is unchanged. The same body is the REST
449
+ `POST /v1/filler/tickets/{orderHash}/{attempt}/receipt`; AsyncAPI carries both examples.
450
+ `TicketReceiptMessage` is now the union `TicketReceiptEvm | TicketReceiptCanton`.
451
+ - `0.2.0-rc.7` — sync the variant A `CancoreRouter` and `ICancoreRouter` ABIs from
452
+ evm-contracts commit `c214f56f6fe5a62097833c5f1335b0cb5351b225` (CAN-2140).
453
+ - Both the package root and `/abi`, and the shipped `spec/abi/` JSON, expose
454
+ `Filled(orderHash, fillerId, deliveryKey, repayTo, received, recipient, filledAt, attempt)`
455
+ and `Settled(orderHash, fillerId, repayTo, payout, fee)`. Both events index `orderHash` and
456
+ `fillerId`. **Breaking within the RC line**: consumers must decode the new event topics
457
+ and fields; the published `0.2.0-rc.6` still has the old router ABIs.
458
+ - The router's `FillTicket` and `FillProof` tuples now match the variant A typed data
459
+ already shipped in `0.2.0-rc.6`. No typed-data digest changes from `rc.6` to `rc.7`.
460
+ The generated typed-data snapshot now also includes `FillTicket` from the synced schema.
461
+ - Remove the old on-router filler registry views, `setFiller` and `FillerSet`;
462
+ `WrongDeliveryKey` replaces `WrongTicketFiller` and `NotFiller`. Refresh
463
+ `CONTRACTS_RELEASE.commit` and the router build hashes.
464
+ - This package does not deploy a router or complete the Canton/backend/trader rollout.
465
+ - `0.2.0-rc.6` (CAN-2139; previously listed as unreleased) — the settlement design of variant A (protocol.md §3.3, §3.4, §3.15,
312
466
  §3.16; CAN-2139). **Breaking within the RC line**: every digest of the changed types changes.
313
467
  - `FillTicket` is `(orderHash, bytes32 fillerId, address deliveryKey, bytes32 repayTo, attempt,
314
468
  validFrom, validUntil)`; `FillProof` has twelve fields, `fillerId` and `repayTo` in place of
@@ -330,9 +484,9 @@ Full documentation: <https://docs.cancore.io/sdk/contracts>
330
484
  `repayTo`; error codes `STALE_MESSAGE`, `REPLAYED_MESSAGE`, `TICKET_REFUSED` with
331
485
  `reason` (`TICKET_REFUSED_REASONS`); `repayToEvm`, `fillerKeyRegistration` definitions;
332
486
  `sig65` refuses an `s` with its top bit set; `GET /v1/gateway` returns `maxMessageAgeMs`.
333
- - Vectors for every new and changed type; `FillProof.json` is written here ahead of the
334
- router (see «FillProof: what attestors sign»).
335
- - Unreleased (CAN-2018) — filler-gateway → filler `settle.attestations` and `GET /v1/filler/attestations/{orderHash}`
487
+ - Vectors for every new and changed type; the router ABI catches up with these types in
488
+ `0.2.0-rc.7` (see «FillProof: what attestors sign»).
489
+ - `0.2.0-rc.6` (CAN-2018; previously listed as unreleased) — filler-gateway → filler `settle.attestations` and `GET /v1/filler/attestations/{orderHash}`
336
490
  (protocol §3.5, §3.6, §10 D-N): the frame schema with the router's `FillProof` and the EVM and
337
491
  Canton signature entries, the REST endpoint, the error code `ATTESTATIONS_NOT_READY` (404), an
338
492
  AsyncAPI message, golden vectors (`spec/protocol/vectors/settle-attestations.json`), the