Just an update, checked the groestl rig and its pulling 520 watts at the wall. The qubit rig is pulling 460 watts at the wall. This is expected given the optimized kernel of the groestl algo vs inefficient implementation of qubit. I now have 10 million dgb.... ill grab a slightly smaller chair to sit next to HR and 24  Thanks for sharing the wattage! Glad to see the DGB is adding up  |
|
|
|
Since our difficulty adjustment is different than Myriad we have some more protection for this.
I don't see how that follows. It's really the exact same thing but with max adjustments increased 10x. Historically this has led to insane difficulty swings (even at constant hashrates) which can be difficult to distinguish from actual tomfoolery without going in and comparing timestamps. One slight advantage is that -log(max_diff_down)/log(min_diff_up) is 1.94 for Myriad but only 1.5 for DigiByte, meaning the attacker would need a slightly greater share of the hashpower to attack DigiByte. Since DGB has a higher hash rate anyway, a successful attack seems less likely. BTW I've updated my pull request on github. We just saw your pull request! Thank you for contributing it! Long story short, we are vulnerable as well to the same attack if our net hash rate falls too low. But we do, however, have some additional protections built in the Myriad does not. We are going to issue a hard fork in the next few days. We are going to implement some changes to significantly mitigate this problem. In the mean time our chain is moving along fine, but we can use all the hash we can get. It is very likely who ever was behind the Myriad attack will attempt the same with DigiByte. And it does in fact appear that they have already tried / been trying. Is that your polite way of saying "Thanks, but we're just gonna merge Myriad's change"? Please do comment on these "additional protections". As far as I can tell, the difficulty adjustment algorithm was copied verbatim from myriad, and then nMaxAdjustDown and nMaxAdjustUp were increased by a factor of 10. "Moving along fine" is debatable when every single algorithm's difficulty regularly cycles by a factor of 10. It just gives the illusion of moving along fine because at any given time there's usually at least 1 algorithm going through its low phase. No, no. Not at all, we are actually compiling in your pull request as we speak to test. Just sent you a PM. |
|
|
|
Since our difficulty adjustment is different than Myriad we have some more protection for this.
I don't see how that follows. It's really the exact same thing but with max adjustments increased 10x. Historically this has led to insane difficulty swings (even at constant hashrates) which can be difficult to distinguish from actual tomfoolery without going in and comparing timestamps. One slight advantage is that -log(max_diff_down)/log(min_diff_up) is 1.94 for Myriad but only 1.5 for DigiByte, meaning the attacker would need a slightly greater share of the hashpower to attack DigiByte. Since DGB has a higher hash rate anyway, a successful attack seems less likely. BTW I've updated my pull request on github. We just saw your pull request! Thank you for contributing it! Long story short, we are vulnerable as well to the same attack if our net hash rate falls too low. But we do, however, have some additional protections built in the Myriad does not. We are going to issue a hard fork in the next few days. We are going to implement some changes to significantly mitigate this problem. In the mean time our chain is moving along fine, but we can use all the hash we can get. It is very likely who ever was behind the Myriad attack will attempt the same with DigiByte. And it does in fact appear that they have already tried / been trying. |
|
|
|
New Multi Miner:https://github.com/tpruvot/cpuminer-multi/releasesVersion 1.0.7 - VC2013 + MinGW 64 (Tanguy Pruvot) Add NIST5 and QUBIT algos Show current stratum bloc height Fix wallet solo mining Will try Qubit on DGB as i speak Results so far on my gaming rig:  Thank you for sharing! We are definitely going to check this out! |
|
|
|
ALSO:
I’ve got the original Myriad-Groestl srcxxx github optimized files if anyone is interesting in forking them - basically changing the name (since they’re open source to begin with) and then posting it to github. Send me a PM if you’re interested.
Hi HR, thank you for keeping us up to date with your stats. I will have a look on the original Myriad-Groestl srcxxx optimized bins. I thougt these bins only work on his pool. Maybe i can change this to get it work on every pool. Since difficulty is dropping again i could be profitable again to put a bit more power to my cards. He originally developed two different optimized kernels that significantly increased hashrates over the previous sph-sgminer ( https://github.com/prettyhatemachine/sph-sgminer ). His miner, grs-sgminer, allowed you to use the "-k groestlcoin" switch on any pool, or the "-k optimized" switch that only worked on his pool. My understanding is that he depreciated the github files for his original grs-sgminer that allowed you to use either switch. I could be mistaken though, but the idea that I have is that his current grs-sgminer only works with his proprietary "-k optimized" switch. If that's the case, then I think it would be interesting to fork his original grs-sgminer making available new installs once again that permit the use of any of the non-optimized kernels on any pool of the miner's choosing (grs-sgminer, using the " -k myriadcoin-groestl" switch, more than doubles the hashrate of sph-sgminer with only about a 20% increase in electrical usage - not bad at all). https://bitcointalk.org/index.php?topic=652849.msg7503640#msg7503640https://bitcointalk.org/index.php?topic=652849.0HR, We would love to have a link to the original source. We have been looking into this & we have someone who can break it down even farther for us. Right now groestlmyriad is the weakest of the five DigiByte algos. We need to get it sorted out and more mining pools online. Thanks for sharing this! |
|
|
|
|
We want to let everyone know the announcement we were planning for today has been delayed for a week do to circumstances out side of our control. Nothing bad, just timing, as well as market timing. We are working very hard on some cool projects! Stay tuned!
|
|
|
|
just wondering if you could use more than one algo to the daemon at a time. ie im looking to setup a pool for digibyte for both scrypt and sha256 they both would be running from the same daemon
You need to have a separate daemon instance running for each algorithm as the algo= parameter is needed in the coins .conf. On the DigiHash pool we have 1 daemon for each of the 5 algos. One a side note, what is the typical difficulty people are seeing for groestlmyriad on other pools? |
|
|
|
This looks really great! Whats your DigiByte address? (we need to bring this back) |
|
|
|
Hi YC If you order 1 you will receive 1000 DGB. I have bought 4 batches of 1000*1000 = 4000000 Lawzt How were you able to buy at that rate? Max order is 1000 DGB at once. YC Hi all Great day to buy some DGB. Bought 4 Mil @ litebit.eu today only paid 178$  @ Digibyte great news about DigiHash!! im testing it as we speak. Regards I just had a chat with litebit.eu how much Digibyte have been bought. 12.990.136 Digibytes in 24 orders An average 541255 Digibytes each order. This could be much more offcourse! They have a great service and everything works really fine. We need more promotion with Litebit.eu This is a great idea! They seam to have a really solid service! We are updating the website some more to inform people on the best & easiest way to get DigiBytes. |
|
|
|
Help us test out DigiHash! http://digihash.co/We have had blocks & payouts on Scrypt & Sha256. Have had valid shares submitted on Skein & Qubit. We just need to test out groestl. Any help is much appreciated! Qubit : only rejected shares. Works perfectly with my p2pool. Are you mining with a gpu or cpu? Also, what difficulty are you mining at? also, which p2pool settings do you use? Thanks! |
|
|
|
Please don't waste time on setting up pools, logo, easy mining! This should be in second place. Get the worldwide consumer acceptance going!
Thx for reading. Peace out.
A good business needs the stand on his own feet, Youre not getting any worldwide acceptance when you need to rely on others. Others that could run away,could shutdown everything with 1 mouse click. We have seen pools/exchanges come and go, some stayed some disappeared  with not telling anyone! People lost coins with this kind of actions. What would have happened when we had a marketcap of let's say 10mill and a x20 miner support as we have now? (And that's is nothing in comparison of what i'm thinking about for Digibytes future) When youre fundamentals s#ck you cannot build anything on top of that! So Digibyte is following the good steps to make it stable! Good distribution Digibytes own pools Digibyte own exchange Things will follow! This is exactly how we feel. We can't tell you how many times we have had to update the list of pools, exchanges, block and explorers. We want to make sure we have a solid reliable service in each and everyone one of these categories. Plus it helps us became intimately familiar with each part of the digital currency ecosystem and the tools used to make everyones lives easyer. Good news, we are now getting valid shares on the groestl pool! |
|
|
|
Help us test out DigiHash! http://digihash.co/We have had blocks & payouts on Scrypt & Sha256. Have had valid shares submitted on Skein & Qubit. We just need to test out groestl. Any help is much appreciated! Hi, thx for Setting up. But till now NOMP does not support "groestl" algo. Please use rigth name denotation when you talk to miners!!! This is important. It's groestlmyriad not groestl!!!! NOMP: Not working currently:
• Groestl - for Myriadcoin
• Keccak - for eCoin & Copperlark
• Hefty1 (Heavycoin [HVC])
Please don't waste time on setting up pools, logo, easy mining! This should be in second place. Get the worldwide consumer acceptance going! Thx for reading. Peace out. We have changed parts of the NOMP code to support groestlmyriad. We just need to finish testing it out with some more hash. As for consumer acceptance. We are working on that too! Cheers! |
|
|
|
Help us test out DigiHash! http://digihash.co/We have had blocks & payouts on Scrypt & Sha256. Have had valid shares submitted on Skein & Qubit. We just need to test out groestl. Any help is much appreciated! |
|
|
|
Digibyte, I can't install the new android wallet.
android 4.4.2 Samsung S5
What error are you receiving? |
|
|
|
I can do the Dutch translations.
I'm going to do some research about the mining software.
That is great to hear! Thank you! |
|
|
|
Thank you all for the input & suggestions! We will be making the logo slightly darker and we will be doing away with the google translate display on the website. In the coming weeks we will setup bounties for website translations to different languages. But before we do that we need to get DigiByte mining under control & sorted out. We are planning to do several things to make mining easier for people. We want to get the mining guides up on the new site ASAP! In order to do this we need to get the most up to date information for each algorithm. So to help us do this please help us list the best mining software for each algo. Sha256GPU/ASIC: Cgminer 4.7 http://ck.kolivas.org/apps/cgminer/ (does this support GPU still on sha256)? CPU: Should we even bother? ScryptGPU/ASIC: CGMiner 3.7.2 (last version to support scrypt) http://ck.kolivas.org/apps/cgminer/old/3.7/CPU: Any suggestions? What are people using for Scrypt ASICS? SkeinGPU: reorder cgminer 3.7.3 https://github.com/reorder/cgminer_skeinGPU: SPH-sgminer https://bitcointalk.org/index.php?topic=475795.0CPU: Any suggestions? QubitGPU:SPH-sgminer https://bitcointalk.org/index.php?topic=475795.0CPU: Any suggestions? GroestlGPU: SPH-sgminer https://bitcointalk.org/index.php?topic=475795.0CPU: Any suggestions? NVIDIA: Any suggestions? Lets get the most up to date list possible. Please repost & list the miners you use. |
|
|
|
New one is a lot easier to read, the letters really jump out. Old one looks muddled in comparison. I do like the old one, but I can see why the new one was designed. Looking forward to the friday announcement, hope its about Digipay! New website really looks the part, easy to navigate, everything you need is right there. Thank you for the feedback! Our thought was the new logo would be easier for people to read, especially foreign, non native english speaking people. |
|
|
|
|
Show Posts
