I looked at the code and I think its best to leave the code that way it is.
Reason being if we ignore the "unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp" it might make the blockchain get forked because blocks won't be in the proper order.
I can't ban the IP because I only see IP address but not their usernames.
We need to wait until the block times are between 5-10 minutes apart and they won't be able to cheat.
Topic: [ANN][PASL]-[PASCAL Lite]-[The Future is Almost Here] - page 121. (Read 164899 times)
Whith 4 GH i hitm only 1 block, 1.5 hours ago...
Where is this block explorer youre talking about? and to see whos mined a block?
go to the wallet and click on BlockChain Explorer tab
Got my 3rd block! Time is synced with time-a.nist.gov and its all ok!
I run win10, time synced twice at a day (my work need it).
Made on router port mapping for proper work of node.
Made on router port mapping for proper work of node.
My acc 311-93
Sent you 50
mine is 765-23
I will send you 50 once your account matures.
thanks dev 3GhhbourM2LMg6aYW8eYE7BY5m1wHX3hqoZ5opmaSayB7jmAgUEVxJndGFSGarz4LgAWCxEESchyp3E UqMatQRgUrMpoWQKgvuNneE
Where is this block explorer youre talking about? and to see whos mined a block?
If it says you've found a block its because your miner found the correct hash but due to the "INVALID LAST BLOCK TIME" it gets rejected. This is a bug that miners are taking advantage of.
Basically this error is linked to this piece of code
unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp;
If (unixtimediff<0) then begin
WhyNot := 'Invalid Last Block Time';
exit;
I am working on it and will try to get it fixed if I can.
Read time from node (nodes), and ban all shit whith bat timestamp by ip...Basically this error is linked to this piece of code
unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp;
If (unixtimediff<0) then begin
WhyNot := 'Invalid Last Block Time';
exit;
I am working on it and will try to get it fixed if I can.
I agree with this. I can save my miner that proves I found a block 273. that's BS
If it says you've found a block its because your miner found the correct hash but due to the "INVALID LAST BLOCK TIME" it gets rejected. This is a bug that miners are taking advantage of.
Basically this error is linked to this piece of code
unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp;
If (unixtimediff<0) then begin
WhyNot := 'Invalid Last Block Time';
exit;
I am working on it and will try to get it fixed if I can.
Read time from node (nodes), and ban all shit whith bat timestamp by ip... Basically this error is linked to this piece of code
unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp;
If (unixtimediff<0) then begin
WhyNot := 'Invalid Last Block Time';
exit;
I am working on it and will try to get it fixed if I can.
my public key is : 3GhhbokPmX5ZSXyXMegQhgUBzfMzLPQb9TqPLiQcXbgLybu7PQwxKfn6ZhL6gEHeSS1Dr57h6DMNahT YVVTQkNHUT5ebUXtL5xgWJy
On new block, the current block age always starts on -2min is this normal?
yep it says i found block 273, but on the explorer it's bahbahwp07. just my luck....
If it says you've found a block its because your miner found the correct hash but due to the "INVALID LAST BLOCK TIME" it gets rejected. This is a bug that miners are taking advantage of.
Basically this error is linked to this piece of code
unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp;
If (unixtimediff<0) then begin
WhyNot := 'Invalid Last Block Time';
exit;
I am working on it and will try to get it fixed if I can.
Basically this error is linked to this piece of code
unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp;
If (unixtimediff<0) then begin
WhyNot := 'Invalid Last Block Time';
exit;
I am working on it and will try to get it fixed if I can.
My time is synced with time.windows.com in my time settings.. is there a way to fix this? I'm DEFINITELY not getting the blocks that "kontikpr, kontikwp and bahbahwp are, but I don't want to be doing anything I'm not supposed to. Is there a way to fix this manually?
EDIT: Manually changed my time back 3 minutes. Will this help?
If it says you've found a block its because your miner found the correct hash but due to the "INVALID LAST BLOCK TIME" it gets rejected. This is a bug that miners are taking advantage of.
Basically this error is linked to this piece of code
unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp;
If (unixtimediff<0) then begin
WhyNot := 'Invalid Last Block Time';
exit;
I am working on it and will try to get it fixed if I can.
Basically this error is linked to this piece of code
unixtimediff := UnivDateTimeToUnix(DateTime2UnivDateTime(Now)) - Bank.LastOperationBlock.timestamp;
If (unixtimediff<0) then begin
WhyNot := 'Invalid Last Block Time';
exit;
I am working on it and will try to get it fixed if I can.
Its working! Found my 1st block 
how to fix this invalid timestamp?
finally found a block..
its running ^^
its running ^^
did you receive an account? on mine it says I've found 4 blocks but no account
refresh the wallet with the refresh button..
miner says 5blocks found or wallet?
finally found a block..
its running ^^
its running ^^
did you receive an account? on mine it says I've found 4 blocks but no account
Why some blocks i've found disappeared few seconds after ?
8 blocks found, only 4 finally
8 blocks found, only 4 finally
could be worse: found 7 blocks according my miner, but nothing in the wallet...
finally found a block..
its running ^^
its running ^^
Jump to: