You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
about: Suggest a new feature or improvement for Rampage L1
4
+
title: '[FEAT] '
5
+
labels: enhancement
6
+
assignees: RampageRPM1
7
+
---
8
+
9
+
## Feature Summary
10
+
11
+
A clear and concise description of the feature you're requesting.
12
+
13
+
## Problem or Motivation
14
+
15
+
Describe the problem this feature would solve, or why it would be valuable to the Rampage L1 ecosystem.
16
+
17
+
## Proposed Solution
18
+
19
+
Describe the solution you'd like to see implemented.
20
+
21
+
## Alternatives Considered
22
+
23
+
Describe any alternative solutions or features you've considered and why you prefer the proposed approach.
24
+
25
+
## Impact Assessment
26
+
27
+
How does this feature relate to Rampage L1's core mission?
28
+
29
+
-[ ] Improves consensus mechanism
30
+
-[ ] Enhances governance capabilities
31
+
-[ ] Adds IBC/interoperability features
32
+
-[ ] Improves developer experience
33
+
-[ ] Enhances performance or scalability
34
+
-[ ] Security improvement
35
+
-[ ] Documentation / tooling
36
+
-[ ] Other
37
+
38
+
## Scope
39
+
40
+
Estimate the scope of this change:
41
+
-[ ] Small (config change, parameter update)
42
+
-[ ] Medium (new module function, API addition)
43
+
-[ ] Large (new module, consensus change, breaking change)
44
+
45
+
## Additional Context
46
+
47
+
Add any other context, mockups, or references here.
48
+
49
+
---
50
+
51
+
> **Note:** Feature requests that modify core consensus parameters or the governance constitution require approval from the project maintainer before development begins. See [CONTRIBUTING.md](../../CONTRIBUTING.md).
0 commit comments