Who in charge for qubitxplorer? I have create temporary iquidus explorer with better seo for tittle and added market, unfortunately I can't host it on my server. here is the demo: https://q2c.altexplorer.xyz/ source code: https://github.com/jemekite/q2c-explorer |
|
|
|
W00t...  "networkhashps" : 549147501 Is this all yours networkhashps? Have you resolve your rpc problem for p2pool? P2Pool Logs: dev@dev-mint ~/src/p2pool-q2c $ ./run_p2pool.py --net qubitcoin --give-author 0 -f 0
2016-09-29 09:13:29.039084 p2pool (version 16.0-4-gde1be30-dirty)
2016-09-29 09:13:29.039154
2016-09-29 09:13:29.039214 Testing bitcoind RPC connection to 'http://127.0.0.1:7799/' with username 'qubitrpc'...
2016-09-29 09:13:29.042899 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:30.049286 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:31.054248 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:32.060554 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port! No, I'm not mining right now. I still can't resolve P2Pool RPC problem, can you help? repo is here: https://github.com/jemekite/p2pool-qubitcoin It's work great with v0.8.4.1 |
|
|
|
W00t... "networkhashps" : 549147501 |
|
|
|
Pool still not showing correct hashrate...  |
|
|
|
Hi Guys
I am having issues with the dat file for the the wallet, on the old wallet i have it will not update, when copying the dat file to the new wallet it does not work, just want to make sure i do not lose any more noble coins. any have any idea how to get it to work?.
Open your wallet with PoW version of NOBL and export your private key then import your privkey with new PoS wallet More info here: https://github.com/eagleflies/noblecoin/wiki/Importing-private-keys-from-old-wallet.dat-using---salvagewallet-option |
|
|
|
@penambang you can test it on theblocksfactory qubit algo bigibyte my cart gtx 1060 when minining qubit miner showing 12Mh/s and at the grayminer pool showing only 44Kh/s Thanks k0stas, I don't have account there, but here is test result with suprnova dgb  Miner rented from miningrigrentals |
|
|
|
I'm mining with 500+ Mhs but only showed as 2 Mhs on graymines?  |
|
|
|
|
block explorer seems stuck on block 2009297
|
|
|
|
|
what is current vior best block? I'm stuck at 738100
|
|
|
|
willowrose, any idea why rpc won't connected? I tried to setup p2pool on my ubuntu. my QubitCoin.conf server=1
daemon=1
listen=1
rpcuser=qubitrpc
rpcpassword=xxx
rpcport=7799 P2Pool Logs: dev@dev-mint ~/src/p2pool-q2c $ ./run_p2pool.py --net qubitcoin --give-author 0 -f 0
2016-09-29 09:13:29.039084 p2pool (version 16.0-4-gde1be30-dirty)
2016-09-29 09:13:29.039154
2016-09-29 09:13:29.039214 Testing bitcoind RPC connection to 'http://127.0.0.1:7799/' with username 'qubitrpc'...
2016-09-29 09:13:29.042899 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:30.049286 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:31.054248 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port!
2016-09-29 09:13:32.060554 > Check failed! Make sure that you're connected to the right bitcoind with --bitcoind-rpc-port! Debug.log 2016-09-29 02:09:18 Qubitcoin version v0.11.2.1 (2016-09-24 20:19:42 +0200)
2016-09-29 02:09:18 Using OpenSSL version OpenSSL 1.0.2g 1 Mar 2016
2016-09-29 02:09:18 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010)
2016-09-29 02:09:18 Default data directory /home/dev/.QubitCoin
2016-09-29 02:09:18 Using data directory /home/dev/.QubitCoin
2016-09-29 02:09:18 Using config file /home/dev/.QubitCoin/QubitCoin.conf
2016-09-29 02:09:18 Using at most 125 connections (1024 file descriptors available)
2016-09-29 02:09:18 Using 6 threads for script verification
2016-09-29 02:09:18 scheduler thread start
2016-09-29 02:09:18 Binding RPC on address ::1 port 7799 (IPv4+IPv6 bind any: 0)
2016-09-29 02:09:18 Binding RPC on address 127.0.0.1 port 7799 (IPv4+IPv6 bind any: 0)
2016-09-29 02:09:18 Using wallet wallet.dat
2016-09-29 02:09:18 init message: Verifying wallet...
2016-09-29 02:09:18 CDBEnv::Open: LogDir=/home/dev/.QubitCoin/database ErrorFile=/home/dev/.QubitCoin/db.log
2016-09-29 02:09:18 Bound to [::]:7788
2016-09-29 02:09:18 Bound to 0.0.0.0:7788
Netstat: dev@dev-mint ~/src/p2pool-q2c $ netstat -an | grep 7799
tcp 0 0 127.0.0.1:7799 0.0.0.0:* LISTEN
tcp6 0 0 ::1:7799 :::* LISTEN |
|
|
|
|
any idea how to combine mining dust? I have lot of 1 Q2C mined.
|
|
|
|
There is a bug in latest wallet for windows. I couldn't mining with it, got this error when set gen=1 in config or setgenerate true in wallet  |
|
|
|
|
I'll setup latest build on my server to support q2c network.
Any bootstrap available to speed-up sync process?
|
|
|
|
That's exactly what i need, thank you mr. cryptonit. Only one problem - i don't have old pow wallet v.1.0.0.[0-1]. Guys, can someone pls share old wallet if it is still on your hard disk drive. Links on noble site is broken, on wiki same  Here you go: https://transfer.sh/O97GZ/noblecoin-qt-pow.7z |
|
|
|
When will resume network?
Releasing update today with tweak to difficulty calculation to fix problem and prevent it from happening again. Mining will resume from block 2394 with new difficulty parameter. Basically the difficulty adjustment was set too aggressive such that when an aberrant block timestamp came in the difficulty adjustment was too severe for the protocol to allow, so the work from that point on was not accepted. I've made a change to the difficulty adjustment which averages the exponential adjustment rate of the difficulty over a longer period and prevents this from happening again. This new difficulty rate will actually be better for the network overall too. The difficulty was purposely set aggressive so that the variable block time quickly ensures that the chain with the most power will always have the shortest block time and be longest chain. It was just set a bit too aggressive for a larger deviation in the block time stamping. |
|
|
|
|
I hope tor will be updated to v0.2.8.7 on next major update.
|
|
|
|
Latest bootstrap.dat for Britcoin https://transfer.sh/1UJKe/britcoin-bootstrap.tar.xz Please mirror it to another site, files will be automatically deleted after 15 days |
|
|
|
We desperately need people staking. Please get your Brits staking!
I have full node staking all the time, and yes... we need more staking wallet... |
|
|
|
|
Show Posts
