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

[Icebucket]

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.

[Mwalshe89]

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.

[tungfa]

DarkCoin Mac OS X Update v0.9.10.2
updated 20 June 2014

Download and more info:  https://bitcointalk.org/index.php?topic=421615.msg4585071#msg4585071

SUPERSTAR
Tx man
any chance for Darksend version too ?

[Coolstoryteller]

Judging by the fact XC is up 10% since DRK forked looks like a few of the fanclub are realising... XC is a superior coin with a much superior dev.

So when your coin was going down as Cryptcoin was going up, and you were panicking about what was going on with Crypt and why were people buying it instead of "superior XC" what did that mean for XC? That Mindfox is better and "superior" to Dan?

These superiority stuff is bullshit.

Satoshi = brilliant guy that invented TRUSTLESS transactions which solved a decades old problem, not through a "trust learning algo" but through proof of work. Nobody disputes this.

XC = a coin that is "superior" because it goes back to trusted transactions, taking people back to the original problem that should have already been solved.

Apparently XC's dev should have also written a paper on why Satoshi is a fool and why we should all have trusted transactions instead of trustless. He is after all the superior dev of all altcoins.

You obviously don't keep up with the times. XC will be trustless with multi-sig in Rev 2.

Any other arguments?

You said you have the superior coin, when it used TRUSTED transactions. I don't need to make any other argument, you just made a fool of yourself.

All this superiority talk I hear from day one.

Dan makes a centralized mixer "wowwwwwwwwww we did more than DRK did in months"... just for making a centralized mixer, lol.

Then he makes the "decentralized" trusted mixers that lost coins and you are like "WOOOOWWWWW FIRST WORKING ANON", lol.

Now you are telling me, ok I'm not really superior, but one day I will be.

It's june 20th 2014. I've heard about the NSA-proof Rev 2.0 for over a month when it was supposed to be delivered in 2-3 weeks.

=> https://bitcointalk.org/index.php?topic=600706.msg6932856#msg6932856

...and we haven't even solved the issue of trusted transactions.

So, instead of being here and being happy for the problems of others, go back and solve your own problems. It's more productive.

No dude. Your the one making a fool out of yourself. Rev 2 was given a timeline for the first week in July. Dan hasn't missed a deadline yet, unlike Evan who sets deadlines months in advance and still fails to deliver. Rev 2 will use trustless multisig. Please explain how these will be trusted transactions? Owww wait. You can't.

And also, I'm not telling you XC will be superior. I'm telling you XC is superior now. Even Chaplin admitted that DRK won't even be close to XCs level of anonymity until RC4. XC has a 1BTC bounty for finding a link, nobody has broken it yet.

XC has accomplished in six weeks what DRK couldn't do in six months. Imagine how far ahead its going to be in four months when your RC4 is finally released?

And that NSA level security is likely because XC has an NSA level Dev. He's developed groundbreaking world firsts in technology and its internationally renown. He's also worked for companies such as IBM. Allot more than I can say for dan who is struggling to fix one 'simple' bug after a month. Something XC never had a single issue in implementing.

No dude. Your the one making a fool out of yourself. Rev 2 was given a timeline for the first week in July.

You mean updated timeline.

Back in mid to late May, the full-blown implementation was supposed to take place 3-4 weeks later.

Please explain how these will be trusted transactions? Owww wait. You can't.

Yes I can't tell you about future stuff. I can only discuss what you have now.

And also, I'm not telling you XC will be superior. I'm telling you XC is superior now. Even Chaplin admitted that DRK won't even be close to XCs level of anonymity until RC4. XC has a 1BTC bounty for finding a link, nobody has broken it yet,

Ok sell your house and buy XC if you believe in it so much. Why come here and tell us how DRK sucks and why XC is so superior - when it's vapor? You (XC) wouldn't even be here without DRK. XC and a plethora of anoncoins and scamcoins just tried to pull the same pattern as with all other coins.

Dogecoin => let's make some memecoins or animalcoins
Aurora => let's make some countrycoins
Blackcoin => let's make PoW/PoS coins or colorcoins
Darkcoin => let's make anonymous coins (and since we can't do that, let's do hacks with the wallets, setup central mixers or write "whitepapers")

It's always the same for people who lost the train of the first one and want to catch (or create) a train that they can ride on, while crapping on the market leader.

Of course you can explain about future stuff. We both know in two weeks XC will use multisig and that will make the transactions trustless. Your entire argument for why XC is flawed is out of the window.

And what XC has now? We have anonymous transactions with working node systems. Two things DRK doesn't have.

lost the train? Dude, its obvious. Your technology is inferior and your Dev's are inferior. Your still buying yahoo stock while everyone else is about to see google.

I remember when XC was just being born and all the scared DRK fanboys ran over to the XC thread to say it was all empty promises and the technology was flawed. Now all those promises are getting delivered and its your technology that is full of empty promises, and clearly flawed, its nice to return the favour.

Just remember, it took DRK six months to get to the flawed state it is in now, while it took XC 6 week to better it.

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.

[stilgars]

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.

[Denada129]

Can we please stop talking about XC? That shitcoin has its own thread, make use of it.

Are the trolls in need of another tweet ?  

It's not going to correct your flawed code on masternode...

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.

Do it yourself wallet and xnode that get payed is public...

[Mwalshe89]

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.

Ill stop now. I just remember six weeks ago when the DRK fanboys were FUDing XC because it solved all of the problems DRK had. They said it was all false promises and vapourware, now its complete, and its DRK with the failed promises and vapourware I thought I'd return the favour.

Enjoy the market crash for the next few days.

[slapper]

Wow DRK crashed hard. The fact that masternodes failed again might really damage the market.

Not yet Selfish here but I was really hoping to double up my DRK this go around and I know I will. /Evil Laugh.

[sorryforthat]

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.

Pretty sure DRK dev tweeted FUD with nothing to back it up plenty of times.

[Simcom]

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.

[newb4now]

Wow DRK crashed hard. The fact that masternodes failed again might really damage the market.

I dont think the dev really cares anymore. He has already made enough money to retire (early mining).

Many people asked repeatedly for his confirmation that everyone (all pools, exchanges, masternodes etc) had updated the software pre fork. He ignored the warning just as he did last fork.

[AlexGR]

This is disgusting, 3 fucking lines of code would fix this whole problem by banning MN when they fail a version check
I can't believe how bad the dev team handled this

That's too simplistic. If a MN's wallet is hacked to show correct version number maliciously so as to be accepted, what then? You need checks all the way.

[AlexGR]

Many people asked repeated for his confirmation that everyone had updated the software pre fork. He ignored the warning just as he did last fork.

Everyone "important" like pools, exchanges, service providers etc use a mailing list through which they receive notice of updates.

[slapper]

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.

Pretty sure DRK dev tweeted FUD with nothing to back it up plenty of times.

Why do you believe this crap. I watched the XC saga live It was MoosaNYC who posted on btce trollbox that chaeplin had found Fedoracoin cpp file in the then active XC github.

Do you think XC investors were looking at a Darkcoin tweet to make decisions on XC? Dan has been trolling Darkcoin since he came up with XC false operation. You guys are waiting for a rough ride.

[newb4now]

Many people asked repeated for his confirmation that everyone had updated the software pre fork. He ignored the warning just as he did last fork.

Everyone "important" like pools, exchanges, service providers etc use a mailing list through which they receive notice of updates.

I was told this before as well. My response is that just because there is a mailing list does not mean everyone will respond to it. Exchanges may handle 100s of coins and have a hard time keeping up with all of them. Many only fix problems after they occur. I said that dev needed to personally contact each exchange, pool and ask for their confirmation that the update had been completed.

Dev ignored advice from the community and DRK suffered.

[T.Stuart]

First, the hardfork implemetation went perfectly...

Yes

Evan was acting out of an abundance of caution...

Yes

I have already said it and I'll say it again. Be careful panickers because we are in a flash crash that will resolve very shortly.

[dewdeded]

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?)

[benthach]

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!

[crimi]

Masternode payments did work. The difficulty was down so some pools had been on a fork?

[AlexGR]

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.

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?)

It means that they are disabled for the time being after issues or "issues" - depending one's analysis - on the latest fork.