[ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency

[TanteStefana]

Hi all!
Another noob here... name's Ron.
I'm bummed I just this week started investigating crypto$ because I might have been able to get a lot more of these DRKs!  But, oh well.
CPU mining about a tenth of a coin a day!  (i7 870) - Just ordered a R9 270 to replace my old GeForce (I'm poor).

So anyway... I've done graphics for years and when I saw the promotion stuff mentioned I started working on a 3D DarkCoin. I was disappointed to see that the promo team isn't interested in this but here's a few picks of the initial stages I may or may not get back to...

Of course you are welcome to contribute to my well being and time.

DRK donations: XpQZscB95M63vBewcyBWe9hgj4nMhBWi69

maybe you can do a youtube promo, there's a bounty for that!

[slyA]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

One coin(BTC) to rule them all,

One coin to premine them;

One coin to bring them all,

And in the darkness bind them.

I just wanted to bring this up from our good friend slyA. Ahhh, memories....

Lol. i'm still here lurking in the shadows mate. Guarding my preciousss with my life. Eduffield is on top of his game. It will be funny when this coin blows up and we're all snobby well to do folks talking about how we were here when history was being made. I reckon Eduffield would be the rich sociopathic recluse having binary based dementia in his bat cave.

[JGCMiner]

is this cheating trick part of the reason why a lot of coins have 110+% shares to find blocks the past week and more? I was figuring it was just assholes who use a miner that keeps found blocks for themselves...

Any way the dev or some other well connected person can make a list of the pools that can still be hit with this stratum exploit?

As far as I can tell a large number of blocks requiring well over the expected shares to solve is a symptom of this issue and, for example, the popular Such Pool is at 120% for the last hour. Maybe it is nothing, but it would be nice to know for sure that a given pool protects you and your fellow honest miners from being stolen from by those using this exploit.

[CHAOSiTEC]

I pmd with the guy who posted the screens yesterday , but he didnt disclose his software:

hrt
Newbie
*
Online Online

Activity: 27



View Profile Personal Message (Online)
Trust: 0: -0 / +0(0)
   
Re: cpu hashrate
« Sent to: sippsnapp on: March 11, 2014, 06:44:56 PM »
« You have forwarded or responded to this message. »
   Reply with quoteQuote ReplyReply Remove this messageDelete
I run through mining proxy with a changed code. it denies automatic difficulty adjustment on pool stratum server, assign to each share variable hash raws [not unfeigned] thus stratum server is incapable to make up authenticity of this shares. i have always calculated at 0 diff and got all shares accepted, earnings respectively
Report To Admin
hrt
Newbie
*
Online Online

Activity: 27



View Profile Personal Message (Online)
Trust: 0: -0 / +0(0)
   
Re: cpu hashrate
« Sent to: sippsnapp on: March 11, 2014, 08:50:38 PM »
« You have forwarded or responded to this message. »
   Reply with quoteQuote ReplyReply Remove this messageDelete
added several extensions while compiled from 1.3 version in open source
i tried with different algos and at now proxy works on X11, groestl, qubit and sha256d.
saying clearly sha256d is not so useful as 500-1000GH guys play. on sha256d i have 80 iterations per second each pick up a low diff share at speed 48000KH. Running 30 CPU is equal to 115GH
if you are interested and there are other engaged people i can start a new topic with this on mind and share proxy for small donate although pulling out this in public would be risky as this is still cheating

It's cheating because it's not doing any real work, no real hashes.  Hope he didn't get away with much.  In fact, this ought to be brought to all stratum pool administrator's attention!

This is serious, it can kill the coin! But why he wants small donations, if he can mine thousands of dark a day with single CPU

Well, Hrt has been mining MYR for a little while too using the same trick, he also mentioned making 500 or so DRK in a few days in one of his posts (That means he may have syphoned 500+ DRK off miners using at least one other pool)
I'm thinking of posting on the Alt-coin mining thread to try and warn as many pool operators as possible that theirs some parasitic behaviour like this going on.
CHAOSiTEC, is it OK to mention you have a fix? I ask since you might find yourself swamped with requests and you don't seem to like the idea of straight up telling everyone what was done to bugger the system up.(Which is a good temporary call for reasons you outlined)

Hrt sent basically the same message to me btw. (Too bad it's just an exploit, these bugs need to be found eventually though, lol)

no problem :-)

[lolooo]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

Nice! On top as usual!

great dev!!

[bigrcanada]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

Evan... That's epic!  DarkGravity!  Nice!

[chompyZ]

If you need to send anyone basic summary information on Darkcoin & Darksend, here's a list of resources. It's a bit scattered and not perfect, but we're working on that.


http://www.reddit.com/r/DRKCoin/comments/200zlr/explain_darkcoin_in_5_sentences_or_less/

https://bitcointalk.org/index.php?topic=421615.msg5655872#msg5655872

http://www.reddit.com/r/DRKCoin/comments/1zy9y4/what_is_darkcoin_a_summery_for_newcomers/

https://bitcointalk.org/index.php?topic=421615.msg4585001#msg4585001

http://darkcoin.io/downloads/DarkSendv3.pdf

Why don't you add a link to the infosheet ?
You can put the PDF on the Darkcoin site...

[eizh]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

Evan... That's epic!  DarkGravity!  Nice!

You should open source the code for DarkGravity for others to adopt when done. It's good PR for you and DRK. The only thing I know about MegaCoin is that they gave the world KGW.

[CHAOSiTEC]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

Evan... That's epic!  DarkGravity!  Nice!

with a great developer on this coin, working his ass off, what else can you ask for. this is truly one of the few coins where you can see a future..

[AlexGR]

The kgw exploit is real.

The problem is that the software will accept blocks that are timestamped earlier than previous blocks, (for good reasons) up to the median timestamp of the previous 11.  

Kgw counts these as very fast blocks and adjusts the difficulty up by its 20% maximum.  Once.   But you can use that once to roll the timestamp back after five blocks that are long enough to drive the difficulty 20%lower each.  

So the exploit is to start mining your own block chain, time stamping several blocks into the future far enough to get the maximum downward adjustment of difficulty each time.  Then jump backwards in time getting the maximum upward difficulty once.  Rinse, repeat,  and your chain gets ridiculous low difficulty and you mine a whole lot of blocks while advancing your timestamp not much further than the main chain.

When the time in the main block chain catches up, you release your own chain and force a reorganization, which allocates to you all the coins mined for the last umpty ump blocks.

I'm in the process of rewriting KGW for our purposes. I've spend a few hours thoroughly going through the code and I think I can come up with a better implementation that doesn't have these kind of problems. DarkGravity?  

BlackHole
(gravity generation implied )

edit: ah shit, there is a blackcoin around these days... damn...

[chaeplin]

block generated 245 ea

from 32485 to 32729 (~12 hours)

NEWBL 03-13 07:44:39 32485 141.273 Xemt2zeYELCkddJHvsW4x9ytqTEnkiviaH
NEWBL 03-13 17:17:33 32729 266.720 XccPicDbg7HhRfFwPU3Z2CFVpHSYAhuxtu

1 XnBwaSjgNbpJMjatTiFJfxrigPBKpFmrzq
1 XvmAhGsqwnZqdsWxMqMFQtFeTiVhwntHPF
3 cpupool
5 XeCyp1qAMFTb6PMZu431QpZ6sEpTH64Gag
7 official
12 lotterymining
12 p2pool
29 mininghub
65 suchpool
110 coinmine

total network rate (7.55GH/s), coinmine 4.3GH/s.

[baokychen]

If anyone would want to get Spin Wheel and Dice game up for DarkCoin, can pm me for Joint Venture, its true that I am not as famous as Dooglus, but I doubt dooglus will want to do it for Dark Coin as of now, since he already made lots of BTC running the house.

I hope someone will want to cooperate and get Dark coin gambling up.

I had 4 sites setup for 4 alt coins, you can pm me for the details. Its up & running smoothly.

[boubou]

block generated 245 ea

from 32485 to 32729 (~12 hours)

NEWBL 03-13 07:44:39 32485 141.273 Xemt2zeYELCkddJHvsW4x9ytqTEnkiviaH
NEWBL 03-13 17:17:33 32729 266.720 XccPicDbg7HhRfFwPU3Z2CFVpHSYAhuxtu

1 XnBwaSjgNbpJMjatTiFJfxrigPBKpFmrzq
1 XvmAhGsqwnZqdsWxMqMFQtFeTiVhwntHPF
3 cpupool
5 XeCyp1qAMFTb6PMZu431QpZ6sEpTH64Gag
7 official
12 lotterymining
12 p2pool
29 mininghub
65 suchpool
110 coinmine

total network rate (7.55GH/s), coinmine 4.3GH/s.

When this hppened, why is there no atomatic mecanism to deal with?
Why did the pool that is over 45% did not rise its fee at 1% rate each week until it gets back to 45%?
The pool will earn profit and the hash distribution will be automatic. I think this issue is not trivial.

[LimLims]

When this hppened, why is there no atomatic mecanism to deal with?
Why did the pool that is over 45% did not rise its fee at 1% rate each week until it gets back to 45%?
The pool will earn profit and the hash distribution will be automatic. I think this issue is not trivial.

It happens because there is no central authority controlling the pools. It's a free market. The best we can do as individuals is move our hashing power elsewhere, or appeal to the pool operators to close signups or adjust their fee structure.

[CHAOSiTEC]

block generated 245 ea

from 32485 to 32729 (~12 hours)

NEWBL 03-13 07:44:39 32485 141.273 Xemt2zeYELCkddJHvsW4x9ytqTEnkiviaH
NEWBL 03-13 17:17:33 32729 266.720 XccPicDbg7HhRfFwPU3Z2CFVpHSYAhuxtu

1 XnBwaSjgNbpJMjatTiFJfxrigPBKpFmrzq
1 XvmAhGsqwnZqdsWxMqMFQtFeTiVhwntHPF
3 cpupool
5 XeCyp1qAMFTb6PMZu431QpZ6sEpTH64Gag
7 official
12 lotterymining
12 p2pool
29 mininghub
65 suchpool
110 coinmine

total network rate (7.55GH/s), coinmine 4.3GH/s.

it looks like the scammer is on coinmine, i cant tell for sure, since he is anonymous, but if i was pool owner, i would check to see if his highest (1GH) is finding any blocks thats how you will know for sure

[boubou]

I get that, Pool owners want monney and so did not want to refuse some Power.
Users want better service and don't care. Even if you close the registration, the hash will not get away, it will remain the same for a while.

If you raise the fee when you go over 45% (for example), user will start to go away, and the pool owner will get more fees, it seems like a win-win solution.

If all the pools agree to do the same, public oppinion will not be hurted as soon as the fees will get back to normal when the Hash get out of the critical range.

[goin2mars]

I get that, Pool owners want monney and so did not want to refuse some Power.
Users want better service and don't care. Even if you close the registration, the hash will not get away, it will remain the same for a while.

If you raise the fee when you go over 45% (for example), user will start to go away, and the pool owner will get more fees, it seems like a win-win solution.

If all the pools agree to do the same, public oppinion will not be hurted as soon as the fees will get back to normal when the Hash get out of the critical range.

Another method I've seen employed is to ddos the pool with 50% hashrate. Not a nice way of taking care of the problem . . but incredibly effective.

I can understand that most pools that hit 45% and greater aren't looking to cause problems . . but it really makes the coin look weak.

[illodin]

Maybe it would be possible to adjust the block reward according to how often the same wallet finds the block? So if a pool has close to 50% they are finding almost 50% of the blocks, and if the algorithm would start decreasing the reward given to the big pool people would be motivated to move to smaller pools.

[Madychoux]

block generated 245 ea

from 32485 to 32729 (~12 hours)

NEWBL 03-13 07:44:39 32485 141.273 Xemt2zeYELCkddJHvsW4x9ytqTEnkiviaH
NEWBL 03-13 17:17:33 32729 266.720 XccPicDbg7HhRfFwPU3Z2CFVpHSYAhuxtu

1 XnBwaSjgNbpJMjatTiFJfxrigPBKpFmrzq
1 XvmAhGsqwnZqdsWxMqMFQtFeTiVhwntHPF
3 cpupool
5 XeCyp1qAMFTb6PMZu431QpZ6sEpTH64Gag
7 official
12 lotterymining
12 p2pool
29 mininghub
65 suchpool
110 coinmine

total network rate (7.55GH/s), coinmine 4.3GH/s.

it looks like the scammer is on coinmine, i cant tell for sure, since he is anonymous, but if i was pool owner, i would check to see if his highest (1GH) is finding any blocks thats how you will know for sure

Want to avoid 51% Pool ? Go P2Pool !!!!


Join us to MightyPool.net P2Pool Node

Here are the benefits of P2Pool :
You don't need to create an account
You get paid directly after a block is found
You get no transaction fees
Local Pool Hashrate is distributed among all P2Pool nodes

Server hardware configuration :
Xeon E3-1225 v2 @3.2GHz
16 Gb RAM
100 Mbps Internet Broadband

How to join the Node ?
run SPH-SGMINER with those informations :
sgminer -k darkcoin -o stratum+tcp://mightypool.net:7903 -u YourDarkcoinWalletAddress -p x

[CHAOSiTEC]

block generated 245 ea

from 32485 to 32729 (~12 hours)

NEWBL 03-13 07:44:39 32485 141.273 Xemt2zeYELCkddJHvsW4x9ytqTEnkiviaH
NEWBL 03-13 17:17:33 32729 266.720 XccPicDbg7HhRfFwPU3Z2CFVpHSYAhuxtu

1 XnBwaSjgNbpJMjatTiFJfxrigPBKpFmrzq
1 XvmAhGsqwnZqdsWxMqMFQtFeTiVhwntHPF
3 cpupool
5 XeCyp1qAMFTb6PMZu431QpZ6sEpTH64Gag
7 official
12 lotterymining
12 p2pool
29 mininghub
65 suchpool
110 coinmine

total network rate (7.55GH/s), coinmine 4.3GH/s.

it looks like the scammer is on coinmine, i cant tell for sure, since he is anonymous, but if i was pool owner, i would check to see if his highest (1GH) is finding any blocks thats how you will know for sure

Want to avoid 51% Pool ? Go P2Pool !!!!


Join us to MightyPool.net P2Pool Node

Here are the benefits of P2Pool :
You don't need to create an account
You get paid directly after a block is found
You get no transaction fees
The Hasrate is distrubted among all P2Pool nodes

Server hardware configuration :
Xeon E3-1225 v2 @3.2GHz
16 Gb RAM
100 Mbps Internet Broadband

How to join the Node ?
run SPH-SGMINER with those informations :
sgminer -k darkcoin -o stratum+tcp://mightypool.net:7903 -u YourDarkcoinWalletAddress -p x

but you cannot take a situation and use it for your own benefit, as ive told the other p2p pool owners, they might not be affected, but i cannot tell for sure, since i do not have the time to go over the software thoroughly. keep an eye out for big miners, that do not find any blocks..

besides, lotterymining does not charge transaction fees..

Lotterymining server hardware:
Intel(R) Xeon(R) CPU E3-1245 V2 @ 3.40GHz
2x 120GB SSD Striped RAID mode
32 GB ram
1gbps internet connection on tier 1
ddos protection