linda on the forum is saying that she thinks that the program is saying more sol/s that it really is.
does somebody else noticed something like it?
This is what she said:
1 Like
Isn’t it showing more sols on the mining rig because of the dev fee?
That’s how I understood it as well. However I have to say, my experience has been the opposite from @Linda’s. I’ve definitely noticed an increase in Sol/s on the pool side moving from EWBF to dstm’s miner. I’m running 2 rigs on dstm and 2 on Claymore (AMD cards) and there’s roughly 80-100 Sol/s increase on the pool when using dstm’s miner on the 2 machines.
1 Like
If the downtime is minimal. Probably yes.
Yes - it does. Take whatever Sol/s it displays and subtract 2% and that is your true Sol/s. Then you have network latency of your pool connection which can also cause you to have less Sol/s on your pool.
I’ve done more testing and have found that Dstm is somewhat unstable on it’s own, but overall I get about 10-15 more Sol/s registered on Flypool averages than EWBF.
First Stable released!
Just remembering if you have difficulties with your mining stability or you need Telegram notifications, please try this script:
Please read instruction carefully. Do not forget to leave like and feedback. If you need help i’m always here to support.
1 Like
Hey,
I tested your miner with same oc that EWBF’s miner and your miner is 4.1% faster on average with my 1070s. Good job keep it up 
So I updated to version 0.5.3 and started getting zm.exe crashed messages. I run 7x1070 rigs (3 of them) with OC roughly +75/+630 and power limit around 65-75%. Intel G4400 and 4GB RAM. All three rigs crash within a day or so at different times. Sometimes I notice the Windows Antivirus has scanned sometime around when this happens.
Also have an old crap tower from circa 2012 with 2x1070 and a 1050ti running on it that doesn’t crash on the new miner version.
I’ve went back to 0.5.2 for the three main rigs as they’ll run just fine for as many days as I’ve tried. Anybody else getting more crashes with 0.5.3?
They just updated to version 0.5.4 perhaps that works better
1 Like
Version 0.5.4
fix: device selection
fix: latency reporting
add logfile support
add option to disable auto reconnect
handle disconnect periods in web/json stats
add basic GPU responsiveness infrastructure
ui: change timestamps to ISO 8601 format
webui: report: uptime contime server user port
json: report: uptime contime server user port version
Linux x64:
sha1 02816754ab46191109bed9f89f17c073000b0950
https://drive.google.com/file/d/12MmjEm-qIpdK7zc22jatQWD9WmAFIOLy
Win x64:
sha1 e4312b348a04348a6229b0098b7862a1306b0145
https://drive.google.com/file/d/1B7d6Qp9WzSPmCC6Yp0BgeyFQ9osdBTqq
3 Likes
My script updated to support Dstm version 0.5.4.
3 Likes
do you plan to adapt your miner also to Bitcoin Gold ?
Hi
I start mining is better for my 5x GTX 1080Ti EWBF regular 3540/60sol/s now is minimum 3595 regular 3612sol/s great job
Please don’t pump a known scam.
2 Likes
Can we expect further speed optimizations and an optional or lowered dev fee?
yeah shore totally dev talk …like BTG address format stuff …like when a tech talks to a 15 years old “gamer” gaming on android
Feel free to contact them, make your account there, this is Zcash forum here no one care about your scam bitcoin Gold or mining mod clients for their …
1 Like
ohhh so thats the one who didt finished his work and now he is pissed of because he didt get the bounty LMFO …btw test net is running for 7 days test wallets are out there for aprox 3 days to test the sending and receiving all works OK … btw it isnt my B gold …but really thanks for all the flaming just for one question that has been adressed to the dev of DSTM at least i see what sort of people i dealing with on this forum
This is Zcash forum, here no one care about some other coins. Simple as is I know that test net is running, but not interested. Good luck with your coin, use link I did sent you, simple open issue and ask if starbuckBG will fork DSTM for you. Happy mining
For me is bitcoin gold scam.
I’m Zcash loyalist 
2 Likes