-
Notifications
You must be signed in to change notification settings - Fork 8
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
Enhancements - Suggestions for configurable inputs. #289
Comments
Right now (for MVP) the delay will be 7 days in gnosis network. However, this is a minimum value and the UI could propose to add more time but I would like to enforce it from where we create the quest but the only time it is submitted to the contract is at the moment the player claim. The enforcement of having a config for the Quest requires modifying some solidity contracts that we don't have ownership of (GovernQueue.sol schedule function if you have some knowledge on solidity and want to have a look at it). This will be something we will investigate in the future tho because it would be great if its configurable because 7 days doesn't fit the needs for everyone |
That was for point 1, the point 2 is more of a design decision, we wanted a Quest to be driven by the description, so if the creator wants to only allow like 150HNY max for a claim, having it in the description would be enough and if a Player claims more, the claim will likely be challenged by either of the Creator or any other person. The player does not have any interest in doing that because when he claims, he has to deposit collateral and if his claim is successfully challenged, the Player will then lose his deposit (the deposit is sent to the challenger) |
The text was updated successfully, but these errors were encountered: