Thanks!
BTW, please PM me your donation address, so I can send you something for all your previous work!
Topic: [ANN] Zettelkasten - ZTTL, New Algo: BurgerHash V6 🍔, CPU-SOLO-mineable - page 27. (Read 51093 times)
July 28, 2018, 11:42:34 AM
And just like that, balych has already fixed it:
Thanks!
BTW, please PM me your donation address, so I can send you something for all your previous work!
Thanks!
BTW, please PM me your donation address, so I can send you something for all your previous work!
July 28, 2018, 09:53:13 AM
I'm announcing a BOUNTY:
750 ZETTEL (plus 250k BURGER) for whoever creates and hosts a blockexplorer for testnet (BURGER):
https://github.com/zettel-kasten/burgerhash
(bounty is one-time for only the first one who creates such a blockexplorer)
who is up for the job?
@Balych?
750 ZETTEL (plus 250k BURGER) for whoever creates and hosts a blockexplorer for testnet (BURGER):
https://github.com/zettel-kasten/burgerhash
(bounty is one-time for only the first one who creates such a blockexplorer)
who is up for the job?
@Balych?
July 28, 2018, 09:21:27 AM
You will have to resync these affected nodes from scratch.
Looks like they got stuck!
Looks like they got stuck!
Newer bitcoin core have 2 useful commands: invalidateblock and reconsiderblock to avoid long process of resync. I hope to see them on in zettel wallet too
Also making weekly backup of blocks and chainstate folders can help to return on right chain quicker.
And BTW, thanks for keeping the awesome blockexplorer alive.
But can you take a look at this bug here:
The total percentage seems to be wrong, in the case I show in the picture it should show 57.13.
Please fix this, thanks in advance.
July 28, 2018, 07:25:33 AM
Hey Dev, so what other improvements should we expect after the next fork? besides GPU mining resistance of course.
block 200k:
1) burgerhash V3 (requires fork at exactly block 200k)
2) improved debugging (does not require fork, will be released around block 200k)
3) network/node monitor (does not require fork, will be released around block 200k)
block 300k:
1) burgerhash V4 (requires fork at exactly block 300k)
2) moving to a higher bitcoin/litecoin codebase (>=0.14) (requires fork at exactly block 300k)
July 28, 2018, 07:19:41 AM
You will have to resync these affected nodes from scratch.
Looks like they got stuck!
Looks like they got stuck!
Newer bitcoin core have 2 useful commands: invalidateblock and reconsiderblock to avoid long process of resync. I hope to see them on in zettel wallet too
Also making weekly backup of blocks and chainstate folders can help to return on right chain quicker.
Thanks, I will look into this.
July 28, 2018, 04:57:59 AM
You will have to resync these affected nodes from scratch.
Looks like they got stuck!
Looks like they got stuck!
Newer bitcoin core have 2 useful commands: invalidateblock and reconsiderblock to avoid long process of resync. I hope to see them on in zettel wallet too
Also making weekly backup of blocks and chainstate folders can help to return on right chain quicker.
July 27, 2018, 01:55:37 PM
Hey Dev, so what other improvements should we expect after the next fork? besides GPU mining resistance of course.
July 27, 2018, 05:22:42 AM
The -rescan command did not help. I had to delete all the files, except wallet.dat (my file zettelkasten.conf is empty) from -datadir and download the blockchain again.
Correct.
a -rescan will not put you back on the correct chain, it will merely fix block integrity.
It's like salvaging a damaged wallet.
Yes, you have to delete blockdata and start resync from genesis.
July 26, 2018, 11:51:23 PM
The -rescan command did not help. I had to delete all the files, except wallet.dat (my file zettelkasten.conf is empty) from -datadir and download the blockchain again.
July 26, 2018, 06:32:43 PM
I also have the same problem on 2 of my 8 computers that are mining since day one. The other 6 are working great. It happened when the difficulty fall down to ~0.8. All 8 of them are on win10 x64.
Any help would be appreciated!
Any help would be appreciated!
You will have to resync these affected nodes from scratch.
Looks like they got stuck!
All of my nodes and the blockexplorer are fine though, so I'm not sure what exactly caused this.
A handful of people reported this to me, but it seems to be isolated.
An investigation has been started, but for now please resync and run as many FULL NODES as possible (open Port 51339, see that you get atleast 50 connections).
The better you are connected to the rest of the network the less you run the risk of creating (or jumping on) a fork and getting stuck there!
Thanks for the quick answer!
Sorry for the novice question, but how do I resync the wallet from scratch under win10?
Edit:
I found the answer with help from the discord channel.
"delete everything except your wallet and conf file if you have it"
That worked perfectly. And the mining can go on! 😊
July 26, 2018, 05:28:07 AM
New burgerhash (test net) version v0.9.17.1
https://github.com/zettel-kasten/burgerhash/releases
Has a few improvements in preparation of the upcoming test.
(New test-release will be released within a week)
If you help with testnet you can sell BURGER to me for ZETTEL, read more about this here:
https://www.zetteltalk.org/viewtopic.php?f=5&t=28
thanks.
https://github.com/zettel-kasten/burgerhash/releases
Has a few improvements in preparation of the upcoming test.
(New test-release will be released within a week)
If you help with testnet you can sell BURGER to me for ZETTEL, read more about this here:
https://www.zetteltalk.org/viewtopic.php?f=5&t=28
thanks.
July 26, 2018, 01:46:23 AM
I also have the same problem on 2 of my 8 computers that are mining since day one. The other 6 are working great. It happened when the difficulty fall down to ~0.8. All 8 of them are on win10 x64.
Any help would be appreciated!
Any help would be appreciated!
You will have to resync these affected nodes from scratch.
Looks like they got stuck!
All of my nodes and the blockexplorer are fine though, so I'm not sure what exactly caused this.
A handful of people reported this to me, but it seems to be isolated.
An investigation has been started, but for now please resync and run as many FULL NODES as possible (open Port 51339, see that you get atleast 50 connections).
The better you are connected to the rest of the network the less you run the risk of creating (or jumping on) a fork and getting stuck there!
July 25, 2018, 11:46:58 PM
http://picua.org/img/2018-07/26/aft6dnmg9r1z2vehgtm7930xq.png
Hello. The wallet stopped synchronizing a few hours ago. What should be done?
Hello. The wallet stopped synchronizing a few hours ago. What should be done?
I also have the same problem on 2 of my 8 computers that are mining since day one. The other 6 are working great. It happened when the difficulty fall down to ~0.8. All 8 of them are on win10 x64.
Any help would be appreciated!
I also have the same problem on 3 of my 9 computers
July 25, 2018, 08:33:53 PM
http://picua.org/img/2018-07/26/aft6dnmg9r1z2vehgtm7930xq.png
Hello. The wallet stopped synchronizing a few hours ago. What should be done?
Hello. The wallet stopped synchronizing a few hours ago. What should be done?
I also have the same problem on 2 of my 8 computers that are mining since day one. The other 6 are working great. It happened when the difficulty fall down to ~0.8. All 8 of them are on win10 x64.
Any help would be appreciated!
July 25, 2018, 07:53:18 PM
http://picua.org/img/2018-07/26/aft6dnmg9r1z2vehgtm7930xq.png
Hello. The wallet stopped synchronizing a few hours ago. What should be done?
Hello. The wallet stopped synchronizing a few hours ago. What should be done?
July 21, 2018, 09:34:48 PM
On the right burgerhash testnet now && syncd up before starting the miner, testing it twice now with another build set @ gen=1 before fully syncd. Not sure if it mines from the top block from the start of block 0 or it forked off (looked like 18+ blocks mined in the dblog) @ block 50,000+ during sync && didn't want to risk it (even with only testnet, rebuilt the database with gen=0 on both).
// miss the solo CPU mining days a bit (keep it CPU = fair chance for all), though it would be fun && love the algo naming
## should have a few burgers && will look into signing up on the zetteltalk forum
// miss the solo CPU mining days a bit (keep it CPU = fair chance for all), though it would be fun && love the algo naming
## should have a few burgers && will look into signing up on the zetteltalk forum
July 21, 2018, 04:00:58 PM
Yeah sorry I am sure that it was my Linux build (shows in dblog) that forked it (gen=1 set all 8 cores), couldn't get the Linux build to run right of the bat && then forgot about it well waiting for it to sync ;( Then I thought about testing it on Windows, but downloaded the wrong one && was trying to get a connections with testnet on Zettelkasten (not 
Burger) 
Burger) It's ok.
We were taught a lesson that we shouldn't let the hash rate of testnet drop too much.
I am selling 1 ZETTEL for 1000 BURGER. (and you sound like you ate a lot of BURGERS)
Read here:
https://www.zetteltalk.org/viewtopic.php?f=5&t=28
July 21, 2018, 03:58:27 PM
...kind of wish you had a block explorer for testnet
that's exactly what I'm working on.
When my custom explorer is ready I will of course also use it for testnet.
My explorers will be accessible over the official website (coming soon)
&& might be able to build one if you would like?
yes, I would love that.
I am a big fan of redundancy, because then you don't need to rely on a single source.
More explorers please!
July 21, 2018, 03:33:57 PM
looks like the testnet has previously already dropped so much in hashrate that we have effectively forked a few blocks ago.
So there are now 2 testnet chains, just a few 100 blocks apart, starting at around #73500
So if you want to help with testnet, please check that you are on the right chain.
Visit discord for more info.
Thanks
EDIT: ok we fixed it and got most of the testnet network under our control again.
If you are one of the volunteers that had a testnet BURGER wallet running, please check whether you are on the correct testnet chain by typing:
then you are good.
If you are NOT good, then please delete all your testnet data and resync.
So there are now 2 testnet chains, just a few 100 blocks apart, starting at around #73500
So if you want to help with testnet, please check that you are on the right chain.
Visit discord for more info.
Thanks
EDIT: ok we fixed it and got most of the testnet network under our control again.
If you are one of the volunteers that had a testnet BURGER wallet running, please check whether you are on the correct testnet chain by typing:
Code:
getblockhash 73805
ed848f4c6cb6c6c2374aa827b32ceabfca853838b7aca8c97fe44ca9425793be
then you are good.
If you are NOT good, then please delete all your testnet data and resync.
Yeah sorry I am sure that it was my Linux build (shows in dblog) that forked it (gen=1 set all 8 cores), couldn't get the Linux build to run right of the bat && then forgot about it well waiting for it to sync ;( Then I thought about testing it on Windows, but downloaded the wrong one && was trying to get a connections with testnet on Zettelkasten (not
Burger) // building Burger sync now, do kind of wish you had a block explorer for testnet && might be able to build one if you would like?
July 21, 2018, 11:59:59 AM
Do you have any future develop plan? Right now，I can only see that the new algorithm, there is not any new feature, just like a experimental project.
Yes, knowledge gathering and management.
First in a centralized and then in a decentralized fashion.
But that is a pretty bold goal, so that I am not going to drown you in some fancy roadmaps yet.
You'll soon understand with the release of a first "tool".
Meanwhile we have some BURGERS to eat.
Jump to: