Topic: Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS - page 150. (Read 388610 times)

No forks possible if there are no old clients running, simply because the checkpoints won't allow so.

However, it doesn't mean that everything is going well. It's clearly, that using the BCPs for the chain integrity maintaining isn't a normal practice. The block chain should be able to function without BCPs.

Dont know why that message was posted on multipool. Both explorers yourself and Vern were in agreement

Only clients that didnt update in time were affected

Bump so people update

Well the checkpointing server offers the greatest security against these sort of problems. Now that its active users of 1.5.2 are running on one of the most secure blockchains out there. Like ppc and nvc once sufficient coinage is sustained on the network the server will slowly be weakened. And Proof of stake allowed to take over

I dont think changing subisdy ect is a good move. In my opinion its just an attempt to raise the price and provide a larger early  adopter advantage which is exactly the opposite of what caps is about. Its designed so if you started mining today you have the same opportunity to acquire holding as you did if you mined block #1

Something i may be open too is a change in block times with a subsidy change to match keeping the same generation model and fairness it has always had. Maybe a poll is in order to decide the future. But i assure you 1.5.2 is extremely stable and reliable. Any changes from here on out will only be for the longevity of the chain

Crypto currency's are designed to be decentralized. Its one of the greatest advantages. Changing subisdy and generation models goes against everything a decentralized currency is about and is not something i am open to doing if it will cause an artificial rise in price

Changing the rewards for POS is something I would still like to do but if its done would be adopted later in the chain giving everyone a fair opportunity to asses the changes and decide if they would like to continue support of the currency. I suppose this is also changing the generation model but feel its not nearly as drastic as cutting the block reward and drastically decreasing the daily output of the chain

However this is not a dictatorship I am only here to provide a stable and reliable currency if the vast majority of users that make up the network decide it is necessary I will oblige. But it would require great discussion general consensus

I hate to see Caps so low. This must be due to those issues with chains, probably investors waiting for things to resolve... Mullick, I think you should hard fork it like DGC and WDC did, finding the optimal POS/POW, coins, block time, diff settings... So we can resolve this once and for all and so the confidence in the coin returns...

No need to worry for you vern is on track


Ill keep bumping this thread. Im guessing whats left on the other chain is a lot of people stake minting and a few bigger hashers. If you did mine some on the old vlient I still have some donations i could distribute to you to ease the effects of this

In order to get on the right chain closing the client for a few hours or changing your ip will clear your bans and you can redownload thew blockchain to the correct one.

Ill be clearing the peers on the nodes listed in the op regularly

Good point.  I missed that.  So there is a lot more hash going to the right fork.

Right now I show 30 peers with getmininginfo compared to the 27 listed on kicks-ass.

I didn't wait after upgrading so my node is probably banned by kicks-ass which would explain why I locked onto the fork I did.  Is there any way the protocol will recover or is it a matter that requires manual intervention?

So what is going on exactly?  I have deposits in Cryptsy as recently as a few hours ago.

A few people who didnt update to the lastest client which was released a few weeks ago ( 16 days to be exact ) were sent to  bad chain when the checkpointing server was switched on.

The reason the chains stay close in height id the difficulty algorithm which adjust reather quickly. the 2 chains have a wildy seperate difficulty with the correct chain having near 1 and the other ranging around .4

I made sure all pools and explorers were on the same chain and my node was showing 8 out of 61 peers left to upgrade which should have forced the supermajority but it appears someone generated a lot of stake that was rejected by the server and accepted by older peers. Banning them.

If you upgraded in the last 2 days and are on the wrong chain, close your client for a few hours delete the blockchain and redowload this way you will not be bannned by peers from the right network.

Perhaps i should have waited longer to turn it on or even hard forked it with the new key but i didn't want to do a hard fork unless necessary and 8 out of 61 peers after two weeks seemed like a good majority. As well as all pools and explorers ect being on the new client

The checkpoint too old message is designed to warn users that a software update is likely

Somebody is going to be disappointed.

Since the time I posted earlier to now the KAA fork has solved 113 blocks and the fork I am on has solved 104.  That's pretty close to an even split of work that half the people aren't gonna like the result of.  That probably includes me since my miners are on multipool since I am too lazy to manage them by hand.

The CCE3 block explorer: cap.cryptocoinexplorer.com is on the same chain as the Kick-ass crawler.

I did a git pull to make sure the CCE explorer was using the latest Bottlecaps version, and it is.

Are there any p2pools for bottlecaps?

FWIW, multipool is on the same chain as kick-ass

I just saw the dev has returned and posted to this thread.  I have upgraded my client to 1.5.2 and nuked my blockchain and peers.  I had a couple hundred people on one of the forks with me prior to this.

An hour later now that I have redownloaded the blockchain I find I am still on a different fork than http://bottlecaps.kicks-ass.net/block_crawler.php

My client sees:

bottlecapsd getmininginfo
{
    "blocks" : 160976,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.44363437,
    "errors" : "WARNING: Checkpoint is too old. Redownload Blockchain. If warning persist contact the Development Team",
    "generate" : false,
    "genproclimit" : -1,
    "hashespersec" : 0,
    "pooledtx" : 0,
    "testnet" : false
}

but kick-ass.net sees: Block Count: 161,014

People are mining on this fork as the block count increases.  The branch I am on seems to be advancing faster than the one kick-ass.net is on .  Some people are not going to be happy that they are working on the wrong fork, but it is hard to tell which one is right any more.

I gotta tell you that it instils little confidence in a coin when the standard answer is "throw away your block chain and download mine, it is right ... really it is ... trust me.."  I suggest you figure out how to make them converge without requiring a block chain download if you want to be taken seriously.

Forget that...what he NEEDS to update are his servers so that miners are not constantly missing valid payments on random confirmed blocks!! This is STILL going on...months now...many believe it is blatant theft and not just "ongoing server/client problems"...I'm starting to lean that way now too as this is getting ridiculous and he says he knows and is "working on it" but nothing gets done.  Many people are losing a fair bit of their hard earned coins due to this....

Cone on VERN....get this fixed once and for all or be labelled a mining pool operator thief...

PS..its too bad CAPs keeps dropping in value..now in the 0.00007's..way under valued..and the mining has been well under 100 megahashes for long time now...hope to see rebound soon...

Vern was still on 1.5.1 hes updating now

http://www.bottlecapspool.com/   is forked?

Update on currency generation for the first 16 weeks

Total Supply: 1493619.125

Supply from proof of stake: 554.51

Source: www.cryptometer.org

First 96 hours:




First 16 weeks:

Checkpointing server online as of block 157,456

Few peers left to update but we have the super majority so they will listen to us

Also all pools Im aware of have updated

The support of the community really surprises me. We are happy to have you and thank you for your support