Your first post was 11 hours ago, not 38.  It looks like Balls has a 45 sec block time.  With that,  I calculate about 32.8 days before the fork.  Lines up with you math if you figure 11 hours instead of 38.

Tbone, you don't have to do anything.  What your seeing is normal.  You should see you balance slowly increasing, as coins stake.  The stake value is just the coins that are currently being staked and are not available to send.  I haven't really paid much attention to that, but in a well behaved client, the balance, and stake should be your actual total coin balance. 

   Just sit back and watch your investment grow.  And feel good that your contributing to moving along the QBK blockchain. 

  LOL.... 

  To bad we can't see the bad with the good.  When you make assumptions and things look to good to be true, they usually are.  It would still be nice to follow the numbers even if they are not good news.  We can still learn from our failures...   

   Comments on the new build, b8 is the one I tried.  I just used it on Just-dice. 

First the good, I loved being able to chat while the bot was running.  The old version 2.5.5taken back by  took the focus from the chat input each time a bet was made.  I was surprised by the change in the layout.  But was able to figure it out in about 2 minutes..  Took a bit though. 

  The bad.  Or maybe I just don't know what I'm doing.  Manual bets does not provide the full function of the site.  There is no way to double or half your bet easily.  Also the manual bets are not adjusted as the bot plays. 

   I play a modified martingale and stop after X loses.  Then I want to manually bet.  Old version worked great for this.  The new one, I have to manually calculate the bet and type it in. 

    Thanks for the great bot.... 

   Will this be a hard fork?  Are new clients required?  No mention of this in the OP.  I follow this thread, and this one flew right over my head.  I must have been reading fork and thinking it was the fork that just happened 2-3 weeks ago. 

   What fork is this?  Another one or the one that already happened? 

 I wouldn't get to nervous about this.  That's one Man's opinion, note the use of the word "imagine".  

   To keep a POS coin network alive you need to have lot's of nodes moving the block chain along.  The people running the nodes need to be compensated for there time and resources.  At present, the transaction fees are increasing, but don't amount to much.  In the last 6 stakes I've made .0014 from the fees.  hardly enough incentive to keep a node running.  

  BTC generates a 25 coin per block reward for the miners.  They try to average 6 blocks per hour.  So that's 150 BTC per hour Vs. Clams 60 clams per hour.  And the CLAMS block chain is 10X faster then BTC.  When BTC halves the block reward to 12.5 they will still be generating more coins then CLAMS, and the blockchian will still be 10X slower.  

    There may come a day when the volume of Clam transactions, and thus the transaction fee's, are high enough to sustain a network.  If or when that will happen is anyone's guess...

    That's just my opinion.  

Received 3rd payment.  .02 for a total of .1585 of 2.262.  Google spreadsheet updated.
 https://docs.google.com/spreadsheets/d/1JKPeMI91oO9_khnM-1qWFi7SflhXStC6OJC3QSFQDU8

    Keep up the good work.  And much luck in the future. 

   Have you read any of this thread? 

   Are you looking for pump and dump coins? 

    Didn't work on FireFox.  I had to use IE to get the info.  Looks like it was browser specific.  Weird.... 

   Is there a secret to cutting/pasting that UCIcoin wallet address on btcpool?  I can't seem to select it. 

All of the above plus,  He didn't really get into the digging aspect of clams either.  The fact that most users already own them,  Etc.... 

But,,,, He doesn't accept the challenge....   

   Read back a page or 2.  You can add connect statements to you HyperStake.conf file to force the client to only connect to known good clients. 



Also did you have to use the -loadblock=bootstrap.dat option when you reloaded the blockchain? 

I forgot to add that when I recovered and I think I ended up pulling everything from the network.   

   I have the new client (V1.1).  I got this after I thought I was on the wrong fork.  No back up of the chain.  (Is there an easy way to do this?) and last do you have a new bootstrap.dat? 

   I'd love to know how to make my own backup.  I have problem with a few different clients, and making my own would be sweet.  It isn't as simple as making a copy and renaming it?   

Safe from whose point of view?  You the user?  Or Doog the site administrator? 

For you it's safe.  It's showing that the rolls can not be manipulated in the sites favor. 

For Doog, not as safe.  If someone figured out their seed, they could in theory Clean house.   

   What do you suggest if the height is not correct.  The fork I'm on is almost 100 blocks ahead of the explorer. 

For the withdrawal crash.  This is the diag info...

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at DiceBot.JD.Withdraw(Double Amount, String Address, Int32 Counter, String SecretURL, GeckoWebBrowser gckBrowser)
   at DiceBot.cDiceBot.Withdraw()
   at DiceBot.cDiceBot.tmBetting_Tick(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1026 (RTMGDR.030319-1000)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
DiceBot
    Assembly Version: 2.5.5.0
    Win32 Version: 2.5.5.0
    CodeBase: file:///C:/Users/Bob/Bitcoin/Bots/DiceBot-2.5.5/DiceBot.exe
----------------------------------------
System.Windows.Forms
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1002 built by: RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1001 built by: RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1001 built by: RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
Geckofx-Winforms
    Assembly Version: 29.0.11.0
    Win32 Version: 29.0.11.0
    CodeBase: file:///C:/Users/Bob/Bitcoin/Bots/DiceBot-2.5.5/Geckofx-Winforms.DLL
----------------------------------------
Geckofx-Core
    Assembly Version: 29.0.11.0
    Win32 Version: 29.0.11.0
    CodeBase: file:///C:/Users/Bob/Bitcoin/Bots/DiceBot-2.5.5/Geckofx-Core.DLL
----------------------------------------
System.Core
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.233 built by: RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
Accessibility
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
----------------------------------------
System.Configuration
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1009 (RTMGDR.030319-1000)
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
----------------------------------------
System.Xml
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1026 built by: RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
Microsoft.VisualBasic
    Assembly Version: 10.0.0.0
    Win32 Version: 10.0.30319.1 built by: RTMRel
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
PresentationCore
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1009 built by: RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_32/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll
----------------------------------------
WindowsBase
    Assembly Version: 4.0.0.0
    Win32 Version: 4.0.30319.1009 built by: RTMGDR
    CodeBase: file:///C:/windows/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll
----------------------------------------

1) True
2) True - But this is 100% more use then most alt coins. 
3) False - This is straight up FUD.
4) False - There are only 500K Clams.  Your claiming the developers hold over 40% of the clams.  Another FUD Claim. 
5) I think False. 
   Currently 291K Clams have been dug.  That's 1.9% of the potential available clams.  Clams have been around about 9 months.  We need to dig another 1.7 million clams for your claim to be true.  The dig rate increase as the price increases, so maybe, if 1 Clam = 1 BTC, then we will see over 2 million clams dug. 
What was your time frame for this claim? in the next month, year, or infinity... 

seuntjie,

   Super nice bot...  I'll be sending a tip your way, any day now...

Has anyone had a problem using the auto withdrawal from Just-Dice?  I get a windows error panel when the auto withdraw fires.  It's after the withdraw happens, seems like it might have to do with dismissing the withdraw pop-up.  I reply continue and I have to X out of the with draw pop-up.  The auto-invest seems to work flawlessly.  

Also I've had the auto withdraw kick off twice, a few times.  IE when I have 110 coins I want to withdraw 4 to my offsite wallet.  So my balance should not go below 106.
I've seen it go to 102.  Only happened 2 times, out of maybe 8-10 trys.  

Also the max bet info on the stats tab, seems to be off by 1.  This is just something to look out for.  I was looking at several things, and seemed to come to that conclusion.  I don't remember how I came up with it, but I've been basing my betting on max bet -1.  

  Edit: I haven't looked at the code, but I'm assuming the calculation for max bets is using the balance and amount wagered, and it should use the balance and Total amount wagered.  Thats based off the labels in the streak table.

  Also not sure if it's noted anywhere, but the advanced bet settings do not seem to take effect until you stop and restart betting.  If your already betting and make chances they don't work.  Once you realize this everything seems to make more sense.  

    Thanks again for all of you hard work.    Bob