Greetings, dear Blurtians,
Today, as the 9th Witness, I would like to address concerns that have arisen among some Blurtians. I've noticed some questions in comments and posts from those who might not be on Blurt's Official Discord channel: https://discord.blurt.world/
Over the past few days, you may have experienced disruptions and intermittent outages on the Blurt.blog, BlurtWallet and BlurtLatam, some lasting several hours.
These interruptions stem from a problem with Blurt's primary RPC nodes, which have encountered significant failures. With the exception of BeBlurt which was relatively unaffected due to its utilization of a separate RPC node, except for image uploads, which were reliant on the main nodes (until this morning's modification by @saboin).
The precise source of the issue is currently under investigation by @saboin. Preliminary findings suggest that an increased load of resource-intensive requests has led to errors in the nodes, necessitating blockchain replays for their recovery – a process that takes time.
To support @saboin and the entire Blurt community during this challenging period and to minimize interruption times, I've provided a temporary RPC node for more than 12 hours now. This node functions as a relay (and also serves as a configuration test) while modifications are made to the three main RPC nodes.
In light of these events, it would be beneficial, especially during periods of blockchain growth, for others to consider adding new RPC nodes to the network. This collective effort can enhance the stability and performance of the Blurt blockchain, particularly if they operate their own frontends. Currently, the network relies only on the official three RPC nodes and BeBlurt's node.
I hope this clarifies your concerns. If you have further questions, please don't hesitate to ask in the comments of this post.
Now, let's delve into a brief explanation of key technical terms:
Full Node RPC and Witness Node:
A Full Node RPC (Remote Procedure Call) serves as a communication interface between users' actions and the Blurt blockchain. It allows users to interact with the blockchain, including submitting transactions and retrieving information. In contrast, a Witness Node plays a vital role in producing and confirming blocks. While a Full Node RPC focuses on interaction, a Witness Node participates in the blockchain's consensus mechanism. The full node RPC requires far more resources than the Witness node for its execution.Replay of the Blockchain:
A replay of the blockchain involves the process of reconstructing the entire history of the blockchain. This action is performed when there's a need to ensure data consistency, address issues, or recover from interruptions. In the context of the recent disruptions, the blockchain replays were required to restart the main RPC nodes and restore normal operations.
Thank you for your understanding and support during these challenges.
Also, kindly extend your support to @saboin by casting your vote for his witness here https://blurtwallet.com/~witnesses?highlight=saboin or there https://beblurt.com/@saboin/witness
Original background photo of this post by Nijwam Swargiary on Unsplash
Thanks for posting to let us know why things weren't working, and about the coming challenges getting things running properly.
This brings up a point. We like to think of our activities on the blockchain as permanent, always available to us, forever carved in digital stone. And that our wallets are just as sound. We like to imagine that no matter what happens, our posts, comments, and other blockchain actions will always be there, and our funds will always be available. But then something like this happens, and we hear that without the heroic efforts of 1 or 2 people, the most used frontends were down and the wallets were unavailable. It becomes clear that without a few specific people keeping it running, it's NOT permanent, and NOT always available to us. It's not some magical digital machine that has been set in motion, and will always just keep running, no matter what happens. It takes people who can respond to unforeseen emergencies, just like this post describes. We are kind of counting on those people in a big way.
I find that extremely well said 👍
Thanks for making this post!
I have pinned it on
blurt.blog.Thank you sincerely for all that you do for Blurt and its community, respect 👍
I had issues. I wondered if I was alone.
How intensive is it to run an RPC nose? It's it straightforward or do you need to be a developer?
You don't need to be a developer. If you can follow instructions and type some commands in a Linux terminal, you can install and operate a node.
@thegolemseye, you can read this answer I provided in another comment for a better understanding of an RPC node and the knowledge required, even though I admit to being more demanding than @saboin 🤣
Lol, I will look. I dont expect I could do it but if I could I would 👍
Elaborate more on this.
Does this include removing permanently previous text in any accounts? And I do mean permanently. Like for example, a better hidden piece of information than what @regent is right now. It was once an account here and now the explorers doesn't show any transactions for regent. Ever.
What type of history can be erased? Literally everything?
It's impossible to alter the history of the blockchain without breaking it.
When you replay the chain, what it does is go through the blocks and rebuilds the local database for the node.
I think you're conflating it with @blurt.regent, which was an account that had virtual Blurt Power equal to half of the initial supply and decayed to 0 over two years. That account could only vote for witnesses and proposal and it was intended to be a mechanism to be used in case of a sybil attack on the chain. During the last hardfork, the governance voting mechanism was changed in a way that makes a sybil attack almost impossible.
NOTHING can be erased or altered. That's the whole point of a cryptographic block chain.
That is what I had always held, that it was impossible. So when he said that, it kinda threw me off. Thank you for the clarification.
It's worth asking. And let's not forget, that even if it's impossible to alter the history of the blockchain, it may be possible to make it in accessible. For example, this post talks about the heroic efforts of 1 or 2 people to get the chain and wallets working again after and unforeseen problem. Could that happen again? What if the necessary actions aren't taken, does the chain stay offline? I am personally not technical enough to run my own frontend, or work with copies of blockchains, or the like, so if these frontend websites stop working, and if the wallet stops working, I'm a sitting duck. I rely on a few humans, all-but anonymous and situated around the planet, keeping things up and running.
it is obvious that you are ignorant, you want to make a drama out of everything, why don't we talk about the false witnesses that ctime has, or why don't we talk about how useless fervi is. ? or how your sponsors like mmk dog without balls does not contribute anything to the platform.
Asking questions is not making drama. I'm not interested in discussing the uselessness of a person rather to question the things as they are and search for solutions of the contents. Ignorant? Yes, who isn't "ignorant" of something? It's why er ask questions. But you want to interpret that as making drama? Lol, please don't make me laugh with your gaslight.
“We are all very ignorant. What happens is that not all of us are ignorant of the same things». Albert Einstein :)
...it's great fun identifying dimwits through the use of their own linguistics, innit?
(they are too dumb to realize that it's like fingerprint, obviously)
(they think we don't know, bless)
I know to much ,. stood at the edge of the hive chain to see it being devoured by the blocktrader true a account created under his name .
https://wallet.hive.blog/@sepa666/transfers
https://wallet.hive.blog/@lass3/transfers
Not that anyone cares ,. just i know now ,. your keys , your property , is utter bullshit .
Where the threats done on blurt to freeze wallets and accounts and ban them from posting told me already ,. there are back doors build in the chains .
Back doors that contradict any claim made by the foundation holders about the integrity of the chain .
Decentralization ,. with a backdoor ,.. lol , that's like starting up with a lie . And undermines all trust just for being kept a secret .
;-)
Thank you for this update. Communications on these issues are much appreciated.
You're welcome :)
Oh, thank you @nalexadre for the explanation. I thought that it was my internet connection that was not functioning well.
Anyway, thanks to you and to @saboin for working on this problem. Hope this will be resolved permanently. 🙏
To show appreciation for the hardwork done, I have voted already for @saboin, @blurtlatam and you.♥️
Hi, thanks for the mention, but we are not associated in any way with the fronted called just like our account, previously we had one running on blurtlatam.com, however the source code was stolen, plagiarized and I don't know or give credit to the initial developers. Therefore we are not associated in any way with the frontend mentioned.
Dude, are you F in the head?
The source code that runs what, was stolen?
Also who is running blurtlatam.intinte.org? Cannot be trusted then?
freakeao shut down blurtlatam.com because he didn't like the "conspiracy posts" on trending. @fervi, the man who revealed plans to freeze my, lucylin and several other accounts made a fork of open source code on github and is called now a thief. This is ridiculous. @blurtlatam is mentally ill. As for the logo, instead of trolling I would turn to fervi and ask him to remove it
Isn't the logo free to use anyways?
You ball-less dog, you couldn't get control of the platform, as you couldn't control the witnesses, you created fake witnesses. Definitely the people of poland need another holocaust.
There is evil in you dominating over your mind.
We are not associated with that fronted. tell him to at least deign to change the logo he uses and to thank the developer who made improvements to the source code. Nothing more to discuss.
If you want another version, I invite you to read this post: Blurtlatam Frontend Esp-Eng, which puts things back in order and provides context. Despite having differing opinions on some topics with @freakeao, as I may have with other, I support him for what he has unjustly endured. I also encourage you not to stop at this post and conduct your own investigation to form your own opinion on the matter, one that belongs solely to you.
We can all have a different point of view, have a different opinion, have a vision of the world that does not fit with that of another person, however if there is mutual respect, we can sit down to debate and exchange opinions for long hours. Thank you for the mention.
If you don't trust me, you should run your own BlurtLatam.
Lol. Never said i didn't. Never said i did either. But up to now I don't see anythimg wrong. I was only trying to figure out who was the real "culprit" behind blurtlatam.intinte.org
Thank you for keeping it open from censorship. What other advances do you have planned for that front end?
that fervi has created for blurt, apart from just cloning repositories, has only done useless things for the platform.
Which useless things? Could you be specific?
I would also like to know this.
who can trust a guy, who has a blurt account creation system, and who cannot change the passwords......
You can change a password, but after creating account, not before.
That aspect caught my attention: that all the frontends had problems connecting to the nodes, except BeBlurt, which I follow although I still can't publish anything using Linux.
Thanks for the clarification @nalexadre.
Soon, soon @argenvista 🤣 I had planned to work on some fixes for your case and others like @drutter but this came out of the blue without warning 🤣
Thanks for the post and the support to Blurt. You really deserve a top position in the witness ranks for all you done.
Thank you very much for your kind words @tekraze 😊 Thank you also for setting up a new Nexus RPC node and frontend for Blurt and thus participating in its growth 👍
Thanks for the update, I was sure it was a technical issue that would eventually be fixed even though I didn't know what was going on.
You mentioned it would be beneficial for others to add RPC nodes to the network( I don't know what these are), but is this something everyone can do or only those who know how
To perhaps give you a simpler representation @hazqdee & @drutter, an RPC node is like a large database that contains the transcription of each block of the blockchain in a human-readable and usable format, unlike a witness node that primarily works with the raw data of the blockchain file. This implies the need for a sufficiently powerful machine not only to store the data but also to process it in a way that makes it usable, along with a stable and high-performing internet connection to respond to requests and synchronize with other peer-to-peer network nodes in milliseconds.
Setting up such a machine is not overly complicated, given the abundance of available documentation. However, what can be challenging, especially for non-server administrators, is understanding its functionality and being able to troubleshoot any issues it may encounter – whether due to increased data, traffic, or other factors.
I was also wondering that. I assume that since I don't really understand what it means, I'm not likely able to carry out the task, but I'd still like to know.
You guys are doing extremely great. It's indeed a welcome development.
I wish you all More strength and ideas in piloting this platform forward and never to stumble.
Bravo!!!!!💖💖💖💯💯
Thanks a lot for your kind words @joshbam 😊
Congratulations, your post has been curated by @r2cornell, a curating account for @R2cornell's Discord Community.
Terima kasih atas kepedulian anda memberi pemahaman 🙏
thanks for these updates
Re🤬eD
🥓
Thanks for the explanations.
Thank you for the updates @nalexadre and for your help and support hopefully it will be all on track real soon and thank you to all the team working hard on these issues.
Hmmm, it seemed to happen again today. No frontends, no wallet... now we're back on at the moment.
It's been like a broken merry-go-round lately hopefully we stay connected and, on the road, again....lol
Thanks for the update.
Thank you very much for giving us this update. Prayers and love for you, may God keep you well and healthy always.
thanks for the update ☺️🥰
Congratulations! 🏆
You have recieved a coconutty upvote! 🥥
Thank you for contributing to the Blurt Blockchain!
Keep up the great work!
Curated by @outofthematrix!
Gracias por la información me tenía preocupada esa falla.
Thank you so much for the updates
The centralized nature of the reliance of a small number of RPC nodes in Blurt and other social media networks like Blurt is a concern for me. Most people who understand the technology accept this as something that just is. The super light nodes that have to rely on some public-RPC.
Most of the time, web apps will load new data and post to some RPC node for all operations. This problem is similar for networks:
The nodes which are not RPC nodes but are full-nodes in a Bitcoin sense exchange blocks, transactions in a pool and validate them, never communicate with a web browser. I think web clients could be adapted to pass around transactions in such a way perhaps from regular non-RPC nodes, so they don't need to poll RPC nodes while viewing a page for comments or votes or other new transactions.