Best posts made by cryptogrinder

@coutinho thanks for the info… very very helpful for ftc

@Wellenreiter just send you 100ftc as an appreciation… not much but at least smthng

@Cookieboy after rescan I see no errors… so thank you!.. only question is how it got to that state but I guess it’s hard to answer… I think this topic can be mark as solved and if i see that error again I will report again

done https://github.com/FeatherCoin/Feathercoin/pull/254 and thanks… actually I need it asap so I guess I need to use my fork till then

Hi @shadow1117 … you can also check out my pool https://cryptogrinder.com located in Germany, DDoS protection, Nomp based, 0% fee

Hello… having problem to see new transactions/found blocks on Android wallet. Not sure if this is really a problem so maybe someone is able to verify it. My wallet is in sync and I also tried to reset blockchain and sync again but still the same. When I check through http://explorer.feathercoin.com I see different balance for my address. (Maybe it has something to do with new block version 4.0?)

Hello ftc community,

Would it be possible to remove strMiscWarning as here in bitcoin?: https://github.com/bitcoin/bitcoin/issues/6809 I have p2pool which shows it as an error… [I think I don’t have permission to create remote branch for pull request]. In Feathercoin it is in src/util.cpp line 941

based on output it’s fine now… :) so thanks a lot. but not sure what was the problem… ?!

Summary of runtime statistics:

[12:39:24] Started at [2017-09-15 11:48:54]
[12:39:24] Pool: http://cryptogrinder.com:19327
[12:39:24] Run time: 0 hrs 50 mins 29 secs
[12:39:24] Average hash rate: 0.0117 MH/s
[12:39:24] Solved blocks: 0
[12:39:24] Best share difficulty: 28
[12:39:24] Queued work requests: 213
[12:39:24] Share submissions: 2981
[12:39:24] Accepted shares: 2963
[12:39:24] Rejected shares: 18
[12:39:24] Accepted diff1 shares: 33
[12:39:24] Rejected diff1 shares: 0
[12:39:24] Reject ratio: 0.6%
[12:39:24] Hardware errors: 0
[12:39:24] Efficiency (accepted shares * difficulty / 2 KB): 0.05
[12:39:24] Utility (accepted shares / min): 0.02/min
[12:39:24] Work Utility (diff1 shares accepted / min): 0.00/min

[12:39:24] Discarded work due to new blocks: 417
[12:39:24] Stale submissions discarded due to new blocks: 0
[12:39:24] Unable to get work from server occasions: 0
[12:39:24] Work items generated locally: 832
[12:39:24] Submitting work remotely delay occasions: 0
[12:39:24] New blocks detected on network: 47

@Wellenreiter I still can not leave this error behind :[ the reason is that when I see this error in logs my node starts to act differently. I use it for mining. Had actually connected Nomp and also p2pool from your repo to it. So I turned off Nomp to be on a safe side since there is no more active development on it… recreated the node from scratch also rescanned couple times but logs are there again and my node acts strange. I also run other nodes from ltc, vtc in same environment (no problem with them). By strange I mean I got big reject ratio. The height of the block chain seems to be in sync when I checked against explorer. Here is output from nsgminer:

[13:45:35] Started at [2017-09-13 12:53:44]
[13:45:35] Pool: http://46.4.0.101:19327
[13:45:35] Run time: 0 hrs 51 mins 51 secs
[13:45:35] Average hash rate: 0.0112 MH/s
[13:45:35] Solved blocks: 0
[13:45:35] Best share difficulty: 443
[13:45:35] Queued work requests: 177
[13:45:35] Share submissions: 2
[13:45:35] Accepted shares: 2
[13:45:35] Rejected shares: 0
[13:45:35] Accepted diff1 shares: 38
[13:45:35] Rejected diff1 shares: 0
[13:45:35] Reject ratio: 0.0%
[13:45:35] Hardware errors: 0
[13:45:35] Efficiency (accepted shares * difficulty / 2 KB): 0.16
[13:45:35] Utility (accepted shares / min): 0.00/min
[13:45:35] Work Utility (diff1 shares accepted / min): 0.00/min

[13:45:35] Discarded work due to new blocks: 346
[13:45:35] Stale submissions discarded due to new blocks: 0
[13:45:35] Unable to get work from server occasions: 1
[13:45:35] Work items generated locally: 709
[13:45:35] Submitting work remotely delay occasions: 0
[13:45:35] New blocks detected on network: 51

[12:35:41] Started at [2017-09-13 12:21:56]
[12:35:41] Pool: stratum+tcp://cryptogrinder.com:19327
[12:35:41] Run time: 0 hrs 13 mins 45 secs

I’m also running other nodes like ltc, vtc on the same machine.
[12:35:41] Average hash rate: 0.0094 MH/s
[12:35:41] Solved blocks: 0
[12:35:41] Best share difficulty: 21
[12:35:41] Queued work requests: 42
[12:35:41] Share submissions: 560
[12:35:41] Accepted shares: 400
[12:35:41] Rejected shares: 160
[12:35:41] Accepted diff1 shares: 5
[12:35:41] Rejected diff1 shares: 2
[12:35:41] Reject ratio: 28.6%
[12:35:41] Hardware errors: 0
[12:35:41] Efficiency (accepted shares * difficulty / 2 KB): 0.04
[12:35:41] Utility (accepted shares / min): 0.01/min
[12:35:41] Work Utility (diff1 shares accepted / min): 0.00/min

[12:35:41] Discarded work due to new blocks: 16
[12:35:41] Stale submissions discarded due to new blocks: 1
[12:35:41] Unable to get work from server occasions: 32
[12:35:41] Work items generated locally: 195
[12:35:41] Submitting work remotely delay occasions: 0

@Wellenreiter in ‘Peer Monitor’ section I see ‘li341-100.members.linode.com’ couple times… with /Satoshi:0.8.7/… the blocks there are rising so it seems to be in sync… ping is around 300ms… protocol: 60007

I see this in debug.log:

2017-03-30 18:41:59 ERROR: CheckBlockHeader() : block with timestamp before last checkpoint
2017-03-30 18:59:04 ProcessBlock: Preliminary checks
2017-03-30 18:59:04 ERROR: CheckBlockHeader() : block with timestamp before last checkpoint
2017-03-30 18:59:04 ERROR: ProcessBlock() : CheckBlock FAILED

can someone explain what can be wrong?