Hi - Can anyone help?
I've downloaded the latest ver of the wallet (v0.11.0.6) and it's not synchronizing.
Says "no block source available" Stuck at block 199885
Try --reindex |
|
|
|
guys im having issue with darksend Status: conflicted from last transaction now i have 1 drk on balance and rest on pending.... its like that all night! what can i do :O EDIT: just redownloaded blockchain again and its ok now  sorry There's a known issue with Darksend, where it makes "conflicted" transactions. Whenever this happens, simply restart the wallet with --zapwallettxes and it will correct itself. how do i do this "start wallet with --zapwallettxes" ? and this is ok to do with a wallet that just stores DRK yeah ? and it's ok to do when dark mix has not finished ? If you're running windows, you do it by making a link to the executable and adding "--zapwallettxes" to the parameters. Otherwise you can just start it from command line with --zapwallettxes on Mac and Linux. You can do this at anytime without any risk. It syncs your wallet to the blockchain, that's really it. |
|
|
|
guys im having issue with darksend Status: conflicted from last transaction now i have 1 drk on balance and rest on pending.... its like that all night! what can i do :O EDIT: just redownloaded blockchain again and its ok now sorry There's a known issue with Darksend, where it makes "conflicted" transactions. Whenever this happens, simply restart the wallet with --zapwallettxes and it will correct itself. |
|
|
|
Small article on Darkcoin Core V0.11.0 can be found here. " Darkcoin Core V0.11.0 is forked from Bitcoin 0.9.3 in order to take advantage of nearly 2 years of development committed to the Bitcoin core client. " ??Thats *sort* of true isn't it? Fork might be the wrong word... well sorry evan "called" it the same he said this "Fork from Bitcoin 0.9.3 taking advantage of nearly 2 years of development to the Bitcoin core client" my bet We literally forked Bitcoin 0.9.3 then implemented every change that was done to Darkcoin the entire year on top of the new client. We're no longer based on the Litecoin codebase, which is good because it seems like they have no interest in maintaining it. |
|
|
|
Quick question for anyone....
I had to hit the stop darksend mixing button while I had a pending balance. It's been over 30 minutes and that pending balance is not yet confirmed. I can't restart DS because all of my DRK is pending and I don't have the minimum required to hit that button.
Can someone calm my nerves and tell me that I will get my 310 DRK back. It will only work if I believe you, heh.....
Restart with --zapwallettxes and your money will be back magically. It's pretty difficult for Darksend to lose your money, because it simply sends it to yourself over and over. Pretty difficult means possible? It's only possible to lose money if your wallet gets corrupted and you don't have a recent backup. |
|
|
|
Quick question for anyone....
I had to hit the stop darksend mixing button while I had a pending balance. It's been over 30 minutes and that pending balance is not yet confirmed. I can't restart DS because all of my DRK is pending and I don't have the minimum required to hit that button.
Can someone calm my nerves and tell me that I will get my 310 DRK back. It will only work if I believe you, heh.....
Restart with --zapwallettxes and your money will be back magically. It's pretty difficult for Darksend to lose your money, because it simply sends it to yourself over and over. |
|
|
|
QHoster.comI managed to get these folks to accept Darkcoin and they provide fantastic VPS services. The servers are all very high quality and they provide up to 40 IPs per machine, with DDOS protection. I'm running darkcoin.io on these machines now and haven't had any problems since. If you're thinking of starting a masternode, check them out: http://www.qhoster.com/vps.html
|
|
|
|
Darkcoin Core v0.11.0
Sh*t. This stuff is awsome. 10 developers ? (/people) That blows me away. People who helped a lot (even more people than this participated, it's absolutely fantastic): Me, Flare, UdjinM6, Patrick M, Francis R, Vertoe, Daniel A, Crowing, Elbereth, Stuart B, Tiago S, Splawik21 and Moli (not in any order) |
|
|
|
Thanks to everyone who supported me and Darkcoin! It's a great honor to receive an award like this for the work I've been doing, it really means a lot that all of my effort slaving away on this hasn't been wasted. Also thanks to all of you who are helping Darkcoin behind the scenes to become something greater, we couldn't have done it without you.  |
|
|
|
v11 works on mainnet and if you want to help testing, you could run it too. Just make sure you compile from source and run it in a debugger. (The protocol is backwards compatible so separate releases can survive side-by-side together) Of course, Evan knows the true risks. I can't say I agree with it though. It's essentially zero risk. |
|
|
|
An unstable release on main net is unacceptable in my view. Testnet should be scaled up rather than put the network at risk. If this is testing by the devs, it makes me wonder why I pay FIAT to subsidise a portion of testnet to avoid exactly this sort of thing.
V11 is in a state where it's releasable, the final stage of testing is to have some of the main network begin to update and report back. It actually gives us a much lower risk of breaking something when we do it this way. It's not any of the devs though, but I support it if it's just for testing. |
|
|
|
v11 works on mainnet and if you want to help testing, you could run it too. Just make sure you compile from source and run it in a debugger. (The protocol is backwards compatible so separate releases can survive side-by-side together) |
|
|
|
My remote masternodes have become "unstable" lately, they randomly stop syncing the blockchain for some unknown reason. Recently all of them stopped updating, at the same block number. I have had to restart them repeatedly and sometimes that doesn't seem to work so I create a new wallet.dat and delete peers.dat on the remote server and that seems to fix it, at least for a while. Anyone else seeing similar?
Your post prompted me to login to my VPS and check (which I do every so often but hadn't for a few days). My MN was stuck on block 199711 whereas the current block (at the same moment) was 200686. I've never had this happen before. I do often though experience the v0.10.17.24-gee8174a-beta wallet hanging at a block during a network catch-up when the wallet's not been running for a while (on Win 8.1). I sometimes have to restart it a couple of times before it successfully catches up to the current block. I've stopped darkcoind and restarted it on the VPS. It seems to have caught up okay now. Will monitor. all of my mn's were also stuck at 199711 There's a known issue with 17.24 that was discovered yesterday that caused this problem on the network. We're in the process of building 17.26, however feel free to compile from source in the meantime |
|
|
|
We should have a day where everyone goes into Cryptsy/Bitfinex/etc and doubles their sell orders price. Would that even work? It's a pretty interesting thought experiment. I`m in, but how to convince bots ?  Wouldn't bots just follow the lead of humans? |
|
|
|
I bought 3000 DRK at price 0.008 !
What am i do ? Sell them or hold them ? someone please give a prediction of the future of DRK Coin
Sell at 0.016 . We should have a day where everyone goes into Cryptsy/Bitfinex/etc and doubles their sell orders price. Would that even work? It's a pretty interesting thought experiment. |
|
|
|
DDOS'd again, should be up again. Try clearing your cache. |
|
|
|
DDOS, it'll be back up in a bit. Moving things around atm. |
|
|
|
|
Show Posts
