hiero-ledger / hiero-ledger/hiero-consensus-node
Representation of Singletons in StateProofs and BlockStream state changes
- Dominant language
- Java
- Stars
- 406
- Forks
- 226
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 210
Description
As described in this [notion](https://www.notion.so/swirldslabs/Singletons-in-StateProofs-and-BS-State-Changes-1fa7c9ab259180379b19eee93705553d?pvs=4), we currently have `SingletonIdentifier` that is different for each Singleton state.
We could replace all the singletons in `StateIdentifier` with one and then add a singleton enum and add the type of singleton into the value of `SingletonUpdateChange`
Contributor guide
Research direction
Start with the linked Notion design and inspect the usages of SingletonIdentifier, StateIdentifier, and SingletonUpdateChange in the repository. Trace how StateProofs and BlockStream state changes represent singletons, then verify that the implementation uses one singleton identifier, an enum for singleton kinds, and includes that kind in each SingletonUpdateChange value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- distributed-systems
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100