|
Darkcoin.io is going to be down for a bit while I move things around (ran out of space)
|
|
|
|
No!! Holy crap, you're right ! You dont get payed to the same address for multiple nodes. Thats impossible. Wtf !? That address got payed 5x today! Either I'm rading this wrong or I dont know. Will post on DCT. If all the masternodes are running from a start-many wallet, then yes, payments go to the first vin. Nope, it has nothing to do with start-many. It's simply the way the masternodes were funded. |
|
|
|
No!! Holy crap, you're right ! You dont get payed to the same address for multiple nodes. Thats impossible. Wtf !? That address got payed 5x today! Either I'm rading this wrong or I dont know. Will post on DCT. Sure you do.  It's an undocumented feature, if you fund more than 1 masternode in the same transaction, all payments will go to the first address and none to the rest. It makes it really easy to keep track of how much you're making. This person funded 10 at once: http://explorer.darkcoin.fr/block/00000000001226eaed26fc9a551f09da32fa944503f671782afb706e9225be6f |
|
|
|
nice to have drk for betting Crouton, given your strong views around mining and the benefits of P2pool, I'm surprised you haven't commented on this. I commented a page or three back here (I think it's a good idea, but not ideal) but I missed it on DCT back in April. My stance is pretty simple: I am not comfortable trusting my investment (not Earth-shattering, but more than what I call pocket money) to three doofuses on the intertubes. Imagine you had a $million or two. Would you really be happy putting millions of dollars into a system where your $millions could be rendered worthless overnight by somebody locating and compromising 3 servers or 3 server admins? Because that's the situation right now with PoW coins. You'd have to be actively stupid to trust such a system with any serious amount of investment. It's a joke, it's pure toytown, someone could destroy BTC or DRK for a few thousand bucks tops. Mmm...it's certainly worrying. I've read the many interactions you've had with pool admins (if it wasn't so serious they'd be pure entertainment!) I'm not knowledgeable enough on mining and pools to know what's truth/what's fiction. But the fact that you're so concerned about it and the fact that these large pools (and ASICs) seem to be such a major concern means I'm wondering whether this is an elephant in the room that no one wants to deal with. If this risk is as real as you're saying: It's a joke, it's pure toytown, someone could destroy BTC or DRK for a few thousand bucks tops
then we need more debate and I'd really like Evan to comment and discus it too. Evan, can you offer any assessment on the risk to Darkcoin in light of Crouton's concerns? question to evan, would masternodes be able to differentiate p2pool from ordinary pools? No, all miners look the same to the protocol. I like the idea of more users using P2Pool, but It's got to be the users that decide to do that, there's really no way to enforce it. Plus, I think the P2Pool software just needs improvement (complete rewrite probably). The masternode system can't really do donations like people are asking for either, there's not a good way to do that. If people want to donate, they'll have to manually calculate some of the profit and send it that way . |
|
|
|
 What is that? |
|
|
|
Pools as well? I see that it says all users but I was under the impression it was namely for masternodes. Just masternodes |
|
|
|
Can I stay 16.11 until it gets stable? Ah, thanks. Fixed in v15 I think it's better to wait till Evan announce next update 16.15 is not on github yetv0.10.16.15 is available! - Fixed dsee timestamp drift (thx UdjinM6) - 90%+ reduction in collateral charges, should happen every 20+ mixes. - Changed ping time to 5m (would have to have 14 bad propagation events to fall off the list) https://github.com/darkcoin/darkcoin* In the process of compiling it |
|
|
|
Masternode Operators : Please update to v0.10.16.12 - An issue with the Darksend queue gaming protection system has been fixed, stopping hanging Darksend sessions https://www.darkcoin.io/downloads/ |
|
|
|
2014-11-15 19:21:40 dssu - state: 3 entriesCount: 0 accepted: 0 error: Last darksend was too recent
DarkCoin version v0.10.16.6-g80c65cb-beta ()
what is a typical ETA until darksend mixing starts moving up from 0% ? Or doesn't darksend mixing work yet? Do I need to wait for a next update? The thing is flipping between 'idle' and 'Last darksend was too recent'. Anything else I need to do than press the 'start darksend mixing' button? v0.10.16.11 has an issue that's stopped darksend from working, I've fixed it in v12. I'll have the masternode operators update, then you should be able to mix. |
|
|
|
Guys, stop using website to check on the MN network.
What ONLY is reliable is issuing commands from the daemon direct on the masternode network. Elbzo's website is just a reference (and top job btw!!), and I sorely miss chaeplin.
It will only lead to added confusion. They're great when the network is stable, but in these update/buggy moments it only adds noise.
And the refresh rate of the site is once per hour... And wait, don't go for v16.9... It seams like a v16.10 will be pushed out in few minutes... v0.10.16.10 seems to fix all of the issues we're having, thanks to UdjinM6 for helping out! https://github.com/darkcoinproject/darkcoin-binaries(I'll be updating all of the websites here shortly, but feel free to grab the binaries from the repo now) |
|
|
|
I tried it right after your build was complete  , and while the 16.9 Masternodes see each other they get inactive for the 16.8/16.6 Masternodes. I reverted back to 16.8 but can't get them running anymore, seems they are banned for a while for spamming everyone else... Can you give me the 1000DRK address that went offline ( evan@darkcoin.io)? I should be able to see what happened now. Masternode messages won't get you banned, unless you're broadcasting bad signatures. |
|
|
|
|
Show Posts
