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

[AlexGR]

BUMP

Everyone update

Update: Reverting Masternode Payments and New Binaries

https://darkcointalk.org/threads/reverting-rc3-masternode-payments-fork.1458/

[1714675993]

1714675993

[Simcom]

If anyone has any evidence to suggest that the network was "forked" at any point, please share - I have reviewed IRC transcripts and have read every post, and was monitoring the pools throughout the hardfork implementation and there was never any evidence that I am aware of to suggest that the network had actually forked. Hopefully Evan will re-release the same code and we can try to fork RC3 in a couple days.

I was going through the two block explorers and I think it was a ...97 block which I saw on chainz and the official block explorer. They had different values for the same block.

I was refreshing the block explorers periodically, I did notice chainz was behind at one point (chainz often lags for no apparent reason so I wouldn't read much into that), but I didn't see any evidence of a fork, just some lagging.  When the revert went up both explorers (and all pools) were on the correct chain.

several forks where found on the network, that is why reversal was the only logical choice

I understand. Better to be safe than live with the worry that additional forking may occur down the road. You were right about at least some forking occurring, I see that coinmine.pl was on a wrong fork for over an hour https://www2.coinmine.pl/drk/index.php?page=statistics&action=blocks - so I take back my previous statements.

[linked67]

P2PoolCoin.com
P2pool node for DarkCoin

EU server: http://p2poolcoin.com:7903
Canada Server: http://ca.p2poolcoin.com:7903

Dedicated server
Xeon cpu
32Go ram
SSD
1Gbps

Fee: 1% ONLY !!!!

Nodes Updated to the latest version (0.9.10.2)

[DyslexicZombei]

Simcom: BTW, I def. saw some strong evidence of sideforking last night. My biz partner sent me 250DRK last night to top out our fifth community owned node and it just never arrived (he was using .9x I was using .10x). I'm assuming this transaction was orphaned since it never arrived (and I *think* it never left his wallet).

Anything that happened before the hardfork is irrelevant. Likely a run-of-the-mill orphaned block.

It's possible. However, this morning Evan was talking about possible forking issues hours several before the official fork time about 2 hours ago; A problem that may be related to having a mix of old/new software versions among nodes.

[Icebucket]

coins101: Your last was very informative. Plz post moar!!!111

maybe we need some new material. I'll go ask auntie google. brb

The first one you post, long time ago is lot more cute.

haha, the one with the peakish nose and the enormous ....

so in the history books they will say "in the darkest hour, they viewed porn"

lol yeah thats porn, are u Amish by any chance ?

[coins101]

I give up on this non issue for now.

JD & Game of Thrones box set beckons.

Let me know when we are back above 0.02

[TsuyokuNaritai]

These recent posts are clearly stimulating the market, keep going.

[coins101]

These recent posts are clearly stimulating the market, keep going.

I think we need to side chain porn.

Maybe the wallets can have a little pop-up window for porn on side chains, and when we need network information we change the message. Might get a little frustrating if you are getting busy 

[CryptoPleb]

<@evan82> http://pastebin.com/QmbM8dPH
[08:51] <@evan82> I found the problem :-)
[08:51] <@evan82> It's actually rather simple to fix

[AlexGR]

These recent posts are clearly stimulating the market, keep going.

Buyer seems to love girls & chewing DRKs, steadily, whether in small or large chunks.

2014-06-20 22:50:23   BUY   0.01690000   2.00000000   0.03379999
2014-06-20 22:50:23   BUY   0.01690000   0.50000000   0.00844999
2014-06-20 22:49:55   BUY   0.01689000   413.01118429   6.97575890
2014-06-20 22:49:39   SELL   0.01687900   25.00000000   0.42197500
2014-06-20 22:49:37   BUY   0.01689000   252.98881571   4.27298109
2014-06-20 22:49:17   BUY   0.01687900   20.00000000   0.33758000
2014-06-20 22:47:41   BUY   0.01681000   20.97948560   0.35266515
2014-06-20 22:47:16   BUY   0.01681000   5.00134741   0.08407265
2014-06-20 22:47:15   BUY   0.01681000   0.06881023   0.00115670
2014-06-20 22:46:17   SELL   0.01678000   4.00000000   0.06712000
2014-06-20 22:46:16   BUY   0.01680000   57.08594434   0.95904386
2014-06-20 22:46:03   BUY   0.01680000   1142.91405566   19.20095614
2014-06-20 22:46:03   BUY   0.01680000   2.00000000   0.03360000
2014-06-20 22:46:03   BUY   0.01680000   0.59204731   0.00994639
2014-06-20 22:46:03   BUY   0.01679950   57.08764349   0.95904386
2014-06-20 22:45:50   SELL   0.01675000   0.21000000   0.00351750
2014-06-20 22:45:44   BUY   0.01679950   14.76069585   0.24797231
2014-06-20 22:45:44   BUY   0.01679000   0.08000000   0.00134320
2014-06-20 22:45:44   BUY   0.01678000   0.27000000   0.00453060
2014-06-20 22:45:44   BUY   0.01678000   0.29000000   0.00486619
2014-06-20 22:45:19   BUY   0.01675000   41.34610005   0.69254717
2014-06-20 22:45:11   SELL   0.01670000   176.56100757   2.94856884
2014-06-20 22:44:57   SELL   0.01670000   0.01000000   0.00016700
2014-06-20 22:44:52   BUY   0.01670007   18.07702265   0.30188754
2014-06-20 22:44:40   BUY   0.01670000   22.54785000   0.37654909
2014-06-20 22:44:40   BUY   0.01670000   47.30021907   0.78991365
2014-06-20 22:44:40   BUY   0.01670000   2.00000000   0.03340000
2014-06-20 22:44:40   BUY   0.01666110   0.01730000   0.00028823
2014-06-20 22:44:40   BUY   0.01666110   0.50000000   0.00833055
2014-06-20 22:44:40   BUY   0.01666109   35.86125775   0.59748764
2014-06-20 22:44:40   BUY   0.01666109   1.10518450   0.01841357
2014-06-20 22:44:40   BUY   0.01666109   34.39567824   0.57306949
2014-06-20 22:44:40   BUY   0.01666000   10.00000000   0.16660000
2014-06-20 22:44:40   BUY   0.01666000   16.50000000   0.27489000
2014-06-20 22:44:33   BUY   0.01657000   0.01000000   0.00016570
2014-06-20 22:44:16   BUY   0.01665000   0.02000000   0.00033300
2014-06-20 22:44:16   BUY   0.01665000   1.00000000   0.01665000
2014-06-20 22:44:04   SELL   0.01657110   45.00000000   0.74569950
2014-06-20 22:43:38   BUY   0.01664700   74.70146922   1.24355535
2014-06-20 22:43:27   BUY   0.01664700   3.81077251   0.06343793
2014-06-20 22:43:11   BUY   0.01664700   15.48775827   0.25782471
2014-06-20 22:42:50   BUY   0.01660000   32.54000000   0.54016399
2014-06-20 22:42:50   BUY   0.01660000   0.10000000   0.00166000
2014-06-20 22:42:50   BUY   0.01660000   5.00000000   0.08300000
2014-06-20 22:42:50   BUY   0.01660000   9.53651665   0.15830618
2014-06-20 22:42:47   BUY   0.01659000   94.00000000   1.55946000
2014-06-20 22:42:25   BUY   0.01657000   0.02400000   0.00039768
2014-06-20 22:42:25   BUY   0.01656110   0.01330000   0.00022026
2014-06-20 22:41:08   SELL   0.01654000   13.14827959   0.21747254
2014-06-20 22:41:08   SELL   0.01655000   18.00000000   0.29790000
2014-06-20 22:41:08   SELL   0.01656000   1.27304468   0.02108162
2014-06-20 22:40:21   BUY   0.01655000   0.02540000   0.00042036
2014-06-20 22:40:21   BUY   0.01655000   3.70380732   0.06129801
2014-06-20 22:39:39   BUY   0.01655000   14.00000000   0.23170000
2014-06-20 22:38:46   BUY   0.01655000   1.17647235   0.01947061
2014-06-20 22:38:21   BUY   0.01655000   1.11972033   0.01853137
2014-06-20 22:38:21   BUY   0.01655000   0.03311196   0.00054800
2014-06-20 22:38:19   BUY   0.01654000   1.78834418   0.02957921
2014-06-20 22:37:52   BUY   0.01654000   6.00000000   0.09924000
2014-06-20 22:37:43   BUY   0.01654000   20.00000000   0.33080000
2014-06-20 22:37:43   BUY   0.01654000   2.94117647   0.04864705
2014-06-20 22:37:22   BUY   0.01654000   5.01583675   0.08296194
2014-06-20 22:37:20   BUY   0.01654000   5.01583675   0.08296194
2014-06-20 22:37:11   BUY   0.01654000   2.94117647   0.04864705
2014-06-20 22:36:28   BUY   0.01654000   10.29762938   0.17032279
2014-06-20 22:36:28   BUY   0.01654000   31.90542476   0.52771575
2014-06-20 22:35:27   SELL   0.01653835   4.00000000   0.06615340
2014-06-20 22:34:54   BUY   0.01653001   0.03614198   0.00059742
2014-06-20 22:34:52   BUY   0.01653001   5.00252268   0.08269175
2014-06-20 22:33:36   BUY   0.01654000   0.50211608   0.00830500
2014-06-20 22:33:04   BUY   0.01654000   5.00304413   0.08275035
2014-06-20 22:33:02   BUY   0.01654000   5.00304413   0.08275035
2014-06-20 22:32:55   BUY   0.01654000   0.04000000   0.00066159

[CryptoPleb]

[08:51] <@evan82> I found the problem :-)
[08:51] <@evan82> It's actually rather simple to fix
[08:52] <@evan82> anyone care to guess from the paste? I'm curious

<@evan82> http://pastebin.com/QmbM8dPH

[AlexGR]

BUMP

Everyone update

Update: Reverting Masternode Payments and New Binaries

https://darkcointalk.org/threads/reverting-rc3-masternode-payments-fork.1458/

[CryptoPleb]

<@evan82> Two blocks are solved at nearly the same moment on the network, both are propogated and accepted by the network. In the current implementation both blocks have the same hash, but in these blocks there's some discrepency about who to vote for.

<@evan82> In one block the miner votes for 88802 and 88803, in the other the miner abstains from voting. When the next block is solved it's based on of one of the older blocks, so half of the network beleives the miner cheated and rejects the block causing a fork.

<@evan82> The solution to this is rather simple. Any changes to the votes need to also change the hash of the block. The network must not think these two blocks are the same.

[AlexGR]

[01:51] <evan82> http://pastebin.com/QmbM8dPH
[01:51] <evan82> I found the problem :-)
[01:51] <evan82> It's actually rather simple to fix
[01:51] <tifozi> ahem
[01:52] <evan82> anyone care to guess from the paste? I'm curious
[01:52] <tifozi> checking
[01:52] <tifozi> badVote
[01:53] <evan82> Both votes have the same hash, but they have different votes
[01:53] <evan82> er both blocks*
[01:54] <evan82> Two blocks are solved at nearly the same moment on the network, both are propogated and accepted by the network. In the current implementation both blocks have the same hash, but in these blocks there's some discrepency about who to vote for.
[01:54] <evan82> In one block the miner votes for 88802 and 88803, in the other the miner abstains from voting. When the next block is solved it's based on of one of the older blocks, so half of the network beleives the miner cheated and rejects the block causing a fork.
[01:54] <GNULinuxGuy> nice
[01:54] <evan82> The solution to this is rather simple. Any changes to the votes need to also change the hash of the block. The network must not think these two blocks are the same.
[01:54] <tifozi> How come we didnt see this in testnet
[01:54] <tifozi> seems rather simple problem
[01:55] <tifozi> what in mainnet causes it
[01:55] <evan82> Not sure. No one noticed.
[01:55] <qqr> race conditions are hard to witness

[coins101]

The price did move 

Now I'm not sure if that was the problem being found and being an easy fix, or the picture of the little rocket 

[AlexGR]

edit: and of course this is great distraction against FUD, dont get me wrong ppl

I think we should make it an official policy of this thread to post semi-naked chicks every time a FUD-post is posted.

Quote the fuder =>

...FUD

=> chick

WIN

[TsuyokuNaritai]

Someone on mintpal (and only mintpal) hasn't heard the good news.

Last chance for cheap DRK!

[Denada129]

Attention pool operators!

https://darkcointalk.org/threads/issues-with-masternode-payments-fork.858/

Wow. So fast

Today the masternode payments fork went into effect. The fork went off without issue and the network looks very healthy, but it appears there is some issue with pools voting for the wrong masternodes. This is causing payments to not go through as they should.

The fix is rather simple and can be done without a hard fork. After the pools update to the fixed version, the payments will begin to go through.
We’re currently working on a resolution and will provide the new version soon (probably by tomorrow, hopefully in a few hours).

Thanks,

The Darkcoin Team

Pools need to update to the fixed version

[01:51] <evan82> http://pastebin.com/QmbM8dPH
[01:51] <evan82> I found the problem :-)
[01:51] <evan82> It's actually rather simple to fix
[01:51] <tifozi> ahem
[01:52] <evan82> anyone care to guess from the paste? I'm curious
[01:52] <tifozi> checking
[01:52] <tifozi> badVote
[01:53] <evan82> Both votes have the same hash, but they have different votes
[01:53] <evan82> er both blocks*
[01:54] <evan82> Two blocks are solved at nearly the same moment on the network, both are propogated and accepted by the network. In the current implementation both blocks have the same hash, but in these blocks there's some discrepency about who to vote for.
[01:54] <evan82> In one block the miner votes for 88802 and 88803, in the other the miner abstains from voting. When the next block is solved it's based on of one of the older blocks, so half of the network beleives the miner cheated and rejects the block causing a fork.
[01:54] <GNULinuxGuy> nice
[01:54] <evan82> The solution to this is rather simple. Any changes to the votes need to also change the hash of the block. The network must not think these two blocks are the same.
[01:54] <tifozi> How come we didnt see this in testnet
[01:54] <tifozi> seems rather simple problem
[01:55] <tifozi> what in mainnet causes it
[01:55] <evan82> Not sure. No one noticed.
[01:55] <qqr> race conditions are hard to witness

Its going to take one more month for what you call "simple problem" ?

 

[stilgars]

I am somehow surprised that no one thought about modifying the hashes after introducing the MN voting system, especially since it impacts consensus, but hell ...

[TsuyokuNaritai]

Its going to take one more month for what you call "simple problem" ?

Who said anything about one more month? Or are you just trolling?