can someone please update the mac wallet once it is closed by the red circle not quitting the wallet it won't come up unless you quit it and restart it
it should have a show/hide when you right click on the wallet icon to bring it up like the rest of the mac wallets.
Thanks
ryan. I will have a look as soon as I can. I think unick was trying to get it compiled for OSX, does anyone have a good set of instructions? I think adding this line dockIconHandler->setMainWindow((QMainWindow*)this); To bitcoingui.cpp after line 538 should fix this. but I would need someone who can comile and test it. Otherwise I will put this in for 1.4 and see if max can create us another wallet. |
|
|
|
Wrote a few guides for our issues. I'll finish them up later. 5,000 HBN bounty for fixing the assert failure!
Identical bug occurred in blackcoin, all the blocks freshly downloaded, then quit and restart, assert failure. Also Novacoin dies in the same assert. HoboNickels has been working ok for me, though. Has someone tried to reproduce the bug with leveldb 1.15.0? Novacoin had pretty old version of leveldb. Good to know. I used the leveldb src from the newest bitcoin, so it is a revision higher then NVC. Not sure about BC though. EDIT: bummer. blackcoin has leveldb 1.15, so the bug is most probably in the novacoin code. Assuming blackcoin devs did not add their own bugs. My guess is it has something to do with the cached start up routine that NVC implemented a while ago. I also used that code, as well as BC. I am not sure if PHS did, but they just moved to leveldb as well. So it maybe interesting to see if the bug hits the stones. |
|
|
|
Wrote a few guides for our issues. I'll finish them up later. 5,000 HBN bounty for fixing the assert failure!
Identical bug occurred in blackcoin, all the blocks freshly downloaded, then quit and restart, assert failure. Also Novacoin dies in the same assert. HoboNickels has been working ok for me, though. Has someone tried to reproduce the bug with leveldb 1.15.0? Novacoin had pretty old version of leveldb. Good to know. I used the leveldb src from the newest bitcoin, so it is a revision higher then NVC. Not sure about BC though. current hbn has kMinorVersion = 13; in src/leveldb/include/leveldb/db.h ? Anyways, I tested with novacoin, latest leveldb, deleted all the databases and downloaded again.. it did not die with assert tailure. But this does not prove there are no bugs in novacoin.. Yes I can also do this with current HBN multiple times, but just one random time and then it dies. If it does happen with your newer leveldb version let me know. |
|
|
|
Wrote a few guides for our issues. I'll finish them up later. 5,000 HBN bounty for fixing the assert failure!
Identical bug occurred in blackcoin, all the blocks freshly downloaded, then quit and restart, assert failure. Also Novacoin dies in the same assert. HoboNickels has been working ok for me, though. Has someone tried to reproduce the bug with leveldb 1.15.0? Novacoin had pretty old version of leveldb. Good to know. I used the leveldb src from the newest bitcoin, so it is a revision higher then NVC. Not sure about BC though. |
|
|
|
Thanks for maintaining HBN.
You are welcome. Hopefully things settle down here soon. I have been making some headway into the assert failures. Essentially some of the blocks are missing from the index. I still don't know the root cause for this. As it appears to be somewhat random? But I am continuing investigation into this issue. Keeping a running backup of the txleveldb folder and blk???.dat files should help. As you can quickly use a slightly older version, and then re download the missing blocks. I'll put up weekly zips of the files so others won't have to re download the block chain many times. Plus after you have a working backup you can always use that to catchup to current quickly. |
|
|
|
My Growth coin wallet sinks, my Mint coin wallet syncs, all my other wallets work fine. PM your email so I can send you the debug txt, I can't copy paste it here the text exceeds the character limit for the forums and also pastebin free account. Currently on block 2503 now. The wallet still producing PoS, I just mined 17 HBN a min ago. Update: I took out my wallet.dat file and it is syncing like it is supposed to, is my wallet.dat corrupted?  Update: Yay! seems fine now after I synced the wallet and then added my wallet.dat file. The only problem now is the wallet will always go non responsive and freeze if I try to click on an option. This happens with the 1.3.0 and the 1.3.6.0 wallets and only when I have my wallet.dat in my appdata folder. I understand now.. You are producing many PoS blocks and it is causing the GUI to become un-responsive. Yes I have this fixed in 1.3.7+ but i haven't released it yet. For now you can type reservebalance=9999 in your console or when you start up. The 9999 should be 1/2 to 3/4 your coins. The coins in reserve won't stake, but as some stake you can lower the reservebalance. I am working on a few other fixes here before I release it. including the assert failures and the 22 wallet issues. Thanks for your patients. |
|
|
|
I will try that if it does not sync, it is but slow as a snail. Oh! my wallet.dat file was never encrypted.
I just sync'd a few computers last night. The longest took me about 12 hours. What is your log file saying? 1.3.0.0 will need addnodes manually. But should sync after you get connections. I am using these nodes: addnode=174.103.158.220:62683 addnode=68.109.79.96:61187 addnode=65.24.235.56:33299 addnode=144.76.9.247:2304 addnode=75.152.1.226:62062 addnode=108.83.227.44:51053 addnode=85.140.75.107:58473 addnode=94.41.176.140:65508 addnode=75.138.235.246:7372 addnode=5.249.152.30 addnode=54.201.183.106 addnode=178.33.105.250 addnode=123.176.103.130 The wallet seems to sync a block every 10-15 min, so far I am on block 2508. No this is not even close. You will never sync. Something is odd with your connection or your computer. What does your debug log say? |
|
|
|
|
Guys I just did a normal windows update, nothing out of the ordinary. And then brought back up a wallet that has been very steady for me for sometime. I got the assert failure.
This is now public enemy number 1. I am going in deep. I may not be out for a while. Hopefully I surface with a good solution!
|
|
|
|
I will try that if it does not sync, it is but slow as a snail. Oh! my wallet.dat file was never encrypted.
I just sync'd a few computers last night. The longest took me about 12 hours. What is your log file saying? 1.3.0.0 will need addnodes manually. But should sync after you get connections. |
|
|
|
EDIT: just did another transaction and never got caught up by the network... I'll redo the -salvagewallet thing but it's a pain and time consuming  here's the log if that could help From a thread I read on dogecoin subreddit, which uses similar QT, there were problems of the wallet not staying synced properly and causing the type of problems we are seeing. It said the cause of the problem is boost library under version 1.5.5 being used when compiling from source. I am not sure whether this is the problem or not, in the makefile.mingw in the Tranz/HoboNickels repo it is showing boost 1.5.0 - which could be the problem. But also I don't even know if Tranz uses mingw to compile for windows or not. I am trying to mess around with compiling for Windows right now, but this will be a learning experience for me because I have only compiled hobonickelsd on Ubuntu. yeah maybe that is it... I'm using "version" : "v1.3.0.0-g76880ab-hobo" for MAC, maybe that is the problem... I will try to compile the latest version for MAC later tonight... It will be an new experience for me too... let's have fun  For all my windows compiles I use boost 1.55. I did not compile the Mac. I currently do not own a mac. This was going to be a project after I complete 1.4. But there maybe bigger fish to fry. |
|
|
|
Ok I will try that,
and no it was regular transactions this time. What can cause this kind of issue ?
I know that if you send a transaction while not synced, or while having networking issues it can cause this to happen. I had this happen with a different coin a few months ago. I'm still not sure why this happened, as I did make about 10 transactions before sending the 2 that got "stuck". Maybe they were either too fast, or I had network issues that I wasn't aware of. The other thing I can say is that I was combining smaller blocks into bigger ones, (I had over 100 blocks sent into one) and the client was a bit laggy while preparing the transaction... Maybe something went wrong during that process. Anyhow, -salvagewallet cleaned up that mess and I'm all good now. Thanks EDIT: just did another transaction and never got caught up by the network... I'll redo the -salvagewallet thing but it's a pain and time consuming here's the log if that could help 04/02/14 17:47:48 CommitTransaction:
CTransaction(hash=e62f60d62e, nTime=1396460865, ver=1, vin.size=1, vout.size=1, nLockTime=0)
CTxIn(COutPoint(1f0f651975, 0), scriptSig=3045022100d53b3d7ec7ca92)
CTxOut(nValue=1883.598592, scriptPubKey=OP_DUP OP_HASH160 c1deeb3337900432c207e4a0e55c2278e13fcd56 OP_EQUALVERIFY OP_CHECKSIG)
AddToWallet e62f60d62e new
04/02/14 17:47:49 WalletUpdateSpent found spent coin 1883.599592hbn 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d
04/02/14 17:47:49 NotifyTransactionChanged 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d status=1
04/02/14 17:47:49 NotifyTransactionChanged e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b status=0
04/02/14 17:47:49 NotifyTransactionChanged 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d status=1
04/02/14 17:47:49 CTxMemPool::accept() : accepted e62f60d62e (poolsz 1)
04/02/14 17:47:49 AddToWallet e62f60d62e
04/02/14 17:47:49 NotifyTransactionChanged e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b status=1
04/02/14 17:47:49 AddToWallet e62f60d62e new
04/02/14 17:47:49 NotifyTransactionChanged e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b status=0
04/02/14 17:47:49 Relaying wtx e62f60d62e
04/02/14 17:47:49 NotifyAddressBookChanged EzAbwP8XEDByVXLw6rD58gozmvUaiKKQmi isMine=0 status=0
04/02/14 17:47:50 updateWallet 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d 1
04/02/14 17:47:50 inWallet=1 inModel=1 Index=225-226 showTransaction=1 derivedStatus=1
04/02/14 17:47:50 updateWallet e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b 0
04/02/14 17:47:50 inWallet=1 inModel=0 Index=1611-1611 showTransaction=1 derivedStatus=0
04/02/14 17:47:50 updateWallet 1f0f651975818c2e769d370ae02e7df95df505b6e23f887cf9f20f1158d6100d 1
04/02/14 17:47:50 inWallet=1 inModel=1 Index=225-226 showTransaction=1 derivedStatus=1
04/02/14 17:47:50 updateWallet e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b 1
04/02/14 17:47:50 inWallet=1 inModel=1 Index=1611-1612 showTransaction=1 derivedStatus=1
04/02/14 17:47:50 updateWallet e62f60d62e809437dfc8cc19f17aa3a271a3a3ed263c1c2e3955739513ef4a5b 0
04/02/14 17:47:50 inWallet=1 inModel=0 Index=0-0 showTransaction=1 derivedStatus=0
04/02/14 17:47:52 Flushing wallet.dat
04/02/14 17:47:52 Flushed wallet.dat 242ms
Hmm not I am not sure right off hand why it wouldn't get accepted? Did you try resendtx? After salvage wallet did it work? Did you use coin control or something different? |
|
|
|
Foolishly I didnt date the hbn wallet backup like I do with btc. But it is very likely from version 1.3.1.
I wonder if starting the client using -salvagewallet might work? I am running out of ideas real fast. Sorry. Try repairwallet in the console Regarding my wallet it has been trying to sync for over 24 hours. I am using the 1.3.6.0 beta version, are they any extra nodes besides the ones below? 5.249.152.30 54.201.183.106 178.33.105.250 123.176.103.130 Repair wallet is actually in the menu now. You can get more nodes here. http://hbn.blockx.info/connected-nodes |
|
|
|
|
Thanks guys!
I do understand that there are some bugs in the HBN wallet and network. Namely the assert failures dealing the blk*.dat files and the error 22 files dealing with wallets.
I haven't had a wallet error 22 myself, so that is a bit more difficult for me to trouble shoot. I do believe this last case (based on what was said here) is the database directory had some bad data, and this caused the wallet to fail to be loaded. The wallet.dat may have been fine. Difficult to tell from this end. I just wonder if strawie had started a fresh directly with only that wallet, which was causing problems, would the error 22 still have happened?
The assert failures I can now (mostly) duplicate. So I will be looking for the root cause and solution. Both of these will be in focus as we get closer to 1.4. I can not promise I will be able to fix both or either of them, but I will continue to look deeper. If there are any other coin developers that may have any ideas I would be glad to brainstorm.
Remember btc has fairly big team with years of development. HBN has me, and I've only been doing this for about 6 months now. I do my best to search through the pull requests of many coins. BTC, PPC, NVC. If anyone sees pull request that deals with either of these, please bring it to my attention, it may help.
I am trying to push the envelope, good or bad, on what can be done with a coin. Some of this will cause bugs.
I plan to complete a bit more work on stake for charity this week, the move on to some of these and other issues.
I hope that in the next year or so HBN could be part of a bigger picture which many sites choose to use this coin for general spending and for charitable giving. Obviously we will have to work some of these issue out as we go. As I understand they can be frustrating and cause people to turn away. Neither of these is satisfactory in my eye. But for now it is what it is.
Thanks all and carry on the good fight.
|
|
|
|
A real quick question... what to do when you send a transaction, the funds are deducted from the sending wallet, it's being posted to the network (the receiving wallet marks it as unconfirmed) but the network never accept the transaction?
It happened to me 3 times now but I am not sure how to "reset" the transaction
Do I need to -salvagewallet on both wallets (sending and receiving)
what's the correct procedure to recover from that?
I think repairwallet in rpc should fix this right? As long as you have the latest version of the daemon/client. Repair wallet will fix missmatched coins, and orphans from stake or mining, But this type of transaction may not go away. Worth a shot though. Unick was this dealing with multi-signatures. Or just a normal transactions? You could try resendtx. But I think salvage wallet maybe necessary. |
|
|
|
UPDATE!
THE blockchain from the wiki works!
When I let the client re-download it or use any of the copies I got from backups or other machines it doesnt.
I still think you may have a slightly corrupted wallet. You can use dumpprivkey and then importprivkey rpc command. |
|
|
|
|
Hi Strawie.
I am guess this wallet came from version 1.2?
So lets try a few things.
#1 grab version 1.2 from my github releases. ( it won't sync with the network, but we don't need it to)
#2 Create a new directory on your c: ( or other drive ) c:\hbn_1.2 for example
#3 Copy this bad wallet into it calling it wallet.dat ( that should be the only thing in the directory )
#4 Start version 1.2 with the 2 switches -datadir=c:\hbn_1.2 -salvagewallet ( you may also need -listen=0 )
#5 Hopefully the client starts up just fine, after it does shut it down
#6 You should be now able to take the wallet.dat and rename wallet-fixed.dat (or something different)
#7 You can try try to load up the wallet in a version 1.3+
Please me me know if this helps.
|
|
|
|
Hi Tranz, thanks it worked! It took forever to re-download the blockchain and it takes a long time for the wallet to load but it loads fine now....thanks again. Is there any way to deal with the large size blockchain? I understand that this will be an issue for all coins at some point.
Good to hear. Yes the block chain will grow by about 1 - 2 gig each year. Some type of compression my help. Also as it gets much bigger we will likely offer a bootstrap download file to help speed up the process. Hi Tranz, bad news. The Assertion failed error is back, no idea why (see link below for my exact error). I can't open the wallet at all again. I'm not sure what to try next? If I send coins to a new wallet will that help? what else can i try? thanks https://i.imgur.com/hbnB1zz.jpgHi Choppy sorry about the issues. Do me a favor and PM me. I'd like to know what OS you are on and if anything odd has happen to your computer. I will give you further instructions then. Thanks. |
|
|
|
Mmm, that's great but maybe is it possible to explain in 2-3 words for us, non-programmers, what this feature is useful for?  Basically it allows for a more efficient staking process. The gui should not become unresponsive if you are trying to process a lot of separate blocks for stake. |
|
|
|
|
Show Posts
