Topic: [ANN] [BTQ] BitQuark | Super secure hashing | CPU mining - page 54. (Read 162292 times)
█ ★BitQuark (BTQ) █→ Now Live on: http://www.cryptocoinrank.com/BitQuark
Hope you like it! You can also display your Dev news just by creating two widgets and sending me the information like described here: https://bitcointalksearch.org/topic/annwwwcryptocoinrankcom-for-sale-for-sale-for-sale-579901
Enjoy
Awesome! That's right sir! I figured I would add the commands so that the users could build the *.a files in the leveldb directory. Now I just got to figure out how to build a static Linux version so I can add it to the download section.
Good luck with that one. I would think that would be much further down the list of priorities. BTW, I have CentOS running on my wife's laptop. I'll give it a go on that also to try and cover more bases. That should also translate to RedHat. 
SUCCESS!!! 
My only comment would be to "cd .." one more time from the /src directory before running qmake and make. It will not run while working directory is inside /src.
@Wendy5 see this goofy guy's explanation... https://www.youtube.com/watch?v=JVf_jT4DqvA
My only comment would be to "cd .." one more time from the /src directory before running qmake and make. It will not run while working directory is inside /src.
@Wendy5 see this goofy guy's explanation... https://www.youtube.com/watch?v=JVf_jT4DqvA
Awesome! That's right sir! I figured I would add the commands so that the users could build the *.a files in the leveldb directory. Now I just got to figure out how to build a static Linux version so I can add it to the download section.
looking to buy 10k - 50k btq
please pm offer
please pm offer
SUCCESS!!!
My only comment would be to "cd .." one more time from the /src directory before running qmake and make. It will not run while working directory is inside /src.
@Wendy5 see this goofy guy's explanation... https://www.youtube.com/watch?v=JVf_jT4DqvA
My only comment would be to "cd .." one more time from the /src directory before running qmake and make. It will not run while working directory is inside /src.
@Wendy5 see this goofy guy's explanation... https://www.youtube.com/watch?v=JVf_jT4DqvA
is it other quark?just clone?
Ok I think I have the source code fix on github so that you can compile it on Linux. I need someone to try and compile it to confirm that it works. Make sure to follow the "Quick Installation.txt" cuz I had to add the following to the file plus a couple of other files in the leveldb directory.
cd src/leveldb
chmod +x build_detect_platform
./build_detect_platform build_config.mk ./
cd ..
make -f makefile.unix
***You may need to delete the "libleveldb.a" & "libmemenv.a" files first and once you run the above command it should build them as along as you have the deps installed.
***Deps
http://www.openssl.org/source/openssl-1.0.1g.tar.gz
http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
http://sourceforge.net/projects/boost/files/boost/1.54.0/boost_1_54_0.tar.gz/download
http://miniupnp.tuxfamily.org/files/download.php?file=miniupnpc-1.8.tar.gz
I don't understand. Aside from the two incorrect leveldb files that I download according to the previous instructions and miniupnpc gotchas I keep running into, I've been building on Linux all along. One of those node IP you've been sharing is actually me since I have my wallet and daemon up 24/7. Xubuntu 12.04 or 13.10, libdb4.8 and libdb5.1 with libdb5.1-dev.cd src/leveldb
chmod +x build_detect_platform
./build_detect_platform build_config.mk ./
cd ..
make -f makefile.unix
***You may need to delete the "libleveldb.a" & "libmemenv.a" files first and once you run the above command it should build them as along as you have the deps installed.
***Deps
http://www.openssl.org/source/openssl-1.0.1g.tar.gz
http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
http://sourceforge.net/projects/boost/files/boost/1.54.0/boost_1_54_0.tar.gz/download
http://miniupnp.tuxfamily.org/files/download.php?file=miniupnpc-1.8.tar.gz
Oh, wait, now I see what you're doing; building the leveldb files locally. Please stand by..................................................
Ok I think I have the source code fix on github so that you can compile it on Linux. I need someone to try and compile it to confirm that it works. Make sure to follow the "Quick Installation.txt" cuz I had to add the following to the file plus a couple of other files in the leveldb directory.
cd src/leveldb
chmod +x build_detect_platform
./build_detect_platform build_config.mk ./
cd ..
make -f makefile.unix
***You may need to delete the "libleveldb.a" & "libmemenv.a" files first and once you run the above command it should build them as along as you have the deps installed.
***Deps
http://www.openssl.org/source/openssl-1.0.1g.tar.gz
http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
http://sourceforge.net/projects/boost/files/boost/1.54.0/boost_1_54_0.tar.gz/download
http://miniupnp.tuxfamily.org/files/download.php?file=miniupnpc-1.8.tar.gz
cd src/leveldb
chmod +x build_detect_platform
./build_detect_platform build_config.mk ./
cd ..
make -f makefile.unix
***You may need to delete the "libleveldb.a" & "libmemenv.a" files first and once you run the above command it should build them as along as you have the deps installed.
***Deps
http://www.openssl.org/source/openssl-1.0.1g.tar.gz
http://download.oracle.com/berkeley-db/db-4.8.30.NC.tar.gz
http://sourceforge.net/projects/boost/files/boost/1.54.0/boost_1_54_0.tar.gz/download
http://miniupnp.tuxfamily.org/files/download.php?file=miniupnpc-1.8.tar.gz
I need to hook you up with Raptor. He's in your neck of the woods.
On another note, I bought a couple nVidia cards thinking I was going to get ccminer working. Compiling and getting all the necessary modules working has turned out to be a HUGE F*CK*NG PAIN IN MY @$$!!! Two solid days later I have compiled but as of yet have failed to get ccminer to run correctly. I admire Christian and his work but this is a fiasco.
On another note, I bought a couple nVidia cards thinking I was going to get ccminer working. Compiling and getting all the necessary modules working has turned out to be a HUGE F*CK*NG PAIN IN MY @$$!!! Two solid days later I have compiled but as of yet have failed to get ccminer to run correctly. I admire Christian and his work but this is a fiasco.
http://www.coindesk.com/all-things-alt-quarks-shaq-cess-blackcoins-pr-pivot-and-dogecoins-victory-lap/
I would love to do something like what Dogecoin has done in this article! Maybe by next race season BitQuark will have enough traction to do something like this to reach the masses!!! I live in NC and I know a few people in NASCAR so this is definitely doable guys!!!
I would love to do something like what Dogecoin has done in this article! Maybe by next race season BitQuark will have enough traction to do something like this to reach the masses!!! I live in NC and I know a few people in NASCAR so this is definitely doable guys!!!
Looks like https://cpu-pool.net/btq MPOS pool is back up and working right 
Good news guys! BitQuark will be added to http://www.qex.la with in the month after they launch!
looking to buy 10k - 50k btq
please pm offer
please pm offer
thank u, it works now:)
hi,
i opened port 9596 in my tp-lin router for ip 192.168.1.100
i have my bitquark.conf file:
rpcuser=bitquark
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.1.100 (my internal ip ipv4)
rpcport=9108
port=9596
gen=0
server=1
listen=1
i added manually nodes to wallet:
5.9.158.79:9596
173.216.108.94:9596
62.210.123.27:9596
85.25.195.74:9596
76.93.160.74:9596
178.162.192.197:9596
60.241.60.227:9596
217.68.242.45:9596
109.95.19.151:9596
and still wallet will not sync:(
please advise what i should change?
i opened port 9596 in my tp-lin router for ip 192.168.1.100
i have my bitquark.conf file:
rpcuser=bitquark
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.1.100 (my internal ip ipv4)
rpcport=9108
port=9596
gen=0
server=1
listen=1
i added manually nodes to wallet:
5.9.158.79:9596
173.216.108.94:9596
62.210.123.27:9596
85.25.195.74:9596
76.93.160.74:9596
178.162.192.197:9596
60.241.60.227:9596
217.68.242.45:9596
109.95.19.151:9596
and still wallet will not sync:(
please advise what i should change?
These are the the connections I have right now.
62.210.113.211:9596
173.216.108.94:9596
62.210.123.27:9596
46.165.208.136:9596
85.25.195.74:9596
60.241.60.227:9596
5.9.158.79:9596
74.138.244.79:9596
76.182.189.115:9596
81.174.133.189:9596
128.2.209.18:9596
151.231.157.105:9596
74.90.54.187:9596
70.123.187.172:9596
It may not be a bad thing. More hash power means more value of this coin, and may be accepted by more exchanges because of that. I haven't follow up in time when Chris released 0.9. When I got there, the difficulty was very high and I switched to other coins. Now I am in and able to find some blocks. I have no idea on how quickly you can find the blocks before (Chris said he can quickly find it out every a couple of min when difficulty was 70), but now it seems still reasonable -- I only put some of my 750Tis here, and still able to find blocks in acceptable duration.
You will face the difficulty rise eventually. Just keep mining and get as much as you can before it gets really hard. But maybe around that time, it is your cash out time as well.
BitQuark looks nice and not like a pump and dump one so far, and let's wish the best future for it. Quark coin is sailing away already, and hopefully we can catch this boat in time....
You will face the difficulty rise eventually. Just keep mining and get as much as you can before it gets really hard. But maybe around that time, it is your cash out time as well.
BitQuark looks nice and not like a pump and dump one so far, and let's wish the best future for it. Quark coin is sailing away already, and hopefully we can catch this boat in time....
hi,
i opened port 9596 in my tp-lin router for ip 192.168.1.100
i have my bitquark.conf file:
rpcuser=bitquark
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.1.100 (my internal ip ipv4)
rpcport=9108
port=9596
gen=0
server=1
listen=1
i added manually nodes to wallet:
5.9.158.79:9596
173.216.108.94:9596
62.210.123.27:9596
85.25.195.74:9596
76.93.160.74:9596
178.162.192.197:9596
60.241.60.227:9596
217.68.242.45:9596
109.95.19.151:9596
and still wallet will not sync:(
please advise what i should change?
i opened port 9596 in my tp-lin router for ip 192.168.1.100
i have my bitquark.conf file:
rpcuser=bitquark
rpcpassword=password
rpcallowip=127.0.0.1
rpcallowip=192.168.1.100 (my internal ip ipv4)
rpcport=9108
port=9596
gen=0
server=1
listen=1
i added manually nodes to wallet:
5.9.158.79:9596
173.216.108.94:9596
62.210.123.27:9596
85.25.195.74:9596
76.93.160.74:9596
178.162.192.197:9596
60.241.60.227:9596
217.68.242.45:9596
109.95.19.151:9596
and still wallet will not sync:(
please advise what i should change?
Just put in a request to have BTQ added to http://qex.la/ It's an exchange that deals specifically with quark algo coins.
Right now BTQ retargets once every 10 mins (20 blocks), so you guys want it switched to retargeting every 30 sec (1 block)
Right now BTQ retargets once every 10 mins (20 blocks), so you guys want it switched to retargeting every 30 sec (1 block)
Maybe
Linear averaging with up/down limit such as +15/-30
I think it become a very typical requirements for the modern coin to protect the miner from the sneaky pool and miners.
And, qex.la, it is so good news,
the current up/down is +-400%
I will look into changing the targeting to every 30 secs, but from what I've been reading on these other guys thread they will be out of here soon and onto another coin.
maybe that is a kind of doule edge sword, anyway, I hope there is something for the devoted miner in this coin.
actually, the hopper is not a big benefit for the coin, the number of devoted miner is more important I guess,
I just just my personal though,
Just put in a request to have BTQ added to http://qex.la/ It's an exchange that deals specifically with quark algo coins.
Right now BTQ retargets once every 10 mins (20 blocks), so you guys want it switched to retargeting every 30 sec (1 block)
Right now BTQ retargets once every 10 mins (20 blocks), so you guys want it switched to retargeting every 30 sec (1 block)
Maybe
Linear averaging with up/down limit such as +15/-30
I think it become a very typical requirements for the modern coin to protect the miner from the sneaky pool and miners.
And, qex.la, it is so good news,
the current up/down is +-400%
I will look into changing the targeting to every 30 secs, but from what I've been reading on these other guys thread they will be out of here soon and onto another coin.
Just put in a request to have BTQ added to http://qex.la/ It's an exchange that deals specifically with quark algo coins.
Right now BTQ retargets once every 10 mins (20 blocks), so you guys want it switched to retargeting every 30 sec (1 block)
Right now BTQ retargets once every 10 mins (20 blocks), so you guys want it switched to retargeting every 30 sec (1 block)
Maybe
Linear averaging with up/down limit such as +15/-30
I think it become a very typical requirements for the modern coin to protect the miner from the sneaky pool and miners.
And, qex.la, it is so good news,
the current up/down is +-400%
I will look into changing the targeting to every 30 secs, but from what I've been reading on these other guys thread they will be out of here soon and onto another coin.
Jump to: