Pages:
Author

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

hero member
Activity: 526
Merit: 500
Its all about the Gold
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)?
sr. member
Activity: 434
Merit: 250
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
sr. member
Activity: 504
Merit: 254
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
hero member
Activity: 526
Merit: 500
Its all about the Gold
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?
sr. member
Activity: 434
Merit: 250
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
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://bitcointalksearch.org/topic/m.7362114

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.
legendary
Activity: 1540
Merit: 1060
May the force bit with you.
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..
sr. member
Activity: 434
Merit: 250
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!

Cheesy


Your theory was bang on sir!

Excellent! Smiley

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

He should find it difficult to miss.


I received mine as well. Smiley

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

that's like a block party but better  Grin
hero member
Activity: 526
Merit: 500
Its all about the Gold
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://bitcointalksearch.org/topic/m.7362114

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.
sr. member
Activity: 414
Merit: 251
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!

Cheesy


Your theory was bang on sir!

Excellent! Smiley

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

He should find it difficult to miss.


I received mine as well. Smiley

So understated, very civilised - go on, let yourself have a little woohoo 
legendary
Activity: 1148
Merit: 1000
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?
full member
Activity: 145
Merit: 100
I received mine as well. Smiley
sr. member
Activity: 504
Merit: 254
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!

Cheesy


Your theory was bang on sir!

Excellent! Smiley

Hope Tranz reads this. I would love to hear is take on this Wink
sr. member
Activity: 414
Merit: 251
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!

Cheesy


Your theory was bang on sir!
full member
Activity: 216
Merit: 100

EDIT: @PressF1, do you know how old were your blocks when they staked?

Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:

Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.

so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.

One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.


  

I was asking in order to support my theory, were you about at 30 days of age, or more ?

Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur.

I guess the only other thing that needs confirming (I think I have seen this on the explorers already)
Is that stakes that should be receiving more than the cap are being pegged back to 1k and not ignored or rejected
obviously my blocks would have got significantly more than 1k but I am expecting 1k exactly per block

I've had a 5k block of exactly 46 day old, got 1000 CAP on the 4th. if there was no cap, I would of seen 1260 CAP.  if it had a bug, I wouldn' t have seen anything. so I can confirm everything runs smooth.

There is just this mid min/max range threshold before staking that bugs me

I have seen the 1000 max stake at work as well in the BC. So I guess that's fine. I looked more closely to my stakes and made more precise calculations and must come to the conclusion that my observed minimum is a little larger than earlier estimated: 35 days, never less.
sr. member
Activity: 504
Merit: 254

EDIT: @PressF1, do you know how old were your blocks when they staked?

Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:

Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.

so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.

One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.


  

I was asking in order to support my theory, were you about at 30 days of age, or more ?

Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur.

I guess the only other thing that needs confirming (I think I have seen this on the explorers already)
Is that stakes that should be receiving more than the cap are being pegged back to 1k and not ignored or rejected
obviously my blocks would have got significantly more than 1k but I am expecting 1k exactly per block

I've had a 5k block of exactly 46 day old, got 1000 CAP on the 4th. if there was no cap, I would of seen 1260 CAP.  if it had a bug, I wouldn' t have seen anything. so I can confirm everything runs smooth.

There is just this mid min/max range threshold before staking that bugs me
sr. member
Activity: 504
Merit: 254

EDIT: @PressF1, do you know how old were your blocks when they staked?

Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:

Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.

so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.

One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.



I was asking in order to support my theory, were you about at 30 days of age, or more ?

Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur.

Ok thanks, it's good to know.

so far it looks like what I observed on GrowthCoin, no stake was generated under 9 days there.

I'll keep an eye on the 33 days minimum. So I guess if flungspun doesn't get his stake around 6pm tonight... then the next target to look for would be around 33 days.

It would be good to know if anyone can report a stake before 30 days (or near the minimum age)
sr. member
Activity: 414
Merit: 251

EDIT: @PressF1, do you know how old were your blocks when they staked?

Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:

Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.

so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.

One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.


  

I was asking in order to support my theory, were you about at 30 days of age, or more ?

Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur.

I guess the only other thing that needs confirming (I think I have seen this on the explorers already)
Is that stakes that should be receiving more than the cap are being pegged back to 1k and not ignored or rejected
obviously my blocks would have got significantly more than 1k but I am expecting 1k exactly per block
full member
Activity: 216
Merit: 100

EDIT: @PressF1, do you know how old were your blocks when they staked?

Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:

Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.

so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.

One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.


  


I was asking in order to support my theory, were you about at 30 days of age, or more ?

Yes all the blocks that staked were older than 30 days. 33 days is observed minimum. I must add that most of my blocks are quite old though. If I don't forget I'll let you know when stakes < 30 days occur.

EDIT: I get where you're going. Maybe somewhere in the code the original 30 days minimum was not reset to 15 days.

sr. member
Activity: 504
Merit: 254

EDIT: @PressF1, do you know how old were your blocks when they staked?

Not exactly but more or less i do, cause the older they are the more stake they produce, combine that with the amount staking and you can get an idea of their coinage:

Say your block is 100 cap at day 15 it has a weight of 0 and a stake percentage of 8.3%
At day 30 weight is 1500 (1 per cap per day) with a stake percentage of 16.6% and so on.

so if your block of 100 produces a stake 17 you know it's age must have been 30days=1500 weight
In this example the yearly pos rate is 200%. If it gets lower you should take that in account.

One thing I don't take in account is max of 45 days in caps case. Then probably the weight isn't getting larger anymore so no need for complex calculations anymore. Haven't observed this though, so not sure about that.


  


I was asking in order to support my theory, were you about at 30 days of age, or more ?
Pages:
Jump to: