Correct. Right now it will allow you to set the split/combine threshold using startup/config switches. Default is split nothing below 5 and combine if possible up to 20. It can be set to a max of splitthreshold of 10 and combine of 40.
I will allow these to increase for future, but based on wallet size and once the hard fork takes effect.
Thousand, right? Blocks of 40 HBN seem very small. No 40. Blocks of 40 stake fairly quickly. And the QT can easily handle thousands of them with ease. I will be increasing them in the future. For now a user, if they know how, can simply change the code and re-compile it, or they can combine manually. Is this a usable feature at the moment? I would love to not have to do this manually. Yes it is on by default in version 1.5, and can be increased by the start up switches. You can check the current thresholds by clicking network->Current Pos Info or clicking the staking arrow. This will be fully integrated into RPC and the GUI in the time frame noted above. |
|
|
|
Correct. Right now it will allow you to set the split/combine threshold using startup/config switches. Default is split nothing below 5 and combine if possible up to 20. It can be set to a max of splitthreshold of 10 and combine of 40.
I will allow these to increase for future, but based on wallet size and once the hard fork takes effect.
Thousand, right? Blocks of 40 HBN seem very small. No 40. Blocks of 40 stake fairly quickly. And the QT can easily handle thousands of them with ease. I will be increasing them in the future. For now a user, if they know how, can simply change the code and re-compile it, or they can combine manually. |
|
|
|
Guys lets stop with the aggression please. Silver you made your point, you don't like digital, please don't take it out on the rest of the community. Crazyloaf I don't know why you felt the urge to post in this thread but please just leave it, calling people crazy is just purposefully attempting to stir people up. Hilux we don't need to be attacking other peoples coins, Caps and Hyp actually have a good development relationship and we don't want to change that.
If possible could we ignore any more negative comments and concentrate on getting some development done. Development of CAP is what this thread is about and is what will get more people interested in CAP not responses to posts that aren't contributing. After this post I won't be responding to comments unrelated to CAP development and I urge others to do the same( pm if you want we can chat there).
To start off in this light, I have contacted someone to do a Chinese translation of the CAPS thread(for a bounty), we might want to open up talk about what we would like to include in the translation? Just the ANN post? I was thinking of a small easy to understand guide about how CAP works and its 200% interest component. Maybe also we could get a newbie guide sorted on how to set up a wallet easily.. so what we should include?
Thank you James well said. I agree with this especially with the point of attacking other coins. There is absolutely no need for it. HYP is doing quite well and I am a large holder of it. I have also contributed to the development in the past and will so in the future as well. I wish it a long and fruitful life. Even other coins which maybe a bit more controversial, there is still no need to attack. Just let it be. Tit for Tat exchanges rarely offer anything more then spam. In this regard I also agree that ignoring them is the best stagey. I personally don't use the ignore function, as I will take any and all information, even if it is obvious propaganda. Some may tire and go away, others will just continue to stir up the pot. If it truly gets out of hand, we can move to a moderated thread. But truthfully each person's opinion is a valid as the next, even if I don't agree with it. Regarding the translation. I think the OP and a quick FAQ guide regarding staking and QT functionality is a great idea. It would also be nice to get more QT translations available as well. I can offer a method for doing it(perhaps not the best), but not the actual translation itself. |
|
|
|
Any chance of getting the set stake split and s4c options? I leave my wallet open 24/7 without an issue but would like to have the wallet automatically recombine if it can't create 2 blocks of X size.
We've been discussing this earlier and the plan was to make the split threshold not fixed but depended on wallet size. That way the more you own the higher this threshold. So every coin you gain will improve the minimum size of your blocks and thus improve your staking performance. It would motivate to hold and buy in stead of sell and leave and it would eliminate the need for manual recombination at the same time. More people, especially the one's who control the big wallets would probably be the one's finding themselves without a need for manual recombination and let their wallet just stake 24*7 securing the network even better that way. How exactly this will be done and tuned is still open for discussion as far as I know. I've have some idea's for whenever we have to decide what it's going to be, but for now that not too relevant I think. Correct. Right now it will allow you to set the split/combine threshold using startup/config switches. Default is split nothing below 5 and combine if possible up to 20. It can be set to a max of splitthreshold of 10 and combine of 40. I will allow these to increase for future, but based on wallet size and once the hard fork takes effect. |
|
|
|
|
I have opened a ticket on Cryptsy alerting them to the new version, and a quick how-to for updating. I have asked them to give me 24 hours notice before they do the upgrade, so I can let all of you know. Not sure if they will do that but I thought I would ask.
Once/if I hear that this is complete, I will let everyone know.
|
|
|
|
block size should be 10,000 coin effective Jan?
10,000 would hit the max after it matures, yes. 9,000 would be better, as it would give you a few days to stake before the max is reached. If you plan to only open the wallet less frequently, I would use smaller block sizes. The wallet and network are extremely effective at staking, and allowing blocks to split and combine automatically would give you the max yearly PoS percentage and requires almost no work. I keep my wallet into 2000+ inputs. About 100 block sizes. It uses about 1 out of 4 of my cores, but it stakes 24/7 without me doing anything. I never worry about max cap, I never have to worry about splitting and combining. It just works! |
|
|
|
Guys don't you think that 100% stake for 1 year is it to much?
No. Could be better at a higher level (200% like Bottlecaps). 100% is the standard set out originally, and will remain constant. PoS has to have enough incentive for holders to open wallets frequently. There are plenty of lower % PoS coins for you to buy, if you think that is the way to go. Also remember 100% is degrading over difficulty. By adding the 250 max cap, it will also give people more reason to open the wallet, which will create more blocks and potentially lower the inflation rate a bit. I had suspected we would be in the 95-99% range by now. But still closer to 99-100% still. But inflation is holding very steady! See the yearly money supply chart here. http://hobonickels.info/charts.php |
|
|
|
1.5 introduces the 250 max stake right? Friday night math doublecheck...we should make sure blocks are <10,000 so as to not hit the stake ceiling?
I noticed this "250" in OP...I thought that we been talking about 500? Initially we discussed 500. I did some math after looking over the block chain and trying to figure out what was best for both the network, users and inflation rate. 250 seemed a bit better. Based on what I see on the block chain. 99% of stakes are already well below this mark. |
|
|
|
who's the PR person for this coin ?
There is no specific PR person for this coin. But the community is here to answer any questions you may have. How can we help you? Greeting Tranz, I know of your avatar from Hobonickel I'm here to offer our FREE services, we will publish any good news that you have to share about your coin. If you have an article, or press release that you want published just let us know. A link in my sig will bring you to our forum post with detailed info. Great thanks. If anyone is up for writing an article for CAPs, that would be great. I'll be happy to proof it before it is submitted. Thanks! |
|
|
|
who's the PR person for this coin ?
There is no specific PR person for this coin. But the community is here to answer any questions you may have. How can we help you? |
|
|
|
Thank you, for great job! Did I understand correctly that I need delete old blockchain and download new? You only need to do this if you are coming from version 1.4.0.0 or lower. If you use 1.4.0.1 or greater there is no need. It should be a simple exe change. If you do need to do this. A downloaded block chain and index is available to help speed up the process. http://www.mediafire.com/download/y5y9au1f5doxt5d/HoboBlockChain10-12-14.zipOtherwise just remove the blk001.dat and txleveldb and re-download from peers. Or remove txleveldb and rename blk0001.dat to bootstrap.dat. This could also speed up the process. |
|
|
|
|
Hey guys can we keep the in fighting to a minimum? Just take it to PM please.
Thanks..
|
|
|
|
Hey thanks a lot for the answer I will check out your guide and follow it. so did you cross compile from 12.04 ? anyhow i will try this, i'm sure i can inch my way towards getting this going. If i do have success i may try to make a "for dummies" version of these , CAPs and HBN again cheers for the response. maybe my problem was a dependencies one? - the Pi is a B+ but it is still ARM and 32Bit - [/quote] No I didn't cross compile. I compiled on the Pi. It takes a while, but it worked out. Hard to say what your error exactly was, do you have a full log? |
|
|
|
Hi Tranz + Caps HNB lovers. : D Any way to get Caps/HBN going on a Ras Pi? I think because it uses QT5 that is the prob Ras Pi is ARM 32 Bit but Peercoin will compile as per here : http://www.ppcointalk.org/index.php?topic=186.msg572#msg572however error i get is : Qmake error : unknown widgets Which i guess means "Wrong fucking qt chump!" Pi seems to have had qt5-dev etc in its apt-get but it seems to have been pulled?? any solutions ? - getting CAPs and HBN into Pi could well help engagement as a PoW/PoS hybrid. Cheers. Hey DI. I have have compiled the daemon to run on Pi about a year ago for HBN. See this thread https://cryptocointalk.com/topic/8233-pihobonickels/ It runs pretty good, but the memory required for HBN are tough. If you are referring to a QT version I haven't tried it so I am not sure. But I can tell you that HBN and pretty sure CAPs are both QT 4 and 5 compatible. I'll have to test CAPs for sure on my 12.04 Ub system. But I know for sure it works for HBN, and the code base is very close. If there is a specific error it can be corrected no problem. |
|
|
|
Not much, I just need the ability to clone myself. Send one off to work, one to work on crypto and one to keep the kids from killing each other!  Got an 8yo and twin 5yo's...Two words - Perler Beads; ever 30-60 minutes you may have to melt plastic with the iron but outside of that, peace. Pretty much in the same boat, but Irish twins of ~ the same age.
As far as I know the skin-thing was only once suggested and considering the fact that you don't have ample time I'd say lets get a new 2.3 version out with the updates you mentioned and leave it there for now. I can only speak for myself but I am perfectly happy with the way it looks already.
And that way you can also just focus on programming the HBN fork which probably is quite time consuming as well.
Fork for HBN is close to complete, running it through testing now.. I think I can do the things I mentioned for 2.3 for caps and also look to add the skin ability. Most likely an early Christmas present. |
|
|
|
I would like to write a small simple program in VB that can query the HBN network to check for the current work difficulty. Is there an easy way to do that?
If you are running the hbn deamon you can use the rpc command getdifficulty. Otherwise you could try the CCE api call http://www.cryptocoinexplorer.com/apimany need crutches )) for example: 1. cold start the daemon -> demon few minutes unresponsive rpc 2. no simple command - "staking work ?" ... The demon may take a few minutes to start up. But if you are using it for something all the time you wouldn't shut it down. getdifficutly shows both. 09:39:46  getdifficulty 09:39:46  { "proof-of-work" : 24.06406389, "proof-of-stake" : 0.00390625,"search-interval" : 0 } it is not something and does not reflect the real state of the client with an outdated database Well that is true, you have to be connected to the network to get the current difficulty. But if you are running the client you should be up to date. |
|
|
|
|
Show Posts
