Pages:
Author

Topic: EWBF's CUDA Zcash miner with DevFee disabled - page 2. (Read 11695 times)

newbie
Activity: 9
Merit: 0
No. Even with --fee 0.0 it still spends about 5% of time mining on developer's pool. You can check them by 'DevFee' string in the log.

And they called me crazy when I pointed that out. Thanks for this!
sr. member
Activity: 574
Merit: 250
Fighting mob law and inquisition in this forum
Well In the log is nothing and on pool site I have as much shares and constant hash as I had with 3.3b.
suprnova and flypool..

Are you sure the parameter is properly set when you debug/disassemble it?
newbie
Activity: 3
Merit: 0
In my linux/windows miners, 0.3.4b version has 'DevFee Accepted/Rejected share' message even with "--fee 0" argument passed.

Code analysis says the same. That's the part of windows version which processes --fee option. When it set to 0, variable gets assigned to some non-zero value, which influence program's behavior later:
 https://ibb.co/fVoJja
sr. member
Activity: 574
Merit: 250
Fighting mob law and inquisition in this forum
There is no DevFee string if you set --fee 0 it still works as he implemented it in 0.3.3b ..and leave him his devfee.
jr. member
Activity: 30
Merit: 1
Ah, ok. Thanks a lot for this info.
newbie
Activity: 3
Merit: 0
No. Even with --fee 0.0 it still spends about 5% of time mining on developer's pool. You can check them by 'DevFee' string in the log.
jr. member
Activity: 30
Merit: 1
You can choose the fee yourself with EWBF. Adding --fee 0.0 to the command line does the same.
newbie
Activity: 3
Merit: 0
Version of EWBF's zec-miner without developer's fee.

Thread which used to mine for developer's fee now works on your shares, so,
you can notice 'Accepted share' message with wrong share counter in program's output. That's fine.

Address for donations t1PD6bM1L7A3MdDJHvsmKwaD2a96vpRxS6P

Win64: https://mega.nz/#!Q34kQLyb!vekU930d5k6wYgMUYjyhPJtdpQR6kp1mZae0IhncRmg
Linux 64: https://mega.nz/#!4iIClQ4D!tbff8HgrT5Pii8yMDXf9eZd5yFSrwOALHnjsaW7NlWU
Pages:
Jump to: