sei-protocol · alexander-sei · Aug 1, 2026 · Aug 1, 2026
diff --git a/docs.json b/docs.json
@@ -78,6 +78,7 @@
             "pages": [
               "learn/general-governance",
               "learn/proposals",
+              "learn/sips",
               "learn/general-staking"
             ]
           },

diff --git a/learn/sips.mdx b/learn/sips.mdx
@@ -0,0 +1,121 @@
+---
+title: 'Sei Improvement Proposals'
+sidebarTitle: 'SIPs'
+description: 'Browse every Sei Improvement Proposal (SIP) with status, type, authorship, and section outlines pulled live from the sei-protocol/sips repository.'
+keywords: ['SIP', 'Sei Improvement Proposal', 'sei governance', 'protocol proposals', 'SIP process', 'SIP status', 'SIP-1', 'SIP-3', 'sei-protocol/sips']
+---
+
+import { SipIndex } from '/snippets/sip-index.jsx';
+
+A Sei Improvement Proposal (SIP) is a design document for a change to Sei. It might cover a new protocol feature, a change to how the project runs, or a convention for the wider ecosystem. Writing one is how you put an idea in front of the community, and how the reasoning behind a decision gets recorded.
+
+Every SIP lives in the [sei-protocol/sips](https://github.com/sei-protocol/sips) repository, and the list below reads from it directly. Titles, statuses, authors, and section outlines come from the source files rather than a copy that can fall behind.
+
+<Info>
+
+A SIP is not the same as an on-chain governance proposal. The SIP holds the design and the reasoning; the on-chain proposal is the vote that enacts it. One SIP can take several governance proposals to carry out, as SIP-3 did. For the on-chain process, see [Governance](/learn/general-governance) and [Proposals](/learn/proposals).
+
+</Info>
+
+## All proposals
+
+<SipIndex />
+
+## Proposal types
+
+Every SIP declares a type, and the type decides how much community consensus it needs. [SIP-1](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#sip-type) defines all three.
+
+| Type | Scope | Needs consensus |
+| --- | --- | --- |
+| [Standard](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#standard) | Changes that affect most implementations of Sei, such as consensus, networking, RPC, EVM and CosmWasm behavior, and contract standards. Must also declare a category. | Yes |
+| [Process](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#process) | Changes around Sei rather than inside it, such as developer tooling, node and validator procedures, and the SIP process itself. | Yes |
+| [Informational](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#informational) | Guidelines or information for the community, with no change to the protocol or development environment. | No |
+
+### Categories
+
+A Standard SIP must also declare one of five [categories](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#sip-category).
+
+| Category | Covers |
+| --- | --- |
+| Core | Consensus, execution, storage, and account signatures |
+| Networking | Mempool and network protocols |
+| Interface | RPC specifications and lower-level naming conventions |
+| Framework | EVM and CosmWasm contracts and primitives included in the Sei codebase |
+| Application | New EVM or CosmWasm standards and primitives that sit outside the Sei codebase |
+
+## Status lifecycle
+
+A successful SIP usually moves through Draft, Review, Last Call, Final, Implemented, and Activated. Each card above shows the status recorded in that proposal's own source file.
+
+| Status | What it means |
+| --- | --- |
+| [Idea](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#idea) | Written, but not yet admitted to the process and not yet numbered. |
+| [Draft](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#draft) | An editor has accepted the formatting and assigned a number. The author now gathers community feedback. |
+| [Review](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#review) | The author has worked through early feedback. Assigned reviewers now give a formal review, and it takes at least three of them. |
+| [Fast Track](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#fast-track) | For proposals that already reached consensus outside the SIP process. Runs the same way as Review. |
+| [Last Call](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#last-call) | A final window for objections, usually at least one week. |
+| [Final](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#final) | Accepted, and the specification is now frozen. |
+| [Implemented](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#implemented) | Development is complete, but the feature is not yet live on mainnet. |
+| [Activated](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#activated) | Live on Sei mainnet. |
+| [Stagnant](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#stagnant) | Inactive for four weeks while in Draft, Review, or Last Call. |
+| [Withdrawn](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#withdrawn) | The author has withdrawn the proposal. |
+| [Living](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#living) | A continuously updated proposal that never reaches Final, such as SIP-1 itself. |
+
+<Note>
+
+Once a SIP reaches Final, nobody can withdraw or edit it. To change an accepted specification, submit a new SIP that extends or replaces the original.
+
+</Note>
+
+## Guides for specific proposals
+
+SIP-3 and SIP-4 both affect how you use and build on Sei. These pages cover what they mean in practice.
+
+<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.
+  </Card>
+  <Card title="SIP-3 for exchanges" icon="building-columns" href="/learn/sip-03-exchange-migration">
+    Integration changes for exchanges and custodians supporting Sei deposits and withdrawals.
+  </Card>
+  <Card title="Gas and transaction fees" icon="gas-pump" href="/learn/dev-gas">
+    How Sei's EIP-1559 implementation works, including the parameters SIP-4 revises.
+  </Card>
+  <Card title="Cosmos-SDK deprecation" icon="triangle-exclamation" href="/cosmos-sdk">
+    Legacy Cosmos SDK and CosmWasm documentation, deprecated under SIP-3.
+  </Card>
+</CardGroup>
+
+## Submit a proposal
+
+Anyone can author a SIP. Talk the idea over with the community before you write it, so you can gauge whether the proposal is needed at all.
+
+<Steps>
+
+<Step title="Read SIP-1">
+[SIP-1](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md) defines the process, the header fields your file needs, and what authors and editors are each responsible for.
+</Step>
+
+<Step title="Raise the idea with the community">
+Open a thread in [GitHub Discussions](https://github.com/sei-protocol/sips/discussions) to collect early feedback, especially from the people who would implement the change.
+</Step>
+
+<Step title="Fork the repository and add your file">
+Fork [sei-protocol/sips](https://github.com/sei-protocol/sips) and create your proposal at `sips/sip-temporary_title.md`. Put any images in `assets/sip-temporary_title/`.
+</Step>
+
+<Step title="Match the required format">
+Start the file with the two-column header table and follow the section structure described in [SIP format](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#sip-format). Keep the title under 64 characters and don't end it with a period.
+</Step>
+
+<Step title="Open a pull request">
+Submit the pull request from your fork. A [SIP editor](https://github.com/sei-protocol/sips/blob/main/sips/sip-1.md#sip-editor) reviews the formatting, assigns a number, moves the status to Draft, and opens the official comments thread.
+</Step>
+
+</Steps>
+
+<Tip>
+
+From Draft onward, keeping the proposal moving is your job. An editor will help you find the right people to talk to, but won't chase the process for you.
+
+</Tip>