[ANN] Zettelkasten - ZTTL, New Algo: BurgerHash V6 🍔, CPU-SOLO-mineable

[zettelkasten]

Announcement:

So this is definitely going to happen at block 200k:

Burgerhash V3 , StickyPuffyCheese will be added to Burgerhash V2 so that we will have

SpreadDoubleKetchupPrimeGradeABeefStickyPuffyCheese >= block 200k

Schematics of Burgerhash V3 coming soon. (in a nutshell:we will be sinus transforming the input-sizes of the two Keccak functions which will result in more work for these two Keccak functions)

[1714465628]

1714465628

[onionpealer]

I'm having a problem with wallet 0.9.16.2.
I installed it on my Windows 7 x64 machine, run it then closed it and copied my 'wallet.dat' over the default wallet. ...

where did your initial wallet.dat come from?

I just tested importing wallet.dat from linux to linux, linux to win, win to win and win to linux and it all works without problem.

Maybe your wallet.dat is corrupted.
Did you have any recent crashes?

What size does your wallet.dat have?

I had wallet 0.9.16.1 running on my Windows 10 x64 PC and decided to run a backup on my Windows 7 x64 PC. So I installed wallet 0.9.16.2 on the Win7 PC, ran it to create folders then shut it down, but did not let it fully sync before copying wallet from the Win10 PC to the Win7 PC - problems then arose.
The Win10 wallet was about 88K bytes in size.

I have now got it working, this is how.
I deleted everything on the Win7 PC and reinstalled wallet 0.9.16.2 and let it fully sync on the Win7 PC, then imported key from Win10 PC, but not all the Zettel showed up in wallet, so I sent all the Zettel in the Win10 PC to myself and the full balance is now showing in the Win7 PC.

But of a fuss but got there in the end.
Thanks for taking the time to help.

[katastroficar]

I had wallet 0.9.16.1 running on my Windows 10 x64 PC and decided to run a backup on my Windows 7 x64 PC. So I installed wallet 0.9.16.2 on the Win7 PC, ran it to create folders then shut it down, but did not let it fully sync before copying wallet from the Win10 PC to the Win7 PC - problems then arose.
The Win10 wallet was about 88K bytes in size.

I have now got it working, this is how.
I deleted everything on the Win7 PC and reinstalled wallet 0.9.16.2 and let it fully sync on the Win7 PC, then imported key from Win10 PC, but not all the Zettel showed up in wallet, so I sent all the Zettel in the Win10 PC to myself and the full balance is now showing in the Win7 PC.

But of a fuss but got there in the end.
Thanks for taking the time to help.

Set it to mine all coins in same address (in zettelkasten.conf file), one that you have private keys saved.

[cyberspacemonkey]

Is the coin dead yet?  . Not a lot going on it seems other than upgrades on the algo, I wonder if there will be a website soon.

[zettelkasten]

Linux Qt Wallet crash that happened when starting/stopping miner in the mining-tab has been fixed:

https://github.com/zettel-kasten/zettelkasten/commit/1e13de2e7bc603e39329c30f9bfe4876e2039abc

I have opened an issue to explore why this specifically only happens on linux and can be solved by removing a certain piece of code:

https://github.com/zettel-kasten/zettelkasten/issues/8

All other versions (win and mac and linux daemon are unaffected by this)

New linux wallet binary: https://zettelkasten.org/zettelkasten-linux64.tar.gz
(same version just new build)

[Srobzrobert]

What is the total  coin supply?

[zettelkasten]

What is the total  coin supply?

30 Million ZETTEL

[cyberspacemonkey]

What is the total  coin supply?

30 Million ZETTEL

It's as easy as checking the block explorer or your wallet's console with the right command. Glad to see the dev is still around and hasn't bailed yet btw.

[bobon1]

when the ZETTEL is added to the exchange?

[onionpealer]

when the ZETTEL is added to the exchange?

Good question, I have a wallet full of Zettel burning a hole in my pocket. It's like coming back from holiday with a pocket full of funny money and no where to spend it

[magonrus]

Win64 is almost ready. 

Troubles?
We still need it...

[mihachok]

Xeon e5-2650  16 threads     Ubuntu 16.04   -   250 kH/s
                                       Windows 10 x64  - 120 kH/s
why is this happening? 

[chipah]

Xeon e5-2650  16 threads     Ubuntu 16.04   -   250 kH/s
                                       Windows 10 x64  - 120 kH/s
why is this happening? 

You could use WSL and enjoy your Ubuntu hashrate on Win10:
https://docs.microsoft.com/en-us/windows/wsl/install-win10

[grendel25]

Announcement:

So this is definitely going to happen at block 200k:

Burgerhash V3 , StickyPuffyCheese will be added to Burgerhash V2 so that we will have

SpreadDoubleKetchupPrimeGradeABeefStickyPuffyCheese >= block 200k

Schematics of Burgerhash V3 coming soon. (in a nutshell:we will be sinus transforming the input-sizes of the two Keccak functions which will result in more work for these two Keccak functions)

There were a few words that I've seen before in what was just described:  Keccak, Schematics, transforming, nutshell, functions, input-sizes...  This all sounds very interesting but I do not fully understand why it is important to do what you are doing and I would also like to understand the technical side of why it works as you intend it to work.

Is the main point here to contribute towards the aim of a CPU-only algorithm?  I think this is pretty cool and I also want to understand the architecture of 'why' this would work to be better for a CPU.

Is there something that explains the theory behind why the Burgerhash algorithm is significantly more efficient on a CPU than any other computing platform?  I guess I am looking for a comparison/contrast between burger hash and other block diagram/flow chart illustrations of other algorithms.  Not asking for anything new... just maybe a link to other algorithms.  The burgerhash is pretty well illustrated here by the author/developer.  I'm just looking for the connecting info to understand the comparisons better.

Oh... and a for example:  so like there are comparisons of what it would take to do certain things on something like an FPGA or ASIC platform.  I think I read somewhere that to do Xevan on an FPGA one would have to link up two FGPA cards (something like $7500 worth of equipment) just to get a working FPGA product on Xevan which is pretty cost prohibitive for most miners)... This is sort of why I am asking... to get the bigger picture of hardware results and requirements to do the same thing between platforms.

[onionpealer]

Quick question about the wallet updates, how will the wallet let us know when there is an update available - will it flash in big red letter "Update Now!"

[katastroficar]

Quick question about the wallet updates, how will the wallet let us know when there is an update available - will it flash in big red letter "Update Now!"

20k block before HF there will be notification like this in your wallet
https://cdn.discordapp.com/attachments/461012369821138945/463145509951897610/burgerhash-test1-scr.jpg
and if you don't update wallet, after HF you will be getting this
https://cdn.discordapp.com/attachments/461012369821138945/463145512615280640/warning_wrong_fork.png

[onionpealer]

Quick question about the wallet updates, how will the wallet let us know when there is an update available - will it flash in big red letter "Update Now!"

20k block before HF there will be notification like this in your wallet

and if you don't update wallet, after HF you will be getting this

Ah, I like it, clear and unequivocal. I'll keep a look out for it.

[zettelkasten]

Quick question about the wallet updates, how will the wallet let us know when there is an update available - will it flash in big red letter "Update Now!"

20k block before HF there will be notification like this in your wallet

and if you don't update wallet, after HF you will be getting this

Ah, I like it, clear and unequivocal. I'll keep a look out for it.

Exactly. This will be the format of...

---> Warning ---> Update ---> Fork
---> Warning ---> Update ---> Fork
---> Warning ---> Update ---> Fork
...

that we will keep on doing basically forever.
In a predetermined fashion, exactly on every 100k-th block, and always with added complexity for the hash algo (plus other functionality that might require fork)

[zettelkasten]

Is the main point here to contribute towards the aim of a CPU-only algorithm?  I think this is pretty cool and I also want to understand the architecture of 'why' this would work to be better for a CPU.

Yes, we want to stay CPU-ONLY.

But I never claimed that any of the updates is "better" for a CPU.
The main goal behind BurgerHash is to keep on adding to the complexity of the hash algo so that any GPU-miners that are created will be obsolete after the next update.

The basic premise is that coding for GPUs is magnitudes for complex than coding for CPUs.

Is there something that explains the theory behind why the Burgerhash algorithm is significantly more efficient on a CPU than any other computing platform?

Again, I never claimed that, I never used these words. Please only read what I write, not what others say about BurgerHash. (except of course when they have valid criticisms, which are always welcome)
Also, I do not think that such an algorithm even exists (which is provably more efficient on a CPU than on one of the more advanced GPUs. I know that some claims have been made, but I doubt those functions are valid for POW-hashing)

With BurgerHash I try to add various mathematical angles to the hash algo which will force GPU-miners to do more and more extra work to keep up.

So let me give you one example of my thought-process behind the StickyPuffyCheese-Upgrade:

I know for a fact that with changing size of the input-data you need to change a whole lot more in CUDA then you need when just using the KECCAK function of a library like say sph on CPU.
Padding sizes and what not needs to be specifically adjusted when using CUDA which is not necessary for mere C++ on CPU.
A well-versed GPU-dev might do exactly that, and he might be able to mine ZETTEL on GPU for a few weeks, until I throw some more extra shit his way.

That's the basic idea.

BTW: as POW-hash-research continues I might come up with advanced mechanisms that also decrease the amount of hash-benefit a GPU-miner might get compared to CPU. But this remains to be seen.

[zettelkasten]

when the ZETTEL is added to the exchange?

Good question, I have a wallet full of Zettel burning a hole in my pocket. It's like coming back from holiday with a pocket full of funny money and no where to spend it

We are discussing potential good (and bad) exchanges in the zetteltalk forum:

https://www.zetteltalk.org/viewforum.php?f=4

If you know about an interesting exchange, please add its details in the forum. Thanks!

Also, I started saving a bit of BTC and LTC to have some negotiation capital ready for the exchanges.
It's not much (yet) but I'll just keep on saving, and if some of you guys want to donate towards that cause it will speed up the process for sure.
Read more about it here:

https://www.zetteltalk.org/viewtopic.php?f=4&t=23

Thanks