[ANN][Q2C] QubitCoin new secure hashing (CPU/GPU) (NEW) Update 0.8.4.1

[P4rkeR]

good job P4rkeR, but we have a network of nodes that are making noise - every now and again stuck windows wallet. On linux network fortunately does not stop

This new node is on linux network

[wgd]

if someone is able to explain what's going on here? wallet stuck ;/

current block to 897xxx and the arrest shows the last block 1174427  Is it possible that some old test network we try to fasten with this current


Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000127a55a99697d786569e8a2ad38b280bef09baa9e38efce5a8eafcede  height=897937  log2_work=52.847152  tx=1273503  date=2014-11-14 23:19:05 progress=1.000001
ProcessBlock: ACCEPTED
received getdata for: block 0000000127a55a99697d786569e8a2ad38b280bef09baa9e38efce5a8eafcede
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 174.97.15.1:11973 lastseen=598.4hrs
connection timeout
trying connection 2.85.190.125:7788 lastseen=41.4hrs
ProcessSyncCheckpoint: pending for sync-checkpoint 0000000010b64111d2b238bb14c91c15d8b0de7405fbd848c58bfd7ba8129d77
ProcessSyncCheckpoint: pending for sync-checkpoint 0000000010b64111d2b238bb14c91c15d8b0de7405fbd848c58bfd7ba8129d77
ProcessSyncCheckpoint: pending for sync-checkpoint 0000000010b64111d2b238bb14c91c15d8b0de7405fbd848c58bfd7ba8129d77
received block 7da219df4ae80b9180b62a4b0869415ee1d81833fc03e8aacd44516c3682fa5c
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 77.249.199.235:19994 (0 -> 50)
received block 7ee0e90eb1cd3b958ca8d2eb7b990d70a1da64b347ca69d002cdc4dbf46bed12
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 77.249.199.235:19994 (50 -> 100) DISCONNECTING
disconnecting node 77.249.199.235:19994
trying connection 5.9.56.229:7788 lastseen=365557.5hrs
received block 3bfb32a3823cc2f3e954ba0977f29c7f6ad5002a05d9293abc1c4c1b5155ae7d
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 78.46.30.116:11973 (0 -> 50)
received block 75dc3c92cecbb9361cd9c518b7c58b446ff5691922271dad37b6c4c8a212aa0b
ERROR: CheckProofOfWork() : hash doesn't match nBits
ERROR: CheckBlock() : proof of work failed
ERROR: ProcessBlock() : CheckBlock FAILED
Misbehaving: 78.46.30.116:11973 (50 -> 100) DISCONNECTING
disconnecting node 78.46.30.116:11973


root@vps1094:~# ./QubitCoind getpeerinfo|grep subver
        "subver" : "/Satoshi:0.8.4.2/",
       "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.4.2/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
       "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.4.1/",
       "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "",
        "subver" : "/Satoshi:0.8.4.1/",

[P4rkeR]

On my server, when i start getpeerinfo|grep subver :

Code:

***@***:/home/pqt/QubitCoin/src# ./QubitCoind getpeerinfo|grep subver
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.4.2/",
        "subver" : "/Satoshi:0.8.4.2/",
        "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.3.15/",
        "subver" : "/Satoshi:0.8.4.2/",
        "subver" : "/Satoshi:0.8.4.1/",
        "subver" : "/Satoshi:0.8.4.2/",
        "subver" : "",

And getinfo :

Code:

***@***:/home/pqt/QubitCoin/src# ./QubitCoind getinfo
{
    "version" : 80401,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : *,
    "blocks" : 900055,
    "timeoffset" : -36,
    "connections" : 22,
    "proxy" : "",
    "difficulty" : 86.85659852,
    "testnet" : false,
    "keypoololdest" : 1415554595,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "errors" : ""
}

In my log file for the same block :

Code:

received block 0000000127a55a99697d786569e8a2ad38b280bef09baa9e38efce5a8eafcede
CheckSyncCheckpoint: nHeight=897937, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000127a55a99697d786569e8a2ad38b280bef09baa9e38efce5a8eafcede  height=897937  log2_work=52.847152  tx=1273503  date=2014-11-14 23:19:05 progress=0.997261
ProcessBlock: ACCEPTED

No error on my server !

[P4rkeR]

Finaly after 4 or 5 hours my windows wallet crashes like wgd :

Code:

connection timeout
trying connection [2001:0:9d38:6abd:874:5f0:b1f4:d639]:7788 lastseen=227.2hrs
received block 00000000201daa3ea5acbdc1fa7e0c31d79f893fb8f0f5fabdfe60b8be0297ba
CheckSyncCheckpoint: nHeight=900272, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=00000000201daa3ea5acbdc1fa7e0c31d79f893fb8f0f5fabdfe60b8be0297ba  height=900272  log2_work=52.847835  tx=1275838  date=2014-11-15 18:13:29 progress=1.000000
ProcessBlock: ACCEPTED
connection timeout
trying connection 208.84.132.253:7788 lastseen=8.2hrs
connection timeout
trying connection 193.167.41.1:7788 lastseen=35.5hrs
getblocks 900272 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 88.190.43.122:7788 lastseen=9.5hrs
connection timeout
trying connection 119.95.2.122:7788 lastseen=5997.4hrs
connection timeout
socket recv error 10054
disconnecting node 60.173.10.169:7788
trying connection 208.85.4.86:11973 lastseen=4.0hrs
connected 208.85.4.86:11973
send version message: version 70001, blocks=900272, us=82.238.153.195:7788, them=208.85.4.86:11973, peer=208.85.4.86:11973
socket recv error 10054
disconnecting node 208.85.4.86:11973
trying connection 208.84.132.253:7788 lastseen=8.2hrs
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.2hrs
connection timeout
trying connection 105.237.131.168:7788 lastseen=152.7hrs
connection timeout
trying connection 213.87.137.179:7788 lastseen=482.0hrs
connection timeout
trying connection 88.190.22.60:7788 lastseen=8.1hrs
connection timeout
trying connection 78.11.41.198:7788 lastseen=5.4hrs
received block 0000000148dffeb2e195d7dff3bc2fa58b164b2b46fac0c693e9fe41e588de47
CheckSyncCheckpoint: nHeight=900273, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000148dffeb2e195d7dff3bc2fa58b164b2b46fac0c693e9fe41e588de47  height=900273  log2_work=52.847835  tx=1275839  date=2014-11-15 18:14:31 progress=1.000000
ProcessBlock: ACCEPTED
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.3hrs
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 178.221.145.66:7788 lastseen=63.3hrs
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 50.78.40.241:11973 lastseen=225.0hrs
connection timeout
trying connection 213.221.55.130:7788 lastseen=202.7hrs
connection timeout
trying connection 78.30.170.155:7788 lastseen=5876.0hrs
connection timeout
trying connection 125.43.4.89:7788 lastseen=294.8hrs
trying connection 5.9.56.229:7788 lastseen=365576.5hrs
connection timeout
trying connection 125.43.11.215:7788 lastseen=633.5hrs
connection timeout
trying connection 85.10.194.50:7788 lastseen=365576.5hrs
connection timeout
trying connection 67.198.77.55:11973 lastseen=7.3hrs
connection timeout
trying connection 199.233.239.54:7788 lastseen=365576.5hrs
connection timeout
trying connection 178.221.145.66:7788 lastseen=63.3hrs
connection timeout
trying connection 60.173.10.169:7788 lastseen=365576.5hrs
connected 60.173.10.169:7788
send version message: version 70001, blocks=900273, us=82.238.153.195:7788, them=60.173.10.169:7788, peer=60.173.10.169:7788
trying connection 2.85.185.9:7788 lastseen=365576.5hrs
received block 0000000102e046622a67ab2c69dc6ddc749e7a03a31b5dd9ee2ce3051616d2a3
CheckSyncCheckpoint: nHeight=900274, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000102e046622a67ab2c69dc6ddc749e7a03a31b5dd9ee2ce3051616d2a3  height=900274  log2_work=52.847836  tx=1275840  date=2014-11-15 18:15:23 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.2hrs
connection timeout
connection timeout
trying connection [2001:0:9d38:6ab8:c4e:4de:8ea3:17b9]:7788 lastseen=230.2hrs
connection timeout
trying connection [2001:41d0:a:68c4::1]:7788 lastseen=28.3hrs
connection timeout
trying connection 88.190.22.60:7788 lastseen=8.1hrs
connection timeout
trying connection 120.59.195.33:11973 lastseen=7.4hrs
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.3hrs
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.2hrs
received block 00000001e56dd96a98ae262566a03730e2da357260a89290df1dda3cd4fe94f1
CheckSyncCheckpoint: nHeight=900275, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=00000001e56dd96a98ae262566a03730e2da357260a89290df1dda3cd4fe94f1  height=900275  log2_work=52.847836  tx=1275841  date=2014-11-15 18:15:58 progress=1.000000
ProcessBlock: ACCEPTED
connection timeout
trying connection 94.70.53.77:7788 lastseen=174.8hrs
connection timeout
trying connection 112.226.219.132:7788 lastseen=2955.2hrs
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.2hrs
socket recv error 10054
disconnecting node 60.173.10.169:7788
connection timeout
trying connection 67.255.7.120:7788 lastseen=16.8hrs
connection timeout
trying connection 193.167.41.1:7788 lastseen=35.5hrs
connection timeout
trying connection 88.190.43.122:7788 lastseen=9.5hrs
connection timeout
trying connection 128.199.223.65:7788 lastseen=555.7hrs
connection timeout
trying connection 183.213.155.91:12875 lastseen=5.6hrs
connection timeout
trying connection 88.190.43.122:7788 lastseen=9.5hrs
connection timeout
trying connection 77.105.42.60:7788 lastseen=57.4hrs
received block 000000012018d8dfebe52b9ae17037339f6ecf605b6cda3a545cd62cd6676108
CheckSyncCheckpoint: nHeight=900276, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=000000012018d8dfebe52b9ae17037339f6ecf605b6cda3a545cd62cd6676108  height=900276  log2_work=52.847837  tx=1275842  date=2014-11-15 18:16:57 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 213.87.141.226:7788 lastseen=290.0hrs
connection timeout
trying connection 74.96.81.14:7788 lastseen=296.8hrs
connection timeout
trying connection 98.140.223.180:7788 lastseen=503.1hrs
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.3hrs
connection timeout
trying connection 87.97.46.245:11973 lastseen=447.7hrs
received block 00000001ce46853581df4daa327874fe741c0b22ffc5887ca47a27a6205ea95d
CheckSyncCheckpoint: nHeight=900277, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=00000001ce46853581df4daa327874fe741c0b22ffc5887ca47a27a6205ea95d  height=900277  log2_work=52.847837  tx=1275843  date=2014-11-15 18:17:08 progress=0.999999
ProcessBlock: ACCEPTED
trying connection 5.9.56.229:7788 lastseen=365576.5hrs
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 208.84.132.253:7788 lastseen=8.2hrs
connection timeout
trying connection 85.10.194.50:7788 lastseen=365576.5hrs
connection timeout
trying connection 88.190.43.122:7788 lastseen=9.5hrs
connection timeout
trying connection 199.233.239.54:7788 lastseen=365576.5hrs
connection timeout
trying connection 77.105.42.60:7788 lastseen=57.4hrs
connection timeout
trying connection 60.173.10.169:7788 lastseen=365576.5hrs
connected 60.173.10.169:7788
send version message: version 70001, blocks=900277, us=82.238.153.195:7788, them=60.173.10.169:7788, peer=60.173.10.169:7788
trying connection 2.85.185.9:7788 lastseen=365576.5hrs
connection timeout
trying connection 125.43.4.17:7788 lastseen=462.2hrs
connection timeout
connection timeout
received block 0000000093153117d7a4c9f6533432f889dee97f4baa8aef285e77fc38414d0b
CheckSyncCheckpoint: nHeight=900278, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
trying connection 78.11.41.198:7788 lastseen=5.4hrs
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000093153117d7a4c9f6533432f889dee97f4baa8aef285e77fc38414d0b  height=900278  log2_work=52.847837  tx=1275844  date=2014-11-15 18:17:48 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection [2001:41d0:52:d00::9da]:7788 lastseen=24.8hrs
received block 00000002114a215b30ff35acabe8a48a8c801bf11de60ee5deb27bf5aa9ebcbe
ProcessBlock: ORPHAN BLOCK, prev=00000001765935db592becb59f51f252f978aeb6e22238c299e0473dbea0c105
received block 00000001765935db592becb59f51f252f978aeb6e22238c299e0473dbea0c105
CheckSyncCheckpoint: nHeight=900278, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
CheckSyncCheckpoint: nHeight=900279, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
REORGANIZE: Disconnect 1 blocks; 00000001ce46853581df4daa327874fe741c0b22ffc5887ca47a27a6205ea95d..
REORGANIZE: Connect 2 blocks; ..00000002114a215b30ff35acabe8a48a8c801bf11de60ee5deb27bf5aa9ebcbe
Committing 3 changed transactions to coin database...
SetBestChain: new best=00000002114a215b30ff35acabe8a48a8c801bf11de60ee5deb27bf5aa9ebcbe  height=900279  log2_work=52.847838  tx=1275845  date=2014-11-15 18:17:51 progress=0.999999
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 173.13.48.70:7788 lastseen=5.1hrs
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.3hrs
connection timeout
trying connection [2001:41d0:2:6809::]:7788 lastseen=4.3hrs
connection timeout
trying connection 2.85.186.21:7788 lastseen=1349.9hrs
connection timeout
trying connection 113.190.244.18:7788 lastseen=9.5hrs
connection timeout
trying connection 88.85.207.38:7788 lastseen=3.4hrs
connection timeout
Flushed 11816 addresses to peers.dat  83ms
trying connection 78.11.41.198:7788 lastseen=5.4hrs
socket recv error 10054
disconnecting node 60.173.10.169:7788
received block 00000002685167521d31e6afac45aa038dc3f4205a2dbc1e25bd81903a90c9b7
  nActualTimespan = 819  before bounds
GetNextWorkRequired RETARGET
nTargetTimespan = 600    nActualTimespan = 819
Before: 1d021376  0000000213760000000000000000000000000000000000000000000000000000
After:  1d02d571  00000002d571b5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5c28f5
CheckSyncCheckpoint: nHeight=900280, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=00000002685167521d31e6afac45aa038dc3f4205a2dbc1e25bd81903a90c9b7  height=900280  log2_work=52.847838  tx=1275846  date=2014-11-15 18:18:38 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 36.69.214.187:7788 lastseen=698.8hrs
connection timeout
trying connection 74.116.207.170:11973 lastseen=32.9hrs
connection timeout
trying connection 178.221.145.66:7788 lastseen=63.4hrs
connection timeout
trying connection 125.43.0.74:7788 lastseen=667.5hrs
connection timeout
trying connection 113.190.244.18:7788 lastseen=9.5hrs
connection timeout
trying connection 173.13.48.70:7788 lastseen=5.1hrs
connection timeout
trying connection 113.190.244.18:7788 lastseen=9.5hrs
received block 000000023d6d9765ce01e5a4dc48274525b6c44bb0eddab52ef8721bd1565210
CheckSyncCheckpoint: nHeight=900281, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=000000023d6d9765ce01e5a4dc48274525b6c44bb0eddab52ef8721bd1565210  height=900281  log2_work=52.847838  tx=1275847  date=2014-11-15 18:19:17 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 173.13.48.70:7788 lastseen=5.1hrs
received block 0000000297a2dc34a18fb1fc839072942f963694bdda659f431590d120a566b6
CheckSyncCheckpoint: nHeight=900282, hashSyncCheckpoint=0000000000000000000000000000000000000000000000000000000000000000
Committing 1 changed transactions to coin database...
SetBestChain: new best=0000000297a2dc34a18fb1fc839072942f963694bdda659f431590d120a566b6  height=900282  log2_work=52.847838  tx=1275848  date=2014-11-15 18:19:25 progress=1.000000
ProcessBlock: ACCEPTED
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
getblocks -1 to 0000000000000000000000000000000000000000000000000000000000000000 limit 500
connection timeout
trying connection 88.190.22.60:7788 lastseen=8.1hrs
connection timeout
trying connection 78.11.41.198:7788 lastseen=5.5hrs
connection timeout
trying connection 2.85.190.125:7788 lastseen=62.4hrs
connection timeout
trying connection 5.9.56.229:7788 lastseen=365576.6hrs
trying connection 208.84.132.253:7788 lastseen=8.3hrs

Close and restart the wallet solve this problem.....

[zex24]

www.qubitcoin.cc

Still needs a lot of info and makeup but it's better than nothing
Any suggestions are welcome...

[Truecoin]

www.qubitcoin.cc

Still needs a lot of info and makeup but it's better than nothing
Any suggestions are welcome...

Good work, thank you!

Maybe you could consider to add links to Q2C exchanges (if there are any still active).

[zex24]

Yes, ofcourse.  Right now I am relly bussy with my work but as soon as I get a chance I will add it.
Also It would be nice if each one of you can think of something useful that we can put on the web site and post it here.
Thanks 

[wgd]

http://unitus.info/algorithms

Another coin algo uses qubit, ass q2c was without parents  

[neuroMode]

http://unitus.info/algorithms

Another coin algo uses qubit, ass q2c was without parents  

Unitus uses auxPoW on all its algos, including Qubit. You can merge mine Unitus through Qubit. If any Qubit pools wish do enable merge mining with Unitus, let me know and I can add it to the Unitus pool list.

[zex24]

Exchanges added 

http://qubitcoin.cc/

[zex24]

End of road? 

[wgd]

we live we live, but what a life

cheers for the rest of the team q2c !!!

[Majormax]

If you can find ten people that want to represent this coin, I have a plan that would get this coin back on it's feet in a big way

i'm working on a multi-coin crowd funding cooperative that brings 10 different coin communities together to form a crowdfunding platform that accepts fiat and crypto.    It's a opportunity share relationship where all of the member communities share responsibilities and then equally share 80% of the revenue.

Each coin gets great exposure in the crypto world and real world, the high utility and visibility is built into the structure of the plan, for a coin like Qubit it could easily increase 1000x in only a few months.  No pump and dump, no scam, no other investment other than buying your own coin, they only thing you risk is your human resources to make the plan work. 

The plan is finalizing soon, so check it out and start organizing because organization is vital for this plan to work.

Well, I am still watching and interested. Q2C is technically good... This board is the place (if any can) to find out what is left of a community.

[eule]

Lurking too. Still holding.

[nixon99]

On hold.

[zex24]

If you can find ten people that want to represent this coin, I have a plan that would get this coin back on it's feet in a big way

i'm working on a multi-coin crowd funding cooperative that brings 10 different coin communities together to form a crowdfunding platform that accepts fiat and crypto.    It's a opportunity share relationship where all of the member communities share responsibilities and then equally share 80% of the revenue.

Each coin gets great exposure in the crypto world and real world, the high utility and visibility is built into the structure of the plan, for a coin like Qubit it could easily increase 1000x in only a few months.  No pump and dump, no scam, no other investment other than buying your own coin, they only thing you risk is your human resources to make the plan work. 

The plan is finalizing soon, so check it out and start organizing because organization is vital for this plan to work.

Could you tell us more about your plan? What do you mean when you say "people that want to represent this coin"? What exactly would they have to do?
I am always ready to help so you can count me in (if I can help somehow).

[wgd]

me too im holding q2c but would prefer to keep btc: P

[wgd]

q2c bagholders team, nice

[btcluka]

I'm stuck on 1140053 block, still have 1 active connection but ... any sugestion?

[wgd]

my two wallets block 1140302 show, it seems that everything is ok. You have an active nodes?

nie, 8 lut 2015, 09:59:40 CET

    "version" : 80402,
    "protocolversion" : 70001,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 1140302,