A pruned node can not yet run a wallet, you need to wait for 0.12.
You can keep the old files and just enable pruning once you updated.
I hear 0.12 should be released in a few days: What's new in Bitcoin Core 0.12 - Jonas Schnelli, Core DeveloperAs for the blockchain size, he mentions 2GB in the video... which sounds amazing compared to 60GB... a 96% reduction? |
|
|
|
|
With regards to cryptocurrencies, it is also a good idea to segregate the wallets from each other.
Cryptsy lost millions of dollars because of a "virus" in one wallet. If the wallets were each run in a separate ec2 instance, this could have been prevented
|
|
|
|
What's the big deal about an 80Gb directory. The file sizes are still fairly small, and the notebook I am using now has a 2Tb hard drive. It wasn't that expensive either. If you are on a chromebook, or a mobile, then I can see it would matter, but for a reasonable PC, I'd rather have full control of my wallet.
I suppose it depends on the situation. The web hosting service I use charges $0.10 per Gb. That's $8/month, nearly $100 per year... Plus bandwidth costs... Running a full node on my website would cost $1-200/year, and the blockchain is certainly not getting smaller |
|
|
|
|
Same here. page 3 dashtalk. no dash.org at all. uk.
|
|
|
|
|
Is that the Troll Patrol most wanted list?
Edit* Most unwanted list?
|
|
|
|
Goodbye reference node! haha
Step by step, dash will be BIG
when..?? August 29th |
|
|
|
darkcoin.io is a crap website. obviously by newbies
Do better and sell it to us. We'll pay you in the shitcoin of your choice. you are on fire these days ! what is going on, the trolls got to you or what chill chill chill ....>>> You should see me in real life... I have zero tolerance for assholes. Most people have to get riled up to bring the pain, it's just my natural state of mind. I'm always ready to dish out consequences to those who deserve it. The last one tried to pick a fight with one of my girls and I convinced him to punch himself in the face as an apology. It was hilarious. "I'll give you the choice, you can do it or I can do it. I'm kinda mad at you so..."I AM THE CONSEQUENCE. That quote has made my day. |
|
|
|
Thanks! i know of this guys work. I'm very much into futurism. Singularity and such. A.I. Transhumanism. that's how i came across him. |
|
|
|
Well it didn't take long for markets to respond.
Walls going up.
Bang goes my 3 DRK per day masternode income.
What do you think the income will be now?? I'm thinking there might end up being between 250 and 1000 masternodes which means" @250 MN: (3200 x 0.2) / 250 = 2.56 DRK per day @1900 MN: (3200 x 0.2) / 1000 = 0.64 DRK per day However, the dollar income will be more stable because if the number of masternodes increases, the price will have to rise significantly, so you'll get less DRKs but each one will be worth more. (Black line on this graph http://drk.poolhash.org/darksend.html ) i cant imagine selling my dark for cash. Ive grown attach to them and i would much rather spend the drks as they are. fiat is soooo 5 years ago. |
|
|
|
Well it didn't take long for markets to respond.
Walls going up.
Bang goes my 3 DRK per day masternode income.
What do you think the income will be now?? i wouldnt worry, more nodes should mean higher price. so your drk per day will be worth more even if you get less. |
|
|
|
DO NOT POST SESC LINKS I have tracked two masternode list. 1 from my server, 1 from darkcoin.io. After Masternode payment stopped, No of NMs have changed slightly. As initial download of Masternode list, client check several things. If 1,000 DRK is spent, rejected. Problem is updating of Masternode. It has bug. if spent, if time passed this is not working. Inconsistency of masternode list is happened. 21 -22 nodes have moved coin. I think it's core cause of last hassle. And Dev is well aware of. I noticed this too. I tried stopping my node and it still remained. I even moved coins out and it still remained. After removing coins I tried starting the node again with a new wallet. 371 nodes went down to around 300. which i think was a more accurate amount possibly. I did this a few days after the problems, to troubleshoot. |
|
|
|
|
No feeding trolls after midnight or they multiply and get become pests ............oh wait, that's gremlins.
|
|
|
|
|
quick question guys, when i do a masternode stop, my masternode stays on the list. Is this due to the recent problems or something wrong with my client? I diabled it for at least an hour or more last night and it still was showing on darkcoin.io and on the daemon list.
Any ideas?
|
|
|
|
Guys, if you have syncing problems:
1) If you're on wrong fork - run with reindex
2) If you're on the right fork but stuck - stop and restart.
When updating my masternodes last night, all got the right fork - new deamon prevents getting wrong one, however the deamon may get connected to the forked nodes and will not sync past the last correct block. This was the case with 2 of mine.
Restarting without reindex solves the issue.
If only those people (who ever they are..) updated there wallets when they had to. Cheers They'll eventually do... One obvious sign is amount of connections, if it's low (~15 when I was doing it last night), it's the wrong nodes and you have to restart. Once everyone updated and reindexed their MN, this will go away. I dont mind to much though. This is new tech. I am just happy to be a part of it. Whatever obstacle comes I am ready to tackle it and not moan ( well not too much anyway  ) |
|
|
|
Guys, if you have syncing problems:
1) If you're on wrong fork - run with reindex
2) If you're on the right fork but stuck - stop and restart.
When updating my masternodes last night, all got the right fork - new deamon prevents getting wrong one, however the deamon may get connected to the forked nodes and will not sync past the last correct block. This was the case with 2 of mine.
Restarting without reindex solves the issue.
If only those people (who ever they are..) updated there wallets when they had to. Cheers |
|
|
|
i am reindexing, my wallet is stuck on 74873, the correct block seems to be 74878. I have the correct wallet, any ideas what i am doing wrong?
me too. Well I run several wallets and some of them is stuck and some of them is synced. I think we need some fix. Has the same issue, stopping darkcoind and restarting it without -reindex solved it for me Would that be risking syncing to the wrong fork? shouldn't do right? ./darkcoind stop cd ~/.darkcoin/ rm- rf blocks/ rm -rf blocks/ rm -rf chainstate/ cd - ./darkcoind yeah, i was going to do that. Thanks, just the long wait is getting to me. its nearly 9am and i have not slept yet! |
|
|
|
i am reindexing, my wallet is stuck on 74873, the correct block seems to be 74878. I have the correct wallet, any ideas what i am doing wrong?
me too. Well I run several wallets and some of them is stuck and some of them is synced. I think we need some fix. Has the same issue, stopping darkcoind and restarting it without -reindex solved it for me Would that be risking syncing to the wrong fork? shouldn't do right? |
|
|
|
|
Show Posts
