Update cip-template.md with parameter section

celestiaorg · Mar 7, 2024 · 29fba39 · 29fba39
1 parent 2fe05c0
commit 29fba39
Showing 1 changed file with 12 additions and 0 deletions.
diff --git a/cips/cip-template.md b/cips/cip-template.md
@@ -42,6 +42,18 @@ It is recommended to follow RFC 2119 and RFC 8170. Do not remove the key word de
 
 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 and RFC 8174.
 
+## Parameters
+
+The parameters section should summarize any changes to global parameters, including any new parameters. All mainnet parameters are tracked in [CIP-13](./cip-13.md). Once a CIP is accepted and deployed to mainnet, CIP-13 MUST be updated with these parameter changes. If there are no parameter changes in the CIP, this section can be omitted. 
+
+**TODO: Remove the previous comments and update the following table before submitting**
+
+| Parameter     | Default | Summary                                                                                                                | Changeable via Governance |
+|---------------|---------|------------------------------------------------------------------------------------------------------------------------|---------------------------|
+| module1.Name1 | Value1  | Description1                                                            | bool                     |
+| module2.Name2 | Value2  | Description2                                                            | bool                     |
+
+
 ## Rationale
 
 The rationale fleshes out the specification by describing what motivated the design and why particular design decisions were made. It should describe alternate designs that were considered and related work, e.g. how the feature is supported in other languages.