Earlier this evening, I was browsing Hive-Engine, trying to scrape together some DEC to swap for Hive since the exchange rate was favoring DEC. While checking my assets, I noticed that one of my long-term holdings had suddenly crashed in value. A few hours later, after digging deeper, I found troubling signs that the entire community I’ve been part of for nearly half a decade may have been hijacked and possibly compromised.
https://hive.blog/hive/@themarkymark/psa-brofundbromancave-likely-compromised-3sa
I have sold off my remaining BRO at a significant lost but not many tokens. I still have some LGN that are staked so now unable to sell those as it seems to be zero.
I did not hold a large amount of LGN, just a little over 33 tokens, so the loss is relatively small compared to some of my past experiences in crypto. But here’s the concern: if it turns out that any token associated with BroFund has truly been compromised, then my losses could be significantly compounded. It’s a troubling possibility that adds weight to an already unsettling situation.
I'm also invested in other projects connected to BroFund, including DAB and DBOND — a collaborative effort between BroFund and @spinvest. I currently have over 100 DBOND tokens locked, and I just liquidated another 100 DAB. Given recent developments, I'm too uneasy to continue holding anything associated with BroFund. This experience serves as a cautionary tale for other investors on Hive stay vigilant and do your due diligence.
I would believe there are other projects BroFund is involved in since they existed for multiple years on Hive. In any case I am looking through my secondary Hive tokens to make sure I do not own anything related to BroFund.
I sincerely hope this situation gets resolved, but I’m not holding my breath. I’ve seen this story play out too many times before, and I’ve personally been rugged in multiple projects. It’s disheartening to witness it happening again, but I’m doing my best to minimize the damage and I strongly encourage others to take precautions and do the same.
Posted Using INLEO
