Skip to content

Move escalation REP custody into EscalationGame#312

Merged
KillariDev merged 4 commits into
mainfrom
t3code/4f690d1b
Jun 17, 2026
Merged

Move escalation REP custody into EscalationGame#312
KillariDev merged 4 commits into
mainfrom
t3code/4f690d1b

Conversation

@KillariDev

@KillariDev KillariDev commented Jun 12, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Moves active escalation REP custody out of SecurityPool and into EscalationGame, so deposits are held and settled as actual REP tokens instead of synthetic locked pool ownership.
  • Splits fork handling into dedicated escalation-fork flow helpers and shared forker types, with clearer vault REP vs escrow REP accounting.
  • Keeps liquidation, bond checks, and truth-auction accounting scoped to unlocked pool REP while treating escalation escrow as a separate asset path.
  • Fixes own-fork migration edge cases around child REP scaling, collateral movement, forked escrow release, late branch mutation, zero-allocation dust, and vault-scoped escrow accounting.
  • Optimizes unresolved escalation migration by tracking vault-local unresolved deposit references instead of scanning full deposit history, and removes the unused import/replay path in favor of continuation proofs plus escrow backing.
  • Moves Solidity test-only contracts under solidity/contracts/test/peripherals and updates contract helpers, simulator utilities, UI diagnostics, and regression tests for the new model.

Validation

  • bun run tsc
  • bun run test (1277 pass, 1 skip, 0 fail)
  • bun run format
  • bun run check
  • bun run knip

Notes

  • Latest origin/main was merged before squashing; it was already up to date.

@KillariDev KillariDev changed the title Refactor Escrowed REP and Fork Migration Path for Security Pools Move Escalation REP Custody Into EscalationGame and Fix Fork Accounting Jun 14, 2026
@KillariDev KillariDev force-pushed the t3code/4f690d1b branch 4 times, most recently from cc27664 to b79ab5f Compare June 14, 2026 14:07
@KillariDev KillariDev changed the title Move Escalation REP Custody Into EscalationGame and Fix Fork Accounting Move escalation REP custody into EscalationGame Jun 17, 2026
# Conflicts:
#	ui/ts/components/SimulationBanner.tsx
- Add outcome-scoped forked escrow tracking in `EscalationGame` with scaled child REP claims.
- Add batched cursor-based local-deposit export and explicit forked-escrow export APIs.
- Require fork snapshots that include resolution balances and support own-fork carry accounting.
- Update forker flow to return incremental migration progress and allocate escrow by original outcome.
- Fix own-fork auctionable REP calculations by using vault-rep-at-fork instead of inherited auctionable total.
- Revert subtraction of vault escrowed REP when computing `viewerVaultAvailableEscalationRep`
- Add regression test ensuring unlocked pool REP remains fully available when already unlocked
@KillariDev KillariDev merged commit 095e590 into main Jun 17, 2026
0 of 6 checks passed
@KillariDev KillariDev deleted the t3code/4f690d1b branch June 17, 2026 12:27
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