Something still not right... and may be on my end (I'm not strong in the ways of the MAC).

Anyhow, the report is different, so may shed more light:

Process:               ZettelKasten-Qt [356]
Path:                  /Volumes/VOLUME/ZettelKasten-Qt.app/Contents/MacOS/ZettelKasten-Qt
Identifier:            org.zettelkasten.ZettelKasten-Qt
Version:               $VERSION ($VERSION)
Code Type:             X86-64 (Native)
Parent Process:         [1]
Responsible:           ZettelKasten-Qt [356]
User ID:               501

Date/Time:             2021-01-10 15:18:17.575 -0500
OS Version:            Mac OS X 10.10.5 (14F2511)
Report Version:        11
Anonymous UUID:        F2410621-1414-EB30-4A2D-29AF43C1A0E7


Time Awake Since Boot: 390 seconds

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000

Dyld Error Message:
  Symbol not found: _clock_gettime
  Referenced from: /Volumes/VOLUME/ZettelKasten-Qt.app/Contents/MacOS/../Frameworks/libdb_cxx-4.8.dylib (which was built for Mac OS X 10.13)
  Expected in: /usr/lib/libSystem.B.dylib

*** Quick update - testing the same image on a (shhh) hackintosh running Mojave works fine.  Nice update to the wallet interface!

Yosemite on an old Core2 iMac didn't like this new version.

Snippet from report:

Process:               ZettelKasten-Qt [622]
Path:                  /Volumes/VOLUME/ZettelKasten-Qt.app/Contents/MacOS/ZettelKasten-Qt
Identifier:            org.zettelkasten.ZettelKasten-Qt
Version:               
Code Type:             X86-64 (Native)
Parent Process:        [1]
Responsible:           ZettelKasten-Qt [622]
User ID:               501

Date/Time:             2021-01-08 12:51:59.797 -0500
OS Version:            Mac OS X 10.10.5 (14F2511)
Report Version:        11
Anonymous UUID:        F2410621-1414-EB30-4A2D-29AF43C1A0E7


Time Awake Since Boot: 870 seconds

Crashed Thread:        0

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000002, 0x0000000000000000

Application Specific Information:
dyld: launch, loading dependent libraries

Dyld Error Message:
  Library not loaded: /usr/local/Cellar/openssl@1.0/1.0.2t/lib/libcrypto.1.0.0.dylib
  Referenced from: /Volumes/:Users:zettelkastendev:Desktop:QQQ:build-zettelkasten-qt-Desktop_Qt_5_9_9_clang_64bit-Release:ZettelKasten-Qt/ZettelKasten-Qt.app/Contents/Frameworks/libssl.1.0.0.dylib
  Reason: image not found

Thank you sir!

Pot replaced (with 10Kohm .125W) and the 2Pac is back!

--------------------------------------------------------------------------------
 0: GSH 10030331: BM1387:02+ 500.00MHz T:500 P:500 (75:38)  |  100% WU:^94% | 126.6G / 106.8Gh/s WU:1491.9/m
 1: GSD 10020111: BM1384:02  250.00MHz T:250 P:250 (78:156) |  100% WU:100% | 40.30G / 27.57Gh/s WU: 385.1/m
--------------------------------------------------------------------------------

So after just over a year of running happily at 250Mhz in mineral oil, I decided to pull my 2pac out and give it a clean to try air cooling again.

I gave it a quick rinse in 99% Isopropyl Alcohol and while drying, I noticed a portion of the white insolating material from the voltage adjustment pot had come out.  Not sure what this material is made of... is it possible the mineral oil degraded it?

My main question is, what is the value of this potentiometer?

Given it's currently running at 200Mhz along side it's new sibling (a Newpac at 400Mhz), should I just be happy and leave well-enough alone?

Donation sent.

Your efforts are appreciated!

I started mining this coin about 14 hours ago, using a Rock64 (had to use a modified 'atomic_pointer.h to compile for the ARM processor) and have mined 21 blocks so far.

I just want to be sure I'm on the correct chain... block number and nethash matches the explorer listed in original post:

    "blocks" : 275437,
    "currentblocksize" : 1000,
    "currentblocktx" : 0,
    "difficulty" : 0.00024414,
    "errors" : "",
    "generate" : true,
    "genproclimit" : 4,
    "hashespersec" : 4093,
    "networkhashps" : 12837,
    "pooledtx" : 0,
    "testnet" : false

Networkhaskps seems rather low... and looks to be continually dropping.

Also, does a "miningprivkey= " entry in the .conf file work the same as other bitcoin derived alts (to mine to one address)?

Edit: should have included version - is this correct?
    "version" : 80705,
    "protocolversion" : 70002,
    "walletversion" : 60000,

---------------------------------------------------------------
I'm having issues syncing as well with the Windows 2.1.2i daemon.  It almost finished, but now just spams "Wrong block version":

WARNING Failed to validate block fbfa4391392721639d1d7e94998b9044e22a528f1ce1e807c5b8001815bb3ee8: Wrong block version
2018-Oct-31 14:40:28.499226 INFO    [94.15.241.102:58252 INC] Sync data returned unknown top block: 524419 -> 563499 [39080 blocks (54 days) behind]

Anyone else seeing this?[/quote]

Hey RizSphere and Beachboy20,

sorry to hear you have experienced issues. one thing you could do is to delete the old blockchain files and copy the files from this link to that directory.
/2zifc3a]https://[Suspicious link removed]/2zifc3a
---------------------------------------------------------------

I'm trying to import my original key into the Windows GUI wallet but getting the error "Incorrect tracking key size".


I deleted everything from the DB directory and it's currently re-syncing... do I need to wait until it's finished?


I found an old wallet backup and using the Windows 2.1.2i GUI wallet, I was able to restore.  Seems to be all good now, above query can be ignored.

Moral of the story... always backup your wallet!

Seems to be good... at least on an old iMac (2.66Ghz core 2 duo).

Only getting 46Kh/s... but ya, working.

I'm having issues syncing as well with the Windows 2.1.2i daemon.  It almost finished, but now just spams "Wrong block version":

WARNING Failed to validate block fbfa4391392721639d1d7e94998b9044e22a528f1ce1e807c5b8001815bb3ee8: Wrong block version
2018-Oct-31 14:40:28.499226 INFO    [94.15.241.102:58252 INC] Sync data returned unknown top block: 524419 -> 563499 [39080 blocks (54 days) behind]

Anyone else seeing this?

Did you run "dumpprivkey <zettelkastenaddress>" to get your private key? 

Tried it on the 3B+ under Ubuntu 18.04 64bit... didn't seem to like it:

@RaspPi:~/zettel$ ./zettelkastend
-bash: ./zettelkastend: No such file or directory

I'm assuming this daemon is 32bit, built under Raspian and it's not happy with the 64bit Ubuntu environment.

Update: It's much happier using Rasbian (Stretch-Lite):

@raspi:~/zettel $ ./zettelkastend getinfo
{
    "version" : 91801,
    "protocolversion" : 70022,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 295210,
……....

Though the hashrate using 32bit leaves a lot to be desired:

 "hashespersec" : 23597,

But this is really just for a low wattage Full Node, correct?

Well crap... that pic brought back a flood of memories.  I worked in a mine for 20 years... luckily, an open pit mine... not a hell hole these poor sods toiled in.

God or no God, they had reason to pray.

Wait a sec... I left the mine to pursue a career in computers... and I find myself now compute mining.  What the...

Doh!  ...right, the new hash doesn't take until block 100K.

Please pardon my cerebral flatulence.

Just updated my xeon servers running Ubuntu 16.04 and both are getting the same hashrate as before:

Dual e5620 - "hashespersec" : 231110,
Dual x5650 - "hashespersec" : 392413,

Both showing new version:

    "version" : 91601,
    "protocolversion" : 70020,

I'm hoping it doesn't matter, but I left the hidden directory in place with the old .conf file, etc.

Will the source be available at the same time as the binaries?

I'm currently building Burgerhash from source on the Rock64 (ARMv8)... so far, so good!

Update - compile finished (used same modifications for ARMv8 as mainnet).

Hashrate dropped from 200K on ZETTEL to 170K on Burger using 4 cores... is a 15% drop what others are seeing on other platforms?

From what I understand, ZETTEL is GPU and pool resistant... both _could_ be implemented.  At this point, I believe the consensus is to remain CPU only for now.  The Dev would be able to give a much clearer picture, but I think he's heads-down, working on the modified algo mentioned a few posts earlier.

Thank you for the visual... it's impressive and helps understand the algo!

I'm assuming the source files will be updated along with the wallet binaries for the 100K change, correct?

I've forwarded port 51339 on one system and did an "addnode" from a second system to that first system.  First now has 27 connections and second remains at 8.

Launch (mining) began approx. March 27, 2018 10pm

Total Coins: 30 Million ZETTEL
Initial Blockreward: 10 ZETTEL

Info taken from first page, post #1 and #17.

And yes, while getting to be more of a long-shot, still mine-able on a old dual core2 cpu... if you have 200-300Kh/s to throw at it, you should be good for a block a day.  

Coins currently mined = 584860.61565 (so still way over 29 Million to go).

I'm hoping to try solo mining, just for fun.  I've got a Windows box setup ok, but for Linux, I do not see the "miner" software on GitHub.  Is it included in one of the Ubuntu binaries listed there?

Thanks!