 Show Posts
|
|
Pages: [1]
|
is this project death already? price is dropping badly nothing on twitter nothing on telegram channel almos nothing on discord also what happened? care to explain who is on dev team, nothing about dev team can be found anywhere. |
|
|
|
jimswers, very good job done, it's really useful toos to monitor our masternode, thank you so much for great effort! will donate some when i reach ROI in next few days! Hi, I set up new block explorer for Quaz.
This is my custom development.
Very fast & pretty:
https://quaz.overemo.com/
Masternodes stats & roi available:
https://quaz.overemo.com/masternodes
...
Tips QUAZ welcome to address: NEF1iEEXUu7EknoobQE4ueZxPiCSg8Ajx6
Customization of explorer interface is available by request.
possible to point custom DNS subdomain
|
|
|
|
is this: https://github.com/zacacoin/zacacoinsource code of wallets distributed on google drive? looking at the source, it's shitty result of copy & paste. [zacacoin]
> make -j1
/usr/lib/x86_64-linux-gnu/qt5/bin/qmake -o Makefile zaca-coi[Suspicious link removed]o
Cannot find file: zaca-coi[Suspicious link removed]o.
Makefile:791: recipe for target 'Makefile' failed
make: *** [Makefile] Error 2
it turned out that dev forget to rename file to zaca-coin dot pro so, copied zaca dot pro and zaca dot pro dot user to zaca-coin dot pro make again and ended up with this: src/qt/optionsdialog.cpp: In member function ‘void OptionsDialog::setMapper()’:
src/qt/optionsdialog.cpp:146:28: error: ‘class Ui::OptionsDialog’ has no member named ‘anonymizeZaca’
mapper->addMapping(ui->anonymizeZaca, OptionsModel::AnonymizeZacaAmount);
^
Makefile:4281: recipe for target 'build/optionsdialog.o' failed
. got to be careful, too many new coin/mn turned out to be scam. zaca developer? comment please? |
|
|
|
Kalo Nama sesuai dengan kita bisa gan, pesan nama bisa kan, nama ny dari kita, berpa harganya
thanks
iya mas, gak bisa order nama sendiri kah? bakal memudahkan soalnya kalau address kita macam begitu.
bisa, silahkan PM saya. |
|
|
|
since new smart contract deployed, we only got 1 important step to be done: TOKEN SWAP.
...
another important step: WALLPAPER! (not too) long awaited whitepaper is around the corner. deAphoteker |
|
|
|
|
since new smart contract deployed, we only got 1 important step to be done: TOKEN SWAP.
we almost make it, our promise to community when satoshi21 left:
WE WILL NOT GIVE UP EASILY!
and we will fulfill this, just 1 more step...
deAphoteker.
|
|
|
|
I was just checking the bitconnect thread and it started on Nov 2016 and has a total of 153 pages to this day. Bitcoin Cash thread started in July 2017 and to this day has 387 pages. Ebtc thread started on Sept 2017 and in about 1 month it has a whopping 297 pages. lol There sure is a huge interest. If there weren't any coding problems who knows how high the value would be by now. lol Something to think about while we wait for the new contract.  thank you for doing interesting stat let's not waste this momentum. trust is there huge community support is there this is not just a coin, this is eBTCdeAphoteker |
|
|
|
i would give my vote for: #23 by tgl277 it's so simple but geometrically sexy  |
|
|
|
i started ewbf with these: /usr/local/bin/ewbf-miner-0.3.4b --server asia1-zcash.flypool.org --port 3333 --user t1B8vu*.gpu0 --pass x --cuda_devices 0 --logfile /var/log/gpu0.log --log 2 --templimit 74 --pec
/usr/local/bin/ewbf-miner-0.3.4b --server asia1-zcash.flypool.org --port 3333 --user t1B8vu*.gpu1 --pass x --cuda_devices 1 --logfile /var/log/gpu1.log --log 2 --templimit 74 --pec
/usr/local/bin/ewbf-miner-0.3.4b --server asia1-zcash.flypool.org --port 3333 --user t1B8vu*.gpu2 --pass x --cuda_devices 2 --logfile /var/log/gpu2.log --log 2 --templimit 74 --pec
/usr/local/bin/ewbf-miner-0.3.4b --server asia1-zcash.flypool.org --port 3333 --user t1B8vu*.gpu3 --pass x --cuda_devices 3 --logfile /var/log/gpu3.log --log 2 --templimit 74 --pec
/usr/local/bin/ewbf-miner-0.3.4b --server asia1-zcash.flypool.org --port 3333 --user t1B8vu*.gpu4 --pass x --cuda_devices 4 --logfile /var/log/gpu4.log --log 2 --templimit 74 --pec this is single rig with 4 1080Ti (gpu 0-3) and 1 1080 (gpu 4). nvidia-smi output: Sun Sep 3 19:38:25 2017
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 384.47 Driver Version: 384.47 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 108... On | 00000000:01:00.0 Off | N/A |
| 23% 51C P2 202W / 190W | 3305MiB / 11172MiB | 97% Default |
+-------------------------------+----------------------+----------------------+
| 1 GeForce GTX 108... On | 00000000:02:00.0 Off | N/A |
| 13% 48C P2 202W / 200W | 669MiB / 11172MiB | 97% Default |
+-------------------------------+----------------------+----------------------+
| 2 GeForce GTX 108... On | 00000000:03:00.0 Off | N/A |
| 40% 56C P2 199W / 200W | 669MiB / 11172MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
| 3 GeForce GTX 108... On | 00000000:05:00.0 Off | N/A |
| 18% 50C P2 201W / 200W | 669MiB / 11172MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
| 4 GeForce GTX 1080 On | 00000000:06:00.0 Off | N/A |
| 78% 56C P2 169W / 170W | 631MiB / 8114MiB | 99% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 11047 C /usr/local/bin/ewbf-miner-0.3.4b 659MiB |
| 0 11048 C /usr/local/bin/ewbf-miner-0.3.4b 659MiB |
| 0 11049 C /usr/local/bin/ewbf-miner-0.3.4b 659MiB |
| 0 11050 C /usr/local/bin/ewbf-miner-0.3.4b 659MiB |
| 0 11051 C /usr/local/bin/ewbf-miner-0.3.4b 659MiB |
| 1 11048 C /usr/local/bin/ewbf-miner-0.3.4b 659MiB |
| 2 11049 C /usr/local/bin/ewbf-miner-0.3.4b 659MiB |
| 3 11050 C /usr/local/bin/ewbf-miner-0.3.4b 659MiB |
| 4 11051 C /usr/local/bin/ewbf-miner-0.3.4b 621MiB |
+-----------------------------------------------------------------------------+
to me looks like gpu0 also used by pid of gpu1-gpu4, any idea why this is happened and is there any performance impact? |
|
|
|
Has anyone got more hash out of the following card ?
1080ti ASUS TURBO
I now have around 710 - 730 sols ...ewbf 0.3.4 b on windows 10
yes 1080Ti ichill ewbf-miner-0.3.4b on ubuntu 16.4 64bit  ps: 1080Ti is gpu0 in that picture |
|
|
|
i try to compile on Ubuntu 16.04 but display this error at the and of make.
ccminer-ccminer.o: nella funzione "miner_thread(void*)":
ccminer.cpp:(.text+0x7b75): riferimento non definito a "scanhash_timetravel10"
...
anyone can help me?
patch Makefile.am with this: --- Makefile.am 2017-08-24 16:53:35.000000000 +0700
+++ Makefile.am.stock 2017-08-24 20:45:35.000000000 +0700
@@ -66,7 +66,7 @@
qubit/qubit.cu qubit/qubit_luffa512.cu qubit/deep.cu qubit/luffa.cu \
x11/x11.cu x11/fresh.cu x11/cuda_x11_luffa512.cu x11/cuda_x11_cubehash512.cu \
x11/cuda_x11_shavite512.cu x11/cuda_x11_simd512.cu x11/cuda_x11_echo.cu \
- x11/cuda_x11_luffa512_Cubehash.cu x11/x11evo.cu x11/timetravel.cu x11/timetravel10.cu x11/bitcore.cu \
+ x11/cuda_x11_luffa512_Cubehash.cu x11/x11evo.cu x11/timetravel.cu x11/bitcore.cu \
x13/x13.cu x13/cuda_x13_hamsi512.cu x13/cuda_x13_fugue512.cu \
x15/x14.cu x15/x15.cu x15/cuda_x14_shabal512.cu x15/cuda_x15_whirlpool.cu \
x15/whirlpool.cu x15/cuda_x15_whirlpool_sm3.cu \ then: rm Makefile.in ; make clean ; make distclean ; ./autogen.sh ; ./configure ; make |
|
|
|
I seem to not be able to compile it on Debian 9 Linux. I followed the instructions on the Nicehash website and most of it works, except for the make. It goes for awhile but it eventually failed with an error.
P.S. i had to modify the makefile slightly to use clang compiler as it couldn't find any other.
lookslike there's a compatibility issue btween nvcc & clang, i've compiled with gcc without problem, try gcc. |
|
|
|
You're welcome, thanks for all details  Just one detail, According your info posted CORE=1643 MHz but MEMORY value is missing, please add it to update benchmark on website. memory used? i think this ss will explain better  |
|
|
|
GPU's MODEL NAME: GeForce GTX 1080 Ti VRAM: 11GB GDDR5X CORE/MEMORY CLOCK: 1643 MHz HASHRATE: 687sol/s MINER SOFTWARE: EWBF's CUDA Zcash miner 0.3.4b OS: stripped down x86_amd64 ubuntu 16.04 DRIVERS: CUDA 8.0 TDP(OPTIONAL): 220W  CUDA Version: 8.0 CUDA Devices: 1 Device #0 (GeForce GTX 1080 Ti): Clock Rate: 1643 MHz Is Integrated: false Compute Capability: 6.1 Kernel Concurrency: 1 Max Grid Size: 2147483647 Max Threads per Block: 1024 Registers per Block: 65536 Registers per SM: 65536 Processor Count: 28 Shared Memory/Block: 49152 Shared Memory/Proc: 98304 Warp Size: 32  tx for puting efforts on that benchmark site! |
|
|
|
|
