-
Notifications
You must be signed in to change notification settings - Fork 335
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
Stratum spec #37
Comments
Thanks, this will be done. |
So the plan is to make BTG a drop-in replacement for ZCash from a pool's/miner's point of view? |
Confirmed. Existing stratum protocol works well with Bitcoin Gold block format. But some minor changes in pool software are still needed. More specifically, the pool must put the block height in the first 4 bytes of hashReserved field. Anyone who can list popular pool softwares? |
Should that read "existing ZCash stratum protocol"? The ZCash stratum differs quite a bit from the protocol used by the rest of the Bitcoin Heritage of coins. |
I use z-nomp that use node-stratum-pool, this pool can be natively compatible ? If you've made a modification on a pool can you share it ? |
I will share it with open-source license |
thanks, I'm wait to discover this code and test for be ready when mainet opening. |
Will wait for this as well! |
Waiting as well. Also using z-nomp. |
@StarbuckBG you confirm that stratum is compatible with zcash? No one actually interested if you will share something or not, I am independent dev and would like to write my own so I need a spec. |
As an independent developer and intentionally hating person you shall be able to check the code and provide independent solution.
As soon as I finish work on the stratum protocol I will publish the code.
… On 23 Oct 2017, at 14:00, Sammy Libre ***@***.***> wrote:
@StarbuckBG <https://github.com/starbuckbg> you confirm that stratum is compatible with zcash?
No one actually interested if you will share something or not, I am independent dev and would like to write my own so I need a spec.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADrjrSHUKyvY3V49Sj5bZQc1l-U9TWbtks5svHG6gaJpZM4P9r6i>.
|
You just take zcash stratum and go with it, no need for amateur solutions. Everyone will be thankful, I promise. |
Hint: because you probably need existing mining software to work with BTCG. |
Please improve your behaviour as it is completely not professional. I will stop answering all of your questions as all the properties you give to the team and the project are completely irrelevant.
We are here to provide solutions, not to offence!
… On 23 Oct 2017, at 14:12, Sammy Libre ***@***.***> wrote:
Hint: because you probably need existing mining software to work with BTCG.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADrjragJJolci_vcH61HvVT3HmYckvhIks5svHSOgaJpZM4P9r6i>.
|
You are here to scam, you all are not capable to provide solutions. Do not lie to yourself. |
The coin is on the market in few hours, the fork is tomorrow. |
I want you to tell to all the team that is working more than 18 hours a day for the last week, that this is a scam. Tomorrow I will be in the Jimmy Song's show I would definitely have in mind the way you are behaving and that one of the persons that have made that much for the mining society is behaving that way. It is not cool (: |
You are disturbing 100 billion dollars market. I posted a few concerns, if addressed you can make it smooth for everyone, unfortunately you refuse to listen.
If you are not capable to provide a working testnet I have no idea what does "provide solutions" mean. I would join slack if it's possible, but I failed yesterday, link is kinda broken. |
It's still a mistery for me how people are going to launch a bitcoin fork without providing code before launch. Normal launch = post mainnet code 5 minutes before launch so we all can set it up, but there is literally no reason to hold on testnet. You can publish it right now if it's ready. If testnet code is not ready simply don't launch. I am sure people will agree with e that testnet must go with equihash algo since genesis or block 1. There is no need for legacy. For testing transition you should have a reg test. |
The incompatibility with Zcash is made for better as even Daira mentioned that they are planning to add the block height as argument for the block calculation. |
So we are waiting for an altered zcash stratum spec for bitcoin gold in order to start development on our side. |
About the testnet I needed to download the bitcoin testnet in order to check if the change of the PoW is handled and I needed to modify the DNSSeed code. I have done both of the things and have synched all of the testnet. |
1 |
When can I add a coin to the pools? |
|
How you tested the mining process ?
I needed to modify the stratum protocol of z-bono because it didn’t liked the block format.
…Sent from my iPhone 7 plus
On Oct 28, 2017, at 3:25 PM, TheComputerGenie ***@***.***> wrote:
#37 (comment)
Confirmed. Existing stratum protocol works well with Bitcoin Gold block format. But some minor changes in pool software are still needed. More specifically, the pool must put the block height in the first 4 bytes of hashReserved field.
Anyone who can list popular pool softwares?
https://github.com/z-classic/z-nomp
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
We tried to follow zcash stratum spec but most miners still check the version field and the hashReserved field of the block header. So some changes are still needed for the miner side. |
So change it, publish markdown with spec, make a fork of CPU miner so devs can catch up. |
I am already modifying it :) I will publish the spec and the modified nheqminer so the people can start working.
…Sent from my iPhone 7 plus
On Oct 28, 2017, at 4:18 PM, Sammy Libre ***@***.***> wrote:
So change it, publish markdown with spec, make a fork of CPU miner so devs can catch up.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Also not bad to notify claymores and optiminer and so.. |
@h4x3rotab could you publish a diff with zcash format? |
So for block
Or it must be reversed or something else. |
This is working as bitcoin gold pool. |
Will you need to make a new pool? or can be installed on any z-nomp pool? |
@DeadMan993 Because of the stratum edits, merging is best left to qualified pool operators. |
So we can use block version = 4 now, it will make all existing zcash miners compatible, are you going to require exact version from |
@sammy007 version=4 is not feasible for Bitcoin Gold because of bip9 |
@h4x3rotab @sammy007 Out of curiosity, why would you use anything but the version from GBT? Regarding miner compatibility: Wouldn't miner apps still choke on the block height encoded in the first 4 bytes of hashReserved? |
@oliverw because there is a note in zcash spec that miners (software) must warn and don't mine other versions, I know at least one miner (nicehash cpu miner) which refused to mine anything but version 4. The |
@sammy007 True, I remember that. By the way I've never worked on any znomp forks. I'm working on https://github.com/coinfoundry/miningcore. |
Well it was strabucks. |
@sammy007 No problem. This whole story is pretty chaotic. Can anyone recommend a miner compatible with the current BTG testnet? |
They all must be compatible as long as miner don't give fuck to block version or if at least one fuck given and as long as daemon accepts block version 4. |
@sammy007 So they are supposed to completely ignore hashReserved? |
I only used nhequiminer and it works. Must work as long as it is not hardcoded in miner. |
Guys this starts to be more like a chat. Do you want to join BTG slack and to make a group to discuss it and the summarise here ?
… On 3 Nov 2017, at 17:22, Oliver Weichhold ***@***.***> wrote:
https://github.com/StarbuckBG/node-stratum-pool/blob/44d2b721a4164f4763a1b678b8377b50114ecaec/lib/blockTemplate.js#L136 <https://github.com/StarbuckBG/node-stratum-pool/blob/44d2b721a4164f4763a1b678b8377b50114ecaec/lib/blockTemplate.js#L136>
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADrjrRJRakotjqkL6pT9zhtGaJ5K-bGeks5syy-RgaJpZM4P9r6i>.
|
I prefer to talk about it in public here, with slack only a few people will learn. Pretty relevant despite its not an exact issue. A stratum diff with zcash will help and miners can contribute to compatibility spreadsheet. |
Ok!
I will tell you the required changes in nomp and the mining software.
1. The reserved field is having the block height in LSB format in the first 4 bytes. The rest are the same.
2. NHeqminer needed a change in the block version. It was supporting only block version 4, the version of BTG is a lot higher. It is fixed in https://github.com/poolgold/nheqminer <https://github.com/poolgold/nheqminer>
3. I have made some minor changes on z-nomp and nomp because some of the code was not good at all.
4. Mining software is accepting the block format from the stratum protocol and no changes are required for EWBF and Claymores miner.
@sammy007 please mind you language. GitHub is no place for swearing, be business.
@oliver please use this repos for already tested software : https://github.com/poolgold <https://github.com/poolgold>
… On 3 Nov 2017, at 17:25, Sammy Libre ***@***.***> wrote:
I prefer to talk about it in public here, with slack only a few people will learn. Pretty relevant despite its not an exact issue. A stratum diff with zcash will help and miners can contribute to compatibility spreadsheet.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ADrjrWyOTCT7lgMWEhvYmD-qjUEqsNOsks5syzB5gaJpZM4P9r6i>.
|
Since BTCGPU utilises equihash it's wise to follow zcash stratum spec, will make existing miners compatible. https://github.com/str4d/zips/blob/77-zip-stratum/drafts/str4d-stratum/draft1.rst
The text was updated successfully, but these errors were encountered: