Topic: [ANN] They're here! TrollTokens POW/POS sha256 hybrid - page 5. (Read 16872 times)
I made an announcement about the fork, and updated the announcement of this thread a week ago.
There's still an awful lot of folks, including some members of the industry(pools, exchanges, and the block explorer) that haven't updated yet.
Now I know that most folks don't "live" at BTCTalk, but it has been a week.
It's time to update there folks
Now I know that most folks don't "live" at BTCTalk, but it has been a week.
It's time to update there folks
You should have reminded everyone from the beginning and made some big announcement about the fork. Those who haven't updated possibly were not notified.
There's still an awful lot of folks, including some members of the industry(pools, exchanges, and the block explorer) that haven't updated yet.
Now I know that most folks don't "live" at BTCTalk, but it has been a week.
It's time to update there folks
Now I know that most folks don't "live" at BTCTalk, but it has been a week.
It's time to update there folks
Quote
thx for that , here the Status from Pool :
Thanks for reporting in. 
I just sent the GC pool operator an email via the contact form on the pool.
thx for that , here the Status from Pool :
Wallet Status
Version Protocol Version Wallet Version Peers Status Blocks Accounts
v1.2.2.3-gf6f3491 60016 60000 6 OK 20143 1
newest Version from Github
I contacted suprnova as well.
Thank you Bob, I also sent a note regarding the update.
I just sent the GC pool operator an email via the contact form on the pool.
Should be 1 TKN now, after block 20001.
Although I am seeing that there's a few old clients still out there.
Today I'll be rebuilding the seednode and checkpoint "server" to reject connections from any non updated clients.
I don't know if they're on the updated client or not, but they're not connected to the seednode, nor the checkpoint "server", as there's no old nodes connected.
Code:
else if(pindexBest->nHeight+1 >= 20001)
{
nSubsidy = 1 * COIN;
}
Although I am seeing that there's a few old clients still out there.
Today I'll be rebuilding the seednode and checkpoint "server" to reject connections from any non updated clients.
Quote
I dont know if the GC"S pool's is on the new forked wallet? Bob can you comment?
I don't know if they're on the updated client or not, but they're not connected to the seednode, nor the checkpoint "server", as there's no old nodes connected.
I dont know if the GC"S pool's is on the new forked wallet? Bob can you comment?
Blockreward 10 TKN now?
Shouldn t it just be 1TKN, from Block 20 000???
Shouldn t it just be 1TKN, from Block 20 000???
Nice reduction in POW reward after block 20000!
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
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
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.
I have a feeling this coin is going to do really well, I'm in 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.
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.
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.
Why not, I'm due to add another coin anyways.
Quote
What's going on with development?
Nothings broke, so we have to concentrate more on external rather than internal development at this point
[edited in afterwards]
But come to think of it, there's two ultility features that I'm looking at.
The first is the ability to split blocks to a defined size via the GUI.
And the second is the ability to recombine split blocks, again, to a defined size, and again, via the GUI.
What's going on with development?
Quote
IRC has a bad reputation and causes reputational harm by association.
The bad reputation of IRC has much less to do with the chat than it's has to do with all the other bellz n' whistlez added on to try to keep it alive in these days of real time video chat and the like I shall officially endorse this on behalf of the Trolls Union #418 if the developer makes an open and honest attempt to remove irc.cpp from the wallet as well as add in additional "backup" seeds within net.cpp(around line 1235 in net.cpp would suffice) as soon as the resources come available.
Adopt a troll program TKN: PGQCDX9eZL9rzfzggWnVNcCEvL5ghteeq3
Adopt a troll program TKN: PGQCDX9eZL9rzfzggWnVNcCEvL5ghteeq3
Actually, it's fairly simple to "undefine" the IRC server IP number and name in irc.cpp (Lines 227, 229), which then throws a "ThreadIRCSeed exited" message to the debug log, and jumps straight into using the PnSeed array via the ThreadOpenConnections thread, after trying the DNSSeeds, which I also undefined for the sake of this test.
No DNSSeeder and no IRC means zero connections unless of course PnSeeds is being used.
Is there anything in particular that you don't like in irc.cpp other than the fact that it connects to an IRC server.....or at least used to connect to an IRC server?
Sounds perfect for TrollTokens!
Jump to: