Pages:
Author

Topic: [ANN][QBC] Québecoin - X11 - DGW - (BITTREX) - Win/Mac/Linux Wallets - New - page 51. (Read 161843 times)

full member
Activity: 183
Merit: 100
Win Wallet simply dont want to sync....it is stuck on block 786

Ok, I see what's happening right now, there are still some windows clients out there on the wrong fork and propogating the wrong chain, so it's hit or miss if you'll get the correct block 405 right now, probably needs a checkpoint put in at block 405 to make it go to the correct chain, I'll see what I can do to get this done real quick. If JP isn't around to do it.

But if you delete your blocks and chainstate folder a few times you will eventually get on the right chain in the mean time.
legendary
Activity: 1190
Merit: 1000
SoNiC BooM
Win Wallet simply dont want to sync....it is stuck on block 786
full member
Activity: 196
Merit: 100
Guys we are doing well at qbc.cryptoADHD.com especially if you're a small time miner the payout is better. Don't take my word for it though, test it out. Plus the pool op is donating half his fee to charity, win win all over Smiley
legendary
Activity: 1190
Merit: 1000
SoNiC BooM
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??

I haven't had any problems with the new wallet since it was released last night.   Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet?


yeah yeah I already do everything...even run it on 32 and 64 bit machine it is still shitty....sorry man

Could you post your debug.log file on pastebin so we can see where it's failing possibly?

2014-04-20 19:29:30 received block 00000000015d57fd4fae7b56b6d771e5c9c6b38facde6cc7fb460711f78ac6c6
2014-04-20 19:29:30 ProcessBlock: ORPHAN BLOCK, prev=0000000002470cae78f1dfdce05cdc71347519686d7bf8f834c8f725751e7d31
2014-04-20 19:29:31 received block 00000000010a5becc2de4e7af1f48209383924342ed7bbbc822a63df311dc72a
2014-04-20 19:29:31 ERROR: AcceptBlock() : incorrect proof of work
2014-04-20 19:29:31 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-04-20 19:29:31 Misbehaving: 54.86.39.92:44093 (0 -> 100) DISCONNECTING
2014-04-20 19:29:31 disconnecting node 54.86.39.92:44093
2014-04-20 19:30:08 stored orphan tx b84f54a6a1683784660e42cc2cd51d4c60c0c17475c4a01527df81027f57ad2a (mapsz 2)
2014-04-20 19:30:09 stored orphan tx acbfb0365b864e2e2dea807e2c608a567cc48d5059f78bde2b84fa806cb5e1f1 (mapsz 3)
2014-04-20 19:30:10 stored orphan tx 14820c374f913222bd8f0b6a82e10baba8742115a1383a3dc4ada5127053709f (mapsz 4)
2014-04-20 19:30:12 ERROR: CTxMemPool::accept() : inputs already spent
2014-04-20 19:30:12 a1d5cc24e3dd084c5297d273497af1b136ddf7a16704104495263344ad40a2ce from 65.95.14.109:56790 /Satoshi:0.8.6/ was not accepted into the memory pool
2014-04-20 19:30:12 ERROR: CTxMemPool::accept() : inputs already spent
2014-04-20 19:30:12 fc5823fd849dadb5b8ab839bfa06bc58c60f24299864d0da20d59d31ca07b768 from 65.95.14.109:56790 /Satoshi:0.8.6/ was not accepted into the memory pool


There is probably a part in there that says "INVALID PROOF OF WORK" will need about 10 lines before and after that.


2014-04-20 19:37:10 trying connection 66.222.233.110:56790 lastseen=3.2hrs
2014-04-20 19:37:15 connection timeout
2014-04-20 19:37:16 trying connection 5.39.194.244:56790 lastseen=2.7hrs
2014-04-20 19:37:17 accepted connection 120.34.218.78:59048
2014-04-20 19:37:17 send version message: version 70010, blocks=786, us=188.129.93.67:56790, them=120.34.218.78:59048, peer=120.34.218.78:59048
2014-04-20 19:37:17 Added time data, samples 19, offset +44 (+0 minutes)
2014-04-20 19:37:17 nTimeOffset = -1  (+0 minutes)
2014-04-20 19:37:17 receive version message: /Satoshi:0.8.6/: version 70010, blocks=786, us=188.129.93.67:56790, them=[2001:0:9d38:90d7:347a:d6e:87dd:25b1]:56790, peer=120.34.218.78:59048
2014-04-20 19:37:21 connection timeout
2014-04-20 19:37:21 trying connection 206.248.148.140:56790 lastseen=3.4hrs
2014-04-20 19:37:26 accepted connection 69.70.94.86:42842
2014-04-20 19:37:26 send version message: version 70010, blocks=786, us=188.129.93.67:56790, them=69.70.94.86:42842, peer=69.70.94.86:42842
2014-04-20 19:37:26 Added time data, samples 20, offset +1 (+0 minutes)
2014-04-20 19:37:26 Moving 69.70.94.86:56790 to tried
2014-04-20 19:37:26 receive version message: /Satoshi:0.8.6/: version 70010, blocks=786, us=188.129.93.67:56790, them=69.70.94.86:56790, peer=69.70.94.86:42842
2014-04-20 19:37:26 connection timeout
2014-04-20 19:37:27 trying connection 182.91.4.117:56790 lastseen=3.8hrs
2014-04-20 19:37:27 connected 182.91.4.117:56790
2014-04-20 19:37:27 send version message: version 70010, blocks=786, us=188.129.93.67:56790, them=182.91.4.117:56790, peer=182.91.4.117:56790
2014-04-20 19:37:28 Added time data, samples 21, offset -1 (+0 minutes)
2014-04-20 19:37:28 nTimeOffset = -1  (+0 minutes)
2014-04-20 19:37:28 Moving 182.91.4.117:56790 to tried
2014-04-20 19:37:28 receive version message: /Satoshi:0.8.6/: version 70010, blocks=786, us=188.129.93.67:61139, them=182.91.4.117:56790, peer=182.91.4.117:56790
2014-04-20 19:37:30 Added 8 addresses from 182.91.4.117: 52 tried, 388 new
2014-04-20 19:37:30 received block 00000000010a5becc2de4e7af1f48209383924342ed7bbbc822a63df311dc72a
2014-04-20 19:37:30 ERROR: AcceptBlock() : incorrect proof of work
2014-04-20 19:37:30 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-04-20 19:37:30 Misbehaving: 82.247.141.228:56790 (0 -> 100) DISCONNECTING
2014-04-20 19:37:30 disconnecting node 82.247.141.228:56790
2014-04-20 19:37:30 trying connection 184.161.100.149:56790 lastseen=11.4hrs
2014-04-20 19:37:35 connection timeout
2014-04-20 19:37:36 trying connection 46.117.190.251:56790 lastseen=11.1hrs
2014-04-20 19:37:41 connection timeout
2014-04-20 19:37:41 trying connection 99.239.203.179:56790 lastseen=4.9hrs
2014-04-20 19:37:46 connection timeout
2014-04-20 19:37:47 trying connection [2001:0:5ef5:79fd:14b1:20c4:bc14:3522]:56790 lastseen=2.3hrs
2014-04-20 19:37:47 connected [2001:0:5ef5:79fd:14b1:20c4:bc14:3522]:56790
2014-04-20 19:37:47 send version message: version 70010, blocks=786, us=188.129.93.67:56790, them=[2001:0:5ef5:79fd:14b1:20c4:bc14:3522]:56790, peer=[2001:0:5ef5:79fd:14b1:20c4:bc14:3522]:56790
2014-04-20 19:37:48 Added time data, samples 22, offset -1 (+0 minutes)
2014-04-20 19:37:48 Moving [2001:0:5ef5:79fd:14b1:20c4:bc14:3522]:56790 to tried
2014-04-20 19:37:48 receive version message: /Satoshi:0.8.6/: version 70010, blocks=909, us=[2001:0:9d38:6ab8:2caa:2912:437e:a2bc]:55424, them=67.235.202.221:56790, peer=[2001:0:5ef5:79fd:14b1:20c4:bc14:3522]:56790
2014-04-20 19:37:48 Added 7 addresses from 2001:0:5ef5:79fd:14b1:20c4:bc14:3522: 53 tried, 394 new
2014-04-20 19:38:04 stored orphan tx bc35b9f08c83465f304a35cac24a62a3af657f66d2b0550f0a44d35a522c43a5 (mapsz 18)
2014-04-20 19:38:33 connection from 54.86.39.92:44222 dropped (banned)
2014-04-20 19:38:56 accepted connection 184.163.251.183:57543
2014-04-20 19:38:56 send version message: version 70010, blocks=786, us=188.129.93.67:56790, them=184.163.251.183:57543, peer=184.163.251.183:57543
2014-04-20 19:38:56 Added time data, samples 23, offset +0 (+0 minutes)
2014-04-20 19:38:56 nTimeOffset = -1  (+0 minutes)
2014-04-20 19:38:56 Moving 184.163.251.183:56790 to tried
2014-04-20 19:38:56 receive version message: /Satoshi:0.8.6/: version 70010, blocks=786, us=188.129.93.67:56790, them=184.163.251.183:56790, peer=184.163.251.183:57543




DONT HAVE THAT LINE IN TXT.....
full member
Activity: 183
Merit: 100
Actually, I just installed the old version on another PC and it got to 786, it's on the wrong fork, someone has forked the coin with the version of the windows wallet that is incorrect and has been solo mining to it all night it would appear.  The new version of the wallet will work but you have to delete everything in the Quebecoin folder inside of %AppData% other than the wallet.dat file.
full member
Activity: 183
Merit: 100
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??

I haven't had any problems with the new wallet since it was released last night.   Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet?


yeah yeah I already do everything...even run it on 32 and 64 bit machine it is still shitty....sorry man

Could you post your debug.log file on pastebin so we can see where it's failing possibly?

2014-04-20 19:29:30 received block 00000000015d57fd4fae7b56b6d771e5c9c6b38facde6cc7fb460711f78ac6c6
2014-04-20 19:29:30 ProcessBlock: ORPHAN BLOCK, prev=0000000002470cae78f1dfdce05cdc71347519686d7bf8f834c8f725751e7d31
2014-04-20 19:29:31 received block 00000000010a5becc2de4e7af1f48209383924342ed7bbbc822a63df311dc72a
2014-04-20 19:29:31 ERROR: AcceptBlock() : incorrect proof of work
2014-04-20 19:29:31 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-04-20 19:29:31 Misbehaving: 54.86.39.92:44093 (0 -> 100) DISCONNECTING
2014-04-20 19:29:31 disconnecting node 54.86.39.92:44093
2014-04-20 19:30:08 stored orphan tx b84f54a6a1683784660e42cc2cd51d4c60c0c17475c4a01527df81027f57ad2a (mapsz 2)
2014-04-20 19:30:09 stored orphan tx acbfb0365b864e2e2dea807e2c608a567cc48d5059f78bde2b84fa806cb5e1f1 (mapsz 3)
2014-04-20 19:30:10 stored orphan tx 14820c374f913222bd8f0b6a82e10baba8742115a1383a3dc4ada5127053709f (mapsz 4)
2014-04-20 19:30:12 ERROR: CTxMemPool::accept() : inputs already spent
2014-04-20 19:30:12 a1d5cc24e3dd084c5297d273497af1b136ddf7a16704104495263344ad40a2ce from 65.95.14.109:56790 /Satoshi:0.8.6/ was not accepted into the memory pool
2014-04-20 19:30:12 ERROR: CTxMemPool::accept() : inputs already spent
2014-04-20 19:30:12 fc5823fd849dadb5b8ab839bfa06bc58c60f24299864d0da20d59d31ca07b768 from 65.95.14.109:56790 /Satoshi:0.8.6/ was not accepted into the memory pool


There is probably a part in there that says "INVALID PROOF OF WORK" will need about 10 lines before and after that.
legendary
Activity: 1190
Merit: 1000
SoNiC BooM
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??

I haven't had any problems with the new wallet since it was released last night.   Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet?


yeah yeah I already do everything...even run it on 32 and 64 bit machine it is still shitty....sorry man

Could you post your debug.log file on pastebin so we can see where it's failing possibly?

2014-04-20 19:29:30 received block 00000000015d57fd4fae7b56b6d771e5c9c6b38facde6cc7fb460711f78ac6c6
2014-04-20 19:29:30 ProcessBlock: ORPHAN BLOCK, prev=0000000002470cae78f1dfdce05cdc71347519686d7bf8f834c8f725751e7d31
2014-04-20 19:29:31 received block 00000000010a5becc2de4e7af1f48209383924342ed7bbbc822a63df311dc72a
2014-04-20 19:29:31 ERROR: AcceptBlock() : incorrect proof of work
2014-04-20 19:29:31 ERROR: ProcessBlock() : AcceptBlock FAILED
2014-04-20 19:29:31 Misbehaving: 54.86.39.92:44093 (0 -> 100) DISCONNECTING
2014-04-20 19:29:31 disconnecting node 54.86.39.92:44093
2014-04-20 19:30:08 stored orphan tx b84f54a6a1683784660e42cc2cd51d4c60c0c17475c4a01527df81027f57ad2a (mapsz 2)
2014-04-20 19:30:09 stored orphan tx acbfb0365b864e2e2dea807e2c608a567cc48d5059f78bde2b84fa806cb5e1f1 (mapsz 3)
2014-04-20 19:30:10 stored orphan tx 14820c374f913222bd8f0b6a82e10baba8742115a1383a3dc4ada5127053709f (mapsz 4)
2014-04-20 19:30:12 ERROR: CTxMemPool::accept() : inputs already spent
2014-04-20 19:30:12 a1d5cc24e3dd084c5297d273497af1b136ddf7a16704104495263344ad40a2ce from 65.95.14.109:56790 /Satoshi:0.8.6/ was not accepted into the memory pool
2014-04-20 19:30:12 ERROR: CTxMemPool::accept() : inputs already spent
2014-04-20 19:30:12 fc5823fd849dadb5b8ab839bfa06bc58c60f24299864d0da20d59d31ca07b768 from 65.95.14.109:56790 /Satoshi:0.8.6/ was not accepted into the memory pool
full member
Activity: 183
Merit: 100
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??

I haven't had any problems with the new wallet since it was released last night.   Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet?


yeah yeah I already do everything...even run it on 32 and 64 bit machine it is still shitty....sorry man

Could you post your debug.log file on pastebin so we can see where it's failing possibly?
legendary
Activity: 1190
Merit: 1000
SoNiC BooM
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??

I haven't had any problems with the new wallet since it was released last night.   Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet?


yeah yeah I already do everything...even run it on 32 and 64 bit machine it is still shitty....sorry man

it is stuck on block 786
full member
Activity: 196
Merit: 100
I'm really starting to like anonymousxx1503, brocrush! For those of you complaining about a great currency I hope you read a bit before speaking. We have a serious contender in QBC.
full member
Activity: 183
Merit: 100
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??

I haven't had any problems with the new wallet since it was released last night.   Those having problems have you deleted your blocks folder and the chainstate folder from the Quebecoin folder and are you using the most recent wallet?
legendary
Activity: 1036
Merit: 1000
cant pass trough block 786 on wallet, it gets there stucked
legendary
Activity: 1190
Merit: 1000
SoNiC BooM
this shitty wallet have problems every few hours....will you fu.... compile proper wallet already dev??
hero member
Activity: 532
Merit: 500

There's no volume because all the available coins are from the IPO premine.


You have to give miners a chance to catch up and get some QBC too. If you were expecting to magically triple your money on the first day, there's no way that can happen. I clearly stated that all IPO payments would be made three days after launch. I'm starting to send them in order starting from the first investor to the last one beginning on April 22nd. Please be patient, the price will always be above the IPO floor, you're not losing any money on QBC.

Actually i expected to get at least 1000% return, the only one who could have in this case is you as you are holding the premine hostage.

Meanwhile i'll keep mining coins that are more profitable.

Payment of IPO coins should be disclosed in the announcement and prennouncement.



Wow, unbelievable how pathetic you are. First you EXPECT a 1000% return? You can't expect shit in the crypto world, especially not a guaranteed 1000%, stop dreaming.

Second of all don't you know how to read? It was clearly announced that the IPO coins won't be sent for 3 days. And what the fuck would you do with them right now anyways, the market is BRAND NEW , there's like 2 BTC on the buy order side right now on Bittrex. Third, the premine hasn't moved, JP isn't holding the premine "hostage". He told people exactly when he was going to send them. I WOULD FUCKING LOVE if he sent you the coins right now and you sell them right away just to see that you should have waited for people to actually start trading and making it go up.

Completely ridiculous. You should definitely go mine something else. Better yet get your BTC reimbursed for the IPO and cry when it goes up.


Zero active connections on Windows wallet.  Is there some other configuring I need to do?

The dev is setting up a dns seed node as he said earlier, right now you just need to add the seed nodes from the OP to your quebecoin.conf file and it syncs within seconds.
full member
Activity: 183
Merit: 100
Zero active connections on Windows wallet.  Is there some other configuring I need to do?

See this post
https://bitcointalksearch.org/topic/m.6306494
legendary
Activity: 1291
Merit: 1000
Zero active connections on Windows wallet.  Is there some other configuring I need to do?
full member
Activity: 183
Merit: 100
Let's go guys, anyone going to take the lead on this?


Oh - I forgot, 0.05 BTC to the first person to post a compiled MAC Quebecoin-QT client from the latest Github source at www.github.com/jpgagnon/qbc


Be sure to use the latest OPENSSL 1.0.1g




I'm currently working on it, but it will be my first Mac OSX wallet, so we'll see how successful I am, I wouldn't want to stop anyone else from trying in the meantime though.
hero member
Activity: 673
Merit: 500
http://qbc.talesfromthescrypt.org  is ready for some miners!  We have some pretty hardcore DDOS protection
sr. member
Activity: 294
Merit: 250
Is there something wrong with Okaypool now?

Pools are going down again - suchpool front-end is already dead !!

Jesus, who did you québecois pissed off? Huh




And it's back Cheesy
Maybe it was just a glitch on cloudflare Tongue
The stratum was up all the time and balances seem to be ok Wink
sr. member
Activity: 308
Merit: 250
EVERYTHING YOU CAN IMAGINE IS REAL
Let's go guys, anyone going to take the lead on this?


Oh - I forgot, 0.05 BTC to the first person to post a compiled MAC Quebecoin-QT client from the latest Github source at www.github.com/jpgagnon/qbc


Be sure to use the latest OPENSSL 1.0.1g


Pages:
Jump to: