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.

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

Malfeasance V2: Double Post #6140

Closed
fasmat opened this issue Jul 16, 2024 · 1 comment
Closed

Malfeasance V2: Double Post #6140

fasmat opened this issue Jul 16, 2024 · 1 comment

Comments

@fasmat
Copy link
Member

fasmat commented Jul 16, 2024

Description

Contextual validation includes a check that verifies that the same identity didn't participate with their PoST in two different ATXs. In ATX v1 this was known as a Double Publish Proof and proofed that two ATXs were created by the same identity for the same publish epoch.

In ATX v2 this needs to be changed to proof that the same identity provided their PoST to two different ATXs, since the identity in question might not have signed the ATX.

Implementation hints

The malfeasance proof needs to include the following data to be valid:

  1. The provided post(s) must be valid - otherwise the "Invalid Post" malfeasance proof should be used, see Malfeasance V2: Invalid Post #6141
  2. The provided post must have been included by an identity that is part of the same marriage set as the identity that created the post. This requires the malfeasance proof to include proof about the marriage of the identities involved.
  3. The ATXs including the PoSTs by the same identity must have been published in the same epoch.
@fasmat fasmat self-assigned this Jul 16, 2024
@fasmat fasmat changed the title Malfeasance: Double Post Malfeasance V2: Double Post Jul 16, 2024
@fasmat
Copy link
Member Author

fasmat commented Aug 29, 2024

Closed because it can be replaced with #6309

@fasmat fasmat closed this as completed Aug 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Archived in project
Development

No branches or pull requests

1 participant