Skip to content

feat!: compose fill state into the registry poll path#24

Open
mfw78 wants to merge 1 commit into
feat/poll-interfacefrom
feat/registry-poll-path
Open

feat!: compose fill state into the registry poll path#24
mfw78 wants to merge 1 commit into
feat/poll-interfacefrom
feat/registry-poll-path

Conversation

@mfw78

@mfw78 mfw78 commented Jul 10, 2026

Copy link
Copy Markdown

Reshape getTradeableOrderWithSignature around the generator verdict plus an orthogonal, registry-observed fill overlay:

Together with the generator half this delivers the verdict/fill split (closes #16).

BREAKING: getTradeableOrderWithSignature returns (PollResult, bytes); ConditionalOrderCreated and MerkleRootSet gain a bytes context parameter (topic0 changes).

Part of #1.

Reshape getTradeableOrderWithSignature around the structured generator
verdict and an orthogonal, registry-observed fill overlay:

- PollResult composes the handler GeneratorResult with a FillStatus
  (NONE / PARTIALLY_FILLED / FILLED / INVALIDATED) derived from
  GPv2Settlement.filledAmount; invalidateOrder is reported as
  INVALIDATED, not FILLED
- a partially filled partiallyFillable order keeps returning its
  signature, so the remainder is no longer stranded
- checkOrder returns the same composed PollResult and now applies the
  ERC-165 handler gate via the shared _poll helper
- create/setRoot write the cabinet before emitting and carry the
  resolved cabinet value in a new bytes context event field
- emit ConditionalOrderRemoved on order removal
- state mappings use named parameters

BREAKING CHANGE: getTradeableOrderWithSignature returns
(PollResult, bytes); ConditionalOrderCreated and MerkleRootSet gain a
bytes context parameter (topic0 changes).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant