Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

CPIDs not reported correctly at the output of execute beaconreport #1035

Closed
panosguardian opened this issue Mar 26, 2018 · 3 comments
Closed

CPIDs not reported correctly at the output of execute beaconreport #1035

panosguardian opened this issue Mar 26, 2018 · 3 comments

Comments

@panosguardian
Copy link

The first character of CPIDs seems to be dropped in the output. For example, the output is:

"a2d3e3bfc26aad8efca769a548ee841" : "S6bHrZ3BVMJgqfbmWxY62dSiTBp3MDZhYZ"
whereas the real CPID is 1a2d3e3bfc26aad8efca769a548ee841.

I am not sure if that has any implications in terms of staking/rewards.
@iFoggz
Copy link
Member

iFoggz commented Mar 27, 2018

that is interesting. will add to my todos

@floydn
Copy link

floydn commented Apr 3, 2018

I can confirm the same issue. My cpid is e93b3a06604933d3023f1247c12083e4, but this is what shows in the beaconreport:
"93b3a06604933d3023f1247c12083e4" : "SGDpJ8Jc4MKygN8UDUAdhEXXkNiMGZ25cf",

@iFoggz iFoggz mentioned this issue Apr 19, 2018
Merged
@denravonska
Copy link
Member

Fixed in 3.7.12.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@denravonska @floydn @iFoggz @panosguardian