Output getmininginfo
- Dominant language
- C++
- Stars
- 397
- Forks
- 129
- PR merge metrics
- No merged PRs in 30d
Description
#### What happened:
- timelock wrong when more than 1 Operator per Node, only first(?) Node in output
- Operator shows Legacy-Operatoraddress, but Logfile shows Threadstaker, no assignment without external tools between Operator and Threadstaker possible?
#### What you expected to happen:
Show correct timelock for each masternode.
Possibility to see which Threadstaker mint for which Operator or show both in getmininginfo.
#### What are your environment parameters:
AIN 1.8 Latest Release in Testnet

Contributor guide
Research direction
Start at the getmininginfo entry point and trace how timelocks and Operator/Threadstaker assignments are assembled when a node has multiple operators. Done means the output reports the correct timelock for every masternode and makes each Threadstaker-to-Operator relationship identifiable without external tools.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- api, blockchain
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100