Jon Matcho

Posting about software and Bitcoin (money not a database)

[Jon Matcho @JonMatcho]

@arcbtc There is overwhelming opposition to the proposed change within the team, yet it's being pushed forward by actors with reckless abandon for the future of #Bitcoin

https://t.co/v8Wr8bXKC2

[Jon Matcho @JonMatcho]

@heresmynametag @ToneVays @start9labs Interesting, right? It’s because @ToneVays want nodes to prioritize storing everyone else’s data more than he wants Bitcoin to be money.

You don’t have to use Start9. You can run https://t.co/WHXvO70xiB on your PC to support BIP-110: https://t.co/KmHLvvlpkw

[Jon Matcho @JonMatcho]

@Arthur_van_Pelt Run https://t.co/WHXvO70xiB to easily support BIP-110: https://t.co/KmHLvvlpkw

[Jon Matcho @JonMatcho]

@Bitcoinapolis55 Run a node to protect Bitcoin as money (not a place to store junk).

Run https://t.co/WHXvO70xiB to support BIP-110: https://t.co/KmHLvvlpkw

[Jon Matcho @JonMatcho]

@Kurtis_NZ @1914ad Dismantling the Bitcoin Core team IS focusing on governance and productive changes to Bitcoin. There is no better use of time in Bitcoin than to clearly state: Bitcoin is money, and Bitcoin is better money when it has minimal data attached.

[Jon Matcho @JonMatcho]

@hodlonaut @MikeMtk63 https://t.co/lDi3mQgmuk

[Jon Matcho @JonMatcho]

Sheesh, I didn’t even ask why Adam Back went to Epstein’s island!

[Jon Matcho @JonMatcho]

@frankcorva Why?

[Jon Matcho @JonMatcho]

@lukedewolf Why? Or are you just saying that as a knee-jerk reaction like a podcaster-like simpleton?

[Jon Matcho @JonMatcho]

@MrHodl @w_s_bitcoin What?! With the release of Version 30 the Bitcoin Core team officially announced to the world: If you have data — any data whatsoever — we have a free database for you to store it.

You are a deceitful and despicable person.

[Jon Matcho @JonMatcho]

@secsovereign @lukedewolf Activating BIP-110 allows 1 year to figure out “something better”. Kicking the can down the road allows n years of more nonsense to come from the Bitcoin Core team. Now is the time.
https://t.co/KmHLvvlpkw

[Jon Matcho @JonMatcho]

@Nil_compliance @LukeDashjr Running Knots is easier than running Bitcoin Core. https://t.co/WHXvO70xiB to support https://t.co/KmHLvvlpkw

[Jon Matcho @JonMatcho]

@OneSirMeow @LukeDashjr Stupid. datacarriersize has been maliciously marked as deprecated by the Core team. Also, nobody needs zk-proofs courtesy of Shitrea, Inc.

[Jon Matcho @JonMatcho]

@jimmysong https://t.co/FaSuhjlsUl

[Eduardo Prospero @edprospero23]

Bitcoin Core uncapping OP_RETURN is a clear centralization attempt.

Who's behind the operation? Who's trying to take Bitcoin over?

[Jon Matcho @JonMatcho]

@ClimateWarrior7 Pics of your room with an immigrant?

[Jon Matcho @JonMatcho]

@Arthur_van_Pelt @RC_Free_D @Adamus3 Adam Back, presumably for retweeting your post. Frankly I’m not surprised knowing how childish and cowardly he is in the face of any real facts that challenge his weak opinions that have little-to-no factual basis.

[Jon Matcho @JonMatcho]

@MasterTheGame @Jason @PeterSchiff @mattkratter Supportive of who and what?! StRaTEGy?!

[Arthur "lynch mob" van Pelt 🔥 ∞/21M ⚡ @Arthur_van_Pelt]

Do not allow people like @BitMEXResearch, @adam3us, @brian_trollz, @theonevortex and their incompetent ilk call @hodlonaut his articles "slop". Always push back on their nonsense.

[Jon Matcho @JonMatcho]

Sheesh, I didn’t even ask why Adam Back went to Epstein’s island!

[Jon Matcho @JonMatcho]

With the advent of Bitcoin Core’s 30.0 plans and ultimate release, it becomes crystal clear why it’s now critical to run https://t.co/WHXvO70xiB to protect Bitcoin’s primary purpose as money and not a junkyard of data. https://t.co/KmHLvvlpkw

[Luke Dashjr @LukeDashjr]

Don't let the bad actors trick you into thinking Bitcoin Core 30 allows you to re-enable the datacarrier limit:

1) Along with unlimiting the default, they also broke it further. datacarriersize=83 now (as of Core 30) allows for 83 outputs totalling 830 bytes of spam, instead of just 92 bytes of spam (9 bytes of which couldn't be arbitrary) as in Core 29 and earlier.

2) datacarriersize is marked as deprecated, and explicitly planned to be removed in a future release (likely silently, since "it's already deprecated").

3) Core never fixed the Inscription exploits (CVE-2023-50428 and CVE-2024-34149) which allow spammers to bypass the datacarriersize limit.

The only way forward now is a mass migration to Knots. Not the way I wanted things to go, but Core has given us no other choice. Once this is resolved, we should avoid putting all our eggs in one basket, and encourage the creation and use of multiple clients.

[Jon Matcho @JonMatcho]

@ConsumingCrypto No comprendo