FYI around 20k XMG were lost when my hard drive crashed. Make backups!  edit: Or was it 2k? Not sure anymore, which is the worst...  |
|
|
|
Block 715 mined by kontik had a fake timestamp again. What an evil guy...  edit: Block 721 just now too. Block 723 mined by him had a legit timestamp. his node should be blocked or something this guy is a real jerk Dunno, he might just have a shit ton of Amazon instances that are not properly time synced. You can't expect every miner to have his clock set exactly to "internet time", deviations up to 5 minutes are "normal" imo. It is a clear oversight of the Pascalcoin dev and I hope he will release an update, so far his only response was ambiguuous: 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.
This post by Vorksholk is pretty interesting: Not sure what fix the PascalCoin dev is working on, but the usual solution that other PoW blockchains adopt is to let a new block be valid if its timestamp is greater than the median timestamp of the last 'n' (bitcoin chooses 11) blocks, and if it's less than the "network adjusted time" (average of all nodes you're connected to) + m hours (bitcoin chooses 2).
|
|
|
|
|
So solo miners are left in the rain or will the wallet be updated and the bug fixed?
|
|
|
|
Block 715 mined by kontik had a fake timestamp again. What an evil guy... edit: Block 721 just now too. Block 723 mined by him had a legit timestamp. |
|
|
|
5 minutes blocktime makes 288 blocks/day. It still is a bit more blocks than that due to difficulty adjusting. btw: Last block took 22 minutes! edit: Current block age: 25 minutes! Seems like the hashrate is falling.  |
|
|
|
Sorry Norfolk, I misunderstood your post. The spammer(s) are pathetic though. edit: qed... |
|
|
|
Avoid premine. And ICO. |
|
|
|
You could always do a hostile takeover. It depends on the miners, not the dev, which blockchain will prevail. That might be an asshole move though.  I vote for JPC2 with a fresh start. |
|
|
|
So mining is useless until that timething is fixed?
It almost fixed itself now. When block times were low, big miners were submitting blocks with fake timestamps in such a rapid succession, that honest miners were not able to squeeze in their own blocks (due to the last block having a timestamp a few seconds to a minute in the future). Now that blocktimes are close to 5 minutes, it happens very rarely. If they try to set their timestamps more than ~two(?) minutes into the future they risk getting their nodes banned. At least that is my understanding. Not sure how the attack on the original Pascalcoin plays into that, but I guess the impact on Pascalcoin was much lower. |
|
|
|
|
IMO simply clone the coin with fair parameters (no premine, good diff adjustment), no need to watch out for any bagholder's (dev included) feelings.
|
|
|
|
|
Great, will be interesting to see which coin can fix the issue the quickest and most effective.
|
|
|
|
no airdrop ?
I think he already gave away all 10 blocks that he mined. life punishes those who come too late
-Erich Honecker- |
|
|
|
[...
interesting.
Original Pascal did not have this problem? Or perhaps it's more that this feature wasn't evident until the network was far bigger?
Basically you can stall the network by attaching a weird timestamp to the last block, and the client assumes that it is behind the tip by a fair amount, this means that someone with enough hashpower could 51% attack the network and stall it forever mining blocks and releasing them when the timestamp of their finishes... or someone more crafty comes along and attaches a timestamp even further in the future. Couldn't having a bunch of nodes prevent that? I'd assume the nodes would have some sort of consensus on what is the precise time discarding miners who try to cheat. This coin first launched with 2 nodes, not just one like the other coin and as far as I know this one didn't suffer from the attack, but I could be wrong. Whatever the case might be, depending on local timestamps seems like a pretty dumb idea. The original Pascalcoin is being attacked as well and it has quite a few nodes: https://bitcointalk.org/index.php?topic=1583719.msg17705293#msg17705293More nodes are useless, Pascal Lite has over 100 and is still being attacked (although it has much lower impact now), it is the wallet that refuses to submit blocks when there is a "newer" one. Obviously a bug in the code. |
|
|
|
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.
^Won't solo miners be screwed over when they submit a block with a lower timestamp than the last block with faked timestamp? At least that's what happened/happens over at Pascal Lite. |
|
|
|
Nice initiative, but I recommend https://getsharex.com/ for taking videos of the screen. I guess we have to live with the clock attack until the Pascalcoin dev has done the needful? Luckily the attack seems to get more and more useless as time goes on. But since Pascalcoin with it's MUCH higher hashrate now has the same problem, it seems as if it might be indeed a pool doing the attack (someone suspects nanopool). Has to be someone with lots of hashrate for sure. edit: 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.
|
|
|
|
|
@becauseI and his spammer "team" (probably just some sockpuppets):
Spamming this coin everywhere makes me like it even less, so doing that is counterproductive. Only newbs will fall for your badly worded "conversations".
|
|
|
|
Which is the line of the miner, since I cannot mine says invalid credentials to me porfavor and graces  ? You need to set a miner name. @oslak: I agree. Pretty sure that there are more than 34 nodes though. NodeServers Updated: 02.02.2017 13:48:32 Count: 101 If we ban the IPs they will just use TOR or VPNs. Might be worth a try, if only to mildly inconvenience the fuckers. edit: How to identify the rogue nodes anyway? Also 240GH/s!  |
|
|
|
When making a withdrawal from polo to my pasc account what or where do I find payload
AFAIK that is not necessary, just the account number should work fine. |
|
|
|
^Fucking spammers...
Ontopic: Is the clock attack still going on?
Yes, but I've just adjusted my clock to use +30 sec as well That can only be a temporary solution right? Or every other miner has to do the same... Pascalcoin, traveling through time and space. edit: Ah, you were j/k... something needs to be done for sure. @the PureVidz spammers: I reported all of you, you guys are the lowest on btctalk, even lower than the scamcoin creators. |
|
|
|
|
Show Posts
