one of coolest scrypt coins IMO  Thanks, I agree!  |
|
|
|
from a reward perspective its seems like a "fire and forget" type aspect as growth is increasing?
I agree, many people work very hard to combine, split, start and stop the wallet. I rather just turn it on and let it do its thing. It seems to do it well! Overall I am pleased with the growth of the money supply, the users, and the price. |
|
|
|
Does anyone know the RPC command for CAP's version of stake4charity/autosaving? Thanks It is autosavings. "help" will give you all rpc commands. autosavings <BottleCapsaddress> <percent> [min amount] [max amount] Also version 2.2 is available which has it embedded in the gui. ha - red face from me i missed this totally - Tranz I have a couple of generic questions for you before I add this to my "Oracle investment journal." I will Pm you its very general info. Cool. Let us know when it is complete! |
|
|
|
Yes it is a windows 7 PC. I usually turn windows updates off. They can be trouble. I have not seen an update run on this pc in many months.
Ok usually these type of issue happen when the wallet suddenly gets shut off either via update, or power failure. Unusual to have it happen while the wallet was running. Don't think I have seen that. |
|
|
|
Well my friend, good news at last! The second pass worked I deleted everything but the two blockchain files. I ran salvage wallet twice. The wallet has finally passed the bad block. Man I am feeling good. Let me know if you need anymore testing as I now have a test setup and can do testing for you whenever you may need it.
I learned a lot in this adventure.
Glad to hear it. Follow up question; Was your computer(win 7?) recently updated and rebooted, while HBN was running? |
|
|
|
Actually one note to mention right now. The wallet is not working on both PCs. It has been down for 3 days now. I have also tried 1.4.8 1.4.7 and 1.4.0 all fail at the same point.
Okay, trying the experiment right now. I am using the golden 9-16 files I got from you. I have removed the database directory as well. I started from DOS prompt using the -salvagewallet command. I will let you know when the test finishes.
1st pass failed at the same spot I will try one more time with total refresh of files.
[/list] Could also try this. Remove database, use 9-16 block files, rename wallet.dat to noloadwallet.dat. This will create a new fresh wallet. If it syncs rename noloadwallet.dat to wallet-old.dat and use the load wallet function. |
|
|
|
My bank doesn't even pay 1%  I like this demand driven change in the PoS rate. I don't understand what happened over at TEK 100%, but since I'm assuming that more CAP'pers leave their wallets open to stake since they have more blocks due to the max block reward in place, this has been a gradual versus sporadic thing in CAP. For example, I got a 40% TEK stake recently after getting around 20% stakes on the 31st, and now there are reports of a 5% one, but I don't know how true that is. I think TEK should probably move over to a max block reward of some sort like CAP since it will only make the network stronger and any rate changes smoother for wallets to be open as often as possible. Fact is, the demand for CAP staking is greater atm, hence the lower the rate that needs to be paid to entice people to stake. If they don't like it, they can stop staking, sell, and see where demand and, as a result, the stake difficulty go. High PoS coins are demand-driven financial assets that price their prospective rate themselves This is some spooky stuff here; SkyNet is next  This is basically my thoughts as well. I think it is good and working as designed, perhaps a tweak or two in the future, but nothing for sometime. I just wanted uses to be aware.. |
|
|
|
Sexy; thank you I'll check it out in HBN later and if TEK doesn't have this, it needs it posthaste! Every code change is completely public, and available for review, copy, enhancements, whatever. I never release wallets from hidden source, unless expressly told. If someone wants to use the work I do, it's there for their enjoyment! |
|
|
|
Also, that's a nice spec command in CAP. What's the RPC call for it and does any other coin have that? TEK and others definitely need it since it saves on the maths for figuring it out alone.
HBN had it first.  A few other coins may have it as well now. I think GRW and maybe TRK but not sure... That is from the gui. Just click on the network->Current PoS Info. Or click the Staking Icon. The RPC command is getmininginfo 20:44:29

getmininginfo
20:44:29
{
"blocks" : 653796,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 13.33697954,
"errors" : "",
"netmhashps" : 397.79090942,
"netstakeweight" : 373753.01621724,
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"stakeweight" : {
"minimum" : 0,
"maximum" : 0,
"combined" : 0
},
"pooledtx" : 3,
"stakeinterest" : 1860000
"testnet" : false
}
|
|
|
|
Since I saw this was an issue with TEK, although the coin was changed without much discussion, I did want to get out in front of it here, ahead of any complaints. The good news is people are staking wonderfully on the CAP network. Last 1000 blocks like 80-90% are being carried by PoS. This is great! The news is, this is also causing the PoS difficulty to increase. Great for network security, and inflation, but not so good for high yield investment. The bad news (albeit not unexpected) is the staking percentage is lowering, as per the coding requirements, and is sitting at 180-190% per year, currently. ---------------------------
BottleCaps - Extended Staking Information
---------------------------
Client Version: v2.2.0.0-ge1d17f0-Caps2.0
Protocol Version: 70004
Current Wallet Version: 60000
Last PoS Block Number: 653706
Last PoS Block Time: Thu Sep 25 19:46:54 2014
Current PoS Difficulty: 0.00557616
Current PoS Netweight: 450936
Current PoS Yearly Interest: 183%
Wallet PoS Weight: ??
Auto Savings Address: ??
Auto Savings Percentage: 50
Network Money Supply: 6224107.386502 CAP
---------------------------
OK
---------------------------
I am not suggesting and won't do anything rash. I am actually good with it, as it stands right now. I would like a lot more data to analyze before any change is made. At least another 6 months to 1 year. Looks like the staking is starting to slow down, so the difficulty should lower soon. But if we want to discuss changing this at some point, please feel free. Thoughts? Thanks! |
|
|
|
Whats this I am seeing with change address? You getting ready for S4C to send change back to the sending address? This was actually just to add the address book to the coin control change section. Just so it is easier for that. But it will lead to what you suggest as well.... |
|
|
|
Welcome back! We miss you..  I did see that change. Not sure what I am going to do with it quite yet. I was thinking of creating a entirely new transaction type, so it will show up on the message as well as the transaction page. Eventually my goal was to actually incorporate S4C directly into the staking transaction. So if the block is staked, it will split the transaction into the percentage to give to them and the rest back to you. This way it will be faster and free. It does require quite a bit of change, so it is a ways off, but it is my eventual goal.. |
|
|
|
I sent you the link in a PM file via file dropper. I tried reloading from scratch and the wallet hung at about half way through. I then retried using the blockchain you sent a couple of weeks ago. This time I hardwired my PC to the network instead of wireless. Still hangs. I then tried setting up a wireless hotspot using my phone thinking that it might be something wrong with my router or home network. It still would not progress beyond this block number 1241289. This is the last block processed. So far I have eliminated the PC as the problem, I tried it on two PCs. I have eliminated my home network as the problem. I tried it on two networks. I eliminated the wallet as the problem it even sticks with an empty wallet. It appears to me to be a network / code problem where a certain condition occurs and when this condition happens the wallet looses its ability to sync.
There is only one way I can think of to fix this problem without some sort of code change. I will have to obtain a blockchain that is only a few hours old. One that is beyond the block that causes the freeze. This will probably be a temporary fix as this has happened 2 times this month so I am thinking it may happen again until we find what the root cause of this problem is. I used to test software and hardware for a living so let me know if you need some testing help in the future or with this current problem. I like hobonickles and I want to see it be very successful.
Thanks for the support...
Ok got the log, yes your client is rejecting block 1,241,290 I am testing a few things on my end. I'll let you know what I come up with. Thank you for your help too. So I just sync'd up from the 9-16 to current. No issues went right through, as I suspected. I do believe the issue is here, for you. 09/25/14 02:15:05 ERROR: ConnectInputs() : 7ae81d70a1 prev tx already used at (nFile=1, nBlockPos=581778185, nTxPos=581778344) To me this means there is something askew with your wallet.dat or your database. Here is what I would like you to try, if you have time. On your 2nd pc, since you already have it running ok on your other. 1) Replace txleveldb/block001.dat with the 9-16 file. Just so it is faster. Full sync should work as well. 2) Remove the database dir (Normally I wouldn't recommend this, but for this test it should be ok) 3) Start the client with -salvagewallet 4) See if it syncs. If you want to clear our your debug.log and then send it to me again, in case it doesn't work I would appreciate it. Also feel free to post an address for helping debug issues. Always appreciated. Thanks! |
|
|
|
my hobo wallet.dat is probably corrupted
I could not start the client with that .dat
and I was forced to erase everything (took a back up of wallet.dat) and restarted with an empty wallet
is there a way to import that wallet ?
wallet has been encrypted
currently waiting for the blockchain to redownload
You generally do not have to, and should right away just erase everything. You should first backup the wallet and database dir, then try to start the client with -salvagewallet . This usually fixes any corruption. Regarding your question, if you created the export wallet(plain txt) file, you can use the import wallet to combine wallets. You can also use the importprivkey rpc command if you know have the privatekeys. |
|
|
|
I sent you the link in a PM file via file dropper. I tried reloading from scratch and the wallet hung at about half way through. I then retried using the blockchain you sent a couple of weeks ago. This time I hardwired my PC to the network instead of wireless. Still hangs. I then tried setting up a wireless hotspot using my phone thinking that it might be something wrong with my router or home network. It still would not progress beyond this block number 1241289. This is the last block processed. So far I have eliminated the PC as the problem, I tried it on two PCs. I have eliminated my home network as the problem. I tried it on two networks. I eliminated the wallet as the problem it even sticks with an empty wallet. It appears to me to be a network / code problem where a certain condition occurs and when this condition happens the wallet looses its ability to sync.
There is only one way I can think of to fix this problem without some sort of code change. I will have to obtain a blockchain that is only a few hours old. One that is beyond the block that causes the freeze. This will probably be a temporary fix as this has happened 2 times this month so I am thinking it may happen again until we find what the root cause of this problem is. I used to test software and hardware for a living so let me know if you need some testing help in the future or with this current problem. I like hobonickles and I want to see it be very successful.
Thanks for the support...
Ok got the log, yes your client is rejecting block 1,241,290 I am testing a few things on my end. I'll let you know what I come up with. Thank you for your help too. |
|
|
|
Great work!  PressTab. I have taken your CC work and improved it a bit. It will now deselect coins that may have been selected previously, which do not fit the current criteria. Speed it up a bit as well. Pretty easy change. Move this line up and remove it from the ifs to the boost COutPoint outpt(txhash, out.i); And add these lines to the ifs. else {
coinControl->UnSelect(outpt);
itemOutput->setCheckState(COLUMN_CHECKBOX,Qt::Unchecked);
}
I did a few other things dealing with the Potential Stake and Age. Not super important, but if you find bugs it may help.. https://github.com/Tranz5/HoboNickels/commit/2b9588b6dad268a81b1648bab7e751943d13d3f0Enjoy! |
|
|
|
I ran the experiment you suggested on my other PC. It still hung at the same spot. I tried to send the log inside the PM but it was to big. How can I get you the log file. It definitely has a clear error message sequence in there. Just need to send you the log some how.
You can try here. http://www.filedropper.com/Zip it up and password it(if you want), them PM me the link.. |
|
|
|
I am still loading from scratch, probably will not be done until sometime tomorrow. If that does not work I follow your instructions and see if that works. I will let you know tomorrow. Hopefully it will finish loading by then.
Alright if not, don't get too upset. I don't let my users just hang out to dry, we'll figure it out! |
|
|
|
Thanks for the prompt replies tranz. I tried the files you posted twice and it still jams at the same block. I deleted the blockchain files as you suggested and I will attempt to download the entire block chain from the peers and see if that fixes. I even moved everything to another PC and it still sticks at the same spot.
Hmmm. Ok Here is something else to try first. 1) shutdown the wallet 2) copy the wallet(s) and database directory, to somewhere safe(just in case) 3) rename the debug.log file to debug.log_old 4) Remove the 2 files(txleveldb and block0001.dat) and put the ones from the download in place. 5) Start the client up with -zapwallettxes If you are still stuck, please send me the full debug file. There is something at play I am not sure. But we'll figure it out I have no doubt. Also check if the db.log file has any entries in it.. |
|
|
|
I am also getting an error message in the wallet at the top that says:
Warning: Checkpoint is too old. Wait for block chain to download, or notify developers.
Did you see my post? You may need to clear out txleveldb and block001.dat out of the %appdata%/HoboNickels directory then replace it with the file I posted or just re download from peers. The Checkpoint too old message will go away on the next wallet restart.. You can always check it as follows. getinfo "blocks" : 1244290, getcheckpoint { "synccheckpoint" : "28c6a975c98f5e2f75a50ea885f58615919031ca31c74bf0287573f10bd2219d", "height" : 1244290, "timestamp" : "2014-09-24 22:50:02 UTC", "policy" : "strict" } if the height and blocks match you are good. If you continue to have issues, please feel free to PM me. |
|
|
|
|
Show Posts
