-
Notifications
You must be signed in to change notification settings - Fork 20
Open
Description
Current jackpot payment adheres to split between solution0Challengers and solution1Challengers. This becomes an issue for 2 reasons
- Implementation: Verifier needs to get info to redeem payout, this would require two events to be fired. Possible (but also possibly unreliable, as events have strange behavior on solidity code underneath it).
- Incentives: If a verifier challenges both solutions than they receive double payout. This would create incentive to always challenge both solutions (thus negating the need for a forced error).
Possible solution is one array of challengers with a Challenge struct { intent, challengedSolution (1 or 0) }
But this would require filtering when verification game begins (who is participating in verification game or not?). This is bad because such a loop may run out of gas. Could make a solution around it (but would also be a bit complex and probably not elegant)
Metadata
Metadata
Assignees
Labels
No labels