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

Price is dropping quickly as a result.....pools should maybe restrict their size?...I know some litecoin pools did that when there was only a handful of pools. Also helpful if people have their failover set up for solo mining (protect the network).

Note to pool operators: Please put some detection in place: if you client has 0 connections, stop mining blocks.

Damn! Fix it fast please!! This time fix it for real! It is a great coin, shame this thing is happening to it..

BTW Are the coins safe on cryptsy!?

Crypsy seems to be with them as well and they have the longest chain. Guess which one will be chosen.

Edit: this is what we get when one pool has more than 51% of the network

Only www.bottlecapspool.com is running on the wrong chain. Last time it was due to the wallets losing connection. All other pools / block explorers are reporting correctly

If you are mining at that pool stop until the owner can fix the conection

its forked

 

It does look like another fork

My client is on block 56732 as well as multipool.in as well as http://bot.webboise.com:2760/

http://www.bottlecapspool.com/ and cryptsy are on block 56,757.

I guess the problems which caused the last fork were never fixed inside 1.4 client

Has another fork occurred?  Coinchoose is quoting Erundook's pool with difficulty of 1.2, while Vern shows 1.5. Been this way for a few hours. Last time this happened was because of fork.

BTW, mullick, thank you for your in-depth explanation of Proof of Stake.

I simply could not understand what I was reading in the Bitcoin wiki page about it... but then I read your article and it really cleared it up!

Link for those who might be confused like I was on what exactly PoS means:
https://cryptocointalk.com/topic/700-proof-of-stake-explained-rough-draft/

Coins will only become eligible for stake at the 30 day mark. After that keep your wallet open for a chance of some getting staked. It may happen quick it may take longer. The longer you waitt the more likely up to 90 days where your odds dont increase

When you do get a block the coins used will move to the stake column and be unavailable until the block matures your reward we be for 5% of the staked coins

Should be hitting stake-coins today, around 10AM for me (gmt-5)... Or do they just turn into stake-coins?

Update on the unrewarded blocks situation: I got BigVern immediately on chat at cryptsy - one of the programms which checks for missed blocks wasn't running - already solved.

Hi Jaden, thank you for pointing out! It is the same for me here and I only noticed because of your post. There was no reward for 47 of the last 170 confirmed blocks. That is nearly about 30 %.

Anyone know why there are gaps in block payouts on Big Vern's pool? I'm mining 24/7 there, but there are several blocks where I'm not getting anything.

I am also working on a re write of my previous explanation. I am trying not o spread myself too thin here. So once 1.4.1 is out we will have a better break down. The changes wont be effective immedialty in 1.4.1 so you will have time to learn before the protocol switch

Thank you for this. We have delayed the next release while we restructure a few things. Most of which you just mentioned. We are trying to get it out ASAP but want to make sure we have eliminated these issues as much as possible.

Can someone point me to a breakdown of what the hell "5% PoS" means? 

I read an entire article on the Bitcoin wiki about Proof of Stake and I don't think I understood any of it

When rebuilding the database...

addnode=70.79.24.157

was the only connection I got from YOUR list of nodes... This seems to be a rogue node.

Block-level is 53893 and rising... no other nodes in your list seem to have this height.

Time to look around and kill the rogue nodes, remove them from the many postings, and consider the following settings...

splash=0
server=1
gen=0
testnet=0
daemon=1
maxconnections=20
listen=1

Time to remove the addnodes... it is causing problems, because there is no way to enforce it, and the majority of large hashers seem to not be "listening" or "talking" to the network of your nodes. (Thus, they are building multiple solo chains, and not telling the outside world fast enough... or at all.)

Thus, many tall chains, from multi, from cryptsy, from anyone with three fast blocks or more, are creating branches that others see, only after the servers start talking to the outside world again. (After they have built stacks of private branches.)

If you don't add nodes, and LISTEN for more than the list of nodes you provide... (Obviously your nodes are not talking fast enough either... to each-other, or to the outside world.)... then you are aiding the issue. It only takes one person on both nodes to grab the longest one, and bring it back to the network, causing issues. Your nodes seem to ignore the fact that another chain is larger, and correct, forcing us to use the short ones they are attempting to "manage".

This issue goes back to the 27th... that is where the rogue node, listed above, stopped functioning. (Old code?)

Hm ill look into it. The changes made in 1.4 should not effect the issues you are having. Ill do a debug before 1.4.1 just to make sure. But yes 1.4.1 has been only slightly delayed due to the recent events. Still planned for 5% pos reward

The latest release v1.4 is crashing when sending coins from an encrypted wallet, when encrypting the wallet and on successfully changing the pass phrase.

"Microsoft Visual C++ Runtime Library

This application has requested the Runtime to terminate it in an unusual way.

Please contact the application's support team for more information."

Problem signature:
Problem Event Name:APPCRASH
Application Name:BottleCaps-qt.exe

Problem sigs. from QtCore4.dll and msvcrt.dll

Not had the time to investigate yet. However, I've tried multiple wallets, re-installed MS Redistributable's, re-downloaded the block chain and tested on 2x Windows 7 machines and on XP with the same crash results.

Could just be a bad compile ? Anyone else with this issue ?

New build / release soon please. Still planning on 5% PoS ?