[ANN] [BTQ] BitQuark | Super secure hashing | CPU mining

[Bitnet88]

Is there a major problem with this pool http://www.weminebtq.com?  I don't seem to be able to log in into my account.
And iam not getting paid for any items that were mine. It seems that it resets to zero if a day of mining is missed.
Sent 2 emails to query no replies at all.

[BitQuark]

Is there a major problem with this pool http://www.weminebtq.com?  I don't seem to be able to log in into my account.
And iam not getting paid for any items that were mine. It seems that it resets to zero if a day of mining is missed.
Sent 2 emails to query no replies at all.

I have corrected this issue as I've been doing some updates to the pool. Sorry for any inconvenience it may have caused.

[crackfoo]

What's the deal with the daemon alert message to mine on wemine??? Who's responsible for that pool?

[BitQuark]

What's the deal with the daemon alert message to mine on wemine??? Who's responsible for that pool?

That was me testing the alert system. I run the BTQ pool at http://WeMineBTQ.com
Thanks,
BTQ Dev

[ZeroFossilFuel]

Not sure if anyone else has run into this but on my Asus 1215n running Xubuntu 16.04.1 with Intel D525 Atom and 4G mem, there is definitely some kind of memory leak occurring that locks up the wallet application v0.8.3.21. It takes well over 10 minutes just to launch the application during which I can watch the memory usage climb to almost 1GB at about 2MB/s using Gnome System Monitor. Then the CPU thread is released and memory usage stays relatively static. If then I perform a transfer of BTQ to another address, it goes through fine but that's when the application goes back into 100% of one CPU thread and memory usage starts creeping upward about 100KB/s. I waited almost a half hour before killing the process which remains the only way to break free. Then restart and repeat if I want to make any more transfers. Really annoying.

[BitQuark]

Not sure if anyone else has run into this but on my Asus 1215n running Xubuntu 16.04.1 with Intel D525 Atom and 4G mem, there is definitely some kind of memory leak occurring that locks up the wallet application v0.8.3.21. It takes well over 10 minutes just to launch the application during which I can watch the memory usage climb to almost 1GB at about 2MB/s using Gnome System Monitor. Then the CPU thread is released and memory usage stays relatively static. If then I perform a transfer of BTQ to another address, it goes through fine but that's when the application goes back into 100% of one CPU thread and memory usage starts creeping upward about 100KB/s. I waited almost a half hour before killing the process which remains the only way to break free. Then restart and repeat if I want to make any more transfers. Really annoying.

I've noticed this same issue when running the bitquarkd on Linux systems and like you said this doesn't happen with v0.8.3.20. I'm going to look through the code and see if I can find what is causing this issue and do an update on the client. Thanks for your feedback Zero. I want sure if I was the only one experiencing this.
Thanks,
BTQ Dev

[ZeroFossilFuel]

If it helps to pinpoint the bug, the lock up condition occurs on the second consecutive transfer the instant you click the mouse to place the cursor in the amount field. Doesn't matter if it's before or after selecting inputs or even whether or not an address has been entered.

[loveinberlin]

Not sure if anyone else has run into this but on my Asus 1215n running Xubuntu 16.04.1 with Intel D525 Atom and 4G mem, there is definitely some kind of memory leak occurring that locks up the wallet application v0.8.3.21. It takes well over 10 minutes just to launch the application during which I can watch the memory usage climb to almost 1GB at about 2MB/s using Gnome System Monitor. Then the CPU thread is released and memory usage stays relatively static. If then I perform a transfer of BTQ to another address, it goes through fine but that's when the application goes back into 100% of one CPU thread and memory usage starts creeping upward about 100KB/s. I waited almost a half hour before killing the process which remains the only way to break free. Then restart and repeat if I want to make any more transfers. Really annoying.

I've noticed this same issue when running the bitquarkd on Linux systems and like you said this doesn't happen with v0.8.3.20. I'm going to look through the code and see if I can find what is causing this issue and do an update on the client. Thanks for your feedback Zero. I want sure if I was the only one experiencing this.
Thanks,
BTQ Dev

Dev is working hard behind BitQuark  .Thank you .

[BitQuark]

Dev is working hard behind BitQuark  .Thank you .

I try to stay on top with development of BitQuark.  I'm 110% dedicated :-)

[BitQuark]

I need some beta testers to test this pre-release of BitQuark-v0.8.3.22. I think I have the memory issue worked out, just need some tester to confirm.

http://downloads.bitquark.info/BitQuark-0.8.3r22-beta-src.zip

Post your feedback here.

Thanks,
BTQ Dev

P.S. - also added

• moneysupply - displays total coins minted via moneysupply command
• current block value via getmininginfo command

[ZeroFossilFuel]

I need some beta testers to test this pre-release of BitQuark-v0.8.3.22. I think I have the memory issue worked out, just need some tester to confirm.

http://downloads.bitquark.info/BitQuark-0.8.3r22-beta-src.zip

Post your feedback here.

Thanks,
BTQ Dev

P.S. - also added

• moneysupply - displays total coins minted via moneysupply command
• current block value via getmininginfo command

I'll do it, since I'm the one who complained. Should be easy to replicate. Need to break up my wallet into smaller bites first to test. Your dedication and the longevity of this alt coin is the reason I remain committed to it.

[ZeroFossilFuel]

Item 1: autobuild.sh still points to r20. Editing to r22, asked for a github user name and password. Thankfully, compilation proceeded anyway. Normally takes an hour or two on my little Atom D525. Forging on.......

[ZeroFossilFuel]

Compilation successful. Still took 12:34 to load the program and block index on this laptop computer (Only a couple minutes on my desktops).

Moving around some small amounts (10 & 20 BTQ at a time, no more than 3 inputs) half the time I'm getting transaction too large messages, asking for 0.00001 fee? The other half of the time they sail through without a fee. Kinda strange but whatever.

Then I repeated my steps. The problem persists. The first large amount I send to myself to consolidate the wallet (approx 20 inputs) goes through fine and I see memory usage increment about 2MB and hold there. Then, I can select all my inputs for the second transaction, enter the address to send to, but the instant I bring cursor focus to the amount field it locks up solid and starts eating memory 100-150KB/s.

Sorry. No joy. 

There was one small improvement, however. I did not have to use System Monitor to Kill the process. I was able to X out of the program and click OK at the "Program not responding" error message.

[tammuz]

Bounties
250 BTQ - News Article Promoting BitQuark
500 BTQ - Video Promoting BitQuark

Current exchange rate is $0.002858
So if someone make article, he/she will get $0.7 (in case of video $1.4) 

[BitQuark]

Bounties
250 BTQ - News Article Promoting BitQuark
500 BTQ - Video Promoting BitQuark

Current exchange rate is $0.002858
So if someone make article, he/she will get $0.7 (in case of video $1.4) 

Yeah when I originally posted that, the price was around 0.0004 - 0.0005 BTC. I will up it to
2500 BTQ - News Article Promoting BitQuark
5000 BTQ - Video Promoting BitQuark

[BitQuark]

Compilation successful. Still took 12:34 to load the program and block index on this laptop computer (Only a couple minutes on my desktops).

Moving around some small amounts (10 & 20 BTQ at a time, no more than 3 inputs) half the time I'm getting transaction too large messages, asking for 0.00001 fee? The other half of the time they sail through without a fee. Kinda strange but whatever.

Then I repeated my steps. The problem persists. The first large amount I send to myself to consolidate the wallet (approx 20 inputs) goes through fine and I see memory usage increment about 2MB and hold there. Then, I can select all my inputs for the second transaction, enter the address to send to, but the instant I bring cursor focus to the amount field it locks up solid and starts eating memory 100-150KB/s.

Sorry. No joy. 

There was one small improvement, however. I did not have to use System Monitor to Kill the process. I was able to X out of the program and click OK at the "Program not responding" error message.

Well damn, I will work on it some more to see if I can make it more memory friendly

[ZeroFossilFuel]

Well damn, I will work on it some more to see if I can make it more memory friendly

Yeah, I know. I hate being the bearer of bad news. I'm sure you'll find it, though.

[BitQuark]

Delisting from c-cex.com
RIP

Don't worry, it's not going to be delisted.

[kiencuong]

Delisting from c-cex.com
RIP

Don't worry, it's not going to be delisted.

Why did not you come up with a stronger action plan for it? It deserves to grow much stronger !!!

[Bitnet88]

Do you know if Masternodes could be implemented?
Low supply and good marketing strategy for the coin