Author

Topic: [ANN] [PASC] PascalCoin, true deletable blockchain - V3 Hardfork on block 210000 - page 195. (Read 990744 times)

sr. member
Activity: 391
Merit: 250
aka ...
Hi @PascalCoin,


I figured out, I missed some Blocks


here



and here


Got the same behavior in Version 1.4.3 ... mining on the wrong block


as you can see here.


Sometimes I even thought, Supernova Pool was one the wrong block, according 2 dashboard.


When I take a closer look at the Payload/Operations of some blocks, and their time,
my guess is sombody (powerfull) tries 2 freak the System.


 Grin PanneKopp
hero member
Activity: 742
Merit: 500
Many Pascalcoin clones started as I see. Pascal Lite, Turbo pascalcoin...  Undecided
newbie
Activity: 4
Merit: 0
I had to stop mining on Nanopoool because it takes too much time for it to show the miner stats, so I think I am mining to nowhere. In the case of Suprnova, the cpu load for SGIminer is too high, so, at this time I am not able to mine in any pool.

Any chance to mine on Suprnova using other miner?



sgminer-5.5.0-pascal-1-windows-amd64

Hi, thank you for your response. Is that a command to be used with sgminer?

Command:   sgminer.exe -k pascal -o stratum+tcp://pasc.suprnova.cc:5279 -u Weblogin.Worker -p WorkerPassword -I 21 -w 64 -g2

my cpu is running at no load
jr. member
Activity: 58
Merit: 1
I had to stop mining on Nanopoool because it takes too much time for it to show the miner stats, so I think I am mining to nowhere. In the case of Suprnova, the cpu load for SGIminer is too high, so, at this time I am not able to mine in any pool.

Any chance to mine on Suprnova using other miner?



sgminer-5.5.0-pascal-1-windows-amd64

Hi, thank you for your response. Is that a command to be used with sgminer?

Edit: I have used the Sgminer already, but it demands too  much from the CPU. It takes CPU'S activity to 100.
newbie
Activity: 4
Merit: 0
I had to stop mining on Nanopoool because it takes too much time for it to show the miner stats, so I think I am mining to nowhere. In the case of Suprnova, the cpu load for SGIminer is too high, so, at this time I am not able to mine in any pool.

Any chance to mine on Suprnova using other miner?



sgminer-5.5.0-pascal-1-windows-amd64
jr. member
Activity: 58
Merit: 1
I had to stop mining on Nanopoool because it takes too much time for it to show the miner stats, so I think I am mining to nowhere. In the case of Suprnova, the cpu load for SGIminer is too high, so, at this time I am not able to mine in any pool.

Any chance to mine on Suprnova using other miner?
legendary
Activity: 1068
Merit: 1020
these are the code changes nanopool made: https://github.com/nanopool/PascalCoin/commit/f6949c4d16b43b4ffc567c4ed5bc67b48d0ac65c

I see them trying to mess with timestamps and adding an office.  Is that not clear enough?
hero member
Activity: 952
Merit: 500
Should update OP with latest wallet Shocked
legendary
Activity: 1500
Merit: 1002
Mine Mine Mine
has anyone figured out yet how to use sgminer to solo mine ?

i'm sure ocminer will have a solution pretty soon.

let's see how things goes.

btw the link works now, on latest wallet 1.4.3.

** PascalCoin miner ** Version: BETA 0.3 FOR SUPRNOVA TESTING ONLY

thats the latest miner that comes with the latest wallet. so it's meant only for suprnova or can we use it to solo ?
hero member
Activity: 756
Merit: 501
Also to everyone shitting on Pascal Lite:

This coin launch uncovered a major flaw in Pascalcoin, you should be happy that it wasn't abused in a serious way on Pascalcoin and that it was quickly fixed. From my understanding one also needs way less than 51% to perform a 51% attack when abusing this flaw.

Instead you go: "Hurr durr it's a fake!11!"  Roll Eyes
legendary
Activity: 1068
Merit: 1020
Looks like ocminer discovered the exploit and he was getting attacked.  

Sounds like it was one or more parties trying to game the system, not Suprnova.  

The dev may know the answer, but I'm siding with Suprnova.
The exploit was found when Pascal Lite launched, at least two miners got lots of blocks with this technique and caused many miners to not being able to submit their valid blocks.

That makes sense, thanks for speaking up.
hero member
Activity: 756
Merit: 501
Looks like ocminer discovered the exploit and he was getting attacked.  

Sounds like it was one or more parties trying to game the system, not Suprnova.  

The dev may know the answer, but I'm siding with Suprnova.
The exploit was found when Pascal Lite launched, at least two miners got lots of blocks with this technique and caused many miners to not being able to submit their valid blocks.
legendary
Activity: 1068
Merit: 1020
nano shit  pool ban 2 blocks of mine, so i fuck the pool, last days i found prefix  abc_ is luck, give 150% earnings

Is luck? I don't understand.
hero member
Activity: 609
Merit: 500
DMD,XZC
nano shit  pool ban 2 blocks of mine, so i fuck the pool, last days i found prefix  abc_ is luck, give 150% earnings
sr. member
Activity: 273
Merit: 250
Hmm that's a coincidence. 

Suprnova 4 hours running with no block. Who's really the bastard here? Nanopool?
Failure to suprnova
Supernova 59216, blockchain 59236
who are you,the miner abc_ is my solo rigs,now i change the name
You're right, this is a coincidence

Looks like someone is trying to make abc_ as the culprit here.
newbie
Activity: 8
Merit: 0
Hmm that's a coincidence. 

Suprnova 4 hours running with no block. Who's really the bastard here? Nanopool?
Failure to suprnova
Supernova 59216, blockchain 59236
who are you,the miner abc_ is my solo rigs,now i change the name
You're right, this is a coincidence
legendary
Activity: 1068
Merit: 1020
Hmm that's a coincidence. 

Suprnova 4 hours running with no block. Who's really the bastard here? Nanopool?
Failure to suprnova
Supernova 59216, blockchain 59236
who are you,the miner abc_ is my solo rigs,now i change the name
hero member
Activity: 609
Merit: 500
DMD,XZC
Suprnova 4 hours running with no block. Who's really the bastard here? Nanopool?
Failure to suprnova
Supernova 59216, blockchain 59236
who are you,the miner abc_ is my solo rigs,now i change the name
newbie
Activity: 8
Merit: 0
I saw blocks being found by nanopool and by ABC1.  That's what I'm saying.  Nice exploit guys!  

You would say that because you were able to find some blocks..are you coordinating with nanopool?

Suprnova 4 hours running with no block. Who's really the bastard here? Nanopool?
Failure to suprnova

he is nanopool.
http://prntscr.com/e3u57z I'm a little miner, and is not able to find the block
legendary
Activity: 1068
Merit: 1020
Looks like ocminer discovered the exploit and he was getting attacked.  

Sounds like it was one or more parties trying to game the system, not Suprnova.  

The dev may know the answer, but I'm siding with Suprnova.

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] 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] 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] Invalid new block 59002: Invalid timestamp (New timestamp:1486028696 last timestamp (59001):1486028710)
02-02-2017 10:44:59.041 TID:F0977700 [Error] 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..

Jump to: