addnode=88.206.186.58:8065
addnode=68.191.179.141:16385
addnode=68.191.179.141:16386
addnode=68.191.179.141:16387
addnode=68.191.179.141:16388
addnode=68.191.179.141:16389

Progress Report
A friend a I started beta testing the TKN/game interface I've been working on.
Everything looks good, and while a bit clunky in this first beta version, everything works as expected.

As far as c-cex goes, I've offered to subsidize them in the amount that they'd earn at their required .2BTC in trade volume per day, and I've got enough BTC here in my wallet that, along with what I've got sitting on c-cex, I can finance continued listing for close to 6 months if need be.

Get version 1.2.2.4
I'd also, as a precaution dump everything in your %appdata%\roaming folder except for your wallet.dat before starting up the new client.
Or your ~/.TrollTokens directory if you're running some linux variant

And sorry for the slow response.....I'm working on a way for folks to spend TKN other than dumping them on the exchanges.
I've got a skeletal web interface completed which allows one to make deposits and withdrawals, and have the hooks into the database interface for the chosen application now.

I can't access that site, as firefox reports the site is misconfigured.
Do you happen to know which wallet version and more importantly, which network protocol version they're using there?

And what wallet version are you using?

I don't know of any solo pools....but I do know there's a "obsolete" project on github called "stratum solo mining".....and that should fix antminers penchant for adding "stratum+tcp://" to any URL chosen to point a miner at.
I know about this as, I'm a miner at heart.....and my S5's my C1 and my S3+'s add that accursed stratum+tcp:// to any URL that's pointing at a wallet for solomining.

Why antminer decide to do this is beyond me.....unless that is, they think that miners are too stupid to set up their own gear.

(edited in) my S1's don't add that accursed stratum+tcp://......so one might want to reactivate their S1's and point them at a local wallet......or a pool if they so choose

Yeah maybe.

Two community members, I and another person built a new wallet and enabled the checkpoint server to avoid this issue in the future.
I've got the checkpoint server running on a system here, and so far it's working as intended.

the link to this new wallet:
https://mega.nz/#!fU4xWJiS!ywdrBEeT7-cxkhAH9ZWLNByNKOPSAMTBplGWC0UXlD0

Note that this has NOT been released yet by the original dev......but I'm sure he'll release it as son as he's aware of it

Here' the bootstrap listed below in uncreamed by the forum format

https://mega.nz/#!rIpEjAjA!HMdN3kGvMEgNUq1yCHqd1Zz5RF3WjjVE10V_jP4Hado

A software shim is a program that ties two unrelated pieces of software together by sitting between the two and acting as a translator between the two.
Middleware of sorts

Anyways.....we're back up and running at c-cex.
Might be nice to create some traffic there.

I wish to express gratitude to all those who've shown an extraordinary level of patience during these rough times in the life of TrollTokens.
We're over the hump now, and our related services are back online.
Time for me to take a little breather, and then get back to work on a software shim to give TrollTokens some real/cyber world uses.

Thank you,

JustBob (TrollTokens dev)

Type in getmininginfo in the debug console.....under "Errors" there should be nothing.

Even the Error message "Completed" forced the client into safe mode.
That doesn't mean much for home user clients, but it means the world for clients providing services that use the "wallet"

You and me both!

I swear I'll never EVER do another update unless it's absolutely positively REQUIRED!


Like I said, I've been messing with this non-stop for a long time now, and it's eating the time that I wanted to use to both find and create some real/cyber world uses for this coin outside of a mine n' dump or stake n' dump internet trading token.

Ok...the repos are good to go and there's new binaries uploaded to the releases at both Repos
https://bitbucket.org/ZooTaLLures/trolltokens/downloads/TrollTokens-win-v1224.zip

Let me go doublecheck the repos this morning.
The answer was so simple, yet I wasn't thinking on that level.*grumbles*

Updates been running for several hours now.......no error messages.....and everythings looking good.
Bitbucket and github repositories have been updated....haven't updated the windows releases at either repo yet......still testing everything.....BUT....looking "good to go" so far.

think I've found a solution.
It's not an elegant solution, but it is a solution.

Issue is, I can't manage to get past that alert that pertains to all network protocol versions up to and including 60016.
The sendalert syntax is correct, yet it's having issues parsing the JSON of the cancellation of the alert.

I've been at this for 4 fucking days and 4 fucking nights now.....I'm NOT going to let this fucking coin die......even if I gotta' piss on a spark plug to keep it going!

Yeah.....I have to get rid of the error messages in the alerts.
I'm working on it.

That's the second time I get to thank you for bits of info, as quite frankly, I was pulling the very few hairs I have left in my head out, because I couldn't for the life of me, figure out why it was reporting 1.2.2.3 locally but 1.4.4.9 over the network.

Anyways, as of this moment, I think it's more important to get everything stabilized, as that string (1.4.4.9 vs 1.2.2.3) is just that.....a string of characters.
It doesn't seem to affect the functionality of the client, and in many respects, defines the force update release.

Right now, of greater importance is completing the "shim" I'm working on.....to get some "real world" use in the coin, and I think I've got a winner of an idea there.

Well, blockpioneers has updated and they're on the correct blockchain now.
Still waiting for word from c-cex

Or they're not taking the drop in the POW block reward well.


I didn't want to have to do that yet, but if I can't get folks in the industry on the same page, yeah, I guess it's time.

1.2.2.3 talks to both the old version 60014 and the new 60016.

Old version might or might not be on the same fork of the blockchain  depending on the contents of their current peers.dat file, new version won't do that.

Ok, here's the link to the newest official version for windows, linux users can rebuild from the source repositories as the code on both Bitbucket and github has already been updated.

https://bitbucket.org/ZooTaLLures/trolltokens/downloads/TrollTokens-win-forceupdate.zip

This time, being a hard fork to fix the blockchain issue, folks are going to have to dump everything but their wallet.dat file in their ~/.TrollTokens dirctory (linux) or  their %appdata%/roaming/TrollTokens folder in windows.

This of course means users will have to resynch from scratch.
Being a young coin, that shouldn't take too long.

I'll go fix the Opening announcement post now and start sending out to the folks that provide the various services related to TKN within the industry.

On May 7th I called for and released the update, and activated auto checkpointing in the new 1.2.2.3 wallets which are running network protocol version 60016 but accept connections from the earlier network protocol version 60014.

The forceupdate version was released on 5/14.
On May 13th, block 20001 was mined, and all the clients hadn't updated yet.