Why does the Pi with the Cryptopie image sync with the Wahleshares chain?
As we can see here block 16180000 for example, it is the active chain.
RE: Pi support thread
You are viewing a single comment's thread from:
Pi support thread
Authors get paid when people like you upvote their post.
If you enjoyed what you read here, create your account today and start earning FREE BLURT!
If you enjoyed what you read here, create your account today and start earning FREE BLURT!
Strange . The Pi of @dotwin1981 is syncing with blurt .Did u used Wrong image ? Or @megadrive or @jacobgadikian
used the wrong container when they made the image .
Ok forgett my last comment i just saw in the kneipe thread that dotwins pi is also syncing whaleshare
Jacob hat aktuell einen Post in dem wir Fragen stellen können. Dort hab ich schon nachgefragt, warum whaleshares gesynct wird. Mal sehen was Jacob Antwortet, muss ja einen Sinn haben.
Da bin ich sehr gespannt auf die Antwort.
Derweilen schaut (docker logs wls -f) so aus:
Und dann bricht es ab mit: "error from daemon in stream: Error grabbing logs: unexpected EOF"
This resolved itself, correct?
Not quite, I have now stopped the WLS chain completely.
Jacob, can you please explain why the whaleshares chain is synced? I and some others are puzzled about this.
Cryptopie, without WLS:
https://gitlab.com/blurt/blurt/-/jobs/988278263
https://gitlab.com/blurt/blurt/-/pipelines/247214795
In 10 minutes there will be a new image file for you.
Think something went wrong, there is only a new megadrive image megadrive2021-01-26-22:48:56.img.xz but none from cryptopie.
Hard to explain, I myself am not sure.
Originally, it was because I know that WLS needs more witnesses. But I thought that I took it out. Checking the code now.
OK, just checked, here is the relevant code:
https://gitlab.com/-/ide/project/blurt/blurt/edit/dev/-/contrib/cryptopie/Dockerfile
The last bit at the end, that is where it starts WLS, so the answer to your question is:
"I only thought I'd taken it out"