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

[mstrongbow]

Holy crap! 200+ pages after not visiting here for a few days.

Anything important I missed over the last 4 days?

[AlexGR]

Holy crap! 200+ pages after not visiting here for a few days.

Anything important I missed over the last 4 days?

Nope.

[Lebubar]

So Hashrate/dificulty are low, block reward came back to 6?
One of my MN just recieve 2 times 1.2 DRK...

I'm happy, can go in holiday relax and still wining drk  

EDIT:
I don't know if it was mention but I also mine with the cpu of all my MN and work fine, don't disturb the MN as I'd been payed..
I know it's not a lot but if you have lot of MN can help to pay the rent of the server.

[Ozziecoin]

EDIT:
I don't know if it was mention but I also mine with the cpu of all my MN and work fine, don't disturb the MN as I'd been payed..
I know it's not a lot but if you have lot of MN can help to pay the rent of the server.

You never know. Your MN might just get lucky and win a block.

[Ozziecoin]

First lucky node: http://chainz.cryptoid.info/drk/address.dws?XyRzfcdK94NmvYsRPQisNdjzpmuDstqooW.htm

Second lucky node: http://chainz.cryptoid.info/drk/address.dws?XwSPJo3v4253WqS7kRFm7Huo3gDojRWuev.htm

Third lucky node: http://chainz.cryptoid.info/drk/address.dws?XhPweVoEC9BLCWGJnCUonYoL7iC4eq5Hwy.htm

EDIT: These appear to be the luckiest nodes in the network.

[eltito]

Announcing a new X11 pool mining Darkcoin, additional coins will be added.

http://drk.pool1.goodluckpool.com

stratum+tcp://drk.pool1.goodluckpool.com
Prop payout, VarDiff
Only 0.5% fee
Support: goodluckpool@gmail.com

Please give us a try.

Thank you.

Added to the list.

https://darkcointalk.org/threads/pools-exchanges-etc.1456/

[eltito]

https://darkcointalk.org/threads/enhanced-darkcoin-wallet-ui.1705/

I'm excited about this. Hope it's functional and fancy. #iggy

Can we get some more cross posts going, please?

bump

Working on it now.

Also, so everyone knows, I'm working on getting the OP of this thread updated.  That was on my to-do list for today, but I ended up having to work (yay).

[thelonecrouton]

Also, so everyone knows, I'm working on getting the OP of this thread updated. 

Thank you eltito! 

We might appear to the untrained eye to be a pack of ungrateful moaning bastards, but we're not, really. Well, some of us aren't. I'm not, anyway. Sometimes.

[Lebubar]

Also, so everyone knows, I'm working on getting the OP of this thread updated.  

Thank you eltito!  

We might appear to the untrained eye to be a pack of ungrateful moaning bastards, but we're not, really. Well, some of us aren't. I'm not, anyway. Sometimes.

Hi Patner,
Did you saw : pool_unknown_126 didn't pay our MN  
More lucky next time

[flound1129]

Someone explain to me how this voting works, is it random or what?

i.e. what's to stop me from setting up my own masternode and voting for it in all the blocks Multipool finds, or selling my votes to someone?

[thelonecrouton]

Also, so everyone knows, I'm working on getting the OP of this thread updated. 

Thank you eltito! 

We might appear to the untrained eye to be a pack of ungrateful moaning bastards, but we're not, really. Well, some of us aren't. I'm not, anyway. Sometimes.

Hi Patner,
Did you saw : pool_unknown_126 don't pay our MN 
More lucky next time

Yes, just noticed. At least we can be sure it's working though.

I'm going to put my rented Amazon CPUs to work mining tomorrow as well.

[thunderdrum]

Alright cheers, I'm forwarding this to my engineers to see if we could make this work.

We are adapting.  The point is via lazy coding you are increasing the number of headaches in my life and I have enough already.

Dear fellow DRKheads, these guys do have a point, stop ragging on them so much.

Maybe someone with Evan's ear might mention these issues and see what might be done in future to improve the situation?

The whole ecosystem needs to be supported, not just our particular favourite parts of it, anything that can be done to help should be considered.

 

 

+1

I am a DRK supporter.I think the Pool Operator is also a part of the DRK Project. So it will be more helpful to DRK if we reduce the workload of pool operator by optimizing the wallet in future, if possible.

Glad to hear the email works.... 

This was an oversight on my part.  I'll work on getting the stratum update information distributed as soon as possible.

Many thanks, eltito~

[flound1129]

Alright cheers, I'm forwarding this to my engineers to see if we could make this work.

We are adapting.  The point is via lazy coding you are increasing the number of headaches in my life and I have enough already.

Dear fellow DRKheads, these guys do have a point, stop ragging on them so much.

Maybe someone with Evan's ear might mention these issues and see what might be done in future to improve the situation?

The whole ecosystem needs to be supported, not just our particular favourite parts of it, anything that can be done to help should be considered.

 

 

To expand on this, if you are looking for mass adoption, you want every part of the system to be accessible.

Pools do centralize, but fewer pools means more centralization.  So creating barriers or unnecessary complications for pools is a bad idea.

The ideal situation would be to have the coinbase payments handled within the wallet (and return to me an accurate coinbasevalue when I pull the blocktemplate, with the masternode payout already removed), and have the voting stuff be optional (looks like you have already done that).  It seems extremely clunky to me to have stratum-mining be responsible for generating masternode payments.

That said, I am intrigued by this voting system and would like to hear more about exactly how it works.  There is not much information publicly available about it (other than that it exists.)

[newb4now]

Holy crap! 200+ pages after not visiting here for a few days.

Anything important I missed over the last 4 days?

From Darkcointalk https://darkcointalk.org/threads/status-update-7-1-2014.1675/

So if Evan is building a new switch to be implemented in RC4 and RC4 is planned for end july, does that mean there will be no enforcement until end of July?

Yes.

Evan decided he wanted to scrap the RC3 enforcement mechanism in favor of something that did the same thing in a simpler manner.

The choices that left were:

Implement RC3 enforcement in its current form and risk breaking the network again

Write new code to black list blocks from non-paying pool, giving himself sole capability to do so (an option he was not comfortable with, as he felt it gave him too much power), or

Write new code to fix the problem permanently

Options 2 and 3 take a similar amount of time to implement. After he wrote the code for option 2, however, he would have had to start all over again writing the code for option 3. Since that makes no sense whatsoever and Evan is a pretty smart cookie, he just skipped on ahead to option 3."

[ddink7]

Trading volume is incredibly low right now. Buying one MN would move the price from .0108 to .0116 on Mintpal.

[chaeplin]

Someone explain to me how this voting works, is it random or what?

i.e. what's to stop me from setting up my own masternode and voting for it in all the blocks Multipool finds, or selling my votes to someone?

Question : https://darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-12#post-6973
Evan's answer : https://darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-13#post-7060

Thanks for the super detailed report. So what you posted actually looks fine. I'll try to explain what's happening.

Block 14217

Code:

Blockheight    Pubkey    Votes
14214    fgAKRZmRDp53yEPegeBGu3bKmH2pYjM4o    2
14215    nyua6yT2XjttboGdjLdNMWZqSmrtqHeUE    3
14216    QSp8gRBSez2Y6MQCgGSiMsoKxnsa9HVVk    2
14217    Z92SLSwb3z2D47g47Y1E9LczimJiVFtvv    1

If you mined this block, your client added the pubkey for 14217.
It's also allowed to increment each existing vote by one if it agrees with it. So the code goes something like this:

On block 14214 was the pubkey to be paid fgAKRZmRDp53yEPegeBGu3bKmH2pYjM4o?
    If yes increment votes from 1 to 2
    If no and votes=1, change pubkey to the correct one and don't vote (this only can happen get no voting has happening and it looks incorrect)

On block 14215 was the pubkey to be paid nyua6yT2XjttboGdjLdNMWZqSmrtqHeUE?
     If yes increment votes from 2 to 3
     If no, don't vote

On block 14216 was the pubkey to be paid QSp8gRBSez2Y6MQCgGSiMsoKxnsa9HVVk? If yes increment votes from 1 to 2
Added block 14217, pubkey Z92SLSwb3z2D47g47Y1E9LczimJiVFtvv, votes 1

Info on testing :
https://darkcointalk.org/forums/testing.53/


CreateNewBlock : https://github.com/darkcoinproject/darkcoin/blob/master/src/main.cpp#L5211-L5244

Check block : https://github.com/darkcoinproject/darkcoin/blob/master/src/main.cpp#L2675-L2775



Config : https://github.com/darkcoinproject/darkcoin/blob/master/src/main.h#L36-L46

Code:

#define MASTERNODE_PAYMENTS_MIN_VOTES 5
#define MASTERNODE_PAYMENTS_MAX 1
#define MASTERNODE_PAYMENTS_EXPIRATION 10
#define START_MASTERNODE_PAYMENTS_TESTNET 1403568776 //Tue, 24 Jun 2014 00:12:56 GMT
#define START_MASTERNODE_PAYMENTS 1403728576 //Wed, 25 Jun 2014 20:36:16 GMT

#define MASTERNODE_MIN_CONFIRMATIONS           6
#define MASTERNODE_MIN_MICROSECONDS            5*60*1000*1000
#define MASTERNODE_PING_SECONDS                30*60
#define MASTERNODE_EXPIRATION_MICROSECONDS     35*60*1000*1000
#define MASTERNODE_REMOVAL_MICROSECONDS        35.5*60*1000*1000

[HiddenDark]

I've mentioned a couple of times before that I'm working on a little (hopefully it will become big) DRK project. I think it is an important thing for DRK to have if there is to be widespread adoption.

So far I've funded everything myself which has eaten into my DRK holdings quite a bit (I own/owned a very small amount compared to most people here).

What I would like is one or more people who would like to buy a stake (it doesn'thave to be much) in what I'm building so I can add more features sooner. I think this has a good chance of being popular and making some money.

If your want to know more PM me for detalis.

[chaeplin]

First lucky node: http://chainz.cryptoid.info/drk/address.dws?XyRzfcdK94NmvYsRPQisNdjzpmuDstqooW.htm

Second lucky node: http://chainz.cryptoid.info/drk/address.dws?XwSPJo3v4253WqS7kRFm7Huo3gDojRWuev.htm

Third lucky node: http://chainz.cryptoid.info/drk/address.dws?XhPweVoEC9BLCWGJnCUonYoL7iC4eq5Hwy.htm

EDIT: These appear to be the luckiest nodes in the network.

With expected.

http://drk.poolhash.org/masternode.html?srch&nmstr=XyRzfcdK94NmvYsRPQisNdjzpmuDstqooW
http://drk.poolhash.org/masternode.html?srch&nmstr=XwSPJo3v4253WqS7kRFm7Huo3gDojRWuev
http://drk.poolhash.org/masternode.html?srch&nmstr=XhPweVoEC9BLCWGJnCUonYoL7iC4eq5Hwy

[flound1129]

Someone explain to me how this voting works, is it random or what?

i.e. what's to stop me from setting up my own masternode and voting for it in all the blocks Multipool finds, or selling my votes to someone?

Question : https://darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-12#post-6973
Evan's answer : https://darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-13#post-7060

Thanks for the super detailed report. So what you posted actually looks fine. I'll try to explain what's happening.

Block 14217

Code:

Blockheight    Pubkey    Votes
14214    fgAKRZmRDp53yEPegeBGu3bKmH2pYjM4o    2
14215    nyua6yT2XjttboGdjLdNMWZqSmrtqHeUE    3
14216    QSp8gRBSez2Y6MQCgGSiMsoKxnsa9HVVk    2
14217    Z92SLSwb3z2D47g47Y1E9LczimJiVFtvv    1

If you mined this block, your client added the pubkey for 14217.
It's also allowed to increment each existing vote by one if it agrees with it. So the code goes something like this:

On block 14214 was the pubkey to be paid fgAKRZmRDp53yEPegeBGu3bKmH2pYjM4o?
    If yes increment votes from 1 to 2
    If no and votes=1, change pubkey to the correct one and don't vote (this only can happen get no voting has happening and it looks incorrect)

On block 14215 was the pubkey to be paid nyua6yT2XjttboGdjLdNMWZqSmrtqHeUE?
     If yes increment votes from 2 to 3
     If no, don't vote

On block 14216 was the pubkey to be paid QSp8gRBSez2Y6MQCgGSiMsoKxnsa9HVVk? If yes increment votes from 1 to 2
Added block 14217, pubkey Z92SLSwb3z2D47g47Y1E9LczimJiVFtvv, votes 1

Thanks but this doesn't explain where the pubkey to add is coming from.

[chaeplin]

Someone explain to me how this voting works, is it random or what?

i.e. what's to stop me from setting up my own masternode and voting for it in all the blocks Multipool finds, or selling my votes to someone?

Question : https://darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-12#post-6973
Evan's answer : https://darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-13#post-7060

Thanks for the super detailed report. So what you posted actually looks fine. I'll try to explain what's happening.

Block 14217

Code:

Blockheight    Pubkey    Votes
14214    fgAKRZmRDp53yEPegeBGu3bKmH2pYjM4o    2
14215    nyua6yT2XjttboGdjLdNMWZqSmrtqHeUE    3
14216    QSp8gRBSez2Y6MQCgGSiMsoKxnsa9HVVk    2
14217    Z92SLSwb3z2D47g47Y1E9LczimJiVFtvv    1

If you mined this block, your client added the pubkey for 14217.
It's also allowed to increment each existing vote by one if it agrees with it. So the code goes something like this:

On block 14214 was the pubkey to be paid fgAKRZmRDp53yEPegeBGu3bKmH2pYjM4o?
    If yes increment votes from 1 to 2
    If no and votes=1, change pubkey to the correct one and don't vote (this only can happen get no voting has happening and it looks incorrect)

On block 14215 was the pubkey to be paid nyua6yT2XjttboGdjLdNMWZqSmrtqHeUE?
     If yes increment votes from 2 to 3
     If no, don't vote

On block 14216 was the pubkey to be paid QSp8gRBSez2Y6MQCgGSiMsoKxnsa9HVVk? If yes increment votes from 1 to 2
Added block 14217, pubkey Z92SLSwb3z2D47g47Y1E9LczimJiVFtvv, votes 1

Thanks but this doesn't explain where the pubkey to add is coming from.

pubkey of payee ?

It's on getblocktemplate

https://github.com/darkcoinproject/darkcoin/blob/master/src/rpcmining.cpp#L572-L581

Code:

        ExtractDestination(pblock->payee, address1);

https://darkcointalk.org/threads/help-test-rc2-forking-issues.1009/page-13#post-7066

Hi Evan,
thanks for the explanation, i think i got it. The problem was not the algorithm,
but my idea how the voting actually works in P2P networks - i guess i should have read the fucking manual :grin:

So this is my understanding now:

- A certain block is found by a miner
- The miner is looking up the previous block from the blockchain to get the current vote list
- Its appending the pubkey of a MN winner - the actual vote
- Additionally the miner is checking all previous vote pubkeys and if it agrees with it adding another vote - lets call it 'confirm vote'
- If the miner does not agree it replaces the pubkey with a new one. Its the job of the next miner to agree or disagree with that

So what basically confused me was the term 'vote'. My idea was that each miner is only giving ONE vote,
but not confirming the others. That also explains why my math on the expected payout was wrong: I expected that only 1/6th of blocks get paid.
But with the vote confirmations it makes sense again: That way each block will be paid out in the future.

And the scheme we are seeing on the explorer now is expression that the system is working as designed