
Maksim Hapeyenka
640 posts





LiteLLM HAS BEEN COMPROMISED, DO NOT UPDATE. We just discovered that LiteLLM pypi release 1.82.8. It has been compromised, it contains litellm_init.pth with base64 encoded instructions to send all the credentials it can find to remote server + self-replicate. link below



The problem is that, under the current setup, Bitcoin loses in almost every scenario. If Bitcoin’s price doesn’t rise aggressively, we’ll see waves of small miners shutting down because they can’t stay profitable. That funnels hashrate into the top 5 pools and accelerates centralisation. But if Bitcoin does 2x every halving, miners will be fine, yet the network becomes more attractive to attack. The gap between the security budget and the potential payoff from a 51% attack widens. (And before we get lost in “who would do this?” debates - I’m talking about political and reputational attacks, not financially motivated ones.) Paradoxically, the healthiest scenario for Bitcoin is slow price appreciation accompanied by a “fat” security budget that scales with it.










View the @TracNetwork in a whole different dimension. Introducing Trac.vision In early release, expect to iterate it as time goes on. Looking forward to seeing this map GROW and have huge transaction volumes go through the network!

In total, how many Ethereum or Solana transactions have you executed during your entire time in crypto? 👀







