Skip to content

fix: attester slashing versions and signed attestation rewards - #66

Merged
samcm merged 1 commit into
masterfrom
fix/signed-attestation-rewards-and-slashing-versions
Oct 20, 2026
Merged

samcm merged 1 commit into
masterfrom
fix/signed-attestation-rewards-and-slashing-versions

Conversation

@samcm

@samcm samcm commented Oct 20, 2026

Copy link
Copy Markdown
Member

VersionedAttesterSlashing.Attestation1/2 now label Altair and Bellatrix indexed attestations with their own version instead of Phase0, so AttestingIndices, Data and Signature work on them. Attestation rewards decode head, target, source and inactivity as signed int64 in both ideal and total rewards, as the beacon API defines them. Inactivity penalties are negative during a leak (mainnet epoch 200759 returns -5722).

…wards

VersionedAttesterSlashing.Attestation1/2 labelled Altair and Bellatrix
indexed attestations as Phase0 while filling the Altair/Bellatrix field,
so every accessor on the result failed with "no Phase0 indexed
attestation".

The beacon API defines head, target, source and inactivity in both
ideal and total attestation rewards as Int64. Inactivity penalties are
negative during an inactivity leak (mainnet epoch 200759 returns
inactivity -5722), which failed to decode as uint64.

@redpandabot redpandabot Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed 4 changed file(s) @ 91dc4eae — no blocking issues found.

@samcm
samcm merged commit ceca3c2 into master Oct 20, 2026
3 checks passed
@samcm
samcm deleted the fix/signed-attestation-rewards-and-slashing-versions branch October 20, 2026 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant