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

CripLib

full member

Activity: 175

Merit: 100

Crypto Liberty

Update on the DyslexicZombei's Darkcoin MasterNode Services problem, as it is of interest to the whole Darkcoin Community:

Thank you for your support.

Lib

Quote from: CripLib on July 15, 2014, 09:28:25 AM

UPDATE:

I have just received a reply from DZ's partner as follows:

Quote from: thomas_s on July 15, 2014, 02:20:41 PM

Hi CripLib,

I was never fully brought on board for the darkcoin masternodes and don't actively participate in it / have never, while I was planning on it I was never contacted with what I needed to do.

--Thomas

My reply:

Quote from: CripLib on July 15, 2014, 02:26:50 PM

Quote from: thomas_s on July 15, 2014, 02:20:41 PM

Hi CripLib,

I was never fully brought on board for the darkcoin masternodes and don't actively participate in it / have never, while I was planning on it I was never contacted with what I needed to do.

--Thomas

Thank you, Thomas, for your reply. I am so sorry that it took so long for you to clarify it. I'll let the community know it.

Can you please help us get in touch with DZ, or at least understand what is going on with him. as he has been your partner for such a long time, as it seems, it is natural that you are possible to help as here.

Thnak you.

What we can do now:

- We must be clear as who here wants to ACT for a solution, and we must form a group;
- This group must contact the forum admins and request them disclose DZ's IPs information in order that he is tracked down;
- With the knowledge of DZ's real location, start the criminal procedures needed according to his Jurisdiction;
- If he is in the United States, for example, the possible scam victims should take this whole thread to be printed certified as a document in any local (English speaking) Notarial Service or in any United States Consulate, in order to keep the evidences protected.

Let's exchange PMs. let's act.

JGCMiner

hero member

Activity: 611

Merit: 500

Quote from: GhostPlayer on July 15, 2014, 09:09:59 AM

Yes, obviously, when RC4 rolls out, wallets need to be updated to accomodate new changes. But that is different from network consensus.

Darkcoin is not yet fully released !! So again, all is looking gold.

I know I said I was going to drop it, but when I read this quote from Evan I find it very hard to believe that any current clients will on the correct chain when RC4 is enforced.

Quote from: Eduffield @ darkcointalk.org

The Masternode voting system launched with RC3 has been removed from the codebase and replaced with an entirely new consensus protocol. Development is completed for the new consensus protocol and it has been working very well in all of our tests.

https://darkcointalk.org/threads/development-updates-july-7th.1735/

toknormal

legendary

Activity: 3066

Merit: 1188

All those waiting to "buy back in" when the next development is announced, your numbers are mounting. You know what that means - liquidity crisis.

Even with the current price sink there's only about 10,000 DRK on the orderbook. When all these "I'll buy back when the price hits x" or "...when RC4 is announced" folk decide to go long they're going to be fighting over vapour because there's barely any volume in the current dip and so the volume in the asks will dry up like a puddle of meths on a car bonnet in death valley.

The trades right now are all in single or double figures. 1, 2, 10 and 20 DRK shots. The market is illiquid. I'm sorry, but you can't buy in at 8 or 7 or 6. Look what happened last night as soon as any significant liquidity appeared (around 1.5k) - munched in a few minutes.

In short, it's not price you people should be worrying about, it's liquidity. And right now there isn't any cos nobody's selling.

GhostPlayer

legendary

Activity: 1092

Merit: 1000

Yes, obviously, when RC4 rolls out, wallets need to be updated to accomodate new changes. But that is different from network consensus.

Darkcoin is not yet fully released !! So again, all is looking gold.

qwizzie

legendary

Activity: 2548

Merit: 1245

i'm starting to feel an urge to just set time two weeks ahead and be done with it all .. all this tension is getting to me.
eh, any new fitness girls dancing the darkcoin dance ? or something new.. new is good too

luigi1111

legendary

Activity: 1105

Merit: 1000

Quote from: JGCMiner on July 15, 2014, 09:00:05 AM

Quote from: GhostPlayer on July 15, 2014, 08:54:33 AM

Quote from: JGCMiner on July 15, 2014, 08:48:12 AM

Quote from: GhostPlayer on July 15, 2014, 08:39:26 AM

Quote from: JGCMiner on July 15, 2014, 08:34:55 AM

I thought there where incompatible differences between RC3 and RC4. In eltito's quote he says that the enforcement mechanism is going to change. Given that, I don't see how anybody running the RC3 wallet will have their blocks confirmed after RC4 enforcement. What am I missing ?

Two fold. One is pool stratum code, the other is wallet. If stratum is updated, its good to go.
You can safely run with wallet as old as 11.4 right now, no "real" need to have 11.6

RC4 will basically change 6 random votes to deterministic top 10, making the dreaded variance much more in line with regular payouts.

Nothing but good stuff.

Sorry for continuing this discussion, but I still don't see how this works. Versions 11.4 - 11.6 are all RC3 based so I agree that they are all OK assuming stratum is updated. As for RC4, I thought 2 things where changing:

1. Responsibility for selecting winning masternode is moving from the miners to the masternodes themselves
2. Enforcement is being re-written to be "safer"(eltito's phrasing)

If only #1 was happening then I would agree with you, but if #2 is also happening I don't see how everyone will avoid updating. So is #2 NOT happening? And if so, then why is enforcement not already on if it will remained unchanged in RC4 (and since we are already at 99% compliance).

No need to be sorry! We could use a sensible debate instead of troll patrol Wink

Cumulative coding.

#2 "only" means a different algo to determine MN payout rules. Apart other "secret" upgrades.

So you are saying #1 and #2 are really the same thing.... still seems off to me, but there is no point going back and forth as neither of us is privy to RC4 code.

It seems fair to expect that Masternodes will need to be updated for sure, whether "regular" nodes will be affected is up for debate. I don't think anyone "out here" can say with any certainty what will be required. (my personal opinion is in line with JGCMiner)

Edit: if we're adding that improved Darksend(+) will be included in RC4, then most certainly all clients will need to be updated to take advantage of that.

GhostPlayer

legendary

Activity: 1092

Merit: 1000

Quote from: JGCMiner on July 15, 2014, 09:00:05 AM

Quote from: GhostPlayer on July 15, 2014, 08:54:33 AM

Quote from: JGCMiner on July 15, 2014, 08:48:12 AM

Quote from: GhostPlayer on July 15, 2014, 08:39:26 AM

Quote from: JGCMiner on July 15, 2014, 08:34:55 AM

I thought there where incompatible differences between RC3 and RC4. In eltito's quote he says that the enforcement mechanism is going to change. Given that, I don't see how anybody running the RC3 wallet will have their blocks confirmed after RC4 enforcement. What am I missing ?

Two fold. One is pool stratum code, the other is wallet. If stratum is updated, its good to go.
You can safely run with wallet as old as 11.4 right now, no "real" need to have 11.6

RC4 will basically change 6 random votes to deterministic top 10, making the dreaded variance much more in line with regular payouts.

Nothing but good stuff.

Sorry for continuing this discussion, but I still don't see how this works. Versions 11.4 - 11.6 are all RC3 based so I agree that they are all OK assuming stratum is updated. As for RC4, I thought 2 things where changing:

1. Responsibility for selecting winning masternode is moving from the miners to the masternodes themselves
2. Enforcement is being re-written to be "safer"(eltito's phrasing)

If only #1 was happening then I would agree with you, but if #2 is also happening I don't see how everyone will avoid updating. So is #2 NOT happening? And if so, then why is enforcement not already on if it will remained unchanged in RC4 (and since we are already at 99% compliance).

No need to be sorry! We could use a sensible debate instead of troll patrol Wink

Cumulative coding.

#2 "only" means a different algo to determine MN payout rules. Apart other upgrades.

I meant #1 as the change to the MN payout rules meaning that you are saying #1 and #2 are really the same thing.... still seems bit off to me, but there is no point going back and forth as neither of us is privy to RC4 code.

That is the beauty of "spork" technology. A failsafe system that ended up not being needed after all, but quite relieved exists.

In essence, unless the planet explodes, we're good to go.

JGCMiner

hero member

Activity: 611

Merit: 500

Quote from: GhostPlayer on July 15, 2014, 08:54:33 AM

Quote from: JGCMiner on July 15, 2014, 08:48:12 AM

Quote from: GhostPlayer on July 15, 2014, 08:39:26 AM

Quote from: JGCMiner on July 15, 2014, 08:34:55 AM

I thought there where incompatible differences between RC3 and RC4. In eltito's quote he says that the enforcement mechanism is going to change. Given that, I don't see how anybody running the RC3 wallet will have their blocks confirmed after RC4 enforcement. What am I missing ?

Two fold. One is pool stratum code, the other is wallet. If stratum is updated, its good to go.
You can safely run with wallet as old as 11.4 right now, no "real" need to have 11.6

RC4 will basically change 6 random votes to deterministic top 10, making the dreaded variance much more in line with regular payouts.

Nothing but good stuff.

Sorry for continuing this discussion, but I still don't see how this works. Versions 11.4 - 11.6 are all RC3 based so I agree that they are all OK assuming stratum is updated. As for RC4, I thought 2 things where changing:

1. Responsibility for selecting winning masternode is moving from the miners to the masternodes themselves
2. Enforcement is being re-written to be "safer"(eltito's phrasing)

If only #1 was happening then I would agree with you, but if #2 is also happening I don't see how everyone will avoid updating. So is #2 NOT happening? And if so, then why is enforcement not already on if it will remained unchanged in RC4 (and since we are already at 99% compliance).

No need to be sorry! We could use a sensible debate instead of troll patrol Wink

Cumulative coding.

#2 "only" means a different algo to determine MN payout rules. Apart other "secret" upgrades.

I meant #1 as the change to the MN payout rules meaning that you are saying #1 and #2 are really the same thing.... still seems bit off to me, but there is no point going back and forth as neither of us is privy to RC4 code. Wink

luigi1111

legendary

Activity: 1105

Merit: 1000

Quote from: huadaonan on July 15, 2014, 08:58:02 AM

darkcoin team should do sth

Disagree.

Edit: to expand, they should continue "developing", not babysitting the price.

huadaonan

member

Activity: 76

Merit: 10

darkcoin team should do sth

huadaonan

member

Activity: 76

Merit: 10

what the fuck price get down so much low than before .what would u guys thinking

GhostPlayer

legendary

Activity: 1092

Merit: 1000

Quote from: JGCMiner on July 15, 2014, 08:48:12 AM

Quote from: GhostPlayer on July 15, 2014, 08:39:26 AM

Quote from: JGCMiner on July 15, 2014, 08:34:55 AM

I thought there where incompatible differences between RC3 and RC4. In eltito's quote he says that the enforcement mechanism is going to change. Given that, I don't see how anybody running the RC3 wallet will have their blocks confirmed after RC4 enforcement. What am I missing ?

Two fold. One is pool stratum code, the other is wallet. If stratum is updated, its good to go.
You can safely run with wallet as old as 11.4 right now, no "real" need to have 11.6

RC4 will basically change 6 random votes to deterministic top 10, making the dreaded variance much more in line with regular payouts.

Nothing but good stuff.

Sorry for continuing this discussion, but I still don't see how this works. Versions 11.4 - 11.6 are all RC3 based so I agree that they are all OK assuming stratum is updated. As for RC4, I thought 2 things where changing:

1. Responsibility for selecting winning masternode is moving from the miners to the masternodes themselves
2. Enforcement is being re-written to be "safer"(eltito's phrasing)

If only #1 was happening then I would agree with you, but if #2 is also happening I don't see how everyone will avoid updating. So is #2 NOT happening? And if so, then why is enforcement not already on if it will remained unchanged in RC4 (and since we are already at 99% compliance).

No need to be sorry! We could use a sensible debate instead of troll patrol Wink

Cumulative coding.

#2 "only" means a different algo to determine MN payout rules. Apart other upgrades.

JGCMiner

hero member

Activity: 611

Merit: 500

Quote from: GhostPlayer on July 15, 2014, 08:39:26 AM

Quote from: JGCMiner on July 15, 2014, 08:34:55 AM

I thought there where incompatible differences between RC3 and RC4. In eltito's quote he says that the enforcement mechanism is going to change. Given that, I don't see how anybody running the RC3 wallet will have their blocks confirmed after RC4 enforcement. What am I missing ?

Two fold. One is pool stratum code, the other is wallet. If stratum is updated, its good to go.
You can safely run with wallet as old as 11.4 right now, no "real" need to have 11.6

RC4 will basically change 6 random votes to deterministic top 10, making the dreaded variance much more in line with regular payouts.

Nothing but good stuff.

Sorry for continuing this discussion, but I still don't see how this works. Versions 11.4 - 11.6 are all RC3 based so I agree that they are all OK assuming stratum is updated. As for RC4, I thought 2 things where changing:

1. Responsibility for selecting winning masternode is moving from the miners to the masternodes themselves
2. Enforcement is being re-written to be "safer"(eltito's phrasing)

If only #1 was happening then I would agree with you, but if #2 is also happening I don't see how everyone will avoid updating. So is #2 NOT happening? And if so, then why is enforcement not already on if it will remained unchanged in RC4 (and since we are already at 99% compliance).

GhostPlayer

legendary

Activity: 1092

Merit: 1000

Quote from: JGCMiner on July 15, 2014, 08:34:55 AM

I thought there where incompatible differences between RC3 and RC4. In eltito's quote he says that the enforcement mechanism is going to change. Given that, I don't see how anybody running the RC3 wallet will have their blocks confirmed after RC4 enforcement. What am I missing ?

Two fold. One is pool stratum code, the other is wallet. If stratum is updated, its good to go.
You can safely run with wallet as old as 11.4 right now, no "real" need to have 11.6

RC4 will basically change 6 random votes to deterministic top 10, making the dreaded variance much more in line with regular payouts.

Nothing but good stuff.

JGCMiner

hero member

Activity: 611

Merit: 500

Quote from: GhostPlayer on July 15, 2014, 08:27:07 AM

Quote from: JGCMiner on July 15, 2014, 08:24:43 AM

Quote from: GhostPlayer on July 15, 2014, 08:16:55 AM

Quote from: JGCMiner on July 15, 2014, 08:14:14 AM

Quote from: chaeplin on July 15, 2014, 08:05:57 AM

Quote from: JGCMiner on July 15, 2014, 08:04:41 AM

Quote from: chaeplin on July 15, 2014, 07:58:53 AM

Quote from: JGCMiner on July 15, 2014, 07:23:15 AM

Quote from: maese123 on July 15, 2014, 07:20:02 AM

Only if rc4 works, i hope that. but rc2 fail ad rc3 fail two times. RC4 please make me happy Grin

RC3 was reverted once not twice -- it is now working with 99% pool compliance. RC4 is also a "spork" -- i.e. even if enforcement causes problems it can be turned off seamlessly. I really don't think there is much to worry about in terms of RC4 "not working".

I don't think RC4 will use enforcement(spork).
RC4 would be timed-fork(enforcement on), and spork would be used for failsafe.

Is that a guess or has that been confirmed somewhere? Could have sworn I saw eltito say the opposite.

Just a guess. Shocked

LOL

Well El presidente's guesses are better than most. I just wonder if there is enough time to test and give enough lead time for a hardfork by the end of July. A spork could be just 72 hrs or so of lead time, but a hardfork is at least a week. And as far as I know testnet validation is yet to get underway...

A hardfork is at least a week... ? What do you mean by that?

A fork is instant, and network consensus should be extremely quick given block time of (2.5 mins * 6 confirms) / block solving variance

I don't think pools will be at all happy with a "hit-n-run" hardfork. It needs to be announced well in advance to give people the time to update their daemons less we have half the pools/exchanges on the wrong fork and mighty angry.

(Btw, I am not talking about a spork where the switch is flipped after most have upgraded -- rather about a traditional hardfork, which is the same as releasing RC4 with enforcement enabled.)

It has been announced for quite a long time! And with spork already set right now, that is a non issue. Since 99% of pool have upgraded, 99% of pools will feel no difference when the fork is set.

We are GOLD to fork !

I thought there were incompatible differences between RC3 and RC4. In eltito's quote he says that the enforcement mechanism is going to change. Given that, I don't see how anybody running the RC3 wallet will have their blocks confirmed after RC4 enforcement. What am I missing ?

CHAOSiTEC

legendary

Activity: 1358

Merit: 1002

Quote from: Terzo on July 15, 2014, 08:27:19 AM

what is happening 0.0092? Huh

there is 2 sides to this reasoning:

1. moneyflow is restricted, alot of ppl are holding on to their coins

2. market is awaiting RC4 before deciding to buy up coins

the above gives the following:

multipools are dumping mined coins, and since buying power is not being renewed due to market awaiting RC4, the price will automatically go down, second part, there is not a large amount of coins on the sell side either, since ppl are holding... so it will trail downward for a while, until market can reevaluate the release of RC4 and its impact.

CHAOSiTEC

GhostPlayer

legendary

Activity: 1092

Merit: 1000

Quote from: Terzo on July 15, 2014, 08:27:19 AM

what is happening 0.0092? Huh

Nothing... except panic! Grin

Terzo

full member

Activity: 238

Merit: 100

what is happening 0.0092? Huh

GhostPlayer

legendary

Activity: 1092

Merit: 1000

Quote from: JGCMiner on July 15, 2014, 08:24:43 AM

Quote from: GhostPlayer on July 15, 2014, 08:16:55 AM

Quote from: JGCMiner on July 15, 2014, 08:14:14 AM

Quote from: chaeplin on July 15, 2014, 08:05:57 AM

Quote from: JGCMiner on July 15, 2014, 08:04:41 AM

Quote from: chaeplin on July 15, 2014, 07:58:53 AM

Quote from: JGCMiner on July 15, 2014, 07:23:15 AM

Quote from: maese123 on July 15, 2014, 07:20:02 AM

Only if rc4 works, i hope that. but rc2 fail ad rc3 fail two times. RC4 please make me happy Grin

RC3 was reverted once not twice -- it is now working with 99% pool compliance. RC4 is also a "spork" -- i.e. even if enforcement causes problems it can be turned off seamlessly. I really don't think there is much to worry about in terms of RC4 "not working".

I don't think RC4 will use enforcement(spork).
RC4 would be timed-fork(enforcement on), and spork would be used for failsafe.

Is that a guess or has that been confirmed somewhere? Could have sworn I saw eltito say the opposite.

Just a guess. Shocked

LOL

Well El presidente's guesses are better than most. I just wonder if there is enough time to test and give enough lead time for a hardfork by the end of July. A spork could be just 72 hrs or so of lead time, but a hardfork is at least a week. And as far as I know testnet validation is yet to get underway...

A hardfork is at least a week... ? What do you mean by that?

A fork is instant, and network consensus should be extremely quick given block time of (2.5 mins * 6 confirms) / block solving variance

I don't think pools will be at all happy with a "hit-n-run" hardfork. It needs to be announced well in advance to give people the time to update their daemons less we have half the pools/exchanges on the wrong fork and mighty angry.

(Btw, I am not talking about a spork where the switch is flipped after most have upgraded -- rather about a traditional hardfork, which is the same as releasing RC4 with enforcement enabled.)

It has been announced for quite a long time! And with spork already set right now, that is a non issue. Since 99% of pool have upgraded, 99% of pools will feel no difference when the fork is set.

We are GOLD to fork !

JGCMiner

hero member

Activity: 611

Merit: 500

Quote from: GhostPlayer on July 15, 2014, 08:16:55 AM

Quote from: JGCMiner on July 15, 2014, 08:14:14 AM

Quote from: chaeplin on July 15, 2014, 08:05:57 AM

Quote from: JGCMiner on July 15, 2014, 08:04:41 AM

Quote from: chaeplin on July 15, 2014, 07:58:53 AM

Quote from: JGCMiner on July 15, 2014, 07:23:15 AM

Quote from: maese123 on July 15, 2014, 07:20:02 AM

Only if rc4 works, i hope that. but rc2 fail ad rc3 fail two times. RC4 please make me happy Grin

RC3 was reverted once not twice -- it is now working with 99% pool compliance. RC4 is also a "spork" -- i.e. even if enforcement causes problems it can be turned off seamlessly. I really don't think there is much to worry about in terms of RC4 "not working".

I don't think RC4 will use enforcement(spork).
RC4 would be timed-fork(enforcement on), and spork would be used for failsafe.

Is that a guess or has that been confirmed somewhere? Could have sworn I saw eltito say the opposite.

Just a guess. Shocked

LOL

Well El presidente's guesses are better than most. I just wonder if there is enough time to test and give enough lead time for a hardfork by the end of July. A spork could be just 72 hrs or so of lead time, but a hardfork is at least a week. And as far as I know testnet validation is yet to get underway...

A hardfork is at least a week... ? What do you mean by that?

A fork is instant, and network consensus should be extremely quick given block time of (2.5 mins * 6 confirms) / block solving variance

I don't think pools will be at all happy with a "hit-n-run" hardfork. It needs to be announced well in advance to give people the time to update their daemons less we have half the pools/exchanges on the wrong fork and mighty angry.

(Btw, I am not talking about a spork where the switch is flipped after most have upgraded -- rather about a traditional hardfork, which is the same as releasing RC4 with enforcement enabled.)

Topic: [ANN][DASH] Dash (dash.org) | First Self-Funding Self-Governing Crypto Currency - page 4752. (Read 9723814 times)