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

create and publish double-merge malfeasance proof when no checkpoint is involved #6341

Open
poszu opened this issue Sep 19, 2024 · 0 comments · May be fixed by #6339
Open

create and publish double-merge malfeasance proof when no checkpoint is involved #6341

poszu opened this issue Sep 19, 2024 · 0 comments · May be fixed by #6339
Assignees
@poszu
Labels
area/malfeasance feat/atx-v2 feature

Comments

@poszu
Copy link
Contributor

poszu commented Sep 19, 2024

Description

In the "happy path" there was no checkpoint and the proof should include:

  1. There are 2 ATXs with different IDs.
  2. Both ATXs have a valid signature.
  3. Both ATXs contain the same marriage ATX.
  4. Both ATXs were published in the same epoch.
  5. Signers of both ATXs are married - to prevent banning others by publishing an ATX with the same marriage ATX.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@poszu poszu

Labels
area/malfeasance feat/atx-v2 feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

double-merge malfeasance proof spacemeshos/go-spacemesh
1 participant
@poszu