Skip to content

Crown quote-table rows per lane, not per direction - #177

Merged
anderdc merged 1 commit into
testfrom
fix/lane-aware-quote-crowns
Aug 20, 2026
Merged

Crown quote-table rows per lane, not per direction#177
anderdc merged 1 commit into
testfrom
fix/lane-aware-quote-crowns

Conversation

@anderdc

@anderdc anderdc commented Aug 20, 2026

Copy link
Copy Markdown
Collaborator

Problem

On the miner detail page, UID 189 showed a crown on both the native SOL/TAO row and the `TAO BOND` row, while UID 56 also showed sol↔tao crowns. Live `/crown`: 189 holds the tao-backed lane, 56 the sol-backed lane. The quote table matched crowns on direction alone (`crownSet.has("SOL-TAO")`), so the lane distinction was lost.

Change

  • `CrownLane` type; optional `currentCrownLanes?` on `LeaderboardRow` / `MinerStats` (from entrius/das-allways#112).
  • `MinerDetailHeader` keys the quote-table crown on `(direction, backing)` — 189 is now crowned only on the `TAO BOND` row, 56 only on the native row.
  • Falls back to the previous every-lane behaviour when das omits `currentCrownLanes`, so deploy order does not matter.

The header badge (`SOL→TAO TAO→SOL`) is unchanged — still true for both miners, just lane-agnostic.

Depends on: entrius/das-allways#112 (degrades gracefully without it).

The miner header crowned every row of a direction the miner held on any
lane, so a tao-lane sol<->tao crown also gilded the sol-bond row. Key the
crown check on (direction, backing) via das currentCrownLanes; fall back
to the old per-direction behaviour when an older das omits the field.
@anderdc
anderdc merged commit 7abc849 into test Aug 20, 2026
2 checks passed
@anderdc
anderdc deleted the fix/lane-aware-quote-crowns branch August 20, 2026 14:57
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