Topic: [ANN][Q2C] QubitCoin new secure hashing (CPU/GPU) (NEW) Update 0.8.4.1 - page 228. (Read 351528 times)

you can configure this parameters in qubitcoin.conf

Hey, you've got time to compile windows wallet and windows miner. Launching without win wallet is a fail.

+10000000

+10086

+1

Thanks. Usually I have a QT wallet running that provides RPC port with User/Pass. In this case we have no source code, is user 123 and pass hardcoded and can I just c&p your line or where do I configure it?

Oh god please don't release without a Windows wallet, you'll get lots of bad PR. Ask a honorable dev if he can help you, we all know how much compiling on Windows sucks.

So, in 1001 block diff be retargeted 50 times?

So for the first few hours it won't be worth mining, but tomorrow it will kick off when the blocks become 2048...
I like the innovation, shame that other than the hashing it is a near exact quark clone.

example
./minerd -a qubit -o http://127.0.0.1:7799 -u 123 -p 1234567890qwertyuiop -t 2

To run the minderd at launch, do I need to set any settings or just call it ./minderd (on Unix)?

which is the algo name btw?

thank you shai_ found it

working tutorial posted!  

https://bitcointalksearch.org/topic/how-to-mine-qubitcoin-qbt-using-digital-ocean-vps-412342

Yeah can please anyone compile and upload that cpu miner for win 64x?

chmod +x autogen.sh ; ./autogen.sh

or

sh autogen.sh

build on linux ubuntu without many problems

i think for the dependencies run: sudo apt-get install build-essential automake autoconf m4 yasm libssl-dev libcurl4-gnutls-dev
(i probably forget something)
and then: sh ./autogen.sh
(or run: chmod +x autogen.sh ; ./autogen.sh)

./configure
make

shai@shai-Aspire-V3-551:~/QubitCoin-cpuminer$ ldd minerd
   linux-vdso.so.1 =>  (0x00007fff90fff000)
   libcurl.so.4 => /usr/lib/libcurl.so.4 (0x00007f1916403000)
   libjansson.so.4 => /usr/local/lib/libjansson.so.4 (0x00007f19161f7000)
   libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f1915fd8000)
   libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f1915c40000)
   libidn.so.11 => /usr/lib/libidn.so.11 (0x00007f1915a0d000)
   liblber-2.4.so.2 => /usr/lib/liblber-2.4.so.2 (0x00007f19157fe000)
   libldap_r-2.4.so.2 => /usr/lib/libldap_r-2.4.so.2 (0x00007f19155b3000)
   librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f19153ab000)
   libgssapi_krb5.so.2 => /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 (0x00007f1915175000)
   libssl.so.0.9.8 => /lib/libssl.so.0.9.8 (0x00007f1914f22000)
   libcrypto.so.0.9.8 => /lib/libcrypto.so.0.9.8 (0x00007f1914b93000)
   libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f191497a000)
   /lib64/ld-linux-x86-64.so.2 (0x00007f1916682000)
   libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007f191475f000)
   libsasl2.so.2 => /usr/lib/libsasl2.so.2 (0x00007f1914545000)
   libgnutls.so.26 => /usr/lib/x86_64-linux-gnu/libgnutls.so.26 (0x00007f19142a3000)
   libgcrypt.so.11 => /lib/x86_64-linux-gnu/libgcrypt.so.11 (0x00007f1914029000)
   libkrb5.so.3 => /usr/lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007f1913d65000)
   libk5crypto.so.3 => /usr/lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007f1913b3d000)
   libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007f1913939000)
   libkrb5support.so.0 => /usr/lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007f1913731000)
   libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f191352c000)
   libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007f1913329000)
   libtasn1.so.3 => /usr/lib/x86_64-linux-gnu/libtasn1.so.3 (0x00007f1913117000)
   libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f1912f13000)

QubitCoin, I've sent you a PM.

In what order is the hashing of the algo's done?

For us to get the pool working, we need something like this:

https://github.com/Neisklar/quarkcoin-hash-python/blob/master/setup.py

Could anyone build the CPU miner? I can't get my VS to work.

Yes, it will. I am debating whether to mine it at all.

Is the wallet miner different from the CPUminer?