The pool's mining software uses getblocktemplate and asks the client who to pay, how much, what transactions are in the block etc. Then, when the block is solved, it compiles the block in a binary form then submits it to the client. So unless the pool's software understands what "payee" means in getblocktemplate, it's not going to pay a masternode. |
|
|
|
ME: complaining about Blackpool not paying to MN Blackpool: We aren't aware of the situation. More information would be appreciated. ME: Please check your twitter about the darknode payment issue. It says "We have updated our wallet so should be all good." According to my data, drk is being mined by your pool and masternode payments are disabled. Any comments? Jarek Blackpool: Ticket: http://blackcoinpool.freshdesk.com/helpdesk/tickets/189By "masternode payments are disabled" are you implying that this is a feature of your wallet? Or is it something we need to manually implement ourselves? If you have any links to instructions, technical details, or announcements they would help us resolve the issue sooner. Would someone post what exactly they have to do so I won't have to search for it? Thanks! Tell blackpool they need to update their pool software: For Stratum Pools: https://github.com/darkcoinproject/darkcoin-stratumThey'll have to update before the next fork, otherwise all their blocks will get rejected (even if they have the new wallet). |
|
|
|
Did Evan said he was reworking the voting system?
Who the hell knows. There is too much confusion and uncertainty about development status. Apparently if you have time to hang out on IRC all day you are privy to material information that comes from Evan in snippets. Otherwise you are stuck guessing and interpreting out of context quotes and other third or fourth hand information. Markets don't like uncertainty. Evan should post a few sentences about current status and current plans here or on twitter. Dammit why don't we have an useful official source of develoment info for this community The official sources are only useful if you choose to use them  . https://twitter.com/DarkcoinCrypto/status/482224555704848385https://twitter.com/DarkcoinCrypto/status/482011593891262464Edit: Is there a legitimate lack of understanding as to where to obtain official information? If so, I apologize as I didn't think there was, and I will make a concerted effort this week to make it more clear for everyone.I've been busy working for the last few days and obviously haven't been spending much time on the forums and IRC. I just read through the last few pages and it's obvious there is a serious lack of information and a good deal of misinformation. So from this point forward I'm going to be filling in eltito (our community leader) on the development status as it happens and he's going to be the one posting official replies and filling in the community. I'm hoping this helps form a clearer picture of what's going on and the status of everything. |
|
|
|
|
DRK and XC Communities,
The toxic back and forth between our two communities has reached a level with which neither of us are comfortable or impressed. The competitive space for our coins lies in the results, and the results will speak for themselves as they are brought online. Whatever mistakes or provocations were undertaken by either side are in the past, and we would like them to remain there. We are all interested in one thing: the advancement of anonymous cryptocurrency. Let go of the tribalism and start thinking of how you can positively contribute to that end.
Evan and Dan
|
|
|
|
DrkPool.com Shutting Down
We have reason to believe someone unauthorized has gained access to the server. As soon as I found out I took all of the money off the server and database backups so I could pay our users their balances. The funds are being stored at a secure location and I have access to final totals for all users on the server. Sorry for any inconvenience but I figured this is the safest way to deal with an issue like this.
-Evan
http://www.drkpool.com How would people go about getting at the coins that they still have on the pool? Edit: Also can people still see their current balance on the site? Personally, I don't have any coins there but these things always must be handled carefully. The money is safe and I'll be sending out a mass email to all users with further instructions later. |
|
|
|
DrkPool.com Shutting Down
We have reason to believe someone unauthorized has gained access to the server. As soon as I found out I took all of the money off the server and database backups so I could pay our users their balances. The funds are being stored at a secure location and I have access to final totals for all users on the server. Sorry for any inconvenience but I figured this is the safest way to deal with an issue like this.
-Evan
http://www.drkpool.com
|
|
|
|
Just for laughs, can somebody here who is good at statistics give the percentage of MNs that should be paid within 24, 48, and 72 hours at a normal distribution? I'm a history major, so I'm not much help with that =)
Well it will vary wildly with the # of current nodes, but presently we have 379. Using that and assuming we have 100% payouts, we get: (378/379)^576 = ~78% chance of getting paid in 24 hours (378/379)^1152 = ~95% chance of getting paid in 48 hours (378/379)^1728 = ~99% chance of getting paid in 72 hours Exactly what I was looking for!! Thanks!! So using that formula and assuming 2/3 of pools are paying (approx 380 blocks per day): 63%, 87%, and 95% respectively. Thanks for teaching me the formula! P.S. Making a few more assumptions: Day 1: 230 payments (average of 40% participation); MNs approx. 270 Day 2: 316 payments (average of 55% participation); MNs approx. 360 Day 3: 384 payments (average of 67% participation); MNs approx. 450? Day 1 odds of receiving a payment are 57%, Day 2 is 78%, Day 3 is 87%. So it's not inconceivable that some people haven't received payments. Guess I will be patient =) Yup, you got it (not that I checked your math). Basically you convert to the chance of the event NOT happening, then compute to the power of number of iterations. Hmm, I just wrote a script to calculate this and I'm getting different numbers: https://darkcointalk.org/threads/masternode-payment-variance.1636/The calculation we/they did was the chance that one specific masternode gets payed within a given time. if I read your script right you just simulated a run and printed the distribution you got. That's not comparable. edit: ah wait it possible is if you add together the ones that got payed. Ah, I got my script to generate percentages. Pretty close to yours. 72.25 % masternodes were paid in 1 days 92 % masternodes were paid in 2 days 99 % masternodes were paid in 3 days 99 % masternodes were paid in 4 days 99 % masternodes were paid in 5 days 100 % masternodes were paid in 6 days |
|
|
|
Just for laughs, can somebody here who is good at statistics give the percentage of MNs that should be paid within 24, 48, and 72 hours at a normal distribution? I'm a history major, so I'm not much help with that =)
Well it will vary wildly with the # of current nodes, but presently we have 379. Using that and assuming we have 100% payouts, we get: (378/379)^576 = ~78% chance of getting paid in 24 hours (378/379)^1152 = ~95% chance of getting paid in 48 hours (378/379)^1728 = ~99% chance of getting paid in 72 hours Exactly what I was looking for!! Thanks!! So using that formula and assuming 2/3 of pools are paying (approx 380 blocks per day): 63%, 87%, and 95% respectively. Thanks for teaching me the formula! P.S. Making a few more assumptions: Day 1: 230 payments (average of 40% participation); MNs approx. 270 Day 2: 316 payments (average of 55% participation); MNs approx. 360 Day 3: 384 payments (average of 67% participation); MNs approx. 450? Day 1 odds of receiving a payment are 57%, Day 2 is 78%, Day 3 is 87%. So it's not inconceivable that some people haven't received payments. Guess I will be patient =) Yup, you got it (not that I checked your math). Basically you convert to the chance of the event NOT happening, then compute to the power of number of iterations. Hmm, I just wrote a script to calculate this and I'm getting different numbers: https://darkcointalk.org/threads/masternode-payment-variance.1636/ |
|
|
|
*** VERSIONS 9.11.5 AND 10.11.5 ARE AVAILABLE ***
The network has been experiencing some odd banning behavior caused by bad masternode signatures. I removed the code that bans the other party when this happens will I'll find the underlying cause and fix it in RC4. Please update if you're experiencing any problems or run a masternode.
Thanks,
The Darkcoin Team
----------------------------------
Download at:
https://www.darkcoin.io/getstarted.html
|
|
|
|
hi - my pool ( https://www2.coinmine.pl/drk/) has updated wallet and paid few blocks for masternodes but last 3 blocks were not paid - anyone knows why is that? Jump on #darkcoin-test and I'll help you |
|
|
|
So masternodes are actually going to get paid today? I'm in for the ride to 1.9-2.1
They're already being paid. It's just going to take a while to get up to 20%, because until enforcement is switched on you're only getting paid for blocks founds by miners who have updated. It's actually the pools who will matter. If the largest 10 pools update the masternodes will have nearly 20% payments. |
|
|
|
is there anyone here who is versed on some of the technical aspects of this crypto?
Several members have knowledge of technical aspects but obviously Evan can explain the finer details. If you had any questions, feel free to post them so all of us can participate and educate each other I miss the days when AnonyMint and others were hashing out some of the early framework/architecture through open dialogues. Ok then ill just go ahead and ask about it here. What prevents the 2 payment nodes from colluding to fraudulently cash collateral transactions? With the advent of the masternode payments system there was no need to pay the masternodes from the collateral transactions, so they're made out to the bounty fund. If a masternode wants to be evil and cash them, the best they can do is support the coin by funding the bounty fund (plus we control that wallet, so it's reversible). |
|
|
|
Basically it means you can have a node online with the 1000DRK just for 30 seconds, then you activate a secondary "hot" node with no money in it. After that you can literally power down the first node because in the new implementation the hot and cold node share a signing key. |
|
|
|
|
Show Posts
