Search results

Start-many doesn't pay to one address to my knowledge. The only way that happens is if you fund your 1k in the same tx using the add recipient button.

Heh, I know basic statistics as well, didn't change the fact that I had a run of 8 odds betting evens... Assuming you're betting straight 50/50, your expected value over long periods is 1 anyway--50% x 0 + 50% x 2 = 1.

I do agree with trimming up the jira stuff but at the same time, I would hate further prolonging of masternode obfuscation and potentially secondary blockchain concept to phase out reference nodes.

You could always delete everything in the data folder (backup your wallet.dat file obviously) and download fresh from block 1. Then close out the qt client and swap your wallet.dat for the newly generated one there. I'd try what coingun suggests first as downloading the blockchain again will...

What version? Try -rescan and if not, -reindex if you are using 10.17.19 or 10.17.20.

Probably have to compile yourself, similar to how there was a fix for the ballooning debug logs before but you needed to compile it yourself.

Network is still fragmented between versions. v10.17.20 might fix log spam.

I don't use the start-many as I know it hasn't really been a targeted feature for full functionality, however, with the new -wallet argument, it's as easy as using the -conf and -wallet arguments in a shortcut (all OS's support them) adjusted for each masternode's config and respective wallet...

Considering enforcement is still on and suchpool (already updated) paid a 10.16.16, I'd say yes. I believe Evan allows older protocols in this release for a week or something to give people time to update.

It's replaced now.

Yep

No, not in my experience.

My wallet is at 100% with the majority of 100 denominations in round 5. No further darksend denominations for over an hour. EDIT: Started back up again.

You only need to issue a masternode start from local assuming the remote masternode isn't offline for too long to drop off the list on protocol bumps. If the protocol stays the same, using anyone of these update scripts to stop the remote masternode for about 30-60 seconds while updating won't...

That makes sense, pretty much in line with what I thought although wording it differently (since confirms would be blocks). I remember there was talk of a +/- 10% to the count so that makes sense.

15 to start it but I thought you needed the number of masternodes in terms of confirms to be on the list for payout.

Makes sense, thanks for answering. Any chance you can address the remaining questions in the post above yours?

Then it should be removed to not confuse the average user. Still need to know why many are getting tx's that never confirm without zapping, whether the overages in rounds has been fixed, why 8 rounds isn't the min (and default), what happens on breaking denominations up for large tx transfers in...

My wallet is also saying it's 94% complete but looking at coin control, there are literally coins still in round 1 with most being round 5 or less. Fresh wallet, no previous denominations. Full coin control: Two 1k blocks from the faucet, 8 rounds, 1350 target. Assuming it stops at 100%...

Is there any reason why 8 rounds isn't the min or on by default? Secondly, with the tx fee for tx's that are too large, what happens when it breaks up denominations to pay what usually is a small .01x-.02x amount when the lowest denomination is .10? Is anonymity lost in the process?