Indexer/docs: Wasm attribute version matrix for null limit-order metadata #74

New issue

Closed

opened 2026-04-09 03:23:59 +00:00 by PlasticDigits · 5 comments

PlasticDigits commented

2026-04-09 03:23:59 +00:00

(Migrated from gitlab.com)

Evidence

docs/limit-orders.md — older pair code omits attrs → null DB columns

Acceptance criteria

Operator/analytics note committed

Epic

#58

## Evidence - `docs/limit-orders.md` — older pair code omits attrs → null DB columns ## Acceptance criteria - [ ] Operator/analytics note committed ## Epic #58

PlasticDigits commented

2026-04-09 03:24:00 +00:00

(Migrated from gitlab.com)

marked this issue as related to #58

PlasticDigits commented

2026-04-13 04:51:41 +00:00

(Migrated from gitlab.com)

Added operator matrix in docs/limit-orders.md (wasm attrs vs indexer null columns) under Tx attributes. @brouie please sanity-check wording for ops/analytics.

Added operator matrix in `docs/limit-orders.md` (wasm attrs vs indexer null columns) under Tx attributes. @brouie please sanity-check wording for ops/analytics.

PlasticDigits commented

2026-04-13 04:51:46 +00:00

(Migrated from gitlab.com)

mentioned in issue #58

Brouie commented

2026-04-20 06:32:44 +00:00

(Migrated from gitlab.com)

@PlasticDigits Verified on current main. Acceptance criteria:

Operator/analytics note committed: docs/limit-orders.md lines 99-104 include a 'Wasm attribute coverage vs indexer nulls (operators)' table under 'Tx attributes (indexer / analytics)' section. Table covers:

Pair build	Place attrs	Cancel attrs	Indexer null behavior
Current (main branch pair)	side, price, owner, expires_at when set	owner	Metadata columns populated when attrs appear
Legacy (older deployed wasm omitting attrs)	May omit side/price/owner	May omit owner	DB columns stay null; rows still keyed by pair_id, order_id, tx_hash, heights/timestamps
limit_order_fill events	Per-fill order_id, side, maker, price, amounts, commission_amount	—	Indexed in limit_order_fills

Clear separation of current vs legacy behavior, explicit note that legacy rows remain queryable via keys even when metadata columns are null. Useful for ops/analytics. Closing.

@PlasticDigits Verified on current main. Acceptance criteria: - [x] Operator/analytics note committed: docs/limit-orders.md lines 99-104 include a 'Wasm attribute coverage vs indexer nulls (operators)' table under 'Tx attributes (indexer / analytics)' section. Table covers: | Pair build | Place attrs | Cancel attrs | Indexer null behavior | |---|---|---|---| | Current (main branch pair) | side, price, owner, expires_at when set | owner | Metadata columns populated when attrs appear | | Legacy (older deployed wasm omitting attrs) | May omit side/price/owner | May omit owner | DB columns stay null; rows still keyed by pair_id, order_id, tx_hash, heights/timestamps | | limit_order_fill events | Per-fill order_id, side, maker, price, amounts, commission_amount | — | Indexed in limit_order_fills | Clear separation of current vs legacy behavior, explicit note that legacy rows remain queryable via keys even when metadata columns are null. Useful for ops/analytics. Closing.

Brouie (Migrated from gitlab.com) closed this issue

2026-04-20 06:32:48 +00:00

Brouie commented

2026-04-20 07:26:42 +00:00

(Migrated from gitlab.com)

mentioned in issue #100