Steake · Steake · Dec 14, 2025 · Copilot · Dec 14, 2025 · Copilot
diff --git a/docs/issue-45.md b/docs/issue-45.md
@@ -0,0 +1,5 @@
+# Issue 45
+
+Work in progress by Emulated Coder.
+
+Ref: #45
-# Issue 45
-
-Work in progress by Emulated Coder.
-
-Ref: #45
-# Issue 45
-
-Work in progress by Emulated Coder.
-
-Ref: #45
+# Issue 45: Add Groth16 State Circuit Constraints
+
+## Background
+
+Groth16 is a widely used zk-SNARK proving system that requires careful circuit design to ensure correctness, security, and efficiency. In our project, the state circuit is responsible for enforcing the validity of state transitions within the zero-knowledge proof. Proper constraints must be implemented to guarantee that only valid transitions are provable.
+
+## Problem Statement
+
+Currently, the state circuit lacks several necessary constraints to fully support Groth16 proofs. This may allow invalid state transitions to be accepted, undermining the security guarantees of the system. The missing constraints need to be identified, specified, and implemented.
+
+## Proposed Solution
+
+1. **Review the current state circuit implementation** to identify missing or incomplete constraints.
+2. **Specify the required constraints** for Groth16 compatibility, including:
+    - State transition validity (e.g., correct application of operations)
+    - Range checks and field validity
+    - Consistency with public inputs and outputs
+3. **Implement the constraints** in the circuit codebase.
+4. **Write comprehensive tests** to ensure the constraints are enforced and the circuit behaves as expected.
+
+## Implementation Plan
+
+- [ ] Audit the current state circuit for missing constraints.
+- [ ] Document each required constraint and its purpose.
+- [ ] Update the circuit code to add the new constraints.
+- [ ] Add or update test cases to cover all constraint scenarios.
+- [ ] Review and optimize for performance and proof size.
+
+## Technical Specifications
+
+- The constraints should be compatible with the Groth16 proving system.
+- All state transitions must be strictly validated.
+- The implementation should follow best practices for zero-knowledge circuit design.
+
+## References
+
+- [Groth16 paper](https://eprint.iacr.org/2016/260.pdf)
+- [Project Issue #45](https://github.com/your-repo/issues/45)
-# Issue 45
-
-Work in progress by Emulated Coder.
-
-Ref: #45
-# Issue 45
-
-Work in progress by Emulated Coder.
-
-Ref: #45
+# Issue 45: Add Groth16 State Circuit Constraints
+
+## Background
+
+Groth16 is a widely used zk-SNARK proving system that requires careful circuit design to ensure correctness, security, and efficiency. In our project, the state circuit is responsible for enforcing the validity of state transitions within the zero-knowledge proof. Proper constraints must be implemented to guarantee that only valid transitions are provable.
+
+## Problem Statement
+
+Currently, the state circuit lacks several necessary constraints to fully support Groth16 proofs. This may allow invalid state transitions to be accepted, undermining the security guarantees of the system. The missing constraints need to be identified, specified, and implemented.
+
+## Proposed Solution
+
+1. **Review the current state circuit implementation** to identify missing or incomplete constraints.
+2. **Specify the required constraints** for Groth16 compatibility, including:
+    - State transition validity (e.g., correct application of operations)
+    - Range checks and field validity
+    - Consistency with public inputs and outputs
+3. **Implement the constraints** in the circuit codebase.
+4. **Write comprehensive tests** to ensure the constraints are enforced and the circuit behaves as expected.
+
+## Implementation Plan
+
+- [ ] Audit the current state circuit for missing constraints.
+- [ ] Document each required constraint and its purpose.
+- [ ] Update the circuit code to add the new constraints.
+- [ ] Add or update test cases to cover all constraint scenarios.
+- [ ] Review and optimize for performance and proof size.
+
+## Technical Specifications
+
+- The constraints should be compatible with the Groth16 proving system.
+- All state transitions must be strictly validated.
+- The implementation should follow best practices for zero-knowledge circuit design.
+
+## References
+
+- [Groth16 paper](https://eprint.iacr.org/2016/260.pdf)
+- [Project Issue #45](https://github.com/your-repo/issues/45)