[ANN] They're here! TrollTokens POW/POS sha256 hybrid

[JustBob]

I made an announcement about the fork, and updated the announcement of this thread a week ago.

[1714723990]

1714723990

[1714723990]

1714723990

[bytes00]

may i ask, whats the current version ?

i am receiving this error



{
"version" : "v1.2.2.3-gf6f3491",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 1330.18630223,
"newmint" : 0.00000000,
"stake" : 215.58066433,
"blocks" : 20463,
"timeoffset" : -1,
"moneysupply" : 386614.07388360,
"connections" : 12,
"proxy" : "",
"ip" : "2001:e68:5430:41c8:14c8:ac7:dd4b:a0a8",
"difficulty" : {
"proof-of-work" : 385926.46497776,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1460887630,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : "Mandatory update required"
}

[JustBob]

The current version is 60016.
And the error message doesn't apply to that version but is still propagated through that version to the rest of the clients.
Your client can and does work as expected.

Wait, let me double check, as you seem to have too few blocks.
Until either:
a) we get everyone updated to the new version.
or
b)people start using a "forced update" version that refuses connections from the version 60014 clients.

We have a very good chance, and might be seeing a fork in the blockchain.

[crackfoo]

may i ask, whats the current version ?

i am receiving this error



{
"version" : "v1.2.2.3-gf6f3491",
"protocolversion" : 60016,
"walletversion" : 60000,
"balance" : 1330.18630223,
"newmint" : 0.00000000,
"stake" : 215.58066433,
"blocks" : 20463,
"timeoffset" : -1,
"moneysupply" : 386614.07388360,
"connections" : 12,
"proxy" : "",
"ip" : "2001:e68:5430:41c8:14c8:ac7:dd4b:a0a8",
"difficulty" : {
"proof-of-work" : 385926.46497776,
"proof-of-stake" : 0.00024414
},
"testnet" : false,
"keypoololdest" : 1460887630,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : "Mandatory update required"
}

I get this error too... it seems because there are higher wallet versions on the network:

68.117.4.111:16385   TrollTokens:1.4.4.9      
85.25.200.157:16385   TrollTokens:1.4.4.9      

[JustBob]

The checkpoint server and a few clients are running version 1.4.4.9, which is identically the same as 1.2.2.3 with the exception that they refuse connections from clients using network protocol version 60014.
If you'd like that version it's at both Bitbucket in the downloads and github in the releases labeled trolltokens-win-forceupdate.zip.
The code repositories have already been updated......bit I really didn't want to have to "kick folks out" that haven't or maybe didn't want to update.....yet.

[JustBob]

I enabled the checkpoint server feature tonight.
In coming days I'm going to be calling for a mandatory update.
There's a few things that just aren't right in the wallet yet, with the blocktime inaccuracy being only one.
The checkpoint server and the PNseeds "server"(I'm dropping the DNSSeed server) are going to be the transitional link between the old network version and the new.
After a suitable span of time(maybe two weeks) to allow all clients to update, I'll be shutting down the transitional link.
After the transitional link is shut down, the checkpoint server will define which is and is not a valid fork in any potential blockchain forks, and the PNSeeds "server" will provide a basic set of nodes, to keep all clients on the same chain.

On May 4th, I enabled both the checkpoint and the PnSeeds.
It's clearly explained here.

[sesiah]

Trolltokens doubt very goog, looking forward to buying some

[JustBob]

Called for a mandatory upgrade.
adjusted the long term block reward in the hopes of attaining some sort of sense of parity between POW and POS.
Enabled auto checkpointing
Enabled alerts

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.

[ACP]

Called for a mandatory upgrade.
adjusted the long term block reward in the hopes of attaining some sort of sense of parity between POW and POS.
Enabled auto checkpointing
Enabled alerts

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.

I'm pretty sure my wallet received a message about updating client and you have made it clear for people to update respectively,
Some people are Just trying to fudd price down. You are doing well with this coin.

[MilkandPie4U]

I'm updating to version 1.4.4.9, time to force the change.

[JustBob]

Some people are Just trying to fudd price down.

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

I'm updating to version 1.4.4.9, time to force the change.

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.

[JustBob]

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

[BanzaiBTC]

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

Yes

Next time, please pm me with such information 

Also, there is a very small bug in the source... Making version display errors..

https://github.com/Justbob1956/TrollTokens/blob/master/src/version.h#L15-L18
Because you made these changes, the version display information of the "getpeerinfo" rpc call gets multiplied by these changed values
These numbers all need to be 1.. as in:

Code:

1000000 * CLIENT_VERSION_MAJOR
   10000 * CLIENT_VERSION_MINOR
      100 * CLIENT_VERSION_REVISION
         1 * CLIENT_VERSION_BUILD;

If you need more info on that, pm me 


Explorer will go down for another update later today...

Regards,
Banzai

[JustBob]

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.

[MilkandPie4U]

Hey Bob,

Any reason why both pools and the block explorer are not working?

thank you

[glen123]

Hey Bob,

Any reason why both pools and the block explorer are not working?

thank you

cause i just saw that Dev forced AGAIN! a new version ( why dont contact Dev the PoolOwners via PM `? ).

compiling just now , but next time i will pass . 2 new Versions in about 2 Weeks

Regards Glen
Edit : thats the newest Version on GITHUB

l:~/trollcoin/src# ./TrollTokensd getinfo
{
    "version" : "v1.2.2.3-gf6f3491",
    "protocolversion" : 60016,

[glen123]

Doesnt work anymore here :

37/cronjobs# ./findblock.php -f
PHP Fatal error:  Uncaught exception 'Exception' with message 'RPC call did not return 200: HTTP error: 500 - JSON Response: [-2] Safe mode: Completed' in /var/www/html/p3337/include/lib/jsonRPCClient.php:120
Stack trace:
#0 /var/www/html/p3337/cronjobs/findblock.php(35): jsonRPCClient->__call('listsinceblock', Array)
#1 /var/www/html/p3337/cronjobs/findblock.php(35): BitcoinWrapper->listsinceblock('000000000000645...')
#2 {main}
  thrown in /var/www/html/p3337/include/lib/jsonRPCClient.php on line 120



Sorry , will shutdown Pool till i figured out what happend

Edit : not working since Fork from Block 25614 (fully resynced from scratch )=

SetBestChain: new best=000000000000645cda5a  height=25614  trust=96208308562935598236  blocktrust=234220575353736  date=05/21/16 05:20:12
ProcessBlock: ACCEPTED
Flushing wallet.dat
Flushed wallet.dat 51ms


Seems broken / death .

[MilkandPie4U]

Well for now I'm turning off my wallet until Bob has a chance to sort this out, no need to mine POS or POW right now until it's fixed.

[JustBob]

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

[JustBob]

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!