 Show Posts
|
|
Pages: [1] 2 3 4 »
|
bat.minersbest.com is ready to launch
we have after starting the pool directly 60% of nethashrate. we have stopped it again and wait for more hashrate on network or launching date for pools again.
payouts actually work!
we have more than 6.000.000 BATs transfert to the pool wallet to balance the losts.
i hope that now all work and we have no more problems with the wallets.
What happened to my Withdraw? Am I still going to get it? we must go back to the block 3476. sorry, make a manual payout now. |
|
|
|
|
bat.minersbest.com is ready to launch
we have after starting the pool directly 60% of nethashrate. we have stopped it again and wait for more hashrate on network or launching date for pools again.
payouts actually work!
we have more than 6.000.000 BATs transfert to the pool wallet to balance the losts.
i hope that now all work and we have no more problems with the wallets.
|
|
|
|
guys if you won't stop solo with the wallets we won't be able to fix it
the old code is heavily bugged and can cause a fork ON ERVERY BLOCK
we are fixing one fork and finding ourselves on another 3
Hi, Is minersbest on the proper chain or not really? i hope, we are on the latest source an the wallet say sync. |
|
|
|
BatCoin - Mining Pool Server - http://bat.minersbest.com- Stratum - VARDIFF - PPNLS - 1% Fee - network protection (DDoS) - stable Server - great internet connectivity online
|
|
|
|
payouts working again after Batman fix the bug in the wallet Do you mean payouts WILL be working again after Batman fixes the bug in the wallet or Batman has fixed the bug in the wallet and payout are now working? will be, sorry :-D |
|
|
|
payouts working again after Batman fix the bug in the wallet |
|
|
|
|
can anyone make a hardfork?
|
|
|
|
POOLS SHOULD UPDATE TO THE NEW SOURCE
done! |
|
|
|
We are testing our pool, not sure if everything works, but my workers are connected. Help us test if you want: http://qbt.minersbest.com/get an account and use -o stratum+tcp://qbt.minersbest.com:10474 -u Weblogin.Worker -p Worker password in your batch. we have closed the pool. |
|
|
|
We are testing our pool, not sure if everything works, but my workers are connected. Help us test if you want: http://qbt.minersbest.com/get an account and use -o stratum+tcp://qbt.minersbest.com:10474 -u Weblogin.Worker -p Worker password in your batch. Your pool can be reach. However, my worker is still not active, on your pool. And the number of pool worker is ZERO. same here, using - C:\qbit\minerd64.exe -a qubit --url=stratum+tcp://qbt.minersbest.com:10474 --userpass=xxx.xxx:xx -t 4 connects and hashing away but not reported in pool Ok, I give up. I come back to XRP , at least giving my contribution to "scientific" development, instead of wasting time on this crazy coin. all shares at the moment invalid, i dont know, the reason are the diff or the pool. i check the pool at the moment |
|
|
|
so many error
chmod a+x ./leveldb/build_detect_platform
mkdir obj
git clone ... cd QubitCoin/src chmod a+x leveldb/build_detect_platform mkdir obj cd leveldb make cd .. make -f makefile.unix USE_UPNP=- .... i become a error |
|
|
|
Yes. That's why I use solo mining now and network I listen from nutpool stratum. No blocks found for over 30 minutes, woot 
we find blocks :-) |
|
|
|
|
vcc.minersbest.com -> problem solved!
|
|
|
|
|
wait 5 min for become the right diff.
|
|
|
|
Good to know. Looks like still found better with solo mining  nice hashrate per worker :-) have you an proxy running? |
|
|
|
Geez you run a few pools. No problem.
thank you .-) |
|
|
|
is running smoothly since the pool was launched.
Really? The coin launched at 18:00:00 not at 21:49:10. We are the only working pool at launch. But we have a downtime - i know :-D Are you up now minersbest? I try your pool but hashrate cant see on the pool. So I change to try other pool untill I know all is fine. ^^ yes all is fine :-D we are up and running ... your hashrate display 1-2 min after worker start. we find blocks and i cant find any problem :-) |
|
|
|
is running smoothly since the pool was launched.
Really? The coin launched at 18:00:00 not at 21:49:10. We are the only working pool at launch. But we have a downtime - i know :-D Which is why I wrote since the pool launch, not coin launch. oh ... sorry i has read it wrong :-D |
|
|
|
is running smoothly since the pool was launched.
Really? The coin launched at 18:00:00 not at 21:49:10. We are the only working pool at launch. But we have a downtime - i know :-D |
|
|
|
|
