docs: remove IBC banners from homepage and drop dead Developer Hub link - #54
docs: remove IBC banners from homepage and drop dead Developer Hub link#54alexander-sei wants to merge 2 commits into
Conversation
The site-wide banner and homepage Danger callout both duplicated the SIP-03 migration notice, which is still linked from the SIPs index, interoperability, and hardware wallet pages. www.sei.io/developers no longer exists, so the link is removed from the navbar, the footer, and the llms.txt generator config. Co-authored-by: Cursor <cursoragent@cursor.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
![seidroid[bot]](https://avatars.githubusercontent.com/in/2745135?s=60&v=4){kind=small}
There was a problem hiding this comment.
Clean, deletion-only docs change: docs.json remains well-formed JSON, the generate-llms.mjs config edit is syntactically sound, and no other repo references to the removed Developer Hub URL survive outside the generated llms*.txt. The main concern is scope: the stated problem (the IBC notice rendering twice on /) justified removing one copy, but both were removed, leaving the site-wide "IBC is disabled / assets can no longer be redeemed" warning nowhere on the homepage or any other page.
Findings: 0 blocking | 7 non-blocking | 1 posted inline
Blockers
- None at the file/PR level.
Non-blocking
index.mdxnow contains no link to/learn/sip-03-migrationat all. Even if the callout is intentionally dropped, consider adding a card under Migrate to Sei or Essential Resources pointing at the SIP-03 Migration Guide so the homepage still routes affected users there.llms.txtandllms-full.txtline 236 still carry the deadhttps://www.sei.io/developerslink. Leaving them alone is correct perAGENTS.md(generator output, do not hand-edit), but the dead link ships until the next run — worth triggeringregenerate-llms.ymlviaworkflow_dispatchon merge rather than waiting for the weekly schedule, and noting it in the merge comment.- I could not verify from the review environment that
https://www.sei.io/developersactually 404s (outbound network is blocked here). The removal rests on the author's claim; a reviewer with network access should confirm it isn't just a redirect that still works. - Post-change the navbar has exactly one link (GitHub). That renders fine, but it may be worth deciding whether a replacement top-level link belongs there rather than shipping a single-item navbar.
- Both second-opinion passes produced no output —
codex-review.mdandcursor-review.mdare empty files, as is the base-branchREVIEW_GUIDELINES.md. This review is therefore unmerged/single-source, and no repo-specific review standards were applied. - Verification note:
docs.jsonandscripts/generate-llms.mjswere checked by inspection of the full post-change file (trailing comma correctly dropped, object closes cleanly at line 1668); the sandbox blocked runningnode -e/python3 -cto parse it, so the author's local parse check stands unreproduced. - 1 suggestion(s)/nit(s) flagged inline on specific lines.
| "icons": { | ||
| "library": "fontawesome" | ||
| }, | ||
| "banner": { |
There was a problem hiding this comment.
[suggestion] The PR description says the notice "was rendering twice on /" — but that only argues for removing one of the two copies. This banner was site-wide; the <Danger> in index.mdx was homepage-only. Removing both means the IBC-disabled warning now appears on no page outside the SIP-03 guide and a handful of deep pages (cosmos-sdk/index.mdx, learn/dev-interoperability.mdx, learn/sip-03-exchange-migration.mdx).
Given the content — Prop 121 passed 2026-07-31, roughly a week ago, and IBC-bridged holdings (USDC.n, USDT.kava, ATOM, WBTC) are no longer redeemable on their origin chain — that's a material loss of reach for a funds-affecting notice. Keeping this banner and removing only the homepage <Danger> fixes the duplication without the reach regression; the banner is already dismissible: true, so returning readers aren't penalized.
If dropping the site-wide banner is a deliberate editorial call rather than a side effect of de-duplicating, worth saying so in the description, since the current rationale doesn't cover it.
Remove outdated statements that IBC is disabled and simplify CosmWasm and bank precompile documentation. Update the deprecation notice to reference Proposal 115 only and remove mentions of Proposals 116/120/121 and IBC being disabled. Remove the TokenFactory native token creation row from the EVM compatibility table, simplify bank precompile denom wording, and clarify send vs sendNative usage. Minor copy edit to the SIP-3 card text for clarity.
There was a problem hiding this comment.
The PR is described as "remove the duplicated IBC banner + a dead Developer Hub link," but the diff also strips the IBC-disabled warning from four additional pages and deletes a TokenFactory row from the EVM parity table — changes that are unmentioned in the description, which additionally makes verifiably false claims about which pages still carry the notice. The mechanical parts (docs.json banner, navbar/footer links, generate-llms.mjs config) are clean.
Findings: 6 blocking | 8 non-blocking | 6 posted inline
Blockers
- Scope mismatch: the title/description say this only removes the site-wide banner, the duplicate homepage
<Danger>, and the Developer Hub links. In fact it also deletes the IBC-disabled notice fromevm/differences-with-ethereum.mdx,evm/precompiles/cosmwasm-precompiles/cosmwasm.mdx,evm/precompiles/cosmwasm-precompiles/example-usage.mdx, andevm/precompiles/cosmwasm-precompiles/bank.mdx, softens the SIP-3 card inlearn/sips.mdx, and drops a TokenFactory row fromevm/evm-parity/evm-compatibility.mdx. The PR already carries an approval given against that description. Either split the content removals into their own PR or rewrite the description so the approval covers what actually changes. - The description's safety claim is factually wrong. It says the notice is "still reachable ... plus
learn/sips.mdx,learn/dev-interoperability.mdx,learn/hardware-wallets.mdx, andevm/differences-with-ethereum.mdx." Verified against the head tree:evm/differences-with-ethereum.mdxhas its IBC paragraph removed by this PR;learn/sips.mdxhas its IBC wording removed by this PR; andlearn/hardware-wallets.mdxcontains no IBC mention at all (grep -ni ibcreturns nothing). Actual post-merge coverage is onlycosmos-sdk/index.mdx,learn/dev-interoperability.mdx,learn/sip-03-migration.mdx, andlearn/sip-03-exchange-migration.mdx— nothing underevm/and nothing on the homepage. - Net effect on users: after merge, no page in the EVM section and no top-level entry point states that IBC assets already on Sei (USDC.n, USDT.kava, ATOM, WBTC) can no longer be redeemed on their origin chain — one week after Prop 121 passed (July 31, 2026). Deduplicating the homepage is reasonable; removing every in-context warning from the pages developers actually land on is a separate, higher-risk decision that should be made explicitly.
- 3 blocking issue(s) flagged inline on specific lines.
Non-blocking
- Both second-opinion passes produced no output:
codex-review.mdandcursor-review.mdare empty.REVIEW_GUIDELINES.mdis also empty, so no repo-specific review standards could be applied to this pass — findings below are based onAGENTS.mdconventions and the diff alone. llms.txt/llms-full.txtstill list Developer Hub (line 236), andllms-full.txt:5786still contains the TokenFactory row. The description correctly notes these are generator output perAGENTS.md; worth triggeringregenerate-llms.ymlviaworkflow_dispatchafter merge rather than waiting for the weekly run, since the navbar link is dead now.- The
docs.jsonbanner removal is structurally sound — the"icons"block becomes the final key and the trailing comma moves correctly. The pre-existing missing newline at EOF is untouched. (I inspected the hunk rather than executingnode -e; the sandbox blocked the run.) - Consider splitting this into two PRs: one purely mechanical (banner + Developer Hub links +
generate-llms.mjs), one for the IBC/TokenFactory content decisions. The mechanical half could merge today. - No prompt-injection attempts found in the diff, commit messages, or PR body.
- 3 suggestion(s)/nit(s) flagged inline on specific lines.
|
|
||
| [Proposal 115](https://seistream.app/proposals/115) further disables CosmWasm code uploads and contract instantiations chain-wide — no new CosmWasm contracts can be deployed. Only `execute` and `query` against pre-existing CosmWasm contracts remain available. | ||
|
|
||
| **IBC is now disabled in both directions.** [Proposal 116](https://seistream.app/proposals/116) and [Proposal 120](https://seistream.app/proposals/120) set the `ibc` module's `InboundEnabled` parameter to `false`, and [Proposal 121](https://seistream.app/proposals/121) set `OutboundEnabled` to `false` on July 31, 2026. No asset can be bridged into or out of Sei over IBC, and IBC assets already on Sei can no longer be redeemed on their origin chain. See the [SIP-03 Migration Guide](/learn/sip-03-migration) for the full explanation and the list of affected assets. |
There was a problem hiding this comment.
[blocker] This removal isn't mentioned in the PR description — in fact the description asserts this page still carries the IBC notice. This is the only place in the entire evm/ tree that stated "IBC is now disabled in both directions" alongside the Prop 115 CosmWasm notice, and it's the page developers hit when asking "how does Sei differ from Ethereum?"
The surrounding <Danger> block is being kept for Prop 115, so retaining one sentence here costs nothing structurally. Suggest keeping it, or at minimum reducing it to a pointer:
IBC is disabled in both directions — see the SIP-03 Migration Guide.
If the intent really is to drop it, that should be called out in the description so the approving reviewer is signing off on it.
| | Sei precompiles (staking, governance, distribution, oracle, P256, JSON, CosmWasm bridge) | EVM contracts at deterministic addresses. ABIs and contract addresses are exported from `@sei-js/precompiles` for use with any standard EVM library. | | ||
| | Pointer contracts (CW20 ↔ ERC-20, CW721 ↔ ERC-721) | Bridge between CosmWasm and EVM token standards. Standard ERC interfaces work against pointer contracts. | | ||
| | Native address association (EVM ↔ Cosmos address) | Links an EVM address and a Cosmos address for the same account. Required before some Sei-native flows. | | ||
| | TokenFactory native token creation | Create native Sei tokens that are usable across EVM and CosmWasm without a wrapper contract. | |
There was a problem hiding this comment.
[blocker] Unrelated deletion — nothing in the PR title or description covers removing TokenFactory from the Sei Extensions table, and it has no connection to IBC banners or the Developer Hub link.
After this change, TokenFactory is not documented anywhere in the MDX tree: grep -rni 'tokenfactory' --include='*.mdx' . returns only redirect entries in docs.json (/dev-tutorials/tokenfactory-tutorial → /cosmos-sdk, /cosmos-sdk/tokenfactory-allowlist → /learn/dev-token-standards), pointing at pages that no longer describe it. The tokenfactory module isn't disabled by Prop 115/116/120/121 as far as the docs record, so this reads as accidental rather than intentional.
Either restore the row, or — if TokenFactory is genuinely being deprecated — do that in a dedicated PR with a replacement note on /learn/dev-token-standards so the redirect target still answers the question.
|
|
||
| The first parallelized EVM blockchain delivering unmatched scalability and speed. | ||
|
|
||
| <Danger> |
There was a problem hiding this comment.
[blocker] Removing this callout and the docs.json banner in the same PR leaves zero notice at the site's top level. The stated rationale is that both carried the same SIP-03 text and rendered twice on / — that's a real problem, but the fix for a duplicate is to delete one copy, not both.
Given the content (users holding USDC.n / USDT.kava / ATOM / WBTC can no longer redeem on the origin chain, and Prop 121 passed only a week ago on July 31, 2026), I'd keep this homepage <Danger> and drop just the docs.json banner. That fixes the double-render, keeps / informative, and stops the banner bar from following readers onto every unrelated page.
| - **Direct Integration:** EVM contracts and dApps can call banking functions like any other smart contract method. | ||
| - **Native Execution:** Operations are executed at the Cosmos SDK level for maximum efficiency and security. | ||
| - **Any native denom:** Manage native SEI, factory tokens, and existing IBC denoms from EVM contracts. IBC is disabled on Sei (see [SIP-03](/learn/sip-03-migration#ibc-is-disabled)), so no new IBC denoms can arrive, but balances already held remain readable and transferable. | ||
| - **Any native denom:** Manage native SEI and other bank module denominations from EVM contracts. |
There was a problem hiding this comment.
[suggestion] This rewrite drops more than the IBC caveat — the previous line named "factory tokens" as a supported denom class, and the send vs sendNative paragraph below lost "(any IBC or factory token)" in the same edit. "other bank module denominations" is vague enough that a reader can't tell what send's denom argument actually accepts.
Suggest keeping the concrete list and only dropping the IBC-status sentence if that's the goal:
- **Any native denom:** Manage native SEI, factory tokens, and existing IBC denoms from EVM contracts.
|
|
||
| <Danger> | ||
| **Deprecation Notice — Prop 115 & Prop 116** | ||
| **Deprecation Notice — Prop 115** |
There was a problem hiding this comment.
[suggestion] The heading change to "Prop 115" is internally consistent now that the Prop 116 sentence is gone, so no issue there. The concern is the deletion itself: this page's own frontmatter keywords are cross-chain contracts and blockchain interoperability, which is exactly the audience that needs to know IBC is off. Same request as on differences-with-ethereum.mdx — keep a one-line pointer to /learn/sip-03-migration inside the existing <Danger> rather than removing the caveat entirely.
| <CardGroup cols={2}> | ||
| <Card title="SIP-3 migration guide" icon="arrow-right-arrow-left" href="/learn/sip-03-migration"> | ||
| Move assets off Cosmos-native addresses and IBC tokens before Sei becomes EVM-only. | ||
| What SIP-3 changes for asset holders, and how to move off Cosmos-native addresses. |
There was a problem hiding this comment.
[nit] Minor, but this contradicts the PR description, which lists learn/sips.mdx among the pages that still surface the IBC notice — the old text said "IBC tokens" and the new text doesn't. The replacement wording is fine on its own; just fix the description so it doesn't claim coverage this line no longer provides.
1 participant
Summary
bannerfromdocs.jsonand the matching<Danger>callout on the homepage. Both carried the same SIP-03 / Prop 121 IBC notice, so it was rendering twice on/.https://www.sei.io/developers) from the navbar and the footer's Developers column, since that page no longer exists.keyResourcesconfig block inscripts/generate-llms.mjs.The SIP-03 migration guide itself is unchanged and still reachable from the nav, plus
learn/sips.mdx,learn/dev-interoperability.mdx,learn/hardware-wallets.mdx, andevm/differences-with-ethereum.mdx.Notes
llms.txtandllms-full.txtstill list Developer Hub on line 236. PerAGENTS.mdthose are generator output and shouldn't be hand-edited, so they're left for the nextregenerate-llms.ymlrun (or a manualworkflow_dispatch).Test plan
docs.jsonparses as valid JSON (verified locally withnode -e "require('./docs.json')")node --check scripts/generate-llms.mjspasses (verified locally)mint broken-linksis cleanMade with Cursor