Fool me once, shame on you. Fool me twice, shame on me.
...
Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 5133. (Read 9723733 times)
June 20, 2014, 01:00:08 PM
June 20, 2014, 01:00:01 PM
The buy support will came when everything is fine 
/maybe its fine even now/
/maybe its fine even now/ 
June 20, 2014, 12:59:04 PM
Ok im out. Going to buy BC, They at least have solid dev team who can write few lines of code
You were never in June 20, 2014, 12:58:22 PM
New binaries available on Darkcoin site. Just downloaded and its .02 version.
https://www.darkcoin.io/getstarted.html
https://www.darkcoin.io/getstarted.html
Code:
"version" : 101002,
"protocolversion" : 70018,
"protocolversion" : 70018,
June 20, 2014, 12:57:52 PM
oh my goodness.
people want to sell and dump it, the problem is the buy support is so weak. there's hardly any btc that want to buy it atm
people want to sell and dump it, the problem is the buy support is so weak. there's hardly any btc that want to buy it atm
June 20, 2014, 12:57:29 PM
[20:48] Propulsion> git pull
[20:48] yes.
[20:48] vertoe, I think so, that's how I understand it
[20:48] thats what i meant
[20:48] git pull
[20:48] payments are off
[20:48]
[20:48] why?
[20:48] forks
[20:48] so what?
[20:48] no forks
[20:48] mini-forks
[20:48] all my machines are on the correct fork
[20:49] Showing current block 88830.
[20:49] after update.
[20:49] 00000000000b630ff3ddf3db73093b85e38b9bb93e9874883cedb39f2173af7c
[20:49] 88830 hash=00000000000b630ff3ddf3db73093b85e38b9bb93e9874883cedb39f2173af7c
[20:49] yep same.
[20:49] no forks just some clients lagging behind
[20:50] evan wants to fix it
[20:50] donho> I had at least 2 forks
[20:50] donho he's fixing it with the patch.
[20:50] we did have some forks
[20:50] 88831 000000000004e5644016c4f305f423b322b316c24237dd8088e331a73a0cdaa9
[20:50] no he's reverting it
[20:50] then he will fix it
[20:50] Reverting. Doing a git clone. new block height.
[20:50] the statement from evan82 was right, it was fixing itself in 15-20min timeframe
[20:50] but he thinks that's not acceptable, that's his call
[20:50] yes; but as he also said - it's unacceptable for a blockchain.
[20:51] 88832 hash=00000000000ef942f1e9b1db42d3728bdde011f8c76c025f3391a7b265654dba
[20:51] anyway; lets try not to clutter up this w/ speculation and whatnot
[20:51] The Darkcoin network has been experiencing some issues with
[20:51] intermittent blockchain forks. These forks are not as serious as the
[20:51] last update, being they appear to fix themselves after 15-30 minutes.
[20:51] 88832 00000000000ef942f1e9b1db42d3728bdde011f8c76c025f3391a7b265654dba
[20:51] However, we must revert to no masternode payments until we're sure
[20:51] we've discovered the problem.
[20:51] Please recompile if you're running a daemon, otherwise binaries will
[20:51] be made available soon.
[20:51] email just got out
[20:51] Windows binaries are on the darkcoin.io site.
[20:51] Ok p2pool is back up.
[20:52] excellent Ape.
[20:52] thanks InternetApe
[20:52] wget on linux ?
[20:52] I will check if the verbage has been updated, but the files are the reverted.
[20:52] InternetApe: I can just checkout the git source?
[20:52] linux 10.10.2 binaries online?
[20:52] stopeed mns, awaiting binaries
[20:53] <-- Stealth95 ([email protected]) has left this server.
[20:54] <-- heduciwo ([email protected]) has left this channel ("Trennungsnachricht").
[20:55] also stopped mines while waiting for the 10.10.2 binary
[20:55] <-- Light_ ([email protected]) has left this server.
[20:55] <-- nj4752 (~AndChat65@2600:1014:b103:db23:9e72:731a:af29:b2c7) has left this server (Quit: Bye).
[20:56] --> Light_ ([email protected]) has joined this channel.
[20:56] ok reverting the mpos pool now.
[20:56] wrong version showing on website
[20:56] for new win binary
[20:48]
[20:48]
[20:48]
[20:48]
[20:48]
[20:48]
[20:48]
[20:48]
[20:48]
[20:48]
[20:48]
[20:48]
[20:49]
[20:49]
[20:49]
[20:49]
[20:49]
[20:49]
[20:50]
[20:50]
[20:50]
[20:50]
[20:50]
[20:50]
[20:50]
[20:50]
[20:50]
[20:50]
[20:50]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:51]
[20:52]
[20:52]
[20:52]
[20:52]
[20:52]
[20:52]
[20:52]
[20:53] <-- Stealth95 ([email protected]) has left this server.
[20:54] <-- heduciwo ([email protected]) has left this channel ("Trennungsnachricht").
[20:55]
[20:55] <-- Light_ ([email protected]) has left this server.
[20:55] <-- nj4752 (~AndChat65@2600:1014:b103:db23:9e72:731a:af29:b2c7) has left this server (Quit: Bye).
[20:56] --> Light_ ([email protected]) has joined this channel.
[20:56]
[20:56]
[20:56]
June 20, 2014, 12:57:18 PM
Let me interject a common-sense course of action which will be ignored.
Yes, it's going outside confirmation window. But it IS fixing itself.
Reverting will only rob us of the log files needed to find the problem. Let it go for a while, find the problem, then fix it. If we revert we'll never find it...
+1Yes, it's going outside confirmation window. But it IS fixing itself.
Reverting will only rob us of the log files needed to find the problem. Let it go for a while, find the problem, then fix it. If we revert we'll never find it...
June 20, 2014, 12:56:16 PM
Ok im out. Going to buy BC, They at least have solid dev team who can write few lines of code
Good f*ckng riddance.
They deserve parasites like you
June 20, 2014, 12:55:50 PM
I have capitulated.
June 20, 2014, 12:55:10 PM
Ok im out. Going to buy BC, They at least have solid dev team who can write few lines of code
June 20, 2014, 12:54:18 PM
was evan that dumped ? since he knew firsthand?
June 20, 2014, 12:54:02 PM
Is this something that will be fixed in a matter of hours, days or weeks?
June 20, 2014, 12:53:01 PM
Yes, I agree it looked FAR better than the random forks last time - achieving network consensus on its own, but I have no idea if it would remain that way or if it could divert & reconverge. As an outsider if it seems to be working, I align with "if it ain't broken don't fix it". If Evan saw something that needs fixing "under the hood", then he knows better than me (and others saying "keep it"). I believe he wouldn't revert it for the lulz. He probably saw something.
It didn't just look far better, it gave use useful feedback and proved it was self-fixing...Yes, I'm seeing it spontaneously do this over and over. That's my point... Log Files! Nail it instead of throw it away...
June 20, 2014, 12:51:58 PM
FYI - this was just sent out to the mailing list. More information to follow.
Evan Duffield
10:43 AM (7 minutes ago)
to bcc: me
The Darkcoin network has been experiencing some issues with
intermittent blockchain forks. These forks are not as serious as the
last update, being they appear to fix themselves after 15-30 minutes.
However, we must revert to no masternode payments until we're sure
we've discovered the problem.
Please recompile if you're running a daemon, otherwise binaries will
be made available soon.
https://github.com/darkcoinproject/darkcoin
Thanks,
The Darkcoin Team
Evan Duffield
10:43 AM (7 minutes ago)
to bcc: me
The Darkcoin network has been experiencing some issues with
intermittent blockchain forks. These forks are not as serious as the
last update, being they appear to fix themselves after 15-30 minutes.
However, we must revert to no masternode payments until we're sure
we've discovered the problem.
Please recompile if you're running a daemon, otherwise binaries will
be made available soon.
https://github.com/darkcoinproject/darkcoin
Thanks,
The Darkcoin Team
June 20, 2014, 12:51:49 PM
we should have known better!! It happened once. It would happen again. Fuck
Yup, traders know the saying:
If you can't stand the heat, get out of the kitchen.....
June 20, 2014, 12:50:10 PM
This is the biggest plunge of price which I have ever seen in my life ... The problem is that I am watching how I am loosing thousand of dollars just in a minutes ...
Well, how does the saying go:
You win some, you lose some.
Easy come, easy go.
Or my favorite:
After the gathering comes the scattering.
June 20, 2014, 12:49:43 PM
This is the biggest plunge of price which I have ever seen in my life ... The problem is that I am watching how I am loosing thousand of dollars just in a minutes ...
That's crypto, don't act like it can't happen at anytime.
June 20, 2014, 12:49:05 PM
[20:29] But that's not acceptable, so it must be reverted
I'm losing a little faith in Evan on this... He should know better...This will continue as long as bad actors can hit it. Needs time and updated clients. You're right, it's outside standard conf depth. BTC hardforked and had problems like this for WEEKS... It finally leveled out. From waht I'm seeing in my debugs, it's just a matter of time...
I'm not coder, but I'm not stupid, either... This doesn't look so bad. In fact, it looks like exactly what I would expect...
Yes, I agree it looked FAR better than the random forks last time - achieving network consensus on its own, but I have no idea if it would remain that way or if it could divert & reconverge. As an outsider if it seems to be working, I align with "if it ain't broken don't fix it". If Evan saw something that needs fixing "under the hood", then he knows better than me (and others saying "keep it"). I believe he wouldn't revert it for the lulz. He probably saw something.
Anyway: Latest
[20:39]
[20:39]
[20:39]
[20:40]
[20:40] --> PayRoutes__ ([email protected]) has joined this channel.
[20:40]
[20:40]
[20:40]
[20:40]
[20:41]
[20:41]
[20:41]
[20:42]
[20:42]
[20:42]
[20:42]
[20:42]
[20:42]
[20:42]
[20:42]
[20:43]
[20:43]
[20:43]
[20:44] --> CryptoFa_ ([email protected]) has joined this channel.
[20:44] <-- PayRoutes_ ([email protected]) has left this server (Ping timeout: 272 seconds).
[20:44]
[20:45]
[20:45]
[20:45]
[20:45]
[20:45]
[20:45]
[20:46]
[20:46]
[20:46]
[20:46]
[20:46]
[20:46]
[20:46] *** ogi84 has been kicked from the channel by InternetApe (ogi84).
[20:46]
[20:46]
[20:46] <-- IAmNotDoritos (3ab3e3ac@gateway/web/freenode/ip.58.179.227.172) has left this channel.
[20:46]
[20:47]
[20:47]
[20:47]
[20:47]
[20:47]
[20:47]
[20:47]
[20:47]
[20:47]
[20:47]
[20:48]
[20:48]
[20:48]
[20:48]
June 20, 2014, 12:48:13 PM
This is the biggest plunge of price which I have ever seen in my life ... The problem is that I am watching how I am loosing thousand of dollars just in a minutes ...
June 20, 2014, 12:47:53 PM
Let me interject a common-sense course of action which will be ignored.
Yes, it's going outside confirmation window. But it IS fixing itself.
Reverting will only rob us of the log files needed to find the problem. Let it go for a while, find the problem, then fix it. If we revert we'll never find it...
Yes, it's going outside confirmation window. But it IS fixing itself.
Reverting will only rob us of the log files needed to find the problem. Let it go for a while, find the problem, then fix it. If we revert we'll never find it...
so u havent learn anything from it ? what a waste. Such talent xd
Jump to: