-
Notifications
You must be signed in to change notification settings - Fork 0
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
Decentralized Mining Pools #1
Comments
👋 @will-at-stacks |
I would love to contribute to the UI and front-end development on this is someone is interested in handling the smart contract side of things. |
For me, main barrier of entry to mining is running the mining software efficiently. See for a years-long discussion with little code contributions: stacks-network/stacks-core#1969 How can I defined my mining algorithm? How can I change the settings while running my node? Also mining event analysis would be helpful. onstacks.com seems not maintained anymore. How can I get data to make better decisions for mining. |
Running a mining pool requires good dev ops! |
How does this bounty relate to Hiro's patent on "Decentralized fair mining pools" issued November 15, 2022: |
Good question @njordhov I am not sure, but I'll tag @diwakergupta here to weigh in. Diwaker graciously helped us frame the RFP. |
No relation. Also FWIW all Hiro patents are under our patent pledge: https://www.hiro.so/patent-pledge |
I would like to see the goal to be to increase the total number of STX miners by 2,000% instead of 200%. e.g. 5 to 105, not 5 to 15. |
I wonder how a mining pool can be properly decentralised? Even if a Taproot address is used, any miner still needs to run a centralised server that spends the BTC to mine Theoretically, a decentralised miner could hold xBTC and spend it to mine using a Magic Protocol interface contract, similar to what we use for Zest Protocol https://github.com/Trust-Machines/zest-contracts I'm curious what FriendsFerdinand think about this theoretical solution? |
this is definitely very important work and I'm happy to help in any way i.e. design, infra, devops. @will-at-stacks it might help potential teams more if foundation can expand on this statement from notion doc I would think initially a good start would be to track all deposits + withdraws on a clarity contract for transparency and handle everything else centrally in batches (join mining pool for 1 week/month/year). Once this PR stacks-network/stacks-core#3385 is merged, mining operator will have more flexibility. |
We'd love to explore the idea of using DLCs (Bitcoin escrow) to let the user deposit native BTC in a self-custodied way |
btw, StacksOnChain is working on creating a dashboard for mining statistics to reproduce onstacks charts. There are some data that is not available through the API node and has to be extracted directly from the node itself, hence the delay. |
Stacks Degens' Application |
@tenuki thanks for the submission! would you mind adjusting your Notion doc to allow for commenting? thanks! |
Hi @natemiller1 thanks very much for the application! would you mind adjusting the Notion doc settings to allow for commenting? Thanks! |
Ouh, I'm sorry, I think it is ready now. |
@will-at-stacks Sorry about that - should be good to go now! |
@natemiller1 I would like to set up a call with you and your team for either tomorrow or Wed. I am hoping to get some others from the Foundation on the call. Can you please email me your email address, timezone, and availability those days? will at stacks dot org. Thanks |
Dear all applicants, I'm a Stacks Resident who is helping on SIP (Stacks Improvement Proposal) front. Tomorrow (Friday 13th Jan) at 11am ET, I will be hosting a SIP call with @mattyTokenomics who produced STX mining and Stacking report, who also produced docs for 3 decentralized mining proposals. Wish you all good luck and looking forward seeing your work in the future! |
@BowTiedDeployer and the rest of the Stacks Degens team. Congrats, your application for the Decentralized Mining Pool Bounty was selected! We would like to thank all of the other applicants ( @Akibalogh and the DLC.Link team, @tenuki and the CoinFabrik team, and @natemiller1 and the Stack Casimir team)! All of the applications were well crafted and thoughtful. We are so fortunate to have builders like you in the community! We would also like to thank @diwakergupta @owenstrevor @wileyj @tycho1212 @jennymith and Kenny Rogers for their time and effort in conducting a review of the applications! @BowTiedDeployer I will reach out via email with some next steps, but one thing that will be required is the creation of a User Group - which you will lead. @jennymith has offered to help you get it set up and establish a roadmap. Thanks |
@BowTiedDeployer Congrats! We at Trust Machines have been working on a threshold signing library which @jcnelson has pointed out could be used by your project. Joey (GitHub @xoloki) has led the development of the library and you can reach out to us for questions. |
Sounds great! Thank you. |
We’ll reach out for sure, thanks for offering! |
Additional discussion on this critical bounty can be found here. |
Decentralizing of the Stacks network through mining is one of the top priorities for Stacks ecosystem. Fortunately, Stacks 2.1 unlocks mining pools.
The goal of this
CRITICAL BOUNTY
is to promote the decentralization of the Stacks network by increasing the total number of STX miners by a minimum of 200%. The means to promoting this increase is supporting the development of an (or several) end-to-end applications that allow for mining pool participants to:Our belief is that providing easy to use and trustless mining pools (that provide participants with modest returns) will help prevent individual miners and/or mining syndicates from having majority control over mining. Decentralized mining pools will help Stacks expand from its current average miner count to thousands of participants via pools - something that will lead to a more robust, resilient, and decentralized network. We would like to encourage all qualified teams to submit an application to help us build this critical tooling and exiting product.
If you are interested please:
+
)Schedule:
Thanks!
The Stacks Foundation
The text was updated successfully, but these errors were encountered: