Repository navigation
Remove Origin Sonic contracts and automation - #3017
Merged
Merged
Conversation
OS is being wound down: the staking strategy and SwapX AMO are empty and the vault holds enough wS for every outstanding claim. Git history keeps the code if it is ever needed again. - delete the Sonic Solidity sources (vault, OS/wOS, staking strategy, validator delegator, SwapX AMO, harvester, zapper, SwapX/Metropolis pool boosters, proxies, interfaces, MockSFC) and the sonic deploy folder - delete the six Sonic-only Talos actions, their helpers and curated ABIs, and drop their schedules (seed DELETEs the existing rows) - keep otokenAddWithdrawalQueueLiquidity on Sonic: the dapp only shows a request as claimable once the queue's claimable amount covers it - remove the Sonic ops CLI tasks, Sonic from permissionedRebase and the deploy framework, and update docs, CLAUDE.md and agent skills - keep deployments/sonic and addresses.sonic as the address registry
Resolve conflicts with #2973, which removed the permissionedRebase action and its schedules: take master's deletion, drop the Sonic rows on top, and regenerate the Talos inventory.
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
Origin Sonic (OS) is being wound down. Its staking strategy and SwapX AMO are empty, and the vault holds enough wS to cover every claim. This PR removes the Sonic code and automation from the repo. Git history keeps it if we ever need it again.
On-chain state checked at Sonic block ~80.56M:
deployments/sonic/OSVault.json, so deleting026_VaultUpgrade.s.soldrops nothing pending.Code Change
Removed
OSVault,OSonic,WOSonicSonicStakingStrategy,SonicValidatorDelegator,SonicSwapXAMOStrategyOSonicHarvester,OSonicZapperSonicProxiesMockWSandMockSFCscripts/deploy/sonic/folder andbuild/deployments-146.json.DeployManagerandBase.s.solno longer map chain 146.otokenOsRebase,otokenOsCollectAndRelease,otokenOsSonicRestakeRewards,sonicUndelegate,sonicClaimWithdrawals,manageBribeOnSonicpermissionedRebaseitself was removed on master by Add Admin Role to Vault #2973 (merged into this branch)utils/sonic.js,utils/sonicActions.jsabi/sonic_staking_strategy.json,abi/poolBoosterSwapX.json,abi/vault.json,abi/poolBoosterCentralRegistry.json. Only the Sonic actions used them; I checked this repo and the org.pnpm opstaskssonicDefaultValidatorandsonicStaking, plus the Sonic branches intasks/vault.jsanddepositWETH.ACTIONS.md, the Talos inventory (regenerated),CLAUDE.mdand the agent skills.Kept on purpose
otokenAddWithdrawalQueueLiquidityon Sonic (every 10 min).claimWithdrawalfunds the queue on its own. But the dapp (oplabs/defilibs/defi/rebasing/src/hooks.ts) only marks a request claimable whenqueued <= withdrawalQueueMetadata.claimable. Without this poke, OS holders would stay stuck at "pending". The Base/Plume discussion in June 2026 reached the same conclusion. This keeps chain 146 intasks/lib/{network,contracts,deployments}.tsandSONIC_PROVIDER_URLin the runner image.deployments/sonic/*andaddresses.sonicstay as the address registry.brownie/stays: it holds the historical strategist runlogs.Talos schedules (
seed_schedules.sql)The seed now deletes the 6 obsolete Sonic rows on the next boot:
sonic_staking_request_withdrawsonic_staking_claim_withdrawotoken_os_collectAndReleaseotoken_os_sonicRestakeRewardsotoken_os_rebasemodule_rebase_sonic(Add Admin Role to Vault #2973 removed its insert row; this also deletes the existing row)The insert is
ON CONFLICT DO NOTHING, so this uses the same pattern as the Plume row.otoken_addWithdrawalQueueLiquidity_sonicis unchanged.Deploy file vs Talos actions check
The deleted deploy script
sonic/026_VaultUpgradedeployedOSVault(OSONIC_VAULT_IMPL). The only Talos action that still touches Sonic isotokenAddWithdrawalQueueLiquidity. It resolvesOSonicVaultProxyfrom the kept descriptor and uses the curatedabi/IVault.json, so nothing changes for it.Testing
make build-contracts,build-tests-unit,build-tests-fork,build-tests-smokeandbuild-scriptsall pass.tests/unit/**).pnpm test:tasks(75),pnpm test:scripts(66) andpnpm test:layouts(11) all pass. eslint is clean.claimWithdrawalafter the delay, with no keeper: the user receives 100k wS.otokenAddWithdrawalQueueLiquidity --network sonicrun withFORK=true IMPERSONATE=<talos relayer>: it adds the 100k shortfall, andclaimablemoves from 72.22M to 72.32M.🤖 Generated with Claude Code