The WARTHOG Situation Fork it?

💡Tryout HIVEOS Entirely Free:

what is up ladies and gentlemen welcome back to the brandoncoin YouTube channel I hope everybody's having a great day it is February 15 2025 um and you know there's a situation that's happening over on the warthog Network um it's been raised to my attention by quite a few people um I've checked and it looks like pretty much all mining pools on the warthog Network either have been affected or are being affected by this it's a network-wide issue but um I figured we'll dive right into it and go through it like step by step and explain it so uh the big issue on on the front end if you're a user of the warthog network is uh if you're mining on warhog right now pretty much on any pool there's an unusual amount of orphaned blocks it is going down but there's a reason why so previously um I think it's been over a week now uh maybe two weeks ago Zex in exchange was compromised and that is one of the large exchanges that uh supplies uh options for trading for warthog so you can put your warthog on there and you can trade it now um in an effort to secure those funds the warthog developers had pushed out a node update that would essentially Blacklist uh the ZX wallet from being able to um send warthog out in layman's terms um I don't know what all was in that update or not but uh it was presented to us the pool operators because we do have a pool it's the community jellyfish pool um jelly fc.com you can go go there go through the web portal and find the pool uh and it was presented to us that we needed to update and if you're not on the latest node uh then you know it's a problem so it wasn't a uh an ask it was a tell um now warthog had put out an official statement actually the 13th so about a day and a half ago uh and I want to read that statement because I find an issue with it so um they or Al put that block in place to block those funds so even if that the ZX was legitimately compromised the U offender couldn't steal those tokens the only problem is uh people can't get those tokens back until Zex fixes their issues lets people back in so on and so forth so um now time goes on Zex opens back up people are starting to withdraw their coins but they're still blacklisted so uh the warhog developers are like hey we need to lift this BL list we need to um you know update again to essentially roll back roll this back but it's not technically a roll back uh it's just I guess whitelisting this address now I don't know all the technical terms but that's you know essentially what they said so this was not another ask this was another tell um we went ahead and implemented that and then there was another update literally the that night or the next morning where um they noticed people were not updating to uh the new update and it was causing orphans on the Block amongst other things um so they said you know this new update if you don't update to it by this date you will essentially be cut off from the network um and your transactions won't process all that kind of stuff uh so again not another ask but another tell uh so we are on the latest update which is uh as of right now 0.8.0 um and it lifts the funds protection in 5 days from February 13th so right now we have what another 3 Days To Go um and it lifts it at block height 259 8042 just to get like technical technical um now I do want to read their statement that they put out yesterday uh because it not everybody was happy with how the warthog developers handled this situation uh because some could argue and say that this is a very centralized move locking down and blacklisting a wallet um versus decentralized where you can't control it uh and it can do whatever it wants to do so if it gets compromised it's compromised um so let me read their statement and then I'll give you um you know my account of the situation and and what I think about it obviously my opinion means squat but you might consider it a like to yours now let me go down here and pull this up so this was the statement yesterday so statement of Zex fund protection patch about a week ago the Zex exchange was hacked we were given little detail on the situation and rather than simply hoping for the best the warthog development team acted swiftly to develop a plan aimed at protecting funds on Z X's warthog wallet to do this warthog presented an option for the network and node operators who wanted to place a temporary hold on these ZX wallets preventing further unauthorized withdrawals while the ZX team worked on a fix I don't think that this statement right here um is is very becoming of the situation uh this was not an we were not presented as this was an option uh we were told to do this um so maybe I misunderstood but uh if you're not on the latest node uh you will cause problems for the network here's a new node update okay moving forward as always it was our wish to protect warthog users from negative implications we apologize that this time we took quick action without doing proper upfront discussion and voting which was criticized by some parts of the community a lot of the community actually um however the huge support of node operators switching to the patch node can be seen as a vote in favor of the patch no no absolutely not I did not vote on anything we had a mining pool you guys told us to update our nodes are we not now every time that you say you have a node update do we need to go in and search through everything that's in the update log and is that now considered a vote this is very dangerous precedents to set to like to set so now is it up to the node operators to go through and essentially any update is considered a vote that is very I I do not like this statement I I wanted to be really clear about the fact that it was never presented to us as an option or a vote um don't put this on the people that are trying to keep pools running uh on your network I like warthog I like the network I like what it's doing uh I think this was handled wrong does this mean we're going to pull off no we're not I'm still mining warthog we still have a mining pool on warthog hog and we still will be supporting the network um and I am still holding my coins but I I don't like that statement right there uh because then that that puts blame or onus onto the node and and the pool operators anybody operating I think coinx actually is operating a node as well um for their internal wallet so yeah okay back back to the statement let's keep it let's keep it going Brandon um still in any any future emergency event where developers believe blocking potential theft of or mass network damage is necessary we will label these updates so node operators understand that choosing to run the new version is their vote to create a potential Fork if they do not agree with the changes they should not run the update and this will lead to a fork such that the market can decide which chain gets more support we will also give more time for discussion on the implications this is what I'm this is what I'm talking about so now um you are putting all the onus on the Node operators um maybe maybe the node operators need a central location uh to talk about this I don't know where it is um if anybody that is operating a warthog node uh knows where this is please let us know I think having this discussion in the warthog official Discord um is potentially not necessarily A decentralized Loc because if the warthog developers are in favor of one thing but then they know operators don't agree with it now that it's it's been the decision to vote for this is being placed on us uh obviously talking in their Discord about it um may not warrant or or get a a unsolicited uh true you know discussion um so I don't I I really did not like this post um yeah yeah uh so it to me it just feels like hey now and you know maybe I'm reading it the wrong way but it just feels like to me now it's not up to the community it's up to the node operators which honestly are actually a very small part of the community I mean obviously they're a huge part of the network because without the nodes um nothing would happen but man yeah that's just it's a tough cookie it really is um and in my opinion uh obviously everybody can do it their own way with what they want to do um but I think going back to straight up like a a community vote system where everybody's opinion matters not just people running a node um you know talk it out with your Community First have a vote system you know put a poll up I don't know what you need to do um share it on Twitter that way everybody can see it you know go vote on this see what we're going to do regardless but having this I yeah yeah and and you know what maybe I am just super green to operating a node and being in a a a place of of having a vote you know normally my vote doesn't matter too much inside of crypto but um I just I want you know everybody's got a choice everybody's got an opinion and um I don't think since I'm running a note my opinion should be you know or my voice should be heard any louder than anybody else's um so I'd love to hear your questions comments concerns everything down below in the description uh if you are running a warthog node reach out to me and I'd love to set up like a mutual you know uh grounds where maybe we can all have a a big group chat or something where everybody's on Level Playing Field we're not in anybody's specific Discord or anybody's specific chat room uh and it's welcoming to everybody in that situation um so that way if if it's being put on us to vote for situ like to vote what this is and what that's not um maybe we can actually talk it out and uh and understand each update we do if they hold that much weight oh my God my neighbor is bumping some music right now um now going back to their their final block of text here with the Zex now back online and gradually resuming normal operation the warthog team has released node version 0.8.0 yesterday to remove the temporary hold in 4 days at a specific block height 295 8042 this reverts the ZX fund protection and gets us back to normal operation now this node update right here 0.8.0 some people have not done this yet and it's leading to a massive amount of Orphan blocks on the network last night people were reporting upwards of 20% of the blocks that we going through were were orphaned um now the problem here is that it's Network wide uh we had people pulling off of our pool going to other pools and um everybody was experiencing a high un un or unnatural level of Orphan blocks that hurts you know your your bottom end your bottom line minor so then a lot of miners were like hey man I got to pull off till this is this is figured out and that's understandable but I just wanted everybody to know um this is not anything specific that we're doing or another pool's doing um this is what's happening in the network and hopefully I explained this well enough uh to get my point across but um I'd still love to hear what you guys think and yeah yeah I I know you know the warthog team's probably not going to like this video um and it's not meant to be against anything uh I just wanted them to know um and wanted everybody else to know uh how this is being received by not only me but also my team um because I I'm G be honest when running the pool I'm just a very small part of it uh because I I'm just not there on a technical level and um I got a really good team uh with me so shout out again to the jellyfish the jelly FC team you guys have been killing it you know Batman Dave GMG Dragon dag all you guys been uh putting in some good work we are migrating hosts uh we had an issue where our host was had some some switching internal issues for network and we were getting like random like like Network spikes they tried to resolve it they moved us to three different or two different locations still didn't resolve it so we are switching entire hosts I guess this is a good time to do it um so it is going to be minimal downtime but that's not going to fix the orphan issue so anyway guys I'm going to jump off here yall have a good One Peace have a good weekend you know yeah

As found on YouTube

You May Also Like

Leave a Reply

Your email address will not be published. Required fields are marked *