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

pallet-dispute #131

Closed
8 of 9 tasks
f-gate opened this issue May 22, 2023 · 3 comments
Closed
8 of 9 tasks

pallet-dispute #131

f-gate opened this issue May 22, 2023 · 3 comments
Assignees
Labels
enhancement New feature or request Priority | High

Comments

@f-gate
Copy link
Member

f-gate commented May 22, 2023

Pallet Dispute

Objectives

  • Provide a system whereby a jury of accounts can decide the outcome of a dispute over services.
  • Incentivise the jury allowing a simple form of income.??
  • Allow for the fair dispute of briefs with a single owner.

Acceptance Criteria

Raising a dispute

  • One of 2 parties can raise a dispute at any time (timings and possibility to dispute are dictated by pallet proposals).
  • The dispute must contain what exactly is being disputed on and who is disputing (Preferably as a generic). (Could be a set of milestones or a single milestone)
  • Disputes are finalised on a future block as defined in the config.

Voting on a dispute

  • Anyone of the jury can vote either for or against a dispute.
  • Votes are mutable.
  • Autofinalise on unanimous voting.
  • The ability to extend the voting period just once.

Finalising a dispute

  • Call a hook on_completed_dispute() which will allow either party to withdraw or refund the amount.
  • allow the correct party to refund or withdraw from pallet-proposals only out of unapproved milestones (for obvious reasons)

Refactors Required

In this PR we also need to depricate the use of funding type in favor of a new more flexibly alternative. For more details see: #193.

Future Ideas

  • If either party is not happy with the outcome, they can pay more for it to go to a larger jury or higher ranking officials.
  • Roles specifically for a judge or something.
  • Declining the invitation to handle a dispute + slashing.
@f-gate f-gate added enhancement New feature or request Priority | High and removed Priority | Medium labels Aug 7, 2023
@f-gate f-gate mentioned this issue Aug 7, 2023
@mshankarrao mshankarrao self-assigned this Aug 8, 2023
@mshankarrao
Copy link
Contributor

From top to bottom
1)when we say here Jury of trusted accounts can decide, it means one of the handler(which was chosen while submitting the dispute) correct?
2) Incentivising to one of the handlers?
3) Briefs with single owner meaning? Isn't most of the briefs will have single owner
4) Do we need to work on creating the config and work on this first #193

@f-gate
Copy link
Member Author

f-gate commented Aug 10, 2023

  1. The jury is whatever the Handle is
  2. The handlers all need incentivising
  3. Yes most briefs will have a single brief owner
  4. I am working on the config now but for the minute you can ignore it and work on the other parts like voting and architecture

@f-gate
Copy link
Member Author

f-gate commented Aug 30, 2023

Updated to display the new thinking around jury selection

@f-gate f-gate mentioned this issue Sep 12, 2023
12 tasks
@f-gate f-gate closed this as completed Oct 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request Priority | High
Projects
None yet
Development

No branches or pull requests

2 participants