ymod123
|
|
June 28, 2014, 11:26:11 PM |
|
hello! i want to to mine this coin im having trouble when I tried to sync the "quazardcoind.exe" its giving me error "some problem at write an existing connection was forcibly closed by the remote host:10054" that's normal just let it keep going thanks! i just leave the quazarcoind.exe running? i see all red letter and numbers? its normal right? if ever its gonna be succesful synching i could start mining by performing "start_mining" command? if I want to mining in the pool what im going to do? thanks again for your help first time mining a coin.. tnx you can do start_mining yes, pool directions are on pool for example my quasar pool is http://qcn.extremepool.org but not a lot of hash there so you might want to try another pool. you can find a list of pools in the 1st post. how can i connect the quazarcoind.exe to http://qcn.extremepool.org? to start mining DO I NEED TO TYPE THIS TO QUAZARCOIND.EXE thanks again for your help nope just get the miner https://github.com/wolf9466/cpuminer-multiminerd -a cryptonight -o stratum+tcp://qcnpool.org:2222 -u address -p x don't need the daemon to mine on a pool Tnx a lot for your help....
|
|
|
|
OracionSeis (OP)
|
|
June 30, 2014, 02:05:44 PM |
|
And as this is a separate discussion, it would be great if we had additional checkpointing going on. It looks like there's a checkpoint at around block 14500, give or take, but that's the last one. So when you resync the wallet, it's really fast up to block 14K, and then it takes much longer to finish the second half of the block chain sync.
Checkpoints don't affect the simplewallet work.
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
nopedope89
Legendary
Offline
Activity: 1078
Merit: 1059
FROSTING
|
|
June 30, 2014, 05:16:57 PM |
|
Hey guys! Welcome to our pool Minergate.com. We support mining of Quazarcoin and offer two reward models - PPS and PPLNS (you can choose suitable method for each currency individually). Moreover, we have the lowest fees on the market (2% PPS, 1.5% PPLNS). Enjoy the most profitable on our pool! Regards, Minergate.com Enjoy the most profitable mining on our pool
|
|
|
|
33zer0w0lf
|
|
July 01, 2014, 03:49:19 PM |
|
Check out that new luck feature http://qcn.extremepool.org under Pool Blocks Extreme Pool http://www.extremepool.orgWe offer a Pool for every Cryptonote Coin Features: •Fast Payouts directly to your private wallet. •Address Validation •Latest pool code from Zone117x •Variable Difficulty based on your individual CPU performance •Verified Secure •Servers hosted in our own Data Center, not hosted by an online 3rd party provider •Servers secured with enterprise firewalls Come mine with us! We have the most popular BCN and DuckNote pools available! http://www.extremepool.orghttp://qcn.extremepool.org
|
|
|
|
|
OracionSeis (OP)
|
|
July 01, 2014, 04:57:58 PM |
|
Course, I periodically check other CN GitHubs. The BCN devs have uploaded an updated high-level API and now I'm carrying out research. It has some hardcore things and this makes it so interesting. Also I prepare a big update and probably will use some ready-made solutions.
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
|
OracionSeis (OP)
|
|
July 01, 2014, 06:03:55 PM |
|
So if you have a bunch of small transactions and want to combine those into a larger single block, the general idea is that you send your own address a transaction (more or less of maximum size), right? And you repeat this until you have your coins more or less combined into a larger block that can be transmitted? I'm trying to do this but running into problems. I did the following: transfer 0 [my address] [amount] The initial amounts I tried resulted in a transaction that was too large, so I had to try again (and again) until eventually I managed to send a transaction of 1.4 QCN. Woohoo! I then continued sending another small transactions every few minutes until I reached the point where my balance of QCN was exhausted. But then I discovered that all that work was apparently for naught -- most of the transactions failed to get written to the block chain. What's going on!? Best guess: my transactions are being ignored by the block finders because they are large and small -- meaning, maximum size but minimal value in coins. Is this reasonable? I had this happen once already when I tried to transfer coins to Poloniex -- only one of seven transactions actually showed up. I had to delete wallet.bin and then resync the wallet, at which point all of the "lost" coins reappeared in my wallet. Then I did the above sending coins to myself to try and group them into larger units, so I could send a single transaction to Poloniex, and of the transactions I sent yesterday it seems only one of those went through. Has anyone else experienced this? Is there a solution/workaround that I'm not doing properly? It looks like my initial mining of QCN generated 2781 transactions totaling just 10.4 QCN (give or take), and you can only have about 100 inputs into a transaction before it becomes too large. So I wanted to send myself 28 transactions, basically, and then I could send myself one "big" transaction, and then I would be done. But it's not working that way. :-( Also, I'm now getting the following after "resyncing" with the chain: 2014-Jun-26 18:30:28.370301 [RPC1]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <d27babecc9557afef79f440f5ab140a7fd2340f9849c703aeda1aec22c4f7e3a> used already spent key images 2014-Jun-26 18:30:28.379307 [RPC1]Transaction verification failed: <d27babecc9557afef79f440f5ab140a7fd2340f9849c703aeda1aec22c4f7e3a> So it looks like maybe I need to delete the blockchain.bin as well and resync that again. This is seriously a pain in the butt! The wallet needs some help if QCN (and other CryptoNote coins that are similar) want a chance to succeed! So if you have a bunch of small transactions and want to combine those into a larger single block, the general idea is that you send your own address a transaction (more or less of maximum size), right? And you repeat this until you have your coins more or less combined into a larger block that can be transmitted? I'm trying to do this but running into problems. I did the following: transfer 0 [my address] [amount] The initial amounts I tried resulted in a transaction that was too large, so I had to try again (and again) until eventually I managed to send a transaction of 1.4 QCN. Woohoo! I then continued sending another small transactions every few minutes until I reached the point where my balance of QCN was exhausted. But then I discovered that all that work was apparently for naught -- most of the transactions failed to get written to the block chain. What's going on!? Best guess: my transactions are being ignored by the block finders because they are large and small -- meaning, maximum size but minimal value in coins. Is this reasonable? I had this happen once already when I tried to transfer coins to Poloniex -- only one of seven transactions actually showed up. I had to delete wallet.bin and then resync the wallet, at which point all of the "lost" coins reappeared in my wallet. Then I did the above sending coins to myself to try and group them into larger units, so I could send a single transaction to Poloniex, and of the transactions I sent yesterday it seems only one of those went through. Has anyone else experienced this? Is there a solution/workaround that I'm not doing properly? It looks like my initial mining of QCN generated 2781 transactions totaling just 10.4 QCN (give or take), and you can only have about 100 inputs into a transaction before it becomes too large. So I wanted to send myself 28 transactions, basically, and then I could send myself one "big" transaction, and then I would be done. But it's not working that way. :-( Also, I'm now getting the following after "resyncing" with the chain: 2014-Jun-26 18:30:28.370301 [RPC1]ERROR ..\..\src\cryptonote_core\tx_pool.cpp:62 Transaction with id= <d27babecc9557afef79f440f5ab140a7fd2340f9849c703aeda1aec22c4f7e3a> used already spent key images 2014-Jun-26 18:30:28.379307 [RPC1]Transaction verification failed: <d27babecc9557afef79f440f5ab140a7fd2340f9849c703aeda1aec22c4f7e3a> So it looks like maybe I need to delete the blockchain.bin as well and resync that again. This is seriously a pain in the butt! The wallet needs some help if QCN (and other CryptoNote coins that are similar) want a chance to succeed! You was absolutely right when sent transaction for yourself. I recommend to have at least 2 wallet: for small transfers & pool payments and for large transactions. After this your transactions got into the tx pool. It means the network see it, and you can't spend these quazarcoins but hash wasn't found in block explorer. You need to wait a while. If after 24 hours the transaction didn't deliver, QCN back in your wallet.
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
OracionSeis (OP)
|
|
July 01, 2014, 06:05:20 PM |
|
Hey guys! Welcome to our pool Minergate.com. We support mining of Quazarcoin and offer two reward models - PPS and PPLNS (you can choose suitable method for each currency individually). Moreover, we have the lowest fees on the market (2% PPS, 1.5% PPLNS). Enjoy the most profitable on our pool! Regards, Minergate.com Enjoy the most profitable mining on our pool Good news
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
OracionSeis (OP)
|
|
July 01, 2014, 06:06:34 PM |
|
Check out that new luck feature http://qcn.extremepool.org under Pool Blocks
Extreme Poolhttp://www.extremepool.orgWe offer a Pool for every Cryptonote Coin Features: •Fast Payouts directly to your private wallet. •Address Validation •Latest pool code from Zone117x •Variable Difficulty based on your individual CPU performance •Verified Secure •Servers hosted in our own Data Center, not hosted by an online 3rd party provider •Servers secured with enterprise firewalls Come mine with us! We have the most popular BCN and DuckNote pools available! http://www.extremepool.orghttp://qcn.extremepool.org I can safely recommend this pool and this dev.
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
theGypsy
Newbie
Offline
Activity: 29
Merit: 0
|
|
July 01, 2014, 07:48:36 PM |
|
Guys, please advice what's wrong with my QCN daemon? My quazarcoind.log contains thousands of lines as shown below. Binaries of Jun 18. Yes, it is synchronized, but it takes ages to complete.
2014-Jul-01 23:42:21.490158 [P2P1]ERROR c:\projects\quazarcoin\contrib\epee\include\net\levin_protocol_handler_async.h:638 [203.90.182.112:61592 INC]Failed to do_send() 2014-Jul-01 23:42:21.600164 [P2P8]ERROR c:\projects\quazarcoin\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
|
|
|
|
33zer0w0lf
|
|
July 01, 2014, 07:59:42 PM |
|
Guys, please advice what's wrong with my QCN daemon? My quazarcoind.log contains thousands of lines as shown below. Binaries of Jun 18. Yes, it is synchronized, but it takes ages to complete.
2014-Jul-01 23:42:21.490158 [P2P1]ERROR c:\projects\quazarcoin\contrib\epee\include\net\levin_protocol_handler_async.h:638 [203.90.182.112:61592 INC]Failed to do_send() 2014-Jul-01 23:42:21.600164 [P2P8]ERROR c:\projects\quazarcoin\contrib\epee\include\net\abstract_tcp_server2.inl:307 send que size is more than ABSTRACT_SERVER_SEND_QUE_MAX_COUNT(100), shutting down connection
by default the daemon is very verbose, ignore that nothing is wrong.
|
|
|
|
theGypsy
Newbie
Offline
Activity: 29
Merit: 0
|
|
July 01, 2014, 08:07:15 PM |
|
by default the daemon is very verbose, ignore that nothing is wrong.
I would say the daemon is damn verbose, everyone may get frightened watching the endless stream of red messages on the screen...
|
|
|
|
sleepdog
|
|
July 02, 2014, 09:39:25 AM Last edit: July 02, 2014, 12:57:22 PM by sleepdog |
|
EDIT : the post I was replying to got deleted...
|
|
|
|
OracionSeis (OP)
|
|
July 02, 2014, 12:39:46 PM |
|
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
OracionSeis (OP)
|
|
July 02, 2014, 12:40:38 PM |
|
Great initiative as always, I see what I can add. Folks, this man owns the HashInvest pool.
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
OracionSeis (OP)
|
|
July 02, 2014, 12:45:46 PM |
|
by default the daemon is very verbose, ignore that nothing is wrong.
I would say the daemon is damn verbose, everyone may get frightened watching the endless stream of red messages on the screen... I agree with you. In the next update you'll see only important notifications in 'set_log 0'.
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
OracionSeis (OP)
|
|
July 02, 2014, 12:50:29 PM |
|
Thank you! I'll add this link to the top posts & the site.
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
OracionSeis (OP)
|
|
July 02, 2014, 02:47:51 PM |
|
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
OracionSeis (OP)
|
|
July 03, 2014, 09:11:42 AM |
|
Nice, I'll add info in QCN resources.
|
Time off to sleep ... ( ̄︶ ̄)~
|
|
|
|