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

StatusPay - Compare Consensus Designs #256

Open
3 tasks
johannbarbie opened this issue Jul 8, 2020 · 1 comment
Open
3 tasks

StatusPay - Compare Consensus Designs #256

johannbarbie opened this issue Jul 8, 2020 · 1 comment
Labels

Comments

@johannbarbie
Copy link
Member

johannbarbie commented Jul 8, 2020

Bounty

The payment network requires fast economic finality of transactions so that purchases can be made within seconds.

Scope

3 scenarios will be worked out to evaluate possible setups:

  • Single operator: When a single operator runs the network, how can centralization be addressed effectively?
  • Validator network: A closed validator network would provide more decentralization, but hinder fast finality.
  • Open validator Set: Such a setup would allow any-one to propose blocks. Even the Status Wallet app could be used as a validator, as online-requirements are relaxed. Fast finality becomes even harder. related: Merged Mined Consensus

Deliverables

  • written document

Funding Circle

Bounty Owner/Gardener

@johannbarbie as BizDe

Gain for the Role

happy customer

Roles

bounty gardener: <@your github username> / X DAI
bounty worker: name / share
bounty reviewer: name / share

Gardener checklist

@MaxKaay MaxKaay added the size-M 550 DAI label Jul 8, 2020
@johannbarbie
Copy link
Member Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants