Hi all.
I've received ocminer warning and I've found what's going on.
Problem is found and solution too. No problem.
Pools will have a definitive solution in few hours, meanwhile you can mine without problems.
Blockchain is secure and protected, maximum difference of 300 seconds between nodes is still working and protecting blockchain, the problem is that pools do not use a correct timestamp if it's current time is lower than the last blockchain timestamp, meanwhile, if they need, can just increment manually time.
Pool is now updated with the new daemon. |
|
|
|
suprnova unable to connect  and price goes down  [/quote Sorry I've updated the frontend, backend was good all the time. |
|
|
|
^Fucking spammers...
Ontopic: Is the clock attack still going on?
Yes, but I've just adjusted my clock to use +30 sec as well  Just kidding, but this needs to be addresses as the attack is going on |
|
|
|
Yeah those bastards screwed up the entire Pascal Lite coin launch. Right from the very beginning they kept doing that. And during the TEST launch they behaved and didn't do anything wrong so I assumed the network was good to go.
They also seem to have MASSIVE hashpower, I am getting at least 200-300 GPUs on my coin alone and since PascalCoin network is much larger they probably have another 500-1000 GPUs pointed at this coin. This isn't a small miner, its a farm the size of a warehouse.
So who is doing the hack is it Nanopool or that "PasYarYar" or "abc0000000" "pwallet"?
You can't tell as you can set the block header to anything you like I could even just mine blocks with "Nanopool" if I would want to I also think they run a bunch of nodes with clocks synced all the way up to bring the average difference much higher according to if Not IsValidTime(connection_ts) then begin DisconnectInvalidClient(false,'Invalid remote timestamp. Difference:'+inttostr(FLastKnownTimestampDiff)+' > '+inttostr(CT_MaxSecondsDifferenceOfNetworkNodes)); end; Albert tried to fix this issue with the above command but apparently back then the coin wasn't listed on any exchanges and nobody bothered to attack it. Thats possible yes, but I think it's just a unwanted coincidence as they're driving up the diff for themselves as well. |
|
|
|
Yeah those bastards screwed up the entire Pascal Lite coin launch. Right from the very beginning they kept doing that. And during the TEST launch they behaved and didn't do anything wrong so I assumed the network was good to go.
They also seem to have MASSIVE hashpower, I am getting at least 200-300 GPUs on my coin alone and since PascalCoin network is much larger they probably have another 500-1000 GPUs pointed at this coin. This isn't a small miner, its a farm the size of a warehouse.
So who is doing the hack is it Nanopool or that "PasYarYar" or "abc0000000" "pwallet"?
You can't tell as you can set the block header to anything you like I could even just mine blocks with "Nanopool" if I would want to |
|
|
|
There seems to be an attack going on ... I was ddosed and while I was ddosed I noticed blocks with "high" timestamps which subsequently reject my blocks with the correct time:
02-02-2017 10:27:10.151 TID:E5496700 [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Error: Invalid timestamp (New timestamp:1486027668 last timestamp (58999):1486027790) payload:SUPRNOVAROXXXXXXXXXXXXHXpLc/------ timestamp:1486027668 nonce:1303498590
I'm investigating what is actually going on exactly...
Frontend will be fine in a few moments, the DDoS ended.
OK, there are several nodes sending valid blocks with higher timestamps: 02-02-2017 10:45:18.259 TID:F0977700 [Error] <TNetServerClient> Disconecting 89.249.254.45:50962 > Invalid remote timestamp. Difference:227 > 180 Thus making my blocks "invalid" through to too "old" time even though my clock is correct: 02-02-2017 10:44:59.041 TID:F0977700 [Error] <TPCOperationsComp> Invalid new block 59002: Invalid timestamp (New timestamp:1486028696 last timestamp (59001):1486028710) 02-02-2017 10:44:59.041 TID:F0977700 [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Error: Invalid timestamp (New timestamp:1486028696 last timestamp (59001):1486028710) payload:SUPRNOVAROXXXXXXXXXXXXRkmq4------- timestamp:1486028696 nonce:3038414114 What those guys exploit is an old bug which was fixed in bitcoin years ago. They send their blocks with a maximum "drift" ahead .. Example: It's now 11:30:00 and blockchain is at height 59000 Max Drift is 30 seconds So they say they solved Block 59001 at 11:30:30 even though it's just 11:30:00 and now my pool finds the next block as 11:30:20 which is BEFORE 11:30:30 so the blockchain rejects the block and says "Nope, your clock is wrong (even though my clock is right!) and I reject your block because the block before was discovered later"... We need the dev here to fix that.. |
|
|
|
|
There seems to be an attack going on ... I was ddosed and while I was ddosed I noticed blocks with "high" timestamps which subsequently reject my blocks with the correct time:
02-02-2017 10:27:10.151 TID:E5496700 [Error] <TJSONRPCTcpIpClient> Sending Error JSON RPC id () : Error: Invalid timestamp (New timestamp:1486027668 last timestamp (58999):1486027790) payload:SUPRNOVAROXXXXXXXXXXXXHXpLc/------ timestamp:1486027668 nonce:1303498590
I'm investigating what is actually going on exactly...
Frontend will be fine in a few moments, the DDoS ended.
|
|
|
|
|
it'll be back up in a few moments, adding a new server
|
|
|
|
Seems like a lot of work for something that is planned to be obsolete in 2 months. Is the problem that bad that you can't wait? The pool issue is actually quite bad with frequent crashes. Hmm actually I have that under control pretty well... |
|
|
|
Hi all,
what happened with supernova dashboard, suddenly it doesn't show balance and worker hashrate?
cheers1
Someone is DDosing the API currently, I'm fixing it |
|
|
|
|
Suprnova is - of course - updated
|
|
|
|
he mean bounty for everyone  . Do you ad POS feature to this lite pascal No there will be no POS, too hard to code that in. I could do bounty however that means premine. Its up to you guys. I rather leave no premine since the original pascal coin was no premine. I am pretty sure unless you are mining on a CPU, the difficulty will be very small and you can solo mine a few coins. The difficulty will be very low until its hits an exchange and it could be weeks or never until that happens. Or until it hits a pool |
|
|
|
confirmed this morning by Poloniex that suprnova is broken.
quoted from Poloniex staff ...
"It seem that transaction was sent without a xmr payment id"
Till this is fixed can't mine at suprnova.
Sad considering this looked to be decently maintained but appears pool operator ocminer is too busy with pascal these days.
I'm mining on my own pool and I also withdraw to polo. even if you send a payment without payment id to polo, just send them the TXID and the exact amount of your payment and they can still credit the amount to your account - since it's been transferred to their account... There are three checks in the pool software that sending to polo's address is impossible without payment id, first when entering the address, the second when verifying the address and the last when sending to that address.. I doubt it was really sent without polo payment id.. IMHO those ring-ct's have problems sometimes since XMR updated / forked. Chainradar shows NO payment ID (I PM'd you the details) Poloniex said it was sent with NO payment ID and they are forwarding to another department to see if they will credit me or not. 48 hours later, no credit yet. I believe you when you say there are checks in place. Previous payments went through without an issue. I was one of the first to beta test this but this last transaction failed. Having to waste all this time to chase it up, and still no funds, still waiting, something is still broken somewhere. Non integrated payment ID's where IMHO a stupid idea to start with. OK, message me your TXID again and I'll check that once more ! |
|
|
|
confirmed this morning by Poloniex that suprnova is broken.
quoted from Poloniex staff ...
"It seem that transaction was sent without a xmr payment id"
Till this is fixed can't mine at suprnova.
Sad considering this looked to be decently maintained but appears pool operator ocminer is too busy with pascal these days.
I'm mining on my own pool and I also withdraw to polo. even if you send a payment without payment id to polo, just send them the TXID and the exact amount of your payment and they can still credit the amount to your account - since it's been transferred to their account... There are three checks in the pool software that sending to polo's address is impossible without payment id, first when entering the address, the second when verifying the address and the last when sending to that address.. I doubt it was really sent without polo payment id.. IMHO those ring-ct's have problems sometimes since XMR updated / forked. |
|
|
|
ocminer, payout in the address of your pool, I can put the address of poloniex? "Payment Address. Syntax: 123456-12.payload For example Polo: 86646-64.aeb0b5fe99694894" I get Failed to update your account: Invalid coin address on suprnova ! Whats your address? I have Tested Polo addresses and they work Fine |
|
|
|
then pascalcoin being algorithm sha 256, you can pull antminer s5 s9 s7?
no it's a modified sha256, not the sha of bitcoin btw are the estimate correct on suprnova? No, they are not correct yet - I'm working on them within the next 24h. If someone has a good formula, let me know ! BTW I'm seeing a DDoS to Suprnova's PASC frontend currently, page could be a bit slower as usual. |
|
|
|
ZEC pool down?
Hmm, no looks good from here.. What issue do you have ? |
|
|
|
WAHOO! I saw my miner name on suprnova that I found a block! Glad I could help!  ... even for a little fish Congrats, good to have to on the pool ! will we be able to get free pascal accounts if we want to mine to our wallets but dont have an account? thanks made this How To Mine Pascal Coin on Suprnova Tutorial  Thanks, I've added your Video to the Pool header and yes, accounts will be given away for free, but I still have to tweak a few things like Stats/Estimates etc and after that I'll have a look. |
|
|
|
WAHOO! I saw my miner name on suprnova that I found a block! Glad I could help! ... even for a little fish Congrats, good to have to on the pool ! |
|
|
|
|
OK guys, I've got payouts enabled on suprnova now; I already saw quite a bunch of payments going out to Polo, can someone confirm seeing them in their balance already ?
|
|
|
|
|
Show Posts
