init

content/sips/sip-341.md

@@ -51,6 +51,8 @@ The proposed implementation continues to allow the owner address to execute SCCP
 - Create a `setConfigurer` function that can only be called by the system owner.
 - Add a `nominateConfigurer` and `acceptConfigurer` function, such that the configurer (and only the configurer) can transfer its status to another address.
 
+The particular functions that will integrate this functionality will be specified in future SIPs.
+
 ### Configurable Values
 
 - `configurer` - The configurer address, which can be set to the zero address by default.

content/sips/sip-367.md

@@ -30,7 +30,7 @@ This SIP concerns itself with the Pre-Launch and Beta Launch plans and timeline
 1. **Pre-Launch Preparation** Deploy to Arbitrum testnet, begin risk assessment, analyze differences between Arbitrum & existing deployments.
 2. **Beta Launch Phase** (By March 17th) Deploy Synthetix V3 Omnibus on Arbitrum, initially activating LP deposits and stablecoin minting.
 3. **LP Rampup & Collateral Onboarding** Attract a critical mass of LP collateral which can be used to issue stablecoins.
-4. **Enabling Synthetix Perps** Enable the Synthetix Perps market, allowing users to delegate their collateral and subsequent liquidity to Synthetix Perps.
+4. **Enabling Synthetix Perps** Enable the Synthetix Perps market, allowing users to delegate their collateral and subsequent liquidity to Synthetix Perps. This will be specified in future SIPs/SCCPs.
 Gradually enable trading activities, starting with limited volumes to manage risk.
 
 ### Incentive Programs