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

[Woody20285]

Tranz made a change in HBN to make the split threshold to 2500.  Let's hope he does the same for cap...

Nice. Considering the total number of coins the split treshold should be atleast 7500 for bottlecaps. This small change would make it much easier to stake. Hope Tranz have some time for caps soon. 

I would agree... but 2500 would be an improvement over what it is now... 5000 or 7500 would be great...  automation of everything leaves people, myself included, to just leave the wallet open all the time.

Try putting splitstaketheshold=7500 into .conf file

[rdcpsi]

Tranz made a change in HBN to make the split threshold to 2500.  Let's hope he does the same for cap...

Nice. Considering the total number of coins the split treshold should be atleast 7500 for bottlecaps. This small change would make it much easier to stake. Hope Tranz have some time for caps soon. 

I would agree... but 2500 would be an improvement over what it is now... 5000 or 7500 would be great...  automation of everything leaves people, myself included, to just leave the wallet open all the time.

Try putting splitstaketheshold=7500 into .conf file

Which isn't going to help with Bottlecaps.

From memory the relevant switches in Bottlecaps are splitthreshold and combinethreshold.
The limits of these depend on where they are set, which is slightly mad.
In the .conf or command line the max is (IIRC) 200/400 whilst via the RPC is walletbalance/500 and walletbalance/250 respectively.
So to set these to maximum you would need to type into the debug window,

splitthreshold 9999999999

and

combinethreshold 9999999999

And repeat every time you restart the wallet. Alternatively you could have a script that sends the RPC commands at start up.

[Woody20285]

Which isn't going to help with Bottlecaps.

From memory the relevant switches in Bottlecaps are splitthreshold and combinethreshold.
The limits of these depend on where they are set, which is slightly mad.
In the .conf or command line the max is (IIRC) 200/400 whilst via the RPC is walletbalance/500 and walletbalance/250 respectively.
So to set these to maximum you would need to type into the debug window,

splitthreshold 9999999999

and

combinethreshold 9999999999

And repeat every time you restart the wallet. Alternatively you could have a script that sends the RPC commands at start up.

Thanks for the correction.

[vancefox]

Which isn't going to help with Bottlecaps.

From memory the relevant switches in Bottlecaps are splitthreshold and combinethreshold.
The limits of these depend on where they are set, which is slightly mad.
In the .conf or command line the max is (IIRC) 200/400 whilst via the RPC is walletbalance/500 and walletbalance/250 respectively.
So to set these to maximum you would need to type into the debug window,

splitthreshold 9999999999

and

combinethreshold 9999999999

And repeat every time you restart the wallet. Alternatively you could have a script that sends the RPC commands at start up.

Thanks for the correction.

And after every stake... because it'll increase your max threshold.

[bitmaster1x]

Which isn't going to help with Bottlecaps.

From memory the relevant switches in Bottlecaps are splitthreshold and combinethreshold.
The limits of these depend on where they are set, which is slightly mad.
In the .conf or command line the max is (IIRC) 200/400 whilst via the RPC is walletbalance/500 and walletbalance/250 respectively.
So to set these to maximum you would need to type into the debug window,

splitthreshold 9999999999

and

combinethreshold 9999999999

And repeat every time you restart the wallet. Alternatively you could have a script that sends the RPC commands at start up.

Thanks for the correction.

And after every stake... because it'll increase your max threshold.

What threshold you put in, it just gives you a different one. Someone mentioned that the threshold goes up as the amount you have goes up.

[vancefox]

Which isn't going to help with Bottlecaps.

From memory the relevant switches in Bottlecaps are splitthreshold and combinethreshold.
The limits of these depend on where they are set, which is slightly mad.
In the .conf or command line the max is (IIRC) 200/400 whilst via the RPC is walletbalance/500 and walletbalance/250 respectively.
So to set these to maximum you would need to type into the debug window,

splitthreshold 9999999999

and

combinethreshold 9999999999

And repeat every time you restart the wallet. Alternatively you could have a script that sends the RPC commands at start up.

Thanks for the correction.

And after every stake... because it'll increase your max threshold.

What threshold you put in, it just gives you a different one. Someone mentioned that the threshold goes up as the amount you have goes up.

Right... it only goes up if you set the threshold higher after your balance goes up.  It does not go up automatically.

[sacskate]

can someone provide a bootstrap or active nodes? Thanks!

[almightyruler]

can someone provide a bootstrap or active nodes? Thanks!

# coin: bottlecaps
addnode=62.210.122.161
addnode=82.200.205.30
addnode=118.102.74.85
addnode=85.25.197.148
addnode=188.165.235.208
addnode=185.57.31.152
addnode=5.103.138.97
addnode=24.178.175.192
addnode=188.241.58.126
addnode=74.118.192.18
addnode=62.64.86.44
addnode=69.181.165.105
addnode=212.92.104.85
addnode=69.197.188.186
addnode=99.237.62.103
addnode=212.237.21.74


HTH.

[vampirus]

CAP need hardfork.
1. Reduce max PoS reward from 1000 to 500 to reduce inflation.
2. Fix PoS rate to 200% instead of floating rate as now 1-200%
3. Change retarget rules to prevent percentage cheating.
4. Remove PoW mining.

If all agree, I can take over code development.

[Spidersbox]

I like mining caps.
maybe reduce % to 50% or even 25% ??
and get rid of max pos reward.

[vampirus]

I like mining caps.
maybe reduce % to 50% or even 25% ??
and get rid of max pos reward.

CAP with 50% = PHS - not very popular.
CAP with max pos reward = HYP - very popular.
No max PoS reward = not match blocks an little difficulty = ease fork and double spend.

[Spidersbox]

just a thought 

[ReydeApio]

I came to crypto through mining and have always appreciated the notion that anyone with a machine fast enough to play most modern AAA games can setup a Scrypt miner and attempt to grab some blocks. I dont see the flash mining in conjunction with Coinmarketcap rankings as an issue with CAPs and the solution around alternating between PoW and PoS that's been going on in HBN is an interesting solution to flash mining.

I'm having difficulty seeing the upside of removal of max CAPs per block cap, and PoW.

With PoS only the argument by luminaries remains 'Rich get richer' https://youtu.be/3W_3AQrQEOM?t=130 I've seen days where multiple large addresses are staking, and driving down the percentage, when a miner comes in and swipes most of the next 100 blocks - always makes me smile. The variable stake has kept the percentages well below 200% in the past year and like the richlist of most other PoW/PoS coins there is a noticeable pareto distribution.

What would the supply look like if we had a fixed 200%? 2x - 3x higher? What's the theoretical market cap of 386,208,048 - 579,312,072 Million CAPs circulating? I'm not sure making the growth Bottlecaps easier benefits the currency in any game theory scenario.

The uncapping of stake makes sense if there is a shift of staking into tiers - e.g, a 'master node' locks down 100k caps and stakes at x% every y# days with no max, a regular wallets stake less at shorter intervals with a max.

A little crypto-Bikeshedding is fun but with nobody helping Tranz code, nothing changes.

[ReydeApio]

CAP need hardfork.
1. Reduce max PoS reward from 1000 to 500 to reduce inflation.
2. Fix PoS rate to 200% instead of floating rate as now 1-200%
3. Change retarget rules to prevent percentage cheating.
4. Remove PoW mining.

If all agree, I can take over code development.

I'm not looking for any of the above changes but maybe if you setup yes/no voting addresses CAP's holders can send some cap to vote. If you can get some 'yes' votes that carry the weight of the address sending the vote maybe there is some interest in the community.

[shtako]

CAP need hardfork.
1. Reduce max PoS reward from 1000 to 500 to reduce inflation.
2. Fix PoS rate to 200% instead of floating rate as now 1-200%
3. Change retarget rules to prevent percentage cheating.
4. Remove PoW mining.

If all agree, I can take over code development.

1. You want to reduce inflation.
2. You want to increase inflation.

Can you explain why this is a better solution?

3. What is percentage cheating?

4. Is there enough people POS mining for this to be sustainable with the minimum 14 days coin age?

Can you please share a little more details about what you would like to do?

[vampirus]

CAP need hardfork.
1. Reduce max PoS reward from 1000 to 500 to reduce inflation.
2. Fix PoS rate to 200% instead of floating rate as now 1-200%
3. Change retarget rules to prevent percentage cheating.
4. Remove PoW mining.

If all agree, I can take over code development.

1. You want to reduce inflation.
2. You want to increase inflation.

Can you explain why this is a better solution?

3. What is percentage cheating?

4. Is there enough people POS mining for this to be sustainable with the minimum 14 days coin age?

Can you please share a little more details about what you would like to do?

Summary 1 and 2 keep inflation as now.
Fixed PoS rate reduce CPU load, and user not need wait low difficulty to start mining.
3. One of node 62.210.122.161 have wrong time (-1 hour ) and affect to other wallets (you can't PoS minting or difficulty go down)
Also someone can increase PoS rate to 200% get stake and then reduce to 100-130% for others.

[Hilux74]

I vote No to any of the proposed changes.

The core functionality of CAPs is fine as it is.  The current 200% max; variable with difficulty along with the maximum stake reward/block functions just fine.

The only complaints against Bottlecaps with any type of regularity are that the wallet uses too much resources.  Any development should focus on this type of improvement not on changing the fundamentals.

Also, even though the current split/combine thresholds were set by Tranz at the low value levels for a valid reason no one typically leaves there blocks at these sizes and consequently spend a lot of time in coin control managing their block sizes (ie most people manually make their blocks in the 5000-6000 range).  I think for user 'quality of life' having these values be able to be set at whatever a user wants easily would be a nice change.  I changed these for myself in the source code and as a result just leave my wallet running 24/7/365 never having to even bother with the hassle/waste of time of managing blocks in coin control...it's great.

[vampirus]

When you vote yes or no please let us know how much CAP you have.
I have 10M.

[FlungSpun]

I vote No to any of the proposed changes.

The core functionality of CAPs is fine as it is.  The current 200% max; variable with difficulty along with the maximum stake reward/block functions just fine.

The only complaints against Bottlecaps with any type of regularity are that the wallet uses too much resources.  Any development should focus on this type of improvement not on changing the fundamentals.

Also, even though the current split/combine thresholds were set by Tranz at the low value levels for a valid reason no one typically leaves there blocks at these sizes and consequently spend a lot of time in coin control managing their block sizes (ie most people manually make their blocks in the 5000-6000 range).  I think for user 'quality of life' having these values be able to be set at whatever a user wants easily would be a nice change.  I changed these for myself in the source code and as a result just leave my wallet running 24/7/365 never having to even bother with the hassle/waste of time of managing blocks in coin control...it's great.

I'd agree with that

Coin control split-block .
goodness even a sum of value when you filter the transactions list.
First things first before we screw with things that aint broke.

-- Holding .. more than enough that it feels obnoxious to shout about.

[paramind22]

The wallet needs to be recompiled at least so it doesn't use so much resources.  It's one of the most resource-hungry wallets in use.  Can you change it to be less resource hungry?