Skip to content
This repository was archived by the owner on May 22, 2023. It is now read-only.

Do not revert signature fraud submission TX if slashing failed #416

Merged
merged 3 commits into from
Apr 20, 2020

Conversation

pdyraga
Copy link
Member

@pdyraga pdyraga commented Apr 18, 2020

Closes: #356

In practice, the situation when KEEP token slashing failed should never happen (see keep-network/keep-core#1625). However, we want to be very explicit in this contract and protect the owner that even if it happens, the transaction submitting fraud proof is not going to fail and keep owner can seize and liquidate bonds in the same transaction.

In practice, the situation when KEEP token slashing failed should never
happen. However, we want to be very explicit in this contract and
protect the owner that even if it happens, the transaction submitting
fraud proof is not going to fail and keep owner can seize and liquidate
bonds in the same transaction.
@pdyraga pdyraga requested a review from nkuba April 18, 2020 13:20
@@ -1175,6 +1189,8 @@ contract("BondedECDSAKeep", (accounts) => {
"Caller is not the keep member"
)
})

it("does not fail if slashing failed", async () => {})
Copy link
Member

Choose a reason for hiding this comment

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

Missing implementation?

Copy link
Member Author

Choose a reason for hiding this comment

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

I had problems with linter, I do not know what happens here. I removed this line. Test for this scenario is implemented here.

@nkuba nkuba merged commit 6008e7e into master Apr 20, 2020
@nkuba nkuba deleted the no-slash-fail branch April 20, 2020 13:24
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Signature fraud should still be reportable if KEEP slashing fails
2 participants