From 1c0705a7bf8c3cdf7e5295b23f4a6baef561ea02 Mon Sep 17 00:00:00 2001 From: David Meister Date: Thu, 18 Jun 2026 17:40:12 +0000 Subject: [PATCH 1/3] docs(natspec): correct stale calculateClearStateChange cap description The previous prose described the old 'counterparty_IO * counterparty_outputMax' formula. The actual cap logic: each order's output is capped by the counterparty's max output (with input back-derived from the IO ratio). Refs #2671 --- src/concrete/raindex/RaindexV6.sol | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/src/concrete/raindex/RaindexV6.sol b/src/concrete/raindex/RaindexV6.sol index cdc4d04dda..3ee0c19afb 100644 --- a/src/concrete/raindex/RaindexV6.sol +++ b/src/concrete/raindex/RaindexV6.sol @@ -1103,9 +1103,8 @@ contract RaindexV6 is IRaindexV6, IMetaV1_2, ReentrancyGuard, Multicall, Raindex } /// Calculates the clear state change given both order calculations for order - /// alice and order bob. The input of each is their output multiplied by - /// their IO ratio and the output of each is the smaller of their maximum - /// output and the counterparty IO * max output. + /// alice and bob. Each order's output is capped by the counterparty's max + /// output, and each order's input is derived from the IO ratio. /// @param aliceOrderIOCalculation Order calculation for Alice. /// @param bobOrderIOCalculation Order calculation for Bob. /// @return clearStateChange The clear state change with absolute inputs and From 6a1980d6cf88baa56c564e666499b4abd42f4929 Mon Sep 17 00:00:00 2001 From: David Meister Date: Fri, 19 Jun 2026 17:37:35 +0000 Subject: [PATCH 2/3] merge(main): resolve conflicts [merge-update] From dc87aa24faa7c1e4eb46055b997241830a189345 Mon Sep 17 00:00:00 2001 From: David Meister Date: Thu, 25 Jun 2026 01:14:26 +0000 Subject: [PATCH 3/3] merge(main): resolve conflicts [merge-update] Co-Authored-By: Claude