...
I'll provide a Mac Version very soon (and win 64)
We still expect promised I'll provide a Mac Version very soon (and win 64)
Especially Win64 wallet
What? Mac has been online for a long time now.
Win64 is almost ready.
Topic: [ANN] Zettelkasten - ZTTL, New Algo: BurgerHash V6 🍔, CPU-SOLO-mineable - page 30. (Read 51083 times)
June 16, 2018, 07:34:38 AM
Especially Win64 wallet
What? Mac has been online for a long time now.
Win64 is almost ready.
June 16, 2018, 07:33:52 AM
Something bad is happen.Too many orphan blocks...for some reason my old AMD FX-8370 CPU is finding more blocks as my intel i9 CPU.
Hmm... how many connections does your node have?
If you open and forward port 51339 your node will have more connections which will reduce orphans.
Most people are mining happily.
Have you updated your wallet?
If you want to compare the results of different CPUs you have to let them run for a long time to get meaningful statistics, not just a few hours.
June 16, 2018, 04:10:47 AM
Something bad is happen.Too many orphan blocks...for some reason my old AMD FX-8370 CPU is finding more blocks as my intel i9 CPU.
June 14, 2018, 09:09:12 AM
...
I'll provide a Mac Version very soon (and win 64)
We still expect promised I'll provide a Mac Version very soon (and win 64)
Especially Win64 wallet
June 14, 2018, 08:51:45 AM
This project with the translation of its name seems strange
Lowkey I feel weird...
Lowkey I feel weird...
...like, what did your lowkey translation say?
Zettelkasten = Note Box!
June 14, 2018, 08:48:19 AM
To fix "failed to read block" error-make copy of wallet.dat,delete all files from %appdata% folderand launch wallet,and let it sync.Whed blockchain is up to date,just replace your new wallet.dat file with copy what you made before. 
This error shouldn't happen if you use the most recent version.
June 14, 2018, 08:47:00 AM
I think this is a really nice coin
when would be GPU miner and pool?
when would be GPU miner and pool?
Not in the near future if you the read the OP. The algo will be adjusted constantly every 100000 blocks to prevent those two things from happening.
Yes exactly, those 2 things go hand in hand.
But it's possible that we will skip a 100k period if the "quality" of the next algo-extension sucks, or when it needs more time.
Well, in general this 100k interval (ca 10 weeks time) has been chosen to give me enough time for researching and testing, but you can never be sure about these things.
Algo-extensions are a serious matter.
We have to be careful here.
So take this with a grain of salt.
I already said on discord right after the 100k FORK that I'm probably NOT going to do another algo-extension at block 200k.
But since then some time has passed and now I DO have a decent idea for the next algo-extension (code-named: some sort of "sticky cheese").
This is fun.
Stick around for the sticky cheese, everybody!
June 14, 2018, 08:38:31 AM
Also, let me know if you'd like me to run some full nodes on static IPs for the network.
Sure, full nodes are always welcome.
Just set them up and open the port and I will see them.
If your nodes stay accessible over a long period of time (>2 weeks) I will consider putting them as seed nodes in the next update.
(... and/or remove old ones that aren't available anymore)
I find this project's mining concept interesting. I just want to know how long you'll actually keep up on changing the algo.
That remains to be seen.
"Changing the algo" implies that we adjust the algo arbitrarily, but that's not the case.
We keep adding additional features, extending the algo so that its complexity constantly increases (but in a determined fashion).
I have plenty of ideas for future algo extensions, ...
... so the Burger is going to grow!
BurgerhashV3 (cheese) probably already going to happen at block 200k.
and BurgerhashV4 (salad) at block 300k.
But they could just as well be postponed or not happen at all.
It really depends on testnet results and how long it takes to come up with a meaningful algo-extension.
This will never get rushed.
Stick around and I think it'll be very interesting. I've mined myself a nice stack so far and am continuing to do so just in case.
Yes, I guess it's weird to see a dev that actually sticks around... and doesn't suddenly disappear.
June 14, 2018, 05:48:53 AM
I think this is a really nice coin
when would be GPU miner and pool?
when would be GPU miner and pool?
Not in the near future if you the read the OP. The algo will be adjusted constantly every 100000 blocks to prevent those two things from happening.
June 14, 2018, 12:58:00 AM
I think this is a really nice coin
when would be GPU miner and pool?
when would be GPU miner and pool?
June 13, 2018, 04:30:03 AM
To fix "failed to read block" error-make copy of wallet.dat,delete all files from %appdata% folderand launch wallet,and let it sync.Whed blockchain is up to date,just replace your new wallet.dat file with copy what you made before.
June 13, 2018, 04:23:04 AM
This project with the translation of its name seems strange
Lowkey I feel weird...
Lowkey I feel weird...
June 12, 2018, 12:35:41 PM
Make sure you put the releases on github as well, please.
Good point.
I will do so from now on:
https://github.com/zettel-kasten/zettelkasten/releases/tag/v0.9.16.2
Great, thank you. Also, let me know if you'd like me to run some full nodes on static IPs for the network.
I find this project's mining concept interesting. I just want to know how long you'll actually keep up on changing the algo. Stick around and I think it'll be very interesting. I've mined myself a nice stack so far and am continuing to do so just in case.
June 11, 2018, 09:07:31 AM
wts 1700 zettel, pm offers
I hear there is some escrow-trading going on in the discord channel....
June 11, 2018, 09:06:11 AM
If I open up port 51339 and turn my node into a full node what does that do, is there a benefit ?
Yes, a benefit for the whole network: everyone can sync faster the more full nodes there are.
Also it's a benefit for yourself too if you are mining: a full node will allow you much more connections than just 8 and this will help reduce the amount of orphan blocks you run into.
...and I've found this port is blocked and can't figure out what's blocking it, firewall disabled and it's still blocked.
You need to access your router and manually open up port 51339 and forward it to one machine in your local network that you want to turn into a full node.
June 11, 2018, 08:53:49 AM
forum is online:
https://www.zetteltalk.org
We'll be posting announcements, tutorials and general discussions there and link them here.
https://www.zetteltalk.org
We'll be posting announcements, tutorials and general discussions there and link them here.
June 11, 2018, 05:34:26 AM
ok, new builds (version 0.9.16.2) are ready
Downloads:
Windows: https://zettelkasten.org/zettelkasten-win32.zip
Linux: https://zettelkasten.org/zettelkasten-linux64.tar.gz
Mac: https://zettelkasten.org/zettelkasten-mac.dmg
please test and give feedback.
Downloads:
Windows: https://zettelkasten.org/zettelkasten-win32.zip
Linux: https://zettelkasten.org/zettelkasten-linux64.tar.gz
Mac: https://zettelkasten.org/zettelkasten-mac.dmg
please test and give feedback.
Still can`t read the block error on my main pc.On second one all went smooth
June 10, 2018, 07:20:26 PM
I suppose this project is very interesting and cool!
June 10, 2018, 06:52:44 PM
wts 1700 zettel, pm offers
June 10, 2018, 05:17:11 PM
If I open up port 51339 and turn my node into a full node what does that do, is there a benefit ?
...and I've found this port is blocked and can't figure out what's blocking it, firewall disabled and it's still blocked.
...and I've found this port is blocked and can't figure out what's blocking it, firewall disabled and it's still blocked.
Jump to: