Dissem
commented
9 years ago This looks suspicious though:
08-23 10:05:22.119 10254-10976/ch.dissem.apps.abit W/c*.d*.b*.n*.Connection﹕ Insufficient proof of work: 000000d5984ec733 required, 9c6b0d198adcecbb achieved.
08-23 10:05:57.175 10254-10976/ch.dissem.apps.abit W/c*.d*.b*.n*.Connection﹕ Insufficient proof of work: 000000d59b06f624 required, 9c6b0d198adcecbb achieved.
08-23 10:05:59.324 10254-10487/ch.dissem.apps.abit W/c*.d*.b*.n*.Connection﹕ Insufficient proof of work: 000000d59b06f624 required, 9c6b0d198adcecbb achieved.
08-23 10:06:09.496 10254-10487/ch.dissem.apps.abit W/c*.d*.b*.n*.Connection﹕ Insufficient proof of work: 000000d59b06f624 required, 9c6b0d198adcecbb achieved.
08-23 10:06:17.509 10254-10487/ch.dissem.apps.abit W/c*.d*.b*.n*.Connection﹕ Insufficient proof of work: 000000d59b06f624 required, 9c6b0d198adcecbb achieved.
08-23 10:06:45.447 10254-10487/ch.dissem.apps.abit W/c*.d*.b*.n*.Connection﹕ Insufficient proof of work: 000000d59dbf36cf required, 9c6b0d198adcecbb achieved.
08-23 10:07:15.834 10254-10980/ch.dissem.apps.abit W/c*.d*.b*.n*.Connection﹕ Insufficient proof of work: 000000d5a0778935 required, 9c6b0d198adcecbb achieved.
08-23 10:07:18.374 10254-10487/ch.dissem.apps.abit W/c*.d*.b*.n*.Connection﹕ Insufficient proof of work: 000000d5a0778935 required, 9c6b0d198adcecbb achieved.Different requirements, but always 9c6b0d198adcecbb achieved?
Some message seem to have insufficient proof of work, but as I only connect to a local client, this shouldn't happen. It might be related to issue 1 and probably has something to do with a parsing problem that only crops up sparsely.