Agreed…lost the entire weekend and spent a lot of money getting a bot setup. It’s insanely powerful, but I’m still not convinced it’s doing exactly what I’m telling it to do (repeatedly). Will be fun seeing if I can sufficiently tune it. Crazy tech.

My openclaw trading/bitcoin analyst bot (that you and @Marty Bent inspired me to create) is telling me we have another leg down before we go full bullish. This tech is bananas!

A lot of the models are the same under the cover. In other words, some generac and kohler models might use the same Briggs and Stratton engine, same controller, and same switch gear. An apples to oranges comparison might end up being an apples to apples comparison and ultimately just be about price. Dig into the details.

Agree with a lot of the other comments - warranty isn’t worth much. Routine maintenance and regular/weekly exercising are key. They’re pretty basic…learn how to maintain it yourself and you’ll save sats and probably be able to troubleshoot most any issue in an emergency.

Another thought…

We all know Saylor and like are huge advocates of ossification. Maybe they co-opted Core and devised this scheme as a publicity stunt to support their ossification case.

Thanks @Matthew Kratter for making this clear in the most recent videos. Relaying this garbage IS the attack. It’s got nothing to do with the nodes ultimately having to download and store it in their copies of the time chain…it’s about distribution. I totally missed this.

I wonder if this is just a negotiation tactic. In the previous video you referenced an X post that listed two reasons why the devs would do this - because they’re evil or because they want to advance some other business venture. In the post, the former was immediately ruled out leaving just the second option…which, is how all this started to begin with.

In that light, suppose all they needed/wanted was to increase the limit to say 200 bytes (honestly, this has gone on for so long I can’t even remember what the original requirement was). Knowing that a portion of the community would resist even that change, why not go all out and say you’re actually planning to increase it to some astronomical size, let the community drive themselves insane arguing over it, and then, just before shipping the update, make an about face, acknowledge the error in your ways, bend the knee, and set the limit to what you wanted originally?

It’s my understanding that the setting is still ‘tunable’ for now, but the plan going forward is to deprecate even that functionality.

Came here to make the same comment. I love the videos and watch every one of them. I also switched to Knots…even before this op_return nonsense. However, if the transaction is confirmed, your Knots node is going to download and store it whether you chose to relay it or not.

With regard to the ‘attack’, is there some sort of legal distinction between ‘transmitting’ and ‘storing’ this horrific data @Matthew Kratter ?

Nuance, but it’s worse than that:

On a bitcoin standard, the only way to justify current/non-falling prices is to deliver more value.

Seems plausible…borderline obvious. What I can’t get my head around, though, are the implications to the stock and bond holders when said governments flip the switch and expose the plan. Do they just wait until all the bonds convert, let the market drive the nav premium down to 1, and print a bunch of fiat to pay out all the shareholders? Sounds a little too 6102’ish.