feat(precompiles)!: remove IBC and Oracle precompiles

[alexander-sei]

Closes PLT-977.

Note

Stacked on #323 — both touch the ethers barrel and the ethers spec, so this is based on that branch to avoid a conflict. Review #323 first; retarget this to main once it merges.

Why

The IBC and Oracle precompiles are no longer supported on Sei (see CON-283 and CON-205), but the package still shipped a full public surface for both, pointing integrators at endpoints that will fail. Same shape of change as #279, which removed the confidential transfers precompile.

What

Deletes the six source files (precompiles/, ethers/, viem/ for each) and prunes all three barrels and both spec files. Ten exports are removed:

Entrypoint	IBC	Oracle
precompiles/	IBC_PRECOMPILE_ADDRESS, IBC_PRECOMPILE_ABI	ORACLE_PRECOMPILE_ADDRESS, ORACLE_PRECOMPILE_ABI
ethers/	ETHERS_IBC_PRECOMPILE_ABI, getIbcPrecompileEthersV6Contract	ETHERS_ORACLE_PRECOMPILE_ABI, getOraclePrecompileEthersV6Contract
viem/	VIEM_IBC_PRECOMPILE_ABI	VIEM_ORACLE_PRECOMPILE_ABI

Versioning

This removes ten public exports, so it ships as a major (3.0.0). Caret ranges on ^2.x (including this repo's own create-sei templates) will not pick the removal up automatically.

Blast radius

Nothing else in the monorepo referenced these — create-sei's extension and next-template only use the bank precompile, and they pin ^2.1.2. The only remaining ibc/oracle matches in the repo are @sei-js/registry's IBC chain registry, which is unrelated and stays, and the historical changelog.

Verification

• tsc --noEmit clean, 35/35 jest tests pass, biome clean, changeset status resolves @sei-js/precompiles to major.
• The barrel parity test added in fix(precompiles): export solo precompile from ethers entrypoint #323 passes unchanged here: it derives precompile names from each barrel rather than hardcoding a count, so it follows the set down from 12 to 10 and would fail if a barrel got out of sync during the removal.
• Note that the run-tests job does not run on this PR — coverage.yml only triggers for PRs targeting main or feature/**. It will run once this is retargeted to main. build does run and passes.

[seidroid]

A clean, well-scoped deletion of the unsupported IBC and Oracle precompiles: all six source files, three barrels, and both spec files are pruned consistently, no dangling references remain anywhere in the repo, and the changeset is present. The only open items are non-blocking: an explicit call on minor vs major for removing ten public exports, and changelog wording that offers inlining as a migration path for precompiles that no longer work on-chain.

Findings: 0 blocking | 7 non-blocking | 2 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• Cursor's second-opinion pass produced no output (cursor-review.md is empty), so this synthesis reflects only my pass plus Codex's.
• Independently verified the removal is complete: repo-wide grep for IBC_PRECOMPILE* / ORACLE_PRECOMPILE* / getIbcPrecompileEthersV6Contract / getOraclePrecompileEthersV6Contract / oracle finds no remaining references outside the new changeset and the historical packages/precompiles/CHANGELOG.md. src/index.ts re-exports the three barrels with export *, so the removal propagates to the package root entrypoint as well, and neither spec file has a hardcoded precompile count that would silently drift.
• The PR description states the minor bump matches "how #279 shipped the equivalent removal", but packages/precompiles/CHANGELOG.md:13-17 shows that removal shipped as a patch (2.1.2: "Fixed oracle precompile address ... and removed confidential transfers"). The direction (not a major) matches precedent; the level does not. Worth correcting the description so the versioning rationale rests on the actual precedent.
• Merge-order hazard: the PR base is #323's branch, not main. Merging in the wrong order (or squashing #323 without retargeting) would pull #323's barrel-parity test in as part of this PR's history or lose it. The author flagged this — just confirming a human needs to sequence it.
• I disagree with Codex's prompt-injection finding on the PR description. "Review #323 first; retarget this to main once it merges" is ordinary author-to-reviewer prose about stacked-branch logistics, not an attempt to redirect a reviewer agent's instructions or verdict. Flagging it risks desensitizing reviewers to real injection attempts.
• 2 suggestion(s)/nit(s) flagged inline on specific lines.

[seidroid]

[suggestion] Semver: this deletes ten public exports, so a minor lets any consumer on ^2.1.x pick it up on a routine pnpm update and fail to compile. Strict semver would call for major.

Two things temper this, which is why I'm raising it as a suggestion rather than a blocker:

• The repo has precedent for shipping exactly this shape of removal below major. Note that the precedent is looser than the PR description claims: Fixed Oracle Precompile Address & Removed Confidential Transfers Precompile #279 shipped as a patch (packages/precompiles/CHANGELOG.md:13-17, 2.1.2), not a minor. Worth fixing that sentence in the description either way.
• The failure mode is a compile error at the import site, not silent misbehaviour — and since these precompiles are already unsupported on-chain, the pre-removal runtime behaviour was a failing call anyway.

So the substantive question is just whether the team wants 2.2.0 or 3.0.0 here. Flagging for an explicit call rather than asserting the bump is wrong.

[seidroid]

[suggestion] "Consumers still calling these precompiles must inline the address and ABI themselves" sits awkwardly against the PR's own rationale that IBC and Oracle are no longer supported on Sei (CON-283/CON-205). As written it reads as a working migration path — inline 0x...1009 / 0x...1008 and carry on — when the calls will fail regardless of where the ABI lives.

Since the changeset body is what lands in the published changelog, it's the one place downstream integrators will look. Suggest saying the precompiles are no longer supported on-chain and that calls to them fail, then pointing at the replacement path (or stating there isn't one) instead of offering inlining as the remedy.

[alexander-sei]

Both review notes addressed in 29e24a9 and the updated description.

minor vs major — flagging it was right, and this is an explicit call rather than a default: minor, kept deliberately. Reasoning is now written into the description instead of being implicit.

Thanks for catching the precedent error — #279 shipped as a patch (2.1.2), not a minor. The description said this PR "matched" #279, which overstated the precedent in my favour. Corrected: the precedent is looser than what is proposed here, and minor sits between it and strict semver. Still happy to move to major if you would rather hold the strict line.

"inline the address and ABI themselves" — agreed, that read as a working migration path when it is not one. The changeset now says the precompiles are unsupported on-chain, that calls fail wherever the ABI comes from, and that there is no drop-in replacement.

[seidroid]

Clean, complete removal of the IBC and Oracle precompiles — all six source files deleted, all three barrels and both spec fixture tables pruned consistently, and a changeset is present with a clear migration note. The only substantive discussion point is the deliberate choice to ship a public-export removal as a minor rather than a major; nothing here is a correctness or security defect.

Findings: 0 blocking | 6 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• Verified the blast-radius claim independently: after this diff there are zero remaining IBC_PRECOMPILE_* / ORACLE_PRECOMPILE_* / getIbcPrecompile* / getOraclePrecompile* references anywhere outside the changeset itself and the historical CHANGELOG. create-sei's extension and next-template only import BANK_PRECOMPILE_ADDRESS / VIEM_BANK_PRECOMPILE_ABI, and packages/registry's IBC chain registry is unrelated. There is also no typedoc config or docs manifest in packages/precompiles that enumerated the removed files, so nothing is left dangling.
• The barrelParity.spec.ts assertion added in #323 does hold up here as claimed — it derives names via regex over each barrel's exports rather than a hardcoded count, so it tracks the set down from 12 to 10 and would fail if any one barrel were pruned inconsistently. No new test is needed for a deletion of this shape.
• Per the PR note, this targets the #323 branch rather than main, so coverage.yml does not run run-tests on this PR. Worth confirming the full suite is green after retargeting, since the ethers/viem spec fixture tables changed here and only build has exercised them so far.
• The Cursor second-opinion pass produced no output (cursor-review.md is empty), so this review is not corroborated by it. The Codex pass reported "No material issues found in the reviewed diff," which matches my read.
• Docs outside this repo (docs.sei.io, any published typedoc output) may still document the removed exports. Out of scope for this PR, but worth a follow-up so integrators aren't pointed at endpoints that no longer exist in the package or on-chain.
• 1 suggestion(s)/nit(s) flagged inline on specific lines.

[seidroid]

[suggestion] Non-blocking, and I see you explicitly invited this call in the description — but I lean toward major here.

The concrete cost of minor is that caret ranges don't protect anyone. This repo's own packages/create-sei/extensions/precompiles/package.json and templates/next-template/package.json both depend on "@sei-js/precompiles": "^2.1.2", so 2.2.0 is picked up automatically on any fresh install or lockfile refresh. Downstream dApps on ^2.x are in the same position: they receive the removal without an intentional upgrade step. A major is exactly the mechanism that makes the removal opt-in, and it's cheap here — there is no coordinated bump to worry about, since .changeset/config.json sets fixed: [] and linked: [].

On the two arguments for minor: the #279 precedent (patch) is real, but a prior looser call is weak justification for a second one rather than a reason to tighten. And "compile error, not silent misbehaviour" is the right read of the failure mode — it's a loud break — but semver's major signal is about whether consumers opted in, not about how loudly the break surfaces. The **Breaking:** marker in the body does keep the changelog honest, which mitigates but doesn't replace the range semantics.

Happy to defer if the team prefers holding to the #279 precedent; flagging so it's a recorded decision rather than an assumed one.

[cursor]

PR Summary

Medium Risk
Major breaking API removal of ten public exports; low runtime risk since the precompiles already fail on-chain, but dependents still importing them will break at compile time.

Overview
Breaking: removes the IBC and Oracle precompiles from @sei-js/precompiles because they are no longer supported on Sei and on-chain calls already fail.

Deletes the address/ABI definitions plus ethers and viem wrappers, and drops the related barrel exports and tests. Ten public symbols are gone (IBC_* / ORACLE_* addresses and ABIs, ethers factories, and viem ABIs), with no drop-in replacement—consumers must stop using these precompiles.

^{Reviewed by Cursor Bugbot for commit 4407866. Bugbot is set up for automated code reviews on this repo. Configure here.}

[seidroid]

A clean, complete removal of the IBC and Oracle precompiles: all six source files deleted, all three barrels and both spec files pruned in step, no dangling references anywhere in the monorepo, and a correctly-scoped major changeset. No blocking issues — the only notes are procedural (retarget off the stacked base so run-tests actually runs) and a request to cite a public source for the "no longer supported" claim.

Findings: 0 blocking | 5 non-blocking | 1 posted inline

Blockers

• None at the file/PR level.

Non-blocking

• Retarget to main before merging. The PR is based on fix/plt-848-solo-ethers-barrel (stacked on #323), and coverage.yml only triggers for PRs targeting main or feature/** — so the run-tests job has not executed on this PR. The author flags this in the description; worth confirming the test run is green post-retarget, since the barrel parity test is the main guard that the three barrels stayed in sync through the removal.
• Removal rationale is unverifiable from the repo. Per guideline §2, packages/precompiles/src/precompiles/*.ts is hand-maintained source of truth, and this deletes two documented addresses (0x...1009 IBC, 0x...1008 Oracle). The justification cites CON-283 and CON-205, which is appropriate sourcing for reviewers, but neither the diff nor public docs confirm the deprecation. Nothing here looks wrong — flagging only so the deprecation is confirmed against docs.sei.io / sei-chain before a major ships.
• Cursor's second-opinion pass produced no output (cursor-review.md is empty), so this review reflects only Codex's pass ("No material issues found in the PR diff") merged with my own.
• Verified independently: a repo-wide grep for IBC_PRECOMPILE|ORACLE_PRECOMPILE|getIbcPrecompile|getOraclePrecompile across .ts/.tsx/.js/.json/.md/.mdx matches only the changeset text itself. mcp-server, create-sei templates, and packages/precompiles/README.md contain no references to either precompile, so the stated blast radius holds. barrelParity.spec.ts derives precompile names from each barrel by regex rather than a hardcoded count, so it continues to guard three-way barrel/factory parity at the reduced set.
• 1 suggestion(s)/nit(s) flagged inline on specific lines.

[seidroid]

[nit] This changeset is the release note downstream integrators will read, and "Neither precompile is supported on Sei any more" is the whole basis for the breaking change — but it points at nothing they can check. CON-283 / CON-205 are internal and won't resolve for them.

Consider linking a public source (docs.sei.io deprecation notice, or the sei-chain PR/upgrade that removed the precompiles) so integrators hitting a failed build can confirm the on-chain reality for themselves rather than having to take the note on faith. The rest of the wording is good — explicitly saying there is no drop-in replacement and that re-declaring the address locally won't help is exactly the right thing to tell someone who is about to do precisely that.

[alexander-sei]

Superseded by #326 — rebased onto main after #323 merged; this PR could not be reopened after the force-push.