HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 211.

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: georgidimitrov on May 09, 2014, 09:05:09 PM

Quote from: dogechode on May 09, 2014, 08:45:21 AM

Has anyone else using the Windows wallet noticed that it doesn't open fast anymore? When Tranz first released the update where he said he had addressed a problem that was slowing the loading process, my wallet opened lightning fast at first - I think like 10-20 seconds.

My computer had to be restarted yesterday and I noticed the hbn wallet took a really long time to open.

it works really fine for me - 15 to 20 secs to open

Yes, the only time it is slow, is if you set it to start up with Windows. I think windows simply limits the CPU usage until all other process are loaded. I notice the same thing with BitCoin Core as well.

georgidimitrov

member

Activity: 101

Merit: 10

Quote from: dogechode on May 09, 2014, 08:45:21 AM

Has anyone else using the Windows wallet noticed that it doesn't open fast anymore? When Tranz first released the update where he said he had addressed a problem that was slowing the loading process, my wallet opened lightning fast at first - I think like 10-20 seconds.

My computer had to be restarted yesterday and I noticed the hbn wallet took a really long time to open.

it works really fine for me - 15 to 20 secs to open on WinXPsp3/dual pentium 3ghz

---------------------------------------------------
websitetrafficdelivery[dot]tk : HBN & DOGE accepted

ElTomeko27

sr. member

Activity: 371

Merit: 250

Quote from: sandpaper on May 08, 2014, 06:21:58 PM

Anyone else happy HBN is going down? Makes me feel like my BTC is going a much further way.

Just bought a block at 29000:) Stake baby for you daddy:]

dogechode

full member

Activity: 182

Merit: 100

Has anyone else using the Windows wallet noticed that it doesn't open fast anymore? When Tranz first released the update where he said he had addressed a problem that was slowing the loading process, my wallet opened lightning fast at first - I think like 10-20 seconds.

My computer had to be restarted yesterday and I noticed the hbn wallet took a really long time to open.

unick

sr. member

Activity: 504

Merit: 254

Quote from: Tranz on May 08, 2014, 08:59:39 PM

Quote from: unick on May 08, 2014, 08:40:21 PM

Quote from: Tranz on May 08, 2014, 06:50:38 PM

Quote from: unick on May 08, 2014, 05:33:45 PM

I've had 2 crashes in the same situation, trying to send a transaction and the client quits

Code:

Application Specific Information:
abort() called
terminating with uncaught exception of type std::length_error: basic_string::_S_create

it's not a big deal, just wanted to mention it

Which OS is this? And is your wallet encrypted?

I thought I mentioned it Roll Eyes

It's OS X (Mavericks) and yes it's encrypted

Hmm ok.

I think there is still a small bug, that if the wallet is encrypted but unlocked, and you send coins. It first locks the wallet, but still tries to run stake. If you don't type in your password quickly enough, the wallet could crash. If you cancel it, it simply locks the wallet and stops the stake.

A work around, would be to lock the wallet manually first, then send the coins, then unlock when done. Or you could use the rpc command walletpassphrase without the mintonly switch. This will allow all sends, without first locking the wallet, and prompting for password.

I have only thought this could be the case, but didn't see a real world issue till now. I'll look more closely at this.

Thanks unick.

Ok, it happened twice but I didn't pay attention to what was happening, I just noticed the crash report!

Like I said it's no big deal, I will try and see if I can reproduce the error keeping in mind what you just said.

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: unick on May 08, 2014, 08:40:21 PM

Quote from: Tranz on May 08, 2014, 06:50:38 PM

Quote from: unick on May 08, 2014, 05:33:45 PM

I've had 2 crashes in the same situation, trying to send a transaction and the client quits

Code:

Application Specific Information:
abort() called
terminating with uncaught exception of type std::length_error: basic_string::_S_create

it's not a big deal, just wanted to mention it

Which OS is this? And is your wallet encrypted?

I thought I mentioned it Roll Eyes

It's OS X (Mavericks) and yes it's encrypted

Hmm ok.

I think there is still a small bug, that if the wallet is encrypted but unlocked, and you send coins. It first locks the wallet, but still tries to run stake. If you don't type in your password quickly enough, the wallet could crash. If you cancel it, it simply locks the wallet and stops the stake.

A work around, would be to lock the wallet manually first, then send the coins, then unlock when done. Or you could use the rpc command walletpassphrase without the mintonly switch. This will allow all sends, without first locking the wallet, and prompting for password.

I have only thought this could be the case, but didn't see a real world issue till now. I'll look more closely at this.

Thanks unick.

unick

sr. member

Activity: 504

Merit: 254

Quote from: Tranz on May 08, 2014, 06:50:38 PM

Quote from: unick on May 08, 2014, 05:33:45 PM

I've had 2 crashes in the same situation, trying to send a transaction and the client quits

Code:

Application Specific Information:
abort() called
terminating with uncaught exception of type std::length_error: basic_string::_S_create

it's not a big deal, just wanted to mention it

Which OS is this? And is your wallet encrypted?

I thought I mentioned it Roll Eyes

It's OS X (Mavericks) and yes it's encrypted

kingscrown

hero member

Activity: 672

Merit: 500

http://fuk.io - check it out!

Quote from: MarketNeutral on May 08, 2014, 06:38:43 PM

I'm definitely buying at these prices.

Received a stake of almost 900 HBN this morning. Still compounding! Cool

wow how many u got for such stake?

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: unick on May 08, 2014, 05:33:45 PM

I've had 2 crashes in the same situation, trying to send a transaction and the client quits

Code:

Application Specific Information:
abort() called
terminating with uncaught exception of type std::length_error: basic_string::_S_create

it's not a big deal, just wanted to mention it

Which OS is this? And is your wallet encrypted?

JeffK

sr. member

Activity: 350

Merit: 250

I never hashed for this...

I think prices will drop a little more. I will be buying back soon too.

MarketNeutral

sr. member

Activity: 434

Merit: 252

I'm definitely buying at these prices.

Received a stake of almost 900 HBN this morning. Still compounding! Cool

tokyoghetto

legendary

Activity: 1232

Merit: 1000

Quote from: sandpaper on May 08, 2014, 06:21:58 PM

Anyone else happy HBN is going down? Makes me feel like my BTC is going a much further way.

I am. Anyone who is mining on the hashco.ws multipool is loving it too.

sandpaper

sr. member

Activity: 373

Merit: 250

Anyone else happy HBN is going down? Makes me feel like my BTC is going a much further way.

unick

sr. member

Activity: 504

Merit: 254

I've had 2 crashes in the same situation, trying to send a transaction and the client quits

Code:

Application Specific Information:
abort() called
terminating with uncaught exception of type std::length_error: basic_string::_S_create

it's not a big deal, just wanted to mention it

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: carloss on May 08, 2014, 09:08:02 AM

Unfortunately it is doing that all the time Sad

I have libboost 1.54...do you think it is worth to try upgrading to 1.55?

carloss

Quote from: Tranz on May 07, 2014, 05:45:40 PM

Hello Carloss. Does this happen only during initial synchronization with the network? Or all the time.

If all the time, there is a known bug in older version of boost, which can cause the wallet to go out of sync. I am using 1.55 without any issues.

If it is only during the initial block chain download, then restarting once should be more then enough. I occasionally have to do this when doing the init sync. But even on my Pi, I didn't have to do it once. I just started it up and let it go..

Its worth a shot. If this doesn't fix it, let us know. Might need to run the client in -debug mode and give me a bigger log file to help diagnose it. So far this is the first of this specific situation happening.

MarketNeutral

sr. member

Activity: 434

Merit: 252

Quote from: superresistant on May 08, 2014, 03:56:42 PM

Quote from: carloss on May 08, 2014, 09:08:02 AM

Unfortunately it is doing that all the time Sad

I have libboost 1.54...do you think it is worth to try upgrading to 1.55?

Perfect tutorial here for libboost 1.55

https://coderwall.com/p/0atfug

Thank you, superresistant. I was curious about this as well.

superresistant

legendary

Activity: 2156

Merit: 1131

Quote from: carloss on May 08, 2014, 09:08:02 AM

Unfortunately it is doing that all the time Sad

I have libboost 1.54...do you think it is worth to try upgrading to 1.55?

Perfect tutorial here for libboost 1.55

https://coderwall.com/p/0atfug

carloss

member

Activity: 64

Merit: 10

Unfortunately it is doing that all the time Sad

I have libboost 1.54...do you think it is worth to try upgrading to 1.55?

carloss

Quote from: Tranz on May 07, 2014, 05:45:40 PM

Hello Carloss. Does this happen only during initial synchronization with the network? Or all the time.

If all the time, there is a known bug in older version of boost, which can cause the wallet to go out of sync. I am using 1.55 without any issues.

If it is only during the initial block chain download, then restarting once should be more then enough. I occasionally have to do this when doing the init sync. But even on my Pi, I didn't have to do it once. I just started it up and let it go..

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: carloss on May 07, 2014, 04:40:59 PM

Hello,

I have often problems with the wallet (hobonickelsd, running on Ubuntu Server 14.04, compiled from latest git source).

It is often stuck on something like this (snip from debug.log):

Code:

05/07/14 10:13:40 ProcessSyncCheckpoint: pending for sync-checkpoint 0000000002bde252b09a26e27d6c96d5594ca6340d6ff2de5138ca8a1f90d715

and it takes 100% CPU for a very long time or almost indefinitely without doing anything apparently useful.

When I restart it, it can run for few hours or even days fine before this happens again.

Any idea?

Hello Carloss. Does this happen only during initial synchronization with the network? Or all the time.

If all the time, there is a known bug in older version of boost, which can cause the wallet to go out of sync. I am using 1.55 without any issues.

If it is only during the initial block chain download, then restarting once should be more then enough. I occasionally have to do this when doing the init sync. But even on my Pi, I didn't have to do it once. I just started it up and let it go..

Tranz

legendary

Activity: 1540

Merit: 1060

May the force bit with you.

Quote from: dogechode on May 07, 2014, 10:01:48 AM

Quote from: Tranz on May 06, 2014, 08:27:33 PM

Quote from: dogechode on May 05, 2014, 08:44:32 AM

I was going to say I seriously doubt they are keeping the bulk of the coins in a hot wallet. There have also been issues/exploits with malleability concerning POS coins... remember the whole blackcoin CryptoRush debacle?

Do you have a link to this? I'd like to read about it.

This is the main thread that was started about it back in March, just keep in mind you have to filter through all the lies and bullshit that CR tried to push on people. https://bitcointalksearch.org/topic/official-blackcoin-statement-from-cryptorush-very-shocking-information-529779

There was a discussion of how the issue with malleability related to POS coins was updated by the major exchanges like Cryptsy early on so they didn't have any huge problems.

Ok thanks for the information.

So a the main issue was they were using the "accounting" system perhaps incorrectly, and not using any other method to double check inputs/outputs. In addition to that they were allowing the hot wallet to stake, thereby casing even more confusion about it's users balances.

Topic: HoboNickels - HBN - High Fast Stake - Version 2.0! More Secure, Less Intensive - page 211. (Read 478915 times)