Topic: ★★DigiByte|极特币★★[DGB]✔ Core v6.16.5.1 - DigiShield, DigiSpeed, Segwit - page 1174. (Read 3058816 times)

The default parameters are based on the -k groestlcoin kernel, and even then, groestl is always fighting for the top spot. With MYR even more so. I change the parameters to meet with the -k myriadcoin-groestl kernel, and that's double the -k groestlcoin.

Here's something else that looks fairly reliable: https://docs.google.com/spreadsheets/d/1OdhCDxtDtLLuW-dK4hfIrD55c2nBGXbBonG0haBJB0o/edit#gid=0  That groestl data is also based on the simple -k groestlcoin kernel analysis . . . so double what you see there and . . .

BTW: https://dgb-groestl.theblocksfactory.com/ hashrate has shot up by 10x in the last 24 hours. Must be everyone who was on cryptopoolmining. Boostpool is still hammering away too.  

Edit:

People in the U.S. should also seriously consider http://birdspool.no-ip.org:5021/static/stats/ - it's reliable and honest; you just have to wait for the rolling payouts to ramp up (and the other side of that coin is that you continue to receive payouts for the rolling payout period even after you've left!). The new, official, DigiByte NOMP pools look good too.

Because the Dev's expressed an interest in making it DGB official. That's a good thing. It'll give clout to the miner eventually released, and will also add to DigiByte's resume as it were.

Anyone who wants to download the current grs-sgminer (warts and all) that let's you use the -k myriadcoin-groestl kernel can do so by downloading the AidBit wallet http://www.aidbit.net/download/ (be sure to disable your AV beforehand) which installs the windows version along with the wallet install (I believe this is still correct anyway). Then, you'll need to locate your miner install, and independently configure appropriately. For everyone else, I suggest waiting for the DigiByte team to release a new, improved dgb-groestl-sgminer. The Linux version already looks great and ready to go as is, and just needs to be renamed and uploaded to github. The Windows version needs a couple of tweaks and to be made official . . . I think anyway.

I only have remedial code reading abilities, and am not a programmer by any means.

Do you use the default parameters or do you enter data that matches your cards for http://whattomine.com?


Especially given the attacks on Groestl im thinking I need to switch from qubit to groestl.

I have 2 rigs that together use 920 watts and get me about 75-80k DGB per day when running Qubit.

Edit:  This is with my cards being undervolted and running the engine clock at 1050 / mem clock at 1500.  I have a mix of 280x / 270x

Qubit is a distant second, and, even though electrical usage is more or less the same, my cards heat up much more than with groestl. All things considered, groestl is the clear winner in my opinion. How do your Qubit proceeds match the Groestl proceeds depicted below?


It's also always at the top of the list at http://www.whattomine.com/ . Qubit gives Skein a close run for that distant second.

I tried everything
qubit is best for my hd 7xxx: 7970 7950 7850 7790
cold and less diff
and more profit
and all of this perfectly clear here:
https://dgb-qubit.theblocksfactory.com

Why make me chase the dev's?

My periodic postings regarding mining profitability are all groestl.

From what I've been reading, the general opinion is that the most vulnerable "alts" are those that have deviated the most from the original BTC code, with the more "bells and whistles", neglect of basic security issues, and 'coders' who really don't have much of an idea about what they're doing, all leading to the most potential disaster. MYR certainly fits that bill.

Let's hope that DGB's more serious and conservative, security sensitive, and greater knowledge and know-how makes things different for us.

Groestl beats out  qubit in profitability?  I thought pools like boostpool.com were inflating the Groestl difficulty enough that it was harder to get normalized payouts.  

Where do you need the hash the most, groestl? Willing to rent some to secure.

Edit: can't seem to find any groestl rentals.
Do we really need more hash to secure untill the possible upcoming hardfork?

It's out of my hands now as it's been sent to DigiByte to use as they see fit. Perhaps you might send them a PM offering your services. 

I think it should be relatively easy to clean up (a few AV products generate alerts for the Windows exe, for example) and turn into something DigiByte official (giving credit to previous developers of course).

It's by far and away the most profitable way to mine DGB.

This sounds great.

If you wouldn't mind sending me the source code I'll take a crack at it.

I would like to correct something in the above post (it's been a while since things have been on "autopilot" and my memory didn't serve me too well, and, today, when I was putting together some stuff for DigiByte, I realized my mistake):

It was grs-sgminer's original "-k groestlcoin" kernel that doubled sph-sgminer's hashrate, not the "-k myriadcoin-groestl".

The "-k myriadcoin-groestl" kernel quadruples the original sph-sgminer's hashrate! (I even understated it to you DigiByte in the PM I sent by saying it tripled the hash rate . . . it's actually a quadruple!)

More specifically, with a 7950, sph-sgminer ran at about 5 Mh/s, grs-sgminer with -k groestlcoin at about 10 Mh/s, and grs-sgminer with -k myriadcoin-groestl has a hashrate of 20 Mh/s.

This certainly seems to be wrecking havoc on the MYR blockchain. 

What are the suggested fixes for DGB?  I thought I remembered that it wasn't possible to mine more than 6 blocks in a row of a single algorithm.  Wouldn't that successfully mitigate this threat? 

heh! Long day for the myr guys I bet.

Awesome HR, thank you!

Also, to everyone, it appears Myriadcoin has fallen victim to a successful timewarp attack in the past 12 hours. They have issued two hard forks to correct the problem.

It does appear someone is attempting to do something similar to DigiByte on Groestl & other algos. All appears well for the moment, but as always the more hash we can get the better.

If anyone has more details on this please feel free to share. We have been doing a lot of research the past few hours. Since our difficulty adjustment is different than Myriad we have some more protection for this. We are working on an update to fix this issue. We may have to issue an immediate hard fork in the next couple days.

Ooriginal ArtForx Explanation: https://bitcointalksearch.org/topic/m.521772

https://bitcointalksearch.org/topic/bug-time-warp-exploits-why-is-the-attack-chain-accepted-608893

https://bitcointalksearch.org/topic/blocking-the-time-warp-attack-114751

http://www.reddit.com/r/myriadcoin/comments/2l1xfh/myriadcoin_required_update_0925/

http://www.reddit.com/r/myriadcoin/comments/2l22fd/myriadcoin_required_update_0926/

I've sent you a PM.

and next:

./start_cpu_qubit.sh
��������������������������������������������������ͻ
�  qubit cpu-miner (v1.1a)                         �
�  author: ig0tik3d                                �
�  http://www.q2c.cc                               �
��������������������������������������������������ͼ
Launching miner...
[2014-11-02 18:19:43] Starting Stratum on stratum+tcp://digihash.co:3012
[2014-11-02 18:19:43] 4 miner threads started, using 'qubit' algorithm.
[2014-11-02 18:19:43] Stratum detected new block
[2014-11-02 18:20:03] thread 3: 2097152 hashes, 111.17 khash/s
[2014-11-02 18:20:03] thread 0: 2097152 hashes, 110.37 khash/s
[2014-11-02 18:20:03] thread 1: 2097152 hashes, 108.82 khash/s
[2014-11-02 18:20:03] thread 2: 2097152 hashes, 107.88 khash/s
[2014-11-02 18:20:15] Stratum detected new block
[2014-11-02 18:20:15] thread 2: 1382350 hashes, 113.28 khash/s
[2014-11-02 18:20:15] thread 3: 1437992 hashes, 112.53 khash/s
[2014-11-02 18:20:15] thread 1: 1400031 hashes, 113.17 khash/s
[2014-11-02 18:20:15] thread 0: 1426343 hashes, 112.82 khash/s
[2014-11-02 18:20:25] Stratum detected new block
[2014-11-02 18:20:25] thread 2: 1165503 hashes, 116.21 khash/s
[2014-11-02 18:20:25] thread 3: 1154996 hashes, 115.16 khash/s
[2014-11-02 18:20:25] thread 0: 1110128 hashes, 110.69 khash/s
[2014-11-02 18:20:25] thread 1: 1096932 hashes, 109.37 khash/s