diff --git a/content/sips/sip-409.md b/content/sips/sip-409.md
new file mode 100644
index 000000000..cb1159d96
--- /dev/null
+++ b/content/sips/sip-409.md
@@ -0,0 +1,64 @@
+---
+sip: 409
+title: Enable WETH as Perps Collateral on Base
+network: Base
+status: Draft
+type: Governance
+author: GUNBOATs (@gunboatsss)
+created: 2024-09-23
+---
+
+<!--You can leave these HTML comments in your merged SIP and delete the visible duplicate text guides, they will not appear and may be helpful to refer to if you edit it again. This is the suggested template for new SIPs. Note that an SIP number will be assigned by an editor. When opening a pull request to submit your SIP, please use an abbreviated title in the filename, `sip-draft_title_abbrev.md`. The title should be 44 characters or less.-->
+
+
+## Simple Summary
+
+<!--"If you can't explain it simply, you don't understand it well enough." Simply describe the outcome the proposed changes intends to achieve. This should be non-technical and accessible to a casual community member.-->
+
+Enable Wrapped Ether as Collateral for Perps on Base.
+
+## Abstract
+
+<!--A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what *will* be done if the SIP is implemented, not *why* it should be done or *how* it will be done. If the SIP proposes deploying a new contract, write, "we propose to deploy a new contract that will do x".-->
+
+Enable Wrapped Ether as Collateral for Perps on Base.
+
+## Motivation
+
+<!--This is the problem statement. This is the *why* of the SIP. It should clearly explain *why* the current state of the protocol is inadequate.  It is critical that you explain *why* the change is needed, if the SIP proposes changing how something is calculated, you must address *why* the current calculation is inaccurate or wrong. This is not the place to describe how the SIP will address the issue!-->
+
+Ether is the first and the most universal asset on Ethereum. Therefore it make sense to have it as collateral on Perps.
+
+## Specification
+
+<!--The specification should describe the syntax and semantics of any new feature, there are five sections
+1. Overview
+2. Rationale
+3. Technical Specification
+4. Test Cases
+5. Configurable Values
+-->
+
+WETH token address on Base: [0x4200000000000000000000000000000000000006](https://basescan.org/token/0x4200000000000000000000000000000000000006)
+
+### Technical Specification
+
+<!--The technical specification should outline the public API of the changes proposed. That is, changes to any of the interfaces Synthetix currently exposes or the creations of new ones.-->
+
+N/A
+
+### Test Cases
+
+<!--Test cases for an implementation are mandatory for SIPs but can be included with the implementation..-->
+
+N/A
+
+### Configurable Values (Via SCCP)
+
+<!--Please list all values configurable via SCCP under this implementation.-->
+
+The configurable values will use the perps' collateral configuration with following SCCP.
+
+## Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
diff --git a/content/sips/sip-410.md b/content/sips/sip-410.md
new file mode 100644
index 000000000..ff5c72b20
--- /dev/null
+++ b/content/sips/sip-410.md
@@ -0,0 +1,64 @@
+---
+sip: 410
+title: Enable EURC as Perps collateral on Base
+network: Base
+status: Draft
+type: Governance
+author: GUNBOATs (@gunboatsss)
+created: 2024-09-23
+---
+
+<!--You can leave these HTML comments in your merged SIP and delete the visible duplicate text guides, they will not appear and may be helpful to refer to if you edit it again. This is the suggested template for new SIPs. Note that an SIP number will be assigned by an editor. When opening a pull request to submit your SIP, please use an abbreviated title in the filename, `sip-draft_title_abbrev.md`. The title should be 44 characters or less.-->
+
+## Simple Summary
+
+<!--"If you can't explain it simply, you don't understand it well enough." Simply describe the outcome the proposed changes intends to achieve. This should be non-technical and accessible to a casual community member.-->
+
+Enable EURC as Perps collateral on Base.
+
+## Abstract
+
+<!--A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what *will* be done if the SIP is implemented, not *why* it should be done or *how* it will be done. If the SIP proposes deploying a new contract, write, "we propose to deploy a new contract that will do x".-->
+
+Enable EURC as Perps collateral on Base.
+
+## Motivation
+
+<!--This is the problem statement. This is the *why* of the SIP. It should clearly explain *why* the current state of the protocol is inadequate.  It is critical that you explain *why* the change is needed, if the SIP proposes changing how something is calculated, you must address *why* the current calculation is inaccurate or wrong. This is not the place to describe how the SIP will address the issue!-->
+
+EURC is a Euro stablecoin issued by Circle. Enabling EURC has a same risk profile as USDC and tapping into access from Euro users on Base.
+
+## Specification
+
+<!--The specification should describe the syntax and semantics of any new feature, there are five sections
+1. Overview
+2. Rationale
+3. Technical Specification
+4. Test Cases
+5. Configurable Values
+-->
+
+EURC token address: [0x60a3e35cc302bfa44cb288bc5a4f316fdb1adb42](https://basescan.org/token/0x60a3e35cc302bfa44cb288bc5a4f316fdb1adb42)
+
+### Technical Specification
+
+<!--The technical specification should outline the public API of the changes proposed. That is, changes to any of the interfaces Synthetix currently exposes or the creations of new ones.-->
+
+N/A
+
+### Test Cases
+
+<!--Test cases for an implementation are mandatory for SIPs but can be included with the implementation..-->
+
+N/A
+
+### Configurable Values (Via SCCP)
+
+<!--Please list all values configurable via SCCP under this implementation.-->
+
+The configurable values will use the perps' collateral configuration with following SCCP.
+
+
+## Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).
diff --git a/content/sips/sip-411.md b/content/sips/sip-411.md
new file mode 100644
index 000000000..17161f6cd
--- /dev/null
+++ b/content/sips/sip-411.md
@@ -0,0 +1,64 @@
+---
+sip: 411
+title: Enable cbETH and cbBTC as Perps collateral on Base
+network: Base
+status: Draft
+type: Governance
+author: GUNBOATs (@gunboatsss)
+created: 2024-09-23
+---
+
+<!--You can leave these HTML comments in your merged SIP and delete the visible duplicate text guides, they will not appear and may be helpful to refer to if you edit it again. This is the suggested template for new SIPs. Note that an SIP number will be assigned by an editor. When opening a pull request to submit your SIP, please use an abbreviated title in the filename, `sip-draft_title_abbrev.md`. The title should be 44 characters or less.-->
+
+## Simple Summary
+
+<!--"If you can't explain it simply, you don't understand it well enough." Simply describe the outcome the proposed changes intends to achieve. This should be non-technical and accessible to a casual community member.-->
+
+Enable Coinbase Wrapped Staked ETH and Coinbase Bitcoin as perps collateral on Base.
+
+## Abstract
+
+<!--A short (~200 word) description of the proposed change, the abstract should clearly describe the proposed change. This is what *will* be done if the SIP is implemented, not *why* it should be done or *how* it will be done. If the SIP proposes deploying a new contract, write, "we propose to deploy a new contract that will do x".-->
+
+Enable Coinbase Wrapped Staked ETH and Coinbase Bitcoin as perps collateral on Base.
+
+## Motivation
+
+<!--This is the problem statement. This is the *why* of the SIP. It should clearly explain *why* the current state of the protocol is inadequate.  It is critical that you explain *why* the change is needed, if the SIP proposes changing how something is calculated, you must address *why* the current calculation is inaccurate or wrong. This is not the place to describe how the SIP will address the issue!-->
+
+As Base deployment is managed by Coinbase, Coinbase wrapped assets are expected to be widely used in the rollup. Listing cbETH and cbBTC bring the Base deployment closer to the ecosystem.
+
+## Specification
+
+<!--The specification should describe the syntax and semantics of any new feature, there are five sections
+1. Overview
+2. Rationale
+3. Technical Specification
+4. Test Cases
+5. Configurable Values
+-->
+
+cbETH token address on Base: [0x2ae3f1ec7f1f5012cfeab0185bfc7aa3cf0dec22](https://basescan.org/token/0x2ae3f1ec7f1f5012cfeab0185bfc7aa3cf0dec22)  
+cbBTC token address on Base: [0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf](https://basescan.org/token/0xcbb7c0000ab88b473b1f5afd9ef808440eed33bf)
+
+### Technical Specification
+
+<!--The technical specification should outline the public API of the changes proposed. That is, changes to any of the interfaces Synthetix currently exposes or the creations of new ones.-->
+
+N/A
+
+### Test Cases
+
+<!--Test cases for an implementation are mandatory for SIPs but can be included with the implementation..-->
+
+N/A
+
+### Configurable Values (Via SCCP)
+
+<!--Please list all values configurable via SCCP under this implementation.-->
+
+The configurable values will use the perps' collateral configuration with following SCCP.
+
+## Copyright
+
+Copyright and related rights waived via [CC0](https://creativecommons.org/publicdomain/zero/1.0/).