Skip to content

Auction escalation REP and bundle liquidation claims - #645

Open
KillariDev wants to merge 2 commits into
mainfrom
t3code/update-escalation-auction-migration
Open

Auction escalation REP and bundle liquidation claims#645
KillariDev wants to merge 2 commits into
mainfrom
t3code/update-escalation-auction-migration

Conversation

@KillariDev

Copy link
Copy Markdown
Collaborator

Summary

  • include unresolved escalation-game REP in truth-auction repair, proportionally rebase claim balances and curve timing, and preserve a fresh response period after fork continuation
  • make escalation claims nontradeable internal vault claims that move only through bounded, proportional bundled liquidation and remain claimable by their current owner
  • restrict parent-OI migration power to free REP with a distinct migration security multiplier and explicit escalation limits
  • update security-pool UI, liquidation review, reporting and fork copy to distinguish free REP from escalation REP and prevent guaranteed-failure withdrawals while escrow remains
  • document the mechanics, implementation rationale, operational invariants, and game theory; refresh generated references and deterministic deployment manifests

Why

Truth-auction repair must take priority over escalation rewards when open interest is undercollateralized. Applying the same proportional haircut to escalation backing prevents participants from escaping losses by locking REP in the game.

Liquidation transfers the complete proportional position because allowing liquidators to select only free REP would leave debt and likely losing claims behind. Claims remain nontradeable outside liquidation so escalation participation cannot become a transferable side market.

Only free REP routes parent open interest during a fork. Losing escalation REP therefore cannot be used to direct valuable OI into a favorable child universe, while the separate migration multiplier preserves enough unlocked security backing.

All stored claim and ancestry traversal is explicitly bounded to keep Solidity execution predictable.

Validation

  • bun run tsc
  • bun run ensure-contract-artifacts && bun run check:shared-dependencies && bun run test:run -- --bail=1 — 2,574 passed, 0 failed, 16 expected network-dependent Uniswap skips
  • focused truth-auction suite — 53/53
  • focused escalation-migration suite — 33/33
  • focused final UI guard set — 58/58
  • bun run format:check
  • bun run check
  • bun run knip
  • bun run check:generated-clean
  • git diff --check origin/main...HEAD

Post-merge final review: 98/100 with no High, Medium, or Low findings. Documentation review: 98/100. Focused visual/accessibility review: 95/100.

Screenshots

Security pool context

Desktop (1440×900):

Security pool context desktop

Mobile (390×844):

Security pool context mobile

Proportional liquidation review

Desktop (1440×900):

Liquidation review desktop

Mobile (390×844):

Liquidation review mobile

Screenshots are hosted on Sharey with the longest available 90-day expiry.

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