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

[mining-pool] Mining-bot Pool Proposal #19

Open
gzelda opened this issue Oct 15, 2020 · 1 comment
Open

[mining-pool] Mining-bot Pool Proposal #19

gzelda opened this issue Oct 15, 2020 · 1 comment

Comments

@gzelda
Copy link
Member

gzelda commented Oct 15, 2020

Is your feature request related to a problem? Please describe.
Several problems in recent mining-client version:

  • Only one user could use it each time(limit by stacks-node)
  • User must deploy his own stacks node to connect with mining-client
  • User must input his own burnchain(bitcoin) private key into stacks node configuration file. (Refer to [Feature Request] Modification of Mining Module stacks-network/stacks-core#1969, this part is designed for testing feature, the transaction signing should be departed from stacks-blockchain itself for the safety of private-key)

Users are seriously limited by the second problem. Because it's not easy for normal user to deploy a stacks node. Also, usually mining program should be run all day long. It is hard for normal user to do that.

Describe the solution you'd like
Stacks-Mining-Pool is just like normal mining pool as ETH/BTC. It compose of following parts:

  • Server hosts : we need a small cluster of server to provide mining-pool service.
  • Node management : In short, we will deploy a unique stacks-node for each user(discussed with InfStone, for miner's safety, each miner must have ownership of his own node).
  • Client management : Frontend production. Including two kinds of roles,
    (1) Pool operators/administrators, (2) Pool Members.
    • The user will need to select a user type, and the app will need to function differently depending on the type
    • A user must be able to login, select Pool Operator, and be directed through setting up a mining pool and inviting members
    • A user must also be able to login, select Join a Pool, and be able to search through pools to join, before being directed through the process of joining the mining pool of their choice
    • The app will need to provide additional data relevant for each user type. We need to ask ourselves what data is essential. For Pool Operators that could be things like number of members or amount of capital locked. For Pool Members that could be things like their earnings or their proportion ownership over the pool given their capital. There are probably many more data points that could be relevant as well.
    • The App will need to define a default configuration for how a mining pool functions
      We will need to decide to what degree we allow a Pool Administrator to change the mining pool configuration

Describe alternatives you've considered

Additional context
The content above will be optimized by further discussion between Daemon Technologies and Blockstack PBC

@gzelda
Copy link
Member Author

gzelda commented Oct 29, 2020

stacks-mining-pool structure

Initial structure.

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

No branches or pull requests

1 participant