I think no premine , no ico , thats why only 2 connections and dev mining , I think he will release the nodes soon .
Lol yeah and it's snowing in hell too  |
|
|
|
Count me in |
|
|
|
1.Another attempt to associate cryptocurrency with the government. But why?
The government will never agree with the decentralization. It is a complete loss of power and money.
2. What about premine, and if so, how much and where will be used?
premine , most likely is 10% , its seems like the main.cpp from github is missing , that file contain the block reward and premine Subdirectories are missing as well.. |
|
|
|
anyone know an x11 miner for amd on windows?
sgminer nicehash |
|
|
|
Sorry but some folks are trying to mine with scrypt and some strange algos and are flooding the server with that. I'm banning them but they just come back with another ip.
I'll try to ban maybe the subnet
In "getting started" of maxminers pool is explained using sgminer for xzc mining... maybe some people are trying to mine with wrong software in suprnova Yes, that's possible. I've banned the subnet now and I'll write maxminers a pm |
|
|
|
|
Sorry but some folks are trying to mine with scrypt and some strange algos and are flooding the server with that. I'm banning them but they just come back with another ip.
I'll try to ban maybe the subnet
|
|
|
|
WHY IS BOTH MY EMAILS AND PM HERE IGNORED BY YOU! My account has been locked for nearly a week now and your system is not sending me unlock emails! I have checked spam filter and no email! I can't login!
What's your username on the pool? Usually I unlock within a few minutes |
|
|
|
|
Okay guys, I've finally restored the balances from before the fork and also credited all the lost transactions back to your accounts.
Thank for your trust and patience.
|
|
|
|
|
I found a way to extract the "bad" payments from the pool, it takes a bit time but everything should be fixed within the next 3-4h and you should see some balance back in your account.
All new mined blocks and transactions are fully unaffected and are working/paying fine.
Thanks for your patience.
|
|
|
|
Currently the wallet is still reporting coins from the fork as well, so first I need to sort that out and get the wallet rescanned to the actual "real" balance - after that I need to go through the payments of the night, because lots of people tried to withdraw as they saw they had so many coins suddenly and after that I can tell what happens with the old balance. The problem is - even if you had 100 coins before the fork and suddenly 500 during the fork - you then withdraw everything during the fork, from my side, I only see the 500 debit, but I don't see 100 + 400 - if I simply re-credit the 500 coins you'd get 100 "valid" coins and 400 "invalid" coins thus depleting the pools wallet. So i first have to find out which balance is correct This reminds me of the early days of litecoin / darkcoin mining .. It was a crazy time, lots of cheaters, lots of attacks, all sort of TimeWarp / flooding / spoofing attacks etc.. It's exactly the same here as the codebase is very young and not mature yet, so this will 100% happen again and again until all the issues are sorted. |
|
|
|
OCMiner is it safe to mine at your pool again?
I'm on the old 1.4.2 version, the explorer and Nano seems to be on that version too.. So I guess.. yes ?! |
|
|
|
I had over 30 Pascal from valid chain before the fork happened..
So they are lost ..i just see 11PASC left in my account. Despite the coins from the invalid chain that gone too.
No, just let me figure out how to rescan that wallet, I'm waiting for the dev, the coins before the fork are (should be) safe ! |
|
|
|
OK, I get accepted blocks with the old version: http://explorer.pascalcoin.org/block.php?block=59300So the pool is back on track now.. Just really a pity that there are now valid consensus rules, usually old blocks should be rejected... Well.. Thats how it is.. |
|
|
|
Lost 100 Pascal due to this..stupid not to mention also transfers was going from a valid blockchain due to invalid over autopayment in the wrong blockchain maybe lost forever.
How you could reintroduce a bug of bitcoin they had many years ago? This is amateurish.
Ocminer: What about the coins from valid chain that have been transfered due to autopayment when pool was on wrong chain? Are these valid also lost? They should still be there right?
Well.. the problem is, many folks mined much more coins during the fork than they did before. They saw that and then of course withdraw that to polo so the wallet sent the coins there, they never get there but they are at least how it looks gone from the wallet. There doesn't seem to be a "rescan" or "reindex" option in the wallet - i'm looking for that currently to see what is lost and what not... Lets wait for the dev EDIT: What is 100% secure is that one big miner did NOT upgrade from 1.4.2 and subsequently rejected my valid blocks from 1.4.3 |
|
|
|
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon. Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions I'll try to get switched to a backup node running the old version. OC miner. Others miners, just like me, did not have their withdrawals confirmed at Polo. What will be done? The coins are all lost unfortunately, we've mined hot air on the wrong chain. |
|
|
|
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon. Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions I'll try to get switched to a backup node running the old version. thanks for the actions taken, 1 hours ago i had Unconfirmed: 249.6551 PASC, does it mean they are gone now ? Unfortunately yes, all mined on the wrong chain. |
|
|
|
I cannot get the pool synched back to the "other" chain, looks like not everyone has updated and there are still invalid blocks sent which are rejected by the newer daemon. Well, thats what you have with new technology, this is not a well known and good working Bitcoin based coin, it's a new source based on Pascal with all the exploits available fixed in bitcoin versions I'll try to get switched to a backup node running the old version. |
|
|
|
@ocminer: Same problem with suprnova? [2017-02-02 17:58:00] Starting Stratum on stratum+tcp://xzc.suprnova.cc:5596
[2017-02-02 17:58:00] 1 miner threads started, using 'lyra2rev2' algorithm.
[2017-02-02 17:58:30] Stratum connection failed: Connection timed out after 30001 milliseconds
[2017-02-02 17:58:30] ...retry after 10 seconds
[2017-02-02 17:59:10] Stratum connection failed: Connection timed out after 30000 milliseconds
[2017-02-02 17:59:10] ...retry after 10 seconds
[2017-02-02 17:59:50] Stratum connection failed: Connection timed out after 30001 milliseconds
[2017-02-02 17:59:50] ...retry after 10 seconds
[2017-02-02 18:00:11] stratum_recv_line failed
[2017-02-02 18:00:11] ...retry after 10 seconds
[2017-02-02 18:00:51] Stratum connection failed: Connection timed out after 30001 milliseconds
[2017-02-02 18:00:51] ...retry after 10 seconds
[2017-02-02 18:01:31] Stratum connection failed: Connection timed out after 30000 milliseconds
[2017-02-02 18:01:31] ...retry after 10 seconds
Yes, same, sorry ! Fixed now |
|
|
|
|
Show Posts
