Search results

I see the same. from .7 to 1.6% idle -- and 109k to 132k ram usage. here's one processing: (512M box) PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 12838 ubuntu 20 0 803084 112012 8912 S 6.4 22.3 26:55.43 darkcoind

The thought has occurred to me too, but the quicker we can accomplish migration the quicker we can iterate to the next bugfix or enhancement release. We need probably several dozen more releases before we work out most of the kinks. (specifically the ones that we don't know about yet.) This...

I think clear communication is what we need. Pools should be encouraged to register with the mailing list and very clear 72, 48, 24 hour notices posted as enforcement approaches. An automated system would be ideal. I think one week's notice should be ample for most cases, but I don't run a...

I could hug you! Thanks!

They go to the masternodes that haven't updated. I've gotten 3 out of the last 20 payments I was selected for. grr. coinminepl coinotroncom ghashio trademybitcom wafflepool are the current culprits.

once it reaches the payment age it would eventually get selected for it's first payment from the sorted-by-address (leveraging dispersion) list. wouldn't one of the blocks just get orphaned due to it not being 'best' -- in bitcoin thats the number of leading zeros -- nothing similar in x11?

Here's my stab at a possible solution. Please feel free to rip it apart. 1) from blockchain: during daemon startup, walk last 4000 blocks, collect paid masternode addresses. 2) from network: collate all masternode addresses from peers into array 'mnlist' 3) prune masternode addresses having...

There is more than one way to accomplish this is all we're saying.

I also would feel more comfortable with a system that relies on quorum opposed to selected address signatures.

I got a collateral payment of 0.1 drk txn f0e29031a9ba87b4702be28bcaaa32bd951b1ee51bdcd7580c3a6b9b640aa11f -- sent evan darkcoin.io debug.log.

you give up trying to configure ec2-54-211-25-246.compute-1.amazonaws.com ? I've got 2Mh trying to get work from that pool endpoint.

no work available error. tried http://ec2-54-211-25-246.compute-1.amazonaws.com and stratum+tcp://ec2-54-211-25-246.compute-1.amazonaws.com:3333 site help shows: "stratum+tcp://localhost:3333"

"Unable to create account: Coin address is not valid" -- doesn't accept testnet address.

Why is everybody so opposed to making sure each node gets its turn algorithmically? Random selection from top of lists sorted by time-since-paid and time-visible-on-network would work fine. Everybody would get a payment per time window of (number of masternodes mod 576) days.

Evan, will rc4's top-10 masternode system make payouts more even over the short term? For instance, one of my nodes hasn't gotten paid in 4 days and another got three payments in under an hour. I'd like to see more even distribution. Would look better to investors! Would selecting randomly...

BIP 32 comes to darkcoin! Simple instructions for manually generating your own deterministic addresses. Never lose keys again! (providing you don't forget your passphrase) http://en.wiki.dashninja.pl/wiki/DIY_Deterministic_Addresses

script I'm working on to automate my remote node restarts from single local. work in progress, probably safe, your mileage may vary, may kill kittens, caveat emptor: http://pastebin.com/AgKahUff

This is the issue I'd seen. sometimes I'd reboot and get the expected: CDarkSendPool::EnableHotColdMasterNode() sometimes I'd reboot and not get the message. Haven't gotten to the bottom of this one yet.

local/remote for testnet, a single conf with sections containing: # node 1 # pubkey # wif #masternodeaddr=blah #masternodeprivkey=blah # node 2 # pubkey # wif #masternodeaddr=blah #masternodeprivkey=blah and several wallet.dat files named: wallet.dat.node-1 wallet.dat.node-2 wallet.dat.node-3...

Thank you chaeplin. What concerns me the most is I don't know how node 3's address ended up associated with node 1. I'll just have to be more careful launching nodes.