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

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: David Latapie on July 04, 2014, 11:09:34 PM

Quote from: StakeHunter on June 18, 2014, 09:59:25 PM

we need an exchange. my coins are sitting in cryptsy languishing...

https://www.allcoin.com/vote/#CAP
Bottlecaps is #6, keep voting! Once CAP will be adopted, let's all vote for HBN.

I was running 2.0 ntil today (did not notice the update). I am presently syncing 2.1 from start (deleted the blockchain). Before that, I had my wallet open mostly 24/7. I never receive any single stack. ( Was not necessary to delete block chain, just start up 2.1)
=> is the fact that I was on 2.0 (not 2.1) AFTER July 4th detrimental? (NO)
=> is it normal that I did not mint a single CAP ever (I have several thousand CAP)? (it depends on when you got them, and 2.0 had 1 issue with stake. 2.1 will fix you up. )
=> did is lose stacking time? Did I left my wallet open 24/7 for nothing? (You lost nothing, your coins will stake and you will get higher reward for waiting longer then 15 days.)
=> when can I expect next staking? 10 days from now or earlier? (Again depends on when you downloaded the coins. My guess is as soon as you are caught up you will stake)

Thank you.

Also, what is the maximum amount of coin I should have per address to maximise reward? On NOBL, it will be 100k, how many is it on CAP? (Cap is 1,000 max. 10k blocks are a good set to start out with. Let them split and stake for a while.)

See above

David Latapie

hero member

Activity: 658

Merit: 503

Monero Core Team

1.

Quote from: StakeHunter on June 18, 2014, 09:59:25 PM

we need an exchange. my coins are sitting in cryptsy languishing...

https://www.allcoin.com/vote/#CAP
Bottlecaps is #6, keep voting! Once CAP will be adopted, let's all vote for HBN.

2. I was running 2.0 ntil today (did not notice the update). I am presently syncing 2.1 from start (deleted the blockchain). Before that, I had my wallet open mostly 24/7. I never receive any single stack.
=> is the fact that I was on 2.0 (not 2.1) AFTER July 4th detrimental?
=> is it normal that I did not mint a single CAP ever (I have several thousand CAP)?
=> did is lose stacking time? Did I left my wallet open 24/7 for nothing?
=> when can I expect next staking? 10 days from now or earlier?

Thank you.

3. Also, what is the maximum amount of coin I should have per address to maximise reward? On NOBL, it will be 100k, how many is it on CAP?

elrapido

newbie

Activity: 57

Merit: 0

Quote from: Tranz on July 04, 2014, 10:10:56 PM

Quote from: elrapido on July 04, 2014, 10:02:31 PM

Getting mismatched coin errors now, already spent, that kind of stuff. Repairwallet brings em back, but is there any way to know how many of the coins in the wallet are actually spendable now?

I would first try to restart client with -rescan.

A more aggressive approach is to use -salvagewallet. Salvage Wallet will also remove your addresses. So be sure to export them if you need them.

There is a another rpc command -zapwallettxs but that is not in your version of CAP. If neither of the above approaches work, let me know.

Thanks, rescan reduced my coin amount by 4% but at least it should be all there. Learn a new wallet command every day

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: elrapido on July 04, 2014, 10:02:31 PM

Getting mismatched coin errors now, already spent, that kind of stuff. Repairwallet brings em back, but is there any way to know how many of the coins in the wallet are actually spendable now?

I would first try to restart client with -rescan.

A more aggressive approach is to use -salvagewallet. Salvage Wallet will also remove your addresses. So be sure to export them if you need them.

There is a another rpc command -zapwallettxs but that is not in your version of CAP. If neither of the above approaches work, let me know.

elrapido

newbie

Activity: 57

Merit: 0

Getting mismatched coin errors now, already spent, that kind of stuff. Repairwallet brings em back, but is there any way to know how many of the coins in the wallet are actually spendable now?

CrazyLoaf

hero member

Activity: 763

Merit: 534

null

choppy123

sr. member

Activity: 383

Merit: 250

I upgraded to 2.1 today and staking is working fine. All is working smoothly for me! Tongue

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: FlungSpun on July 04, 2014, 06:37:25 PM

Might have an issue over here.
One wallet with 4 blocks of 10k doesn't want to stake.

All day with no stake - 10+ hours. I know I'm unlucky sometimes but ..
Also note my weight is bigger than the network. I've seen this on HBN once or twice with big blocks staking

All four blocks should be over the 1k limit for stake by a fair margin as I was planning on moving funds but didn't this month.

When the earlier problems hit I switched machines and re-downloaded the chain, swapped out wallet on that and still no dice.....
but machines both agree with current block on http://cap.cryptocoinexplorer.com/

Please make sure you are using 2.1 Version 2.0 had an issue with large stakes.

https://github.com/Tranz5/bottlecaps/releases

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: FlungSpun on July 04, 2014, 06:37:25 PM

Might have an issue over here.
One wallet with 4 blocks of 10k doesn't want to stake.

All day with no stake - 10+ hours. I know I'm unlucky sometimes but ..
Also note my weight is bigger than the network. I've seen this on HBN once or twice with big blocks staking

All four blocks should be over the 1k limit for stake by a fair margin as I was planning on moving funds but didn't this month.

When the earlier problems hit I switched machines and re-downloaded the chain, swapped out wallet on that and still no dice.....
but machines both agree with current block on http://cap.cryptocoinexplorer.com/

The network is just jammed full of blocks right now I would expect. I have known for a while that most clients network stake weight calculations aren't accurate, I have a high stake weight as well without any stakes yet. They will come I am sure, but at this point I think that luck is a major factor.

The good news is that PoS blocks are overwhelming the PoW blocks on the chain right now. There is a big queue but it is being served quickly.

FlungSpun

sr. member

Activity: 414

Merit: 251

Might have an issue over here.
One wallet with 4 blocks of 10k doesn't want to stake.

All day with no stake - 10+ hours. I know I'm unlucky sometimes but ..
Also note my weight is bigger than the network. I've seen this on HBN once or twice with big blocks staking

All four blocks should be over the 1k limit for stake by a fair margin as I was planning on moving funds but didn't this month.

When the earlier problems hit I switched machines and re-downloaded the chain, swapped out wallet on that and still no dice.....
but machines both agree with current block on http://cap.cryptocoinexplorer.com/

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: unick on July 04, 2014, 01:06:59 PM

Quote from: flound1129 on July 04, 2014, 12:44:46 PM

Quote from: unick on July 04, 2014, 12:35:00 PM

The CP server being down and signing wrong blocks did mess up Crypsty most of all... Trades that occurred before the roll back screwed their accounting.

I'm sure everything will be fine on their end once they audit the transactions.

As far as for flound, he should be made aware of the consequences of the signing blocks when not in sync! Good job on everything Tranz, and for quickly messaging flound about this!

Live and learn Wink

It looks like this was either a deliberate attack or a misbehaving peer that caused the checkpoint server to become lagged.

If it was deliberate then the attacker got very lucky because the CP server is not configured to accept incoming connections. So it happened to connect out to that peer and then got inundated with getblocks request which caused the daemon to become lagged. So lagged in fact that only 2 peers were still connected by the time I logged into the server this morning.

I've seen this happen with other currencies and I'm pretty sure it's some kind of attack. Just a very bad time for it to occur. I was working all day yesterday on Multipool issues with our east provider so I didn't really have time to check on it. I'm going to give Tranz control of the checkpoints so that he can monitor things more closely. For now the server is turned off.

Thanks for the update, It looks like everything is back to normal

Yep lots of PoS blocks coming through. Good luck everyone that is PoS hashing, I hope I find some before you though Grin

unick

sr. member

Activity: 504

Merit: 254

Quote from: flound1129 on July 04, 2014, 12:44:46 PM

Quote from: unick on July 04, 2014, 12:35:00 PM

The CP server being down and signing wrong blocks did mess up Crypsty most of all... Trades that occurred before the roll back screwed their accounting.

I'm sure everything will be fine on their end once they audit the transactions.

As far as for flound, he should be made aware of the consequences of the signing blocks when not in sync! Good job on everything Tranz, and for quickly messaging flound about this!

Live and learn Wink

It looks like this was either a deliberate attack or a misbehaving peer that caused the checkpoint server to become lagged.

If it was deliberate then the attacker got very lucky because the CP server is not configured to accept incoming connections. So it happened to connect out to that peer and then got inundated with getblocks request which caused the daemon to become lagged. So lagged in fact that only 2 peers were still connected by the time I logged into the server this morning.

I've seen this happen with other currencies and I'm pretty sure it's some kind of attack. Just a very bad time for it to occur. I was working all day yesterday on Multipool issues with our east provider so I didn't really have time to check on it. I'm going to give Tranz control of the checkpoints so that he can monitor things more closely. For now the server is turned off.

Thanks for the update, It looks like everything is back to normal

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: flound1129 on July 04, 2014, 12:44:46 PM

Quote from: unick on July 04, 2014, 12:35:00 PM

The CP server being down and signing wrong blocks did mess up Crypsty most of all... Trades that occurred before the roll back screwed their accounting.

I'm sure everything will be fine on their end once they audit the transactions.

As far as for flound, he should be made aware of the consequences of the signing blocks when not in sync! Good job on everything Tranz, and for quickly messaging flound about this!

Live and learn Wink

It looks like this was either a deliberate attack or a misbehaving peer that caused the checkpoint server to become lagged.

If it was deliberate then the attacker got very lucky because the CP server is not configured to accept incoming connections. So it happened to connect out to that peer and then got inundated with getblocks request which caused the daemon to become lagged. So lagged in fact that only 2 peers were still connected by the time I logged into the server this morning.

I've seen this happen with other currencies and I'm pretty sure it's some kind of attack. Just a very bad time for it to occur. I was working all day yesterday on Multipool issues with our east provider so I didn't really have time to check on it. I'm going to give Tranz control of the checkpoints so that he can monitor things more closely. For now the server is turned off.

Thanks for the update. I am against checkpoint servers in general, but do agree that they have some benefits.

flound1129

hero member

Activity: 938

Merit: 1000

www.multipool.us

Quote from: unick on July 04, 2014, 12:35:00 PM

The CP server being down and signing wrong blocks did mess up Crypsty most of all... Trades that occurred before the roll back screwed their accounting.

I'm sure everything will be fine on their end once they audit the transactions.

As far as for flound, he should be made aware of the consequences of the signing blocks when not in sync! Good job on everything Tranz, and for quickly messaging flound about this!

Live and learn Wink

It looks like this was either a deliberate attack or a misbehaving peer that caused the checkpoint server to become lagged.

If it was deliberate then the attacker got very lucky because the CP server is not configured to accept incoming connections. So it happened to connect out to that peer and then got inundated with getblocks request which caused the daemon to become lagged. So lagged in fact that only 2 peers were still connected by the time I logged into the server this morning.

I've seen this happen with other currencies and I'm pretty sure it's some kind of attack. Just a very bad time for it to occur. I was working all day yesterday on Multipool issues with our east provider so I didn't really have time to check on it. I'm going to give Tranz control of the checkpoints so that he can monitor things more closely. For now the server is turned off.

unick

sr. member

Activity: 504

Merit: 254

The CP server being down and signing wrong blocks did mess up Crypsty most of all... Trades that occurred before the roll back screwed their accounting.

I'm sure everything will be fine on their end once they audit the transactions.

As far as for flound, he should be made aware of the consequences of the signing blocks when not in sync! Good job on everything Tranz, and for quickly messaging flound about this!

Live and learn Wink

cryptmebro

hero member

Activity: 786

Merit: 1000

Quote from: presstab on July 04, 2014, 10:30:08 AM

Quote from: cryptmebro on July 04, 2014, 10:22:31 AM

Quote from: Tranz on July 04, 2014, 10:19:39 AM

Quote from: cryptmebro on July 04, 2014, 10:18:50 AM

Quote from: presstab on July 04, 2014, 10:13:59 AM

Wow network stake weight is huge right now!

hmm, i thought coin age was reset with the fork . i dont have any mature coins

It was changed to 15 days start. Nothing was reset.

Thought i read that everyone was starting at day one with the fork. guess not

As far as I know it is nearly impossible to reset everyones coinage, because it would either require advanced coding, or to force everyone to send their coins in new transaction.

yeah i just misinterpreted something then.

presstab

legendary

Activity: 1330

Merit: 1000

Blockchain Developer

Quote from: cryptmebro on July 04, 2014, 10:22:31 AM

Quote from: Tranz on July 04, 2014, 10:19:39 AM

Quote from: cryptmebro on July 04, 2014, 10:18:50 AM

Quote from: presstab on July 04, 2014, 10:13:59 AM

Wow network stake weight is huge right now!

hmm, i thought coin age was reset with the fork . i dont have any mature coins

It was changed to 15 days start. Nothing was reset.

Thought i read that everyone was starting at day one with the fork. guess not

As far as I know it is nearly impossible to reset everyones coinage, because it would either require advanced coding, or to force everyone to send their coins in new transaction.

cryptmebro

hero member

Activity: 786

Merit: 1000