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

[dr_chen]

If everyone would stop bumping this thread and let this dumb coin die then the name wouldn't even matter anymore.

This coin is very interesting,
new algorithm, no premining.
why let it die.

In your opinion, is that which you mined a lot is a good coin, others are shit?

[getwork]

I like the coin and will mine it!

[stas]

can't synch.. any nodes please?!

thanks

[stas]

I have added all provided nodes, still no synch... any ideas?

[silicon_chip]

can't synch.. any nodes please?!

thanks

addnode=188.230.132.226:7788
addnode=88.193.180.145:7788
addnode=151.224.242.33:7788
addnode=113.2.235.63:7788
addnode=80.121.18.48:7788
addnode=176.99.185.190:7788
addnode=92.255.221.181:7788
addnode=5.164.93.142:7788
addnode=83.215.164.206:7788
addnode=87.113.166.62:7788
addnode=93.83.25.85:7788
addnode=82.246.47.198:7788
addnode=80.220.12.202:7788
addnode=61.174.239.236:7788
addnode=74.88.177.35:7788
addnode=89.93.16.199:7788
addnode=176.15.49.142:7788
addnode=115.207.173.185:7788
addnode=174.100.51.46:7788
addnode=211.93.43.59:7788

From my wallet

"addr" : "222.65.44.96:7788",
"services" : "00000001",
"lastsend" : 1389601196,
"lastrecv" : 1389601208,
"bytessent" : 3807,
"bytesrecv" : 62097,
"conntime" : 1389601194,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3252,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "23.240.155.166:7788",
"services" : "00000001",
"lastsend" : 1389601208,
"lastrecv" : 1389601208,
"bytessent" : 3091,
"bytesrecv" : 13870,
"conntime" : 1389601195,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3252,
"banscore" : 0
},
{
"addr" : "87.97.154.27:7788",
"services" : "00000001",
"lastsend" : 1389601209,
"lastrecv" : 1389601214,
"bytessent" : 1545,
"bytesrecv" : 9211,
"conntime" : 1389601202,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3252,
"banscore" : 0
},
{
"addr" : "[2001:0:9d38:6abd:1872:3e6b:d1f5:c88a]:7788",
"services" : "00000001",
"lastsend" : 1389601237,
"lastrecv" : 1389601245,
"bytessent" : 230,
"bytesrecv" : 10528,
"conntime" : 1389601236,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3253,
"banscore" : 0
},
{
"addr" : "93.183.173.190:7788",
"services" : "00000001",
"lastsend" : 1389601245,
"lastrecv" : 1389601247,
"bytessent" : 230,
"bytesrecv" : 10468,
"conntime" : 1389601243,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3253,
"banscore" : 0
},
{
"addr" : "180.155.136.78:7788",
"services" : "00000001",
"lastsend" : 1389601249,
"lastrecv" : 1389601254,
"bytessent" : 230,
"bytesrecv" : 10468,
"conntime" : 1389601249,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3253,
"banscore" : 0
},
{
"addr" : "199.188.178.180:7788",
"services" : "00000001",
"lastsend" : 1389601257,
"lastrecv" : 1389601266,
"bytessent" : 230,
"bytesrecv" : 10468,
"conntime" : 1389601255,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3253,
"banscore" : 0
},
{
"addr" : "124.228.106.35:7788"

[stas]

can't synch.. any nodes please?!

thanks

addnode=188.230.132.226:7788
addnode=88.193.180.145:7788
addnode=151.224.242.33:7788
addnode=113.2.235.63:7788
addnode=80.121.18.48:7788
addnode=176.99.185.190:7788
addnode=92.255.221.181:7788
addnode=5.164.93.142:7788
addnode=83.215.164.206:7788
addnode=87.113.166.62:7788
addnode=93.83.25.85:7788
addnode=82.246.47.198:7788
addnode=80.220.12.202:7788
addnode=61.174.239.236:7788
addnode=74.88.177.35:7788
addnode=89.93.16.199:7788
addnode=176.15.49.142:7788
addnode=115.207.173.185:7788
addnode=174.100.51.46:7788
addnode=211.93.43.59:7788

From my wallet

"addr" : "222.65.44.96:7788",
"services" : "00000001",
"lastsend" : 1389601196,
"lastrecv" : 1389601208,
"bytessent" : 3807,
"bytesrecv" : 62097,
"conntime" : 1389601194,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3252,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "23.240.155.166:7788",
"services" : "00000001",
"lastsend" : 1389601208,
"lastrecv" : 1389601208,
"bytessent" : 3091,
"bytesrecv" : 13870,
"conntime" : 1389601195,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3252,
"banscore" : 0
},
{
"addr" : "87.97.154.27:7788",
"services" : "00000001",
"lastsend" : 1389601209,
"lastrecv" : 1389601214,
"bytessent" : 1545,
"bytesrecv" : 9211,
"conntime" : 1389601202,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3252,
"banscore" : 0
},
{
"addr" : "[2001:0:9d38:6abd:1872:3e6b:d1f5:c88a]:7788",
"services" : "00000001",
"lastsend" : 1389601237,
"lastrecv" : 1389601245,
"bytessent" : 230,
"bytesrecv" : 10528,
"conntime" : 1389601236,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3253,
"banscore" : 0
},
{
"addr" : "93.183.173.190:7788",
"services" : "00000001",
"lastsend" : 1389601245,
"lastrecv" : 1389601247,
"bytessent" : 230,
"bytesrecv" : 10468,
"conntime" : 1389601243,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3253,
"banscore" : 0
},
{
"addr" : "180.155.136.78:7788",
"services" : "00000001",
"lastsend" : 1389601249,
"lastrecv" : 1389601254,
"bytessent" : 230,
"bytesrecv" : 10468,
"conntime" : 1389601249,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3253,
"banscore" : 0
},
{
"addr" : "199.188.178.180:7788",
"services" : "00000001",
"lastsend" : 1389601257,
"lastrecv" : 1389601266,
"bytessent" : 230,
"bytesrecv" : 10468,
"conntime" : 1389601255,
"version" : 70001,
"subver" : "/Satoshi:0.8.3.15/",
"inbound" : false,
"startingheight" : 3253,
"banscore" : 0
},
{
"addr" : "124.228.106.35:7788"

thank you .
Your nodes are helping:)

[Marty19]

I thought Cubits (V3) used the coin code QBT .... how can this coin also use it?

[shanent]

I like the idea behind this new coin but there are many black holes in this.

The first is the difficulty that has grown very fast in little time. Now is around 1480 after about 12 hours from the launch.

The second is the lack of a dedicated miner.

The third is the reuse of an existing name and the relative abbreviation.

I just mined 1 block yesterday and after nothing, I hope that someday QBT will have some value but in this moment I've many doubts...

[TulipBit]

I like the idea behind this new coin but there are many black holes in this.

The first is the difficulty that has grown very fast in little time. Now is around 1480 after about 12 hours from the launch.

The second is the lack of a dedicated miner.

The third is the reuse of an existing name and the relative abbreviation.

I just mined 1 block yesterday and after nothing, I hope that someday QBT will have some value but in this moment I've many doubts...

The name isn't a big problem I think, devs could change it release a new wallet with QUBIT instead QBT...

[QubitCoin]

so, how i see we have 2 problems, first is for linux users was trouble with building on linux os ... and for trolls was big problem with abbreviation QBT (yes it was my mistake and carelessness) ... in new release i try fix bug with linux version.. about QBT ... wait proposals from community, may be QBC or QTC or Q2C ?
i think in next release will fix this..
   

[Applemuzi]

WTS 30000 qrt for btc/ltc

[forgetme]

HI, this night i've mined with my solo in wallet 2048 QubitCoins. But in the wallet it's shown as "immature" anybody can tell me if this amount will be ever confirmed?

[fenix79]

WTS 20 000 pm me

[napoleon2121]

anyone know the stratum changes for this algo ? or a stratum ready ?

[lest]

qbt.mypool.cc pool is working great. I executed manual payout and successfully received coins to my wallet. Thanks for running the pool!

[forgetme]

I'm getting a strange issues with minerd on qbt.mypool, when i launch with the bat file start running so fast with all rejected shares and (booo) message prompted. Never happened with other pools and coins..Anyone?

I'm mining with an i5 intel quad core on win7..

[QubitCoin]

I'm getting a strange issues with minerd on qbt.mypool, when i launch with the bat file start running so fast with all rejected shares and (booo) message prompted. Never happened with other pools and coins..Anyone?

I'm mining with an i5 intel quad core on win7..

minerd64 -a qubit -o stratum+tcp://qbt.mypool.cc:10043 -u Weblogin.Worker -p Worker password

[ex_mac]

Bug fixed...

Pool: http://mine-pool.net/qbt/
work fine ...

Pool fee for 3 days to 0 ...

Welcome ...

[forgetme]

I'm getting a strange issues with minerd on qbt.mypool, when i launch with the bat file start running so fast with all rejected shares and (booo) message prompted. Never happened with other pools and coins..Anyone?

I'm mining with an i5 intel quad core on win7..

minerd64 -a qubit -o stratum+tcp://qbt.mypool.cc:10043 -u Weblogin.Worker -p Worker password

If i use this config it doesn't even open it... why should i put minerd64 when the exe is called minerd??

[shanent]

I'm getting a strange issues with minerd on qbt.mypool, when i launch with the bat file start running so fast with all rejected shares and (booo) message prompted. Never happened with other pools and coins..Anyone?

I'm mining with an i5 intel quad core on win7..

minerd64 -a qubit -o stratum+tcp://qbt.mypool.cc:10043 -u Weblogin.Worker -p Worker password

If i use this config it doesn't even open it... why should i put minerd64 when the exe is called minerd??

Only minerd goes well. If there is an error try to launch with -qubit or -aqubit without space