...
my stakes are around 85 to 90
I have set the minimum to 20 and max 50
and I have the percentage set to 50
Ryan, thanks for the log file. I have looked it over and your questions appear valid. I only see where it sent a few early on, and then none for a long time and then it sent one. Did you do something? I re-looked over the code. I don't have an explanation as of yet. If you wouldn't mind trying to empty out the min and max string and re-clicking the enable button. I just want to verify that there is nothing odd about the those settings that might be throwing it off. Otherwise I may have to make a quick custom wallet that will add a few extra debug statements to find the source of the issue. I have a few suspicions, but until I re-create the issue here, it is difficult to troubleshoot. Thanks for your help and understanding. Tranz, I haven't studied your multi-wallet code, but is it possible that the settings are only be written to one walletdb when there are multiple walletdb's? Just a shot in the dark here.... Hey thanks for the suggestion. I guess I didn't consider the fact that he maybe running s4c on a secondary wallet? Ryan is this the case? I did test using it for many wallets, but perhaps I missed something. Yes, it is on a secondary wallet Ok thanks.. Still shouldn't make much of a difference. I was able to run 8 wallets on the same client, all running S4C, and all starting up fine. Do you only have S4C running on the secondary wallet and not on the default? |
|
|
|
Presstab. I know you are crazy right now. Have you issued an alert to the clients? If not you should immediately issue a high priority alert.
Hey Tranz, I do believe he has contacted everyone. Right I am sure he did, to the best he could. But there could be hundreds of nodes running HYP, and many are people who will remain anonymous. Issuing an alert will reach every client that is running. And if someone comes back from holiday and starts up the client, the alert will pop up and let them know there is an issue. |
|
|
|
|
Presstab. I know you are crazy right now. Have you issued an alert to the clients? If not you should immediately issue a high priority alert.
|
|
|
|
...
my stakes are around 85 to 90
I have set the minimum to 20 and max 50
and I have the percentage set to 50
Ryan, thanks for the log file. I have looked it over and your questions appear valid. I only see where it sent a few early on, and then none for a long time and then it sent one. Did you do something? I re-looked over the code. I don't have an explanation as of yet. If you wouldn't mind trying to empty out the min and max string and re-clicking the enable button. I just want to verify that there is nothing odd about the those settings that might be throwing it off. Otherwise I may have to make a quick custom wallet that will add a few extra debug statements to find the source of the issue. I have a few suspicions, but until I re-create the issue here, it is difficult to troubleshoot. Thanks for your help and understanding. Tranz, I haven't studied your multi-wallet code, but is it possible that the settings are only be written to one walletdb when there are multiple walletdb's? Just a shot in the dark here.... Hey thanks for the suggestion. I guess I didn't consider the fact that he maybe running s4c on a secondary wallet? Ryan is this the case? I did test using it for many wallets, but perhaps I missed something. |
|
|
|
...
my stakes are around 85 to 90
I have set the minimum to 20 and max 50
and I have the percentage set to 50
Ryan, thanks for the log file. I have looked it over and your questions appear valid. I only see where it sent a few early on, and then none for a long time and then it sent one. Did you do something? I re-looked over the code. I don't have an explanation as of yet. If you wouldn't mind trying to empty out the min and max string and re-clicking the enable button. I just want to verify that there is nothing odd about the those settings that might be throwing it off. Otherwise I may have to make a quick custom wallet that will add a few extra debug statements to find the source of the issue. I have a few suspicions, but until I re-create the issue here, it is difficult to troubleshoot. Thanks for your help and understanding. |
|
|
|
solo mining still going? and is it the same config as the first page?
Yes you can still solo, assuming you have the hash. The addnodes are a bit out of date, but you can grab as many as you need here: http://cap.cryptocoinexplorer.com/peerinfo (the port should be omitted). Otherwise it is a standard solo mining config. |
|
|
|
Sounds cool. What does everyone else think? What is the best way to apply. |
|
|
|
Guys is there any issue with S4C?
I have it setup but it does not always send the coins, and they all meet the criteria, that I have in place.
I am using v1.5.0
Ryan there does appear to be a bug, as first noticed by pressf1 and confirmed just recently by me, where the s4c does not re-enable after a wallet restart. It does not happen all the time. If this does happen, just go to the s4c tab after restart and hit enable. That usually does the trick. Otherwise I haven't see of any other issues. Can you be more specific? My wallet has been running for few days, and I did not restarted it, when it first stakes, the first one or the second one works "s4c" the rest do not work at all. I have been staking for 3 days now and only 1 S4C was processed. Interesting.. What are your min and max settings at? Have you tried to re-click "enable". Also have you looked at the log file to see if they are trying to be processed? You can search for the string "StakeForCharity" and "s4c". What are my stakes are around 85 to 90 I have set the minimum to 20 and max 50 and I have the percentage set to 50 I would be interested to see the debug.log file, if that is ok. Sure, how can i sent it to you? Just upload it to some sharing site. You can zip and password it if you like, just PM me the link then. Thanks! |
|
|
|
Guys is there any issue with S4C?
I have it setup but it does not always send the coins, and they all meet the criteria, that I have in place.
I am using v1.5.0
Ryan there does appear to be a bug, as first noticed by pressf1 and confirmed just recently by me, where the s4c does not re-enable after a wallet restart. It does not happen all the time. If this does happen, just go to the s4c tab after restart and hit enable. That usually does the trick. Otherwise I haven't see of any other issues. Can you be more specific? My wallet has been running for few days, and I did not restarted it, when it first stakes, the first one or the second one works "s4c" the rest do not work at all. I have been staking for 3 days now and only 1 S4C was processed. Interesting.. What are your min and max settings at? Have you tried to re-click "enable". Also have you looked at the log file to see if they are trying to be processed? You can search for the string "StakeForCharity" and "s4c". What are my stakes are around 85 to 90 I have set the minimum to 20 and max 50 and I have the percentage set to 50 I would be interested to see the debug.log file, if that is ok. |
|
|
|
Guys is there any issue with S4C?
I have it setup but it does not always send the coins, and they all meet the criteria, that I have in place.
I am using v1.5.0
Ryan there does appear to be a bug, as first noticed by pressf1 and confirmed just recently by me, where the s4c does not re-enable after a wallet restart. It does not happen all the time. If this does happen, just go to the s4c tab after restart and hit enable. That usually does the trick. Otherwise I haven't see of any other issues. Can you be more specific? My wallet has been running for few days, and I did not restarted it, when it first stakes, the first one or the second one works "s4c" the rest do not work at all. I have been staking for 3 days now and only 1 S4C was processed. Interesting.. What are your min and max settings at? Have you tried to re-click "enable". Also have you looked at the log file to see if they are trying to be processed? You can search for the string "StakeForCharity" and "s4c". What are |
|
|
|
Guys is there any issue with S4C?
I have it setup but it does not always send the coins, and they all meet the criteria, that I have in place.
I am using v1.5.0
Ryan there does appear to be a bug, as first noticed by pressf1 and confirmed just recently by me, where the s4c does not re-enable after a wallet restart. It does not happen all the time. If this does happen, just go to the s4c tab after restart and hit enable. That usually does the trick. Otherwise I haven't see of any other issues. Can you be more specific? |
|
|
|
Update2: With a fresh install of Ubuntu 14.04 and following the guide provided everything went very smooth. I believe all my playing and changing stuff on the old 12.04 installation corrupted packages which was the cause of all my drama. Linux wallet is now synced and should start staking within the week. Thanks to all that provided input  ~rgm Awesome! Now you can try out small code changes and see what happens. |
|
|
|
|
So it looks like it all worked. I am 100% synced and the client is looking good.
I am testing staking now.
I'll write up a new wiki page for help with the mac. I have learned a few things that could be useful for other people.
|
|
|
|
I have been playing as much as possible, in my spare time, with the Mac wallet. And no matter what I tried, I continued to run into issues after I got past a certain point in the block chain. It has nothing to do with bad blocks from other clients, or bugs in the client. I began to think the issue was dealing with some type of memory bug, I was wrong(I think) but close. What appears to be the issues is the max file descriptors is being hit. This is not allowing new blocks (or index files) to be opened and read/written to. I found 2 PR request in BTC that look like they are dealing with the issue: https://github.com/sipa/bitcoin/commit/2233fc531850892c7becf82d6906f3706090f8d7https://github.com/sipa/bitcoin/commit/ba29a5590bc4479d74454f0b9fdaf007d9d80221For now I think I also have a work around for Mac Users. In a terminal run the following: sudo launchctl limit maxfiles 1000000 1000000 This will change the default setting from 256 to 1,000,000 I am still playing with this, but for now it seems promising. Edit: still failed, so I also set this: Then launched the client from the same window. /Users/me/Desktop/HoboNickels-Qt.app/Contents/MacOS/HoboNickels-qt & See if it works this time now. |
|
|
|
Money supply according to the debug console of the client is 8,816,651 HBN, but Coinmarketcap only reads 8,208,723 HBN. That makes our marketcap seem a little smaller than it actually is. Novacoin for example hasn't been updated either, whereas the number for Peercoins is always up to date.
Does anybody know if this is a known issue with Coinmarketcap?
It benefits IPO-Scams over coins with honest mining.
The issue is coinmarketcap is getting it's money supply from an old ABE explorer that is out of commission. They need to change to CCE API. Could I trouble you to ask them to switch? By CCE you mean the Cryptocoinexplorer, right? I have sent them a request via the Request Form. Included this link: http://www.cryptocoinexplorer.com/api Now let's wait and see. Yes, correct, and thanks! |
|
|
|
Thank you, that worked like a charm, and took a lot less than an hour!
Your points about the notice that was given are well taken: I was speaking from a position of fear and worry!!
regards,
Mark.
No problem, glad it worked out for you. It has taken me that long in the past when using -zapwallettxes. I also have a wallet from when the chain is just a few days old and staking going for all that time, so that is why mine can take a long time  . Sorry if I seemed snarky, I do my best to not sneak things under the users noses, and be as transparent as possible. But no matter how much time, or how many notices are given, some people can miss it or just be simply too busy to be bothered. I understand this and do my best to make sure everyone is taken care of. In any event glad you are back on the chain! |
|
|
|
Money supply according to the debug console of the client is 8,816,651 HBN, but Coinmarketcap only reads 8,208,723 HBN. That makes our marketcap seem a little smaller than it actually is. Novacoin for example hasn't been updated either, whereas the number for Peercoins is always up to date.
Does anybody know if this is a known issue with Coinmarketcap?
It benefits IPO-Scams over coins with honest mining.
The issue is coinmarketcap is getting it's money supply from an old ABE explorer that is out of commission. They need to change to CCE API. Could I trouble you to ask them to switch? they are prety fast with swaps so shouldnt take long Cool, do you have the thread for contact information for them handy? |
|
|
|
Hmm, I have been running Hobonickels for quite a while, on and off. Every now and then I forget about it.
The other day I started my client up. It didnt seem to work well and after a while I noticed HARD FORK UPGRADE!!
So I did but it still didnt work well, it re-downlownloaded the blockchain taking several days but never caught up.
So I started a fresh installation , it synced, shutdown and then and then put my wallet.dat in that and restarted.
Now I have 0.001 HBN and roughly 5700 unconfirmed worth of pos mined transactions.
Unless I am mistaken I have just lost the entire contents of my wallet due to the 1.5 hard fork, or is there a way to recover this?
These are all dated within minutes of me starting the 1.4 client on the 31st Jan, after the hard fork on 17th.
No I didnt have any idea this was going on and I still dont understand why it was necessary.
I thought such things were generally done slowly and with plenty of warning?
The first warning of the hard fork was November 11, 2014. A full 3 months before version 1.5 took effect. It was necessary to fix multiple issues, including various attack vectors. Regarding your coins, they should be safe, as long as your wallet was backed up. What you need to do is start the gui with -zapwallettxes. This should clean up the missing transactions. Please be patient with this, it can take some time(30-60mins+) to rescan the block chain. If you need help on how to accomplish this, please let us know. |
|
|
|
Tranz, the "Current Block Info" and "Current PoS Block Info" tabs sometimes do not work. I have to click them several times or wait a little and try again. It's about 50/50 they show up or not.
I am using Windows 7 on an Intel Atom. It's a very slow CPU, so that could be the cause.
One of the changes done in version 1.5 was how the gui and core held locks. When certain functions are called in the code, they have to hold certain pieces of information. The old version would allow the gui to always operate even if the core was busy. The new version only allows certain gui functions to work when the core is not busy. I do have some ideas to help this a bit in future updates. To both protect the core, and to allow a bit smoother gui. |
|
|
|
|
Show Posts
