@double-u made such a great suggestion!
Don't discord, blurt!
Is the raspberry pie support thread. You just put your problem in here and throw some screenshots in here, possibly links to logs at github gist
And my friend you shall be supported!
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!
Awesome.... I posted link to this Topic in The Blurt Channel on Noise.Cash .... https://noise.cash/n/blurt
Excellent proposal for people to share their experiences with the community, especially to expand the use of blurt to homes or offices.
People can make tutorials, suggestions, at this point people should be informed and given access to information so that they can undertake their projects.
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.
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.
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"
If you've set up a witness, tell me and it shall be voted!
PI TO THE RESCUE!
Excellent, so everything will be in one place. Some people don't use discord.
Excilent your post wow.
@double-u sir is a very good minded person who always wants to help people so that people can do a lot of good things from here. I have known him for about two months now. I like his work technique so I help everyone but to have a fun in it so that people's talents can be highlighted. He competes in a quiz one day a week.Happy with the vote.
So nice
I also am crossing fingers waiting for this time to come (The Don't discord) very soon, by now many thanks to you boss @jacobgadikian and the rest of the sleepless team.
I'm totally in support of this, its a good development, every problems should be tackled right here while others can also learn and fix their problems themself
Yes.
WLS was synced because they needed more witnesses, and I wrote the code for WLS to be able to run on Pi and 1 pi can be a witness on multiple chains.
Also, WLS is no longer being synced. The reason I stopped syncing it isn't a sudden hatred of WLS or a reaction to comments about it-- well, except for one comment.
One of the Pi pilots mentioned that the WLS chain was filling up their microsd, and we can't be having that.