hiero-ledger / hiero-ledger/hiero-consensus-node
Identify stateful and stateless classes in the smart contracts module
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
### Problem
Some classes that were originally designed to be stateless may no longer be.
### Solution
Clear identify stateless and stateful classes and bring them back into conformity. Examples are ProxyWorldUpdate, FrameRunner and FrameBuilder
### Alternatives
_No response_
Contributor guide
Research direction
Start by locating ProxyWorldUpdate, FrameRunner, and FrameBuilder in the smart contracts module, then inspect how each class manages state. Compare their current behavior with the module's stateless/stateful conventions; done means the classes are clearly identified and brought back into conformity, though the issue does not name tests or specific files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- blockchain
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100