Auction escalation REP and bundle liquidation claims - #645
Open
KillariDev wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
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 tscbun 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 skipsbun run format:checkbun run checkbun run knipbun run check:generated-cleangit diff --check origin/main...HEADPost-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):
Mobile (390×844):
Proportional liquidation review
Desktop (1440×900):
Mobile (390×844):
Screenshots are hosted on Sharey with the longest available 90-day expiry.