I tried zapping you but it's returning errors

Same 😔

He doesn't know how to set up a lightning wallet

As I've said many times, Citrea really seems like a shady coverup of the whole thing. Why can Alpen Labs fit everything in just under 80 bytes?

Bitcoin bridge | Alpen

If Citrea sucks as a layer 2 it's its team that should find a better way of doing things instead of Bitcoin Core changing long standing, non controversial policy.

He doesn’t want the sats clearly. Loads have tried to zap him but he doesn’t set it up. Maybe he’s trying to prove he has no financial incentive in this debate

I was listening to a Jim Rohn video this morning and he was talking about defending your values. We value Bitcoin as Money not as an Image file distribution system. Anyway... run Bitcoin Knots! View quoted note →

ha! good one! 🙄

I cannot believe these these cOrE v30 proponents are engaging in this horrible slander!

Lopps shitcoining ways. Go back to eth loser

This PR, replacing #32359, doesn’t remove the -datacarrier or -datacarriersize options. Contrary to what many are saying, the PR does not force the user to accept larger datacarrier transactions in transaction relay. Setting -datacarrier=0 still turns it off, and -datacarriersize=83 gives you the original default (the same amount of data but across 1 or more outputs). Some developers still believe the option should be removed, but there is consensus for waiting at least 1 release like we did for -mempoolfullrbf. No timeline is set for removal. read more:

GitHub

policy: uncap datacarrier by default by instagibbs · Pull Request #32406 · bitcoin/bitcoin

Retains the -datacarrier* args, marks them as deprecated, and does not require another startup argument for multiple OP_RETURN outputs. If a user h...

It worked like a month ago.

People need to open their eyes. Truth matters.

Love your videos! ❤️

If interested , highly recommend Keep study and stack sats 🇮🇹🔥 @Matthew Kratter View quoted note →