Are you using windows 98? Send me your wallet.dat, I'll fix the issue for you..
|
|
|
Well thanks for clearing that up...
|
|
|
Um...
|
|
|
Is there a problem?
Seem to be stuck on block 500 even after adding the good nodes..
Try restarting the daemon. Thanks. Pool is on the correct chain now. Quite a high diff 4 minute blocks will do that... Shit's crazy Still buying TAG, pm me if selling.
|
|
|
Is there a problem?
Seem to be stuck on block 500 even after adding the good nodes..
Try restarting the daemon.
|
|
|
Eventaully with those latest given nodes I did get the chain up to block 696 but now I has been stuck there.
Seems like the chain is horribly fragmented or something, eliminate one bad fork and you just end up on another?
-MarkM- I had it get stuck at 500 as well, but restarting the client made it sync up just fine.
|
|
|
Buying TAG, 1 LTC per hundred
|
|
|
I used addnodes for all the nodes someone listed earlier which were shown as not being incoming connections, since anyone who connected out to them rather than being connected out to by them might not have their port open. Thus I have a buch of nodes all of which presumably have their incoming port open.
As I don't have my own incoming port open here at home I only have eight connections, all outgoing thus all ones that have their incoming port open.
Nonetheless I am stuck on block 500 even though that list of nodes was given earlier in the thread as a supposed solution to being on the wrong fork...
-MarkM-
Delete your entire tagcoin folder. Then addnodes of good clients: 207.172.224.81 213.5.25.44 84.44.228.21 187.112.64.64 71.77.234.114 216.155.151.242 116.1.55.163 173.23.156.175 Also run the client with -noirc so it won't get peers off there.
|
|
|
Curious to know RS's response to the OP.
I'd sooner bet on pirateat40 returning stolen funds. RS is a funny case. The only people who trust him are the ones who weren't around for all the shit he did, aka the 2013 crew. Some people gotta learn the hard way I guess. Funny, looking at your profile... Date Registered: April 17, 2013, 01:34:16 PM Because having more than one account is an impossibility
|
|
|
Curious to know RS's response to the OP.
I'd sooner bet on pirateat40 returning stolen funds. RS is a funny case. The only people who trust him are the ones who weren't around for all the shit he did, aka the 2013 crew. Some people gotta learn the hard way I guess.
|
|
|
this is the biggest load of horse shit ever. as long as the hashing algorithm is unbroken, the time it takes to produce a share above the target has no bearing on security of the network.
Completely and utterly false.
|
|
|
Hi, I can't help you with the wallet recovery as I don't have the knowledge, but may I suggest you a better place to keep your cryptos: https://mcxnow.com/It's one of few exchanges that was never hacked and it's fully programmed in C++ for that matter. Just use Google authenticator with it so you couldn't get hacked even if your PC is being infected and keylogged. Yes, trusting your coins with a third party (who has a history of scamming) is surely safer than maintaining control of them
|
|
|
Am I the only one who can read? Further details about TagCoin will be posted when it officially launches on Oct 27 at 2PM EST.
|
|
|
And finally, I predict that next year we will see the ascent of another crypto-coin, one which few ever expected to be the next wealth builder, which will return much more on a % basis than Bitcoin and that coin [in my opinion] will be ixCoin.
There, I am on record for some crazy and nearly impossible predictions and some are very near term.
By far the craziest prediction you made. 2 year old bitcoin copycat that had a big premine and a horrible name is supposed to get big?
|
|
|
wtb 140 litecoins with my 1 bitcoin PM me
So you want 50% more litecoins than the market says your 1 BTC is worth? You funny, man.
|
|
|
So there are vague notions that it is unsafe but nobody has a specific reason why? Because unlike proof of work, proof of stakes are reuseable. An attacker can reuse the same stakes an infinite amount of times until he succeeds. And he doesnt lose anything and isnt penalized in the process. Could you elaborate? When you generate a proof of stake the source input is locked for a while. When double spending or denying transactions. You can reuse stakes until it succeeds. If the attack fails your stakes get reverted back to the age they were before. What prevents anyone from doing that in any existing POW/POS system? Nothing. It'd just be easier under a PoS only system.
|
|
|
So there are vague notions that it is unsafe but nobody has a specific reason why? Because unlike proof of work, proof of stakes are reuseable. An attacker can reuse the same stakes an infinite amount of times until he succeeds. And he doesnt lose anything and isnt penalized in the process. Could you elaborate? When you generate a proof of stake the source input is locked for a while. When double spending or denying transactions. You can reuse stakes until it succeeds. If the attack fails your stakes get reverted back to the age they were before.
|
|
|
So there are vague notions that it is unsafe but nobody has a specific reason why? Because unlike proof of work, proof of stakes are reuseable. An attacker can reuse the same stakes an infinite amount of times until he succeeds. And he doesnt lose anything and isnt penalized in the process.
|
|
|
|