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

[thelonecrouton]

Hi all, I have been been following todays events closely and I have few (maybe controversial) remarks:

First, the hardfork implemetation went perfectly as far as I can tell. The network never became forked at any point. Immediately following the hardfork a couple of the pools were 1-5 minutes behind the highest block, but at no point did any of the pools ever fork - despite repeated claims to the contrary by people that should know better ::cough cough::. I believe Evan mistakenly interpreted this 1-5 minutes of lag on certain pools and masernodes as a fork, when in fact it was not (probably due to the differences in blockheight reported by the pools and those reported to him by masternode owners). As others have suggested, the reason for this lag is probably because the solved blocks were just taking longer than usual to propagate through the network because there were a lot of old clients on the network, something not entirely unexpected.  

This minor issue solved itself approximately 15-20 minutes after the hardfork took effect, and the network hummed along perfectly fine for another 30 minutes before the reversion was released on github.  During this time masternode payments were also working perfectly.  In retrospect, the decision to revert the code was probably a mistake, but I understand the decision as Evan was acting out of an abundance of caution and that bit of lag spooked him.

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.

+1

I think you're right, the network seemed to be sorting itself out, but maybe Evan spotted something we didn't? I've noticed a minute or two of lag both locally and on my masternodes before, they all always catch up, no forks, no problems.



Also, in case anyone hasn't figured out how to update and restart their masternodes with the newfangled cold/remote setup, here is what worked for me:

On remote:

darkcoind stop
mv darkcoind darkcoind-old-version-number
wget http://www.darkcoin.io/downloads/rc/darkcoind
chmod 755 darkcoind
darkcoind

...wait for it to sync up if needed


On local:

Stop local client if running
Edit your darkcoin.conf and put back in:
masternode=1
masternodeprivkey=your-priv-key-for-that-masternode
masternodeaddr=x.x.x.x:9999

Rename your copy wallet for that masternode back to wallet.dat and fire up the local client or daemon
Wait for it to sync up if needed, then
masternode start 'your-wallet-passphrase'

- you should get 'masternode started sucessfully' and you can now take the local wallet offline again, your masternode should appear at http://drk.poolhash.org/masternode.html within a minute or two.

[coins101]

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.

really? I've been out and trying to catch-up

[AlexGR]

BUMP

Everyone update

Update: Reverting Masternode Payments and New Binaries

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

[stilgars]

Hi all, I have been been following todays events closely and I have few (maybe controversial) remarks:

First, the hardfork implemetation went perfectly as far as I can tell. The network never became forked at any point. Immediately following the hardfork a couple of the pools were 1-5 minutes behind the highest block, but at no point did any of the pools ever fork - despite repeated claims to the contrary by people that should know better ::cough cough::. I believe Evan mistakenly interpreted this 1-5 minutes of lag on certain pools and masernodes as a fork, when in fact it was not (probably due to the differences in blockheight reported by the pools and those reported to him by masternode owners). As others have suggested, the reason for this lag is probably because the solved blocks were just taking longer than usual to propagate through the network because there were a lot of old clients on the network, something not entirely unexpected.  

This minor issue solved itself approximately 15-20 minutes after the hardfork took effect, and the network hummed along perfectly fine for another 30 minutes before the reversion was released on github.  During this time masternode payments were also working perfectly.  In retrospect, the decision to revert the code was probably a mistake, but I understand the decision as Evan was acting out of an abundance of caution and that bit of lag spooked him.

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.

+101

+1
The communication is catastrophic, despite repeated demands for more transparence and openess from the community - and  still no official comment on what really happened. Really dissapointed.

[Denada129]

XC is a dead coin that was pumped and dumped by people looking to make a quick buck that missed the Darkcoin train. Don't mistake p/d'ers chasing a quick buck for innovation. Fuck they can't even come up with their own branding! Darkcoin didn't simple copy paste the another coin's code and launch "AnothercoinsAlgocoin". Then turn around and talk shit about the originalcoins devs. In fact, I haven't personally witnessed any of the DRK devs degrade another coins development team; In fact, it's quite the opposite.. They've been working with other developers from other coins which is how the crypto community should ACTUALLY be functioning - not against each other.

Any person that goes into another coin's thread and spreads bullshit to promote his or her coin is trash. Same goes to any coin developer - if you need to talk shit about a coin you copied to make up for its lack of innovation it translates into you and your coin project are trash.

Chaeplin,AlexGR,ilodin... all over the XC thread spreading fud, your community have created a thread for bash XC community "XC unmoderated" where you promote your darkfork !!!
Please....

Delete this thread that you have created and after you can speak !

Just curious has XC figured out how to handle people that reprogram their wallet to steal the coins ?

So no XC promoter answered this, I will just presume that this issue still persists then.

Current Rev 1.5 uses trusted transactions. Multisig is an easy implementation and will fix this. This is set for the first week in July, knowing dan though, it will be earlier.

Could you please people discuss your coin in its thread ? It is embarrassing now.

Search for the XC unmoderated thread in announcement and you will understand...
...
...
...
You want a moderated thread ?

[GhostPlayer]

What does "no masternode payment yet" mean?

- masternode payments don't work?
- masternode payments not activated?
- masternode payments working/in progress but still need time for first MN payment to go through? (if this: Why?)

DRK = failed!

True. If you understand nothing about cryptos, finances and responsibility in development... You might have point.

 If you think this fork affected the coin... you're wrong.
 If it postponed Masternode payments... you're right
 If you think anonymity is flawed... you're wrong
 If you want to dump... you're right!! (just pleeeeease give me a head's up!!)

[coins101]

We are here, so lets have the party anyway 

[whazzledazzle]

<@CHAOSiTEC> so, today we gained alot of wisdom, and we are working on a new way to implement masternode payments, that will work... (my idea) :-p
and a bit later...
<@CHAOSiTEC> ive come up with a new solution for masternodes payment, we are working on that now

New dev on the job helping Evan, no ETA was given.

[UdjinM6]

so basically nothing happened, we just need one more testing phase here

[ymer]

Update: Reverting Masternode Payments and New Binaries

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

So, release was postponed... again?

What's this the 5th time in the last 2 months?

Smoke and mirrors to keep the bubble from bursting as long as this scam artists can.

[GhostPlayer]

XC is a dead coin that was pumped and dumped by people looking to make a quick buck that missed the Darkcoin train. Don't mistake p/d'ers chasing a quick buck for innovation. Fuck they can't even come up with their own branding! Darkcoin didn't simple copy paste the another coin's code and launch "AnothercoinsAlgocoin". Then turn around and talk shit about the originalcoins devs. In fact, I haven't personally witnessed any of the DRK devs degrade another coins development team; In fact, it's quite the opposite.. They've been working with other developers from other coins which is how the crypto community should ACTUALLY be functioning - not against each other.

Any person that goes into another coin's thread and spreads bullshit to promote his or her coin is trash. Same goes to any coin developer - if you need to talk shit about a coin you copied to make up for its lack of innovation it translates into you and your coin project are trash.

Chaeplin,AlexGR,ilodin... all over the XC thread spreading fud, your community have created a thread for bash XC community "XC unmoderated" where you promote your darkfork !!!
Please....

Delete this thread that you have created and after you can speak !

Just curious has XC figured out how to handle people that reprogram their wallet to steal the coins ?

So no XC promoter answered this, I will just presume that this issue still persists then.

Current Rev 1.5 uses trusted transactions. Multisig is an easy implementation and will fix this. This is set for the first week in July, knowing dan though, it will be earlier.

Could you please people discuss your coin in its thread ? It is embarrassing now.

Search for the XC unmoderated thread in announcement and you will understand...
...
...
...
You want a moderated thread ?

That was a direct consequence of stupid accusations and a flood of XC trolls spreading FUD.
Since we have actual proficient guys on the team, they went and did an unmoderated debate to ascertain the blatant confrontation.

 What happened was a technical analysis and proof that XC is flawed in the core, and that tx can be linked.
 Deal with it.

 To this day, no one has done the same with DRK. You're very welcomed to try.

[coins101]

Update: Reverting Masternode Payments and New Binaries

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

So, release was postponed... again?

What's this the 5th time in the last 2 months?

Smoke and mirrors to keep the bubble from bursting as long as this scam artists can.

Something for your short attention span to focus on

[GhostPlayer]

Update: Reverting Masternode Payments and New Binaries

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

So, release was postponed... again?

What's this the 5th time in the last 2 months?

Smoke and mirrors to keep the bubble from bursting as long as this scam artists can.

 Look who's back!!! My favourite troll ever!!

 You hide beneath a rock, and only come out when there is shit to eat.

 Good appetite!

[thelonecrouton]

peurile nonsense

chaeplin proved XC mixing wasn't anonymous and your coins can get stolen by anyone with a modified wallet, now fuck off back to your shitcoin, the grownups are talking here.

Ignore list growing mightily today.

[abercrombie]

I'm an investor in BTC, but a trader in DKR.

As a trader, I'm loving the DRK movements.  The volatility is better than anything out there.  Up 4 points, down 6 points... the price movements are awesome. 

As a potential investor, I would like to see a successful masternode payment.  Otherwise, there is little incentive to propogate the system aside from conviction.  Until the masternode payment system is ironed out, I'll remain a trader.

[newb4now]

Update: Reverting Masternode Payments and New Binaries

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

So, release was postponed... again?

What's this the 5th time in the last 2 months?

Smoke and mirrors to keep the bubble from bursting as long as this scam artists can.

Its funny how the same people who were calling long time DRK holders paranoid when raising concerns prior to the fork are being silent now.

The only positive I can see from this is a new dev being brought in. Perhaps Evan will agree to step down or at least hand off communication to someone who values the community

[ymer]

Update: Reverting Masternode Payments and New Binaries

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

Wasn't the 1 month under the testnet enough to... well test it?

LOL   , this bubble is just about to burst.

[stilgars]

<@CHAOSiTEC> so, today we gained alot of wisdom, and we are working on a new way to implement masternode payments, that will work... (my idea) :-p
and a bit later...
<@CHAOSiTEC> ive come up with a new solution for masternodes payment, we are working on that now

New dev on the job helping Evan, no ETA was given.

waou ... I thought the current RC3 solution has been extensively tested for weeks on testnet, and suddenly, after two hours following another botched attempt, evan realizes that he needs more development for yet ANOTHER solution AND additional support?
If he is not qualified enough, he needs to step down.

[thelonecrouton]

so basically nothing happened, we just need one more testing phase here

I'm not convinced there was a problem at all, just Evan being responsibly cautious. In any case, lessons will be learned, it's all part of the development process, which the ADD kiddies have a hard time grasping.

DRK is financial privacy for everyone in the making, not a two week p&d wonder.

[crimi]

To da moon, just kidding...