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
Update "Penalties table" page on Wiki #360
Comments
The main idea for this update was to simplify the penalties by creating a document that can fit most of the cases, instead of a document where all possible cases are included.
I find that we need to add the following:
|
Yes I think this is good practice. If more traders start doing this then it will facilitate a scenario where traders can sign the payout transactions themselves (with agreed compensation), therefore, avoiding mediation and speeding up trades. |
Thanks @w0000000t and @MwithM for updating this. It looks much improved. |
This might be out of the scope of the Penalties article, and be more appropriately added in the trading rules section, at least in my opinion; then the Penalties could briefly reference this |
I think traders discussing and agreeing penalties / compensation between them is within the scope of the article. The article should be used as a guideline but if traders agree between them something different that is fine and even preferred. |
I'll make some edits to reflect that, so we can discuss about wording and placement |
Closing as implemented |
During the first support meeting call of 2022, the idea of a new approach to penalties, and a new format of the "Table of penalties" wiki article, has been discussed.
Following this, me and @MwithM collaborated to prepare a new version of the table that is shorter, easier to read and understand, and also allows partial judgment to the mediator, in order to evaluate the severity of each situation and choose a penalty percentage according to that, "up to" the defined percentages.
The proposed new version of the article can be found here, please share your opinion.
The text was updated successfully, but these errors were encountered: