Bottlecaps 2.1 UPDATE REQUIRED - HARDFORK JULY 4 2014 to 200% Annual PoS

[FlungSpun]

I would like to quietly point out that in the last few moments

I GOT MY STAKE!

Many thanks for your efforts in drilling into the logic here

and while i was typing

I GOT MORE STAKE!




Your theory was bang on sir!

[unick]

I would like to quietly point out that in the last few moments

I GOT MY STAKE!

Many thanks for your efforts in drilling into the logic here

and while i was typing

I GOT MORE STAKE!




Your theory was bang on sir!

Excellent!

Hope Tranz reads this. I would love to hear is take on this

[Ense04]

I received mine as well.

[ryanb]

my CAPS last stake was on 6/28/14 on the old fork.

It has been showing that my coins will  stake within an hour for the past 2 days.

How long do i have to wait for the stake?

[FlungSpun]

I would like to quietly point out that in the last few moments

I GOT MY STAKE!

Many thanks for your efforts in drilling into the logic here

and while i was typing

I GOT MORE STAKE!




Your theory was bang on sir!

Excellent!

Hope Tranz reads this. I would love to hear is take on this

He should find it difficult to miss.

I received mine as well.

So understated, very civilised - go on, let yourself have a little woohoo 

[GoldBit89]

I haven't staked yet either despite having held coins forever now.

db.log has this

Code:

Lock table is out of available lock entries

and debug.log has this:

Code:

  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  received block 0ac317b1ecb264b379c1
  SetBestChain: new best=0ac317b1ecb264b379c1  height=527925  trust=2145786651908  date=  rocessBlock: ACCEPTED

for the db lock try this
https://bitcointalk.org/index.php?topic=241445.msg7362114#msg7362114

for mempool error, restart the client. we had a big rollback on the 4th and your client still holds old transactions in memory.

my client has been restarted multiple times after the 4th and i am using latest 2.1 client and still have those mempool errors as well as these errors : ERROR: CTxMemPool::accept() : ConnectInputs failed 4e61361746
  ERROR: FetchInputs() : 60f3a93cdc mempool Tx prev not found c03c31f9d8
  stored orphan tx 60f3a93cdc (mapsz 2).

so restarting client does not fix this issue at all.

[raskul]

I would like to quietly point out that in the last few moments

I GOT MY STAKE!

Many thanks for your efforts in drilling into the logic here

and while i was typing

I GOT MORE STAKE!




Your theory was bang on sir!

Excellent!

Hope Tranz reads this. I would love to hear is take on this

He should find it difficult to miss.

I received mine as well.

So understated, very civilised - go on, let yourself have a little woohoo 

that's like a block party but better  

[Tranz]

Hi guys. I looked at the code a bit more and Unick was right on. Old blocks would still need to age 30 days. Newer blocks would begin staking at 15 days.  The discrepancy is with the getweightfromvalue function. It assumes after the fork all blocks that are 15 days min age. But the function that actually allows stakes, would only allow coins that were sent pre fork to start at 30 days. Coins sent to wallet, or staked after the fork should begin to get min age at 15 days.

I will keep a close eye on this to make sure.

Thanks everyone..

[Tranz]

I haven't staked yet either despite having held coins forever now.

db.log has this

Code:

Lock table is out of available lock entries

and debug.log has this:

Code:

  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  ERROR: mempool transaction missing input
  received block 0ac317b1ecb264b379c1
  SetBestChain: new best=0ac317b1ecb264b379c1  height=527925  trust=2145786651908  date=  rocessBlock: ACCEPTED

for the db lock try this
https://bitcointalk.org/index.php?topic=241445.msg7362114#msg7362114

for mempool error, restart the client. we had a big rollback on the 4th and your client still holds old transactions in memory.

my client has been restarted multiple times after the 4th and i am using latest 2.1 client and still have those mempool errors as well as these errors : ERROR: CTxMemPool::accept() : ConnectInputs failed 4e61361746
  ERROR: FetchInputs() : 60f3a93cdc mempool Tx prev not found c03c31f9d8
  stored orphan tx 60f3a93cdc (mapsz 2).

so restarting client does not fix this issue at all.

If a restart doesn't help the mempool erros. You can try to restart the client with -rescan.

You can also try -salvagewallet, this is much more aggressive so please be sure you have a wallet backup and your addressed exported before attempting it.

The other errors regarding FetchInputs, are more normal errors. I get them on all clients, but they do seem to be more prevalent right now with CAPs. As more people get on the right chain and get their clients cleaned up, they should begin to diminish.

[raskul]

http://www.thescribe.eu/portfolio/ZIM_XXX_HYP.rar

in case you didn't see HYPE

[GoldBit89]

maybe a oddity:

07/08/14 01:04:08 out 1.955578
07/08/14 01:04:08 trying connection 46.164.247.229:7685 lastseen=5.5hrs
07/08/14 01:04:08 AddToWallet dcd74bab3a  new
07/08/14 01:04:08 WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
07/08/14 01:04:08 NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
07/08/14 01:04:08 updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
07/08/14 01:04:08 NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"07/08/14 01:04:08 WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

[unick]

maybe a oddity:

07/08/14 01:04:08 out 1.955578
07/08/14 01:04:08 trying connection 46.164.247.229:7685 lastseen=5.5hrs
07/08/14 01:04:08 AddToWallet dcd74bab3a  new
07/08/14 01:04:08 WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
07/08/14 01:04:08 NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
07/08/14 01:04:08 updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
07/08/14 01:04:08 NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"07/08/14 01:04:08 WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

this is just an old reference in the debug outputs.

you should indeed read cap there

[raskul]

central caverns facebook page updated  Grin please mine your Bottlecaps with us
Website|http://www.centralcavern.uk
NOMP|http://eu.centralcavern.uk:8080
Facebook|https://www.facebook.com/coincount?ref=tn_tnmn
Forum Thread|https://bitcointalk.org/index.php?topic=676478.msg7661479#msg7661479
Bottlecaps|http://cap.centralcavern.uk/index.php?page=dashboard
HoboNickels|http://hbn.centralcavern.uk/index.php?page=dashboard
BTC P2Pool (Amsterdam)|http://eu.centralcavern.uk:9332/static/
VTC P2Pool (Amsterdam)|http://eu.centralcavern.uk:9171

[GoldBit89]

maybe a oddity:

  out 1.955578
  trying connection 46.164.247.285 lastseen=5.5hrs
 ddToWallet dcd74bab3a  new
  WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
  NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
  updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
  NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"  WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

this is just an old reference in the debug outputs.

you should indeed read cap there

Meaning this is just a display overlook in the debug section? Or is it a client wide internal overlook (meaning i thought that the debug section was just that a debug of the whole client and more)?

[Tranz]

maybe a oddity:

  out 1.955578
  trying connection 46.164.247.285 lastseen=5.5hrs
 ddToWallet dcd74bab3a  new
  WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
  NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
  updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
  NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"  WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

this is just an old reference in the debug outputs.

you should indeed read cap there

Meaning this is just a display overlook in the debug section? Or is it a client wide internal overlook (meaning i thought that the debug section was just that a debug of the whole client and more)?

Just 2 lines of code.

And now it is updated! 

https://github.com/Tranz5/bottlecaps/commit/06b92fd3e7de615c930d5781a70b9ff70bacb406

[Tranz]

Yep. Confirming v2.1 works for me.  Thanks for all your work on this Tranz.  I see a lot of improvements since v1.52.

The only issue I'd like to report is a highlighted message at the top of the Overview page stating that "Info: Minting suspended due to locked wallet" when in fact the wallet is unlocked and staking.

Thanks I actually meant to remove that, as we now have the staking icon.

Removed this message.
https://github.com/Tranz5/bottlecaps/commit/3cd7486ddc2df829583b01671b76f26bc667b314

[GoldBit89]

maybe a oddity:

  out 1.955578
  trying connection 46.164.247.285 lastseen=5.5hrs
 ddToWallet dcd74bab3a  new
  WalletUpdateSpent found spent coin 0.986359nvc 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8
  NotifyTransactionChanged 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 status=1
  updateWallet 2229d4160d497111400c1f2a69fa537e1a6f2f6b7b4267db16ca6c09286a5ba8 1
  NotifyTransactionChanged dcd74bab3a8991ef220e68ca2662722b75ea0d113fbca5302a9f03ddcdf35c03 status=0

"  WalletUpdateSpent found spent coin 0.986359nvc "

this just happened like 2 hours ago my time- nvc?

this is just an old reference in the debug outputs.

you should indeed read cap there

Meaning this is just a display overlook in the debug section? Or is it a client wide internal overlook (meaning i thought that the debug section was just that a debug of the whole client and more)?

Just 2 lines of code.

And now it is updated! 

https://github.com/Tranz5/bottlecaps/commit/06b92fd3e7de615c930d5781a70b9ff70bacb406

You rock  Tranz !! Keep up the great work. Thank you.

[raskul]

only paying bounties to bottlecaps miners
https://bitcointalk.org/index.php?topic=676478.msg7661479#msg7661479

[eBit]

Cryptsy CAP wallet is back online for deposits/withdrawals.  Humpty Dump(ty) if you must.

https://www.cryptsy.com/markets/view/53

[raskul]

Cryptsy CAP wallet is back online for deposits/withdrawals.  Humpty Dump(ty) if you must.

https://www.cryptsy.com/markets/view/53

hooray for the dumpers!