SkylerByrden
Skyler Byrden ⚡️BIP444 ⚡️UASF

Feel free to steal my memes

Public Key

npub1xhanzgrhhkfqzk3zm3kae66lxdrm2hxkvm6h4xamn35py4qw4fhqes278r

Profile Code

nprofile1qqsrt7e3ypmmmysptg3dcmwuad0nx3a4tntxdat6nwaec6qj2s825mspz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsnx3uup

Publishing to

relay.damus.io

nos.lol

Author Public Key

npub1xhanzgrhhkfqzk3zm3kae66lxdrm2hxkvm6h4xamn35py4qw4fhqes278r

Show more details

Last Notes

2025-10-12 15:08:37 UTC

- reply

It’s Malware
https://blossom.primal.net/72f97e6f7c8c35a79cb3979339bb0523ba8a2ddddbef80df46e77381fab4b840.jpg

2025-10-12 01:47:16 UTC

Dump Core Run Knots
https://blossom.primal.net/592d855091037ed717bc99ce78b8e8435d8ebf79d4fbf84b5982a0bb7b8c7670.jpg

2025-10-12 01:28:29 UTC

- reply

https://blossom.primal.net/72f97e6f7c8c35a79cb3979339bb0523ba8a2ddddbef80df46e77381fab4b840.jpg

2025-10-10 23:49:31 UTC

- reply

There’s an interview with Casey Rodarmor where he talks about beginning ordinals development while working at Chaincode. He said they were supportive and enthusiastic.

2025-10-09 02:17:38 UTC

Core getting brutally dragged on twitter
https://x.com/bitcoincoreorg/status/1972412122631217271?s=46&t=2ZhyThxZdxYbJmVEltym3w

2025-10-07 18:50:37 UTC

- reply

It’s been completely redesigned.
https://blossom.primal.net/074b77902066acc025a1dd56173f93719d9798d47f34a2fbd1e5a6ce52365f97.jpg

2025-10-07 16:33:36 UTC

- reply

Why would they completely redesign a filter and announce that it’s deprecated in the same release?
nevent1qqs8va4ydeg6ralxzcc4sk4adac409flzl9n5z4v5hwvjkj9yet3pdcpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhg437fan

2025-10-07 02:53:39 UTC

- reply

https://blossom.primal.net/ddbc4b8f1b1691209a367d69aa92915e62b0a09a02b1c8227d5d06712135e909.jpg

2025-10-06 16:07:53 UTC

- reply

“satoshi's vision was cash, not data dumps; core preserves that purity.”
How did you conclude that core preserves the purity of bitcoin as cash and not data dumps?

2025-10-06 16:04:56 UTC

- reply

Are you hallucinating?

2025-10-06 16:02:47 UTC

- reply

https://blossom.primal.net/3c22725cc38a77bec570fa1b5d568a9dbb56ddc7bd61b6b7025c80c37bc5193b.jpg

2025-10-05 21:23:03 UTC

- reply

Scorecard:
-0% of thr network running Core 30
-21% of nodes now properly filtering inscriptions and climbing
-Core Devs credibility in the toilet
What metric are using that doesn’t point to this being a disaster of their own making?

2025-10-04 17:34:59 UTC

- reply

All I see is 0% Core v30

2025-10-01 12:46:01 UTC

- reply

Chaincode Labs is astroturfing Bitcoin Core by funding & training devs to push permissive data storage (e.g., expanding OP_RETURN limits), creating a false sense of community consensus. Ex: Antoine Poinsot’s proposal to raise OP_RETURN from 80 bytes to ~4MB, backed by Peter Todd, is framed as “harm reduction” but enables non-financial bloat like inscriptions, favoring layer-2 systems over Bitcoin’s monetary focus. With ties to wealthy donors like Balaji Srinivasan ($500k, investor in Citrea) & centralized Manhattan offices, Chaincode’s influence steers protocol toward BitVM/Ethereum-like agendas, undermining decentralization. This “corporate capture” fuels distrust, forks like Bitcoin Knots, & accusations of prioritizing profit over sovereignty.

2025-09-30 21:57:44 UTC

The June 2025 Joint Statement on Bitcoin Core development and transaction relay policy is published on the Bitcoin Core website. It outlines the developers’ views on permissive relay for fee-paying transactions, including those with non-monetary data like inscriptions.
Half of the developers that signed the statement have direct ties to Chaincode labs.
There is no evidence of any developers with ties to Chaincode Labs publicly speaking out against inscriptions or other forms of spam on Bitcoin.
1. Anthony Towns - Chaincode Labs alum, participated in residency programs, and has ties through MIT’s Digital Currency Initiative (DCI) with overlapping Chaincode funding.
2. Gloria Zhao - Associated with Chaincode through residency programs and funding, also affiliated with Brink.
3. Gregory Sanders - Chaincode Labs residency alum, contributed to Lightning Network projects often funded by Chaincode, later joined Blockstream.
4. Pieter Wuille - Received Chaincode grants, contributed to Bitcoin Core development, and is a Blockstream co-founder with Chaincode ties.
5. Fabian Jahr (fjahr) - Participated in Chaincode residencies, received funding, and is a full-time Bitcoin contributor.
6. Martin Zumsande - Linked through Chaincode residency programs and contributions to Bitcoin Core.
7. Antoine Poinsot - Participated in Chaincode residencies and received funding for Bitcoin development.
8. b10c (0xB10C) - Associated with Chaincode through residency participation and Bitcoin Core contributions.
9. David Gumberg - Linked via Chaincode residency programs and developer training initiatives.
10. Josie Baker - Participated in Chaincode’s BOSS (Bitcoin Open Source Software) program or related residencies.
11. Matthew Zipkin - Connected through Chaincode residencies and contributions to Bitcoin-related projects.
12. Murch (Mark Erhardt) - Associated with Chaincode through residencies and funding for Bitcoin Core work.
13. Niklas Gögge - Linked via Chaincode residency programs and developer contributions.
14. Sergi Delgado - Participated in Chaincode residencies or seminars, contributing to Bitcoin ecosystem projects.
15. TheCharlatan - Connected through Chaincode residency programs and Bitcoin Core development.
https://blossom.primal.net/756b7dbfd91f7d335848a30d860653872ec82f5da90345556afba9f886af2dac.jpg

2025-09-30 04:38:58 UTC

argsman.AddArg("-uaspoof=<ua>", strprintf("Replace entire user agent string with custom identifier (should be formatted '%s' as specified in BIP 14)", BIP14_EXAMPLE_UA), ArgsManager::ALLOW_ANY | ArgsManager::DEBUG_ONLY, OptionsCategory::CONNECTION);
uaspoof=/Fuck_Core:30.0/

2025-09-30 01:58:46 UTC

- reply

#nevent1q…ptaf

2025-09-30 01:55:52 UTC

- reply

#nevent1q…ptaf
https://blossom.primal.net/190b3ef7ccb3abb8f61bf36a14b0c6fe4fddcd7d124b05a0b46c968e93121988.jpg

2025-09-29 23:48:53 UTC

- reply

TIL Casey Rodarmor (creator of the Ordinals protocol) worked at Chaincode as a resident engineer while developing Ordinals.
#nevent1q…gavm

2025-09-29 21:28:19 UTC

- reply

The pow of the hashcash stamp is a fee costing the sender.
The pow of bitcoin ensures no entity can mine every block.
Do you really not understand the distinction?

2025-09-29 17:51:06 UTC

A breakdown of who funded key Bitcoin Core devs involved in the datacarriersize redefinition (PR #27832) and rejection of the anti-spam fix (PR #28408), which allowed inscription spam to persist.
Supported Redefinition (PR #27832):
• Marco Falke (maflcko): Authored PR. Funded by Okcoin, Paradigm, BitMEX, Spiral, MIT DCI, OpenSats. Past Chaincode Labs grants. Independent, tied to exchanges/VCs.
• Anthony Towns (ajtowns): ACKed change. Funded by Paradigm, Coinbase, ex-Xapo. Works for Paradigm (crypto VC).
• Greg Sanders (instagibbs): ACKed change. Funded by Spiral; ex-Blockstream (2016). Employed by Spiral (Block Inc.).
• Michael Ford (fanquake): Merged PR. Funded by Gemini, Independent Reserve, Brink, Hardcore Fund. Independent, tied to exchanges/non-profits.
Rejected Anti-Spam Fix (PR #28408):
• Sjors Provoost (Sjors): Concept NACK. Funded by BitMEX, OpenSats, ex-Chaincode, DG Lab, Blockchain.info. Independent.
• Peter Todd (petertodd): Concept NACK; worried about mempools. Funded by Hardcore Fund, ex-BTCC, Bitfinex, Chaincode. Works with Coinkite.
• Antoine Poinsot (darosior): Concept NACK. Funded by Chaincode Labs. Engineer at Chaincode; co-founder of Wizardsardine (Bitcoin security).
• michaelfolkson: Concept NACK. Self-funded; runs RiskBazaar (decentralized platform). Ex-PwC (non-crypto).
• Pieter Wuille (sipa): Concept NACK; flagged feerate issues. Funded by Chaincode Labs; ex-Blockstream co-founder. Engineer at Chaincode.
• Gloria Zhao (glozow): Concept NACK; cited node harm. Funded by Brink (via HRF, Spiral, Okcoin). Engineer at Brink.
• Mark Erhardt (murchandamus): Concept NACK; said market handles spam. Funded by Chaincode Labs. Runs Localhost Research.
• Anthony Towns (ajtowns): Approach NACK; wanted opt-in. (See above for funding/ties.)
Closed Fix PR:
• Andrew Chow (achow101): Closed PR #28408; cited controversy. Funded by Blockstream. Engineer at Blockstream.

2025-09-29 15:53:37 UTC

- reply

did you know that the transaction was mined by Luke 12 years ago
did you know it would be filtered out by the current version of Knots and Core
https://blossom.primal.net/1dbfb48a2ad081e6d466bb06f36f3f2c8629bb912f029590115188c6a8f0e684.jpg

2025-09-29 14:48:41 UTC

- reply

A breakdown of key Bitcoin Core devs involved in the datacarriersize redefinition (PR #27832) and rejection of the anti-spam fix (PR #28408), which allowed inscription spam to persist.
Devs Who Supported the Redefinition (ACKed or Merged PR #27832):
• Marco Falke (maflcko): Authored the PR, focused on clarification without opposition.
• Anthony Towns (ajtowns): ACKed the change, suggested dropping redundant options like -datacarrier.
• Greg Sanders (instagibbs): ACKed the change.
• Michael Ford (fanquake): Merged the PR.
Devs Who Supported the Rejection of the Fix (NACKed or Opposed PR #28408):
• Sjors Provoost (Sjors): Concept NACK.
• Peter Todd (petertodd): Concept NACK; argued it would encourage private mempools and harm fee estimation.
• Antoine Poinsot (darosior): Concept NACK.
• douglaz: Concept NACK.
• aviv57: Concept NACK.
• eragmus: Concept NACK; argued inscriptions don’t significantly spam the UTXO set and filtering worsens out-of-band issues.
• mmgen: Concept NACK.
• alpeshvas: Concept NACK; called the discussion “noise.”
• michaelfolkson: Concept NACK.
• Pieter Wuille (sipa): Concept NACK; concerned about disrupting feerate estimation and compact block relay.
• Gloria Zhao (glozow): Concept NACK; summarized arguments against, noting ineffectiveness and potential harm to nodes. (Note: In Issue #29187, she suggested broadening the scope as an alternative, but opposed this specific fix.)
• Mark Erhardt (murchandamus): Concept NACK; argued market forces handle spam and filtering reduces miner revenue.
• 1440000bytes: Approach NACK.
• Anthony Towns (ajtowns): Approach NACK; cited CI issues and opposed default changes, suggesting an opt-in instead.
Devs Involved in Closing the Fix PR:
• Andrew Chow (achow101): Closed PR #28408 as maintainer, citing controversy and lack of consensus; locked the conversation due to heat.

2025-09-29 14:30:46 UTC

- reply

Why? It’s not like you’ll actually run it
permitephemeral=send,dust,anchor

2025-09-29 13:22:22 UTC

- reply

I use lightning and coinjoins with Knots. Zero problems. Both of your statements are false.

2025-09-29 13:06:18 UTC

- reply

More lies

2025-09-29 13:05:57 UTC

- reply

Lies

2025-09-29 03:29:22 UTC

- reply

2025-09-29 02:24:06 UTC

A breakdown of key Bitcoin Core devs involved in the datacarriersize redefinition (PR #27832) and rejection of the anti-spam fix (PR #28408), which allowed inscription spam to persist.
Devs Who Supported the Redefinition (ACKed or Merged PR #27832):
• Marco Falke (maflcko): Authored the PR, focused on clarification without opposition.
• Anthony Towns (ajtowns): ACKed the change, suggested dropping redundant options like -datacarrier.
• Greg Sanders (instagibbs): ACKed the change.
• Michael Ford (fanquake): Merged the PR.
Devs Who Supported the Rejection of the Fix (NACKed or Opposed PR #28408):
• Sjors Provoost (Sjors): Concept NACK.
• Peter Todd (petertodd): Concept NACK; argued it would encourage private mempools and harm fee estimation.
• Antoine Poinsot (darosior): Concept NACK.
• douglaz: Concept NACK.
• aviv57: Concept NACK.
• eragmus: Concept NACK; argued inscriptions don’t significantly spam the UTXO set and filtering worsens out-of-band issues.
• mmgen: Concept NACK.
• alpeshvas: Concept NACK; called the discussion “noise.”
• michaelfolkson: Concept NACK.
• Pieter Wuille (sipa): Concept NACK; concerned about disrupting feerate estimation and compact block relay.
• Gloria Zhao (glozow): Concept NACK; summarized arguments against, noting ineffectiveness and potential harm to nodes.
• Mark Erhardt (murchandamus): Concept NACK; argued market forces handle spam and filtering reduces miner revenue.
• 1440000bytes: Approach NACK.
• Anthony Towns (ajtowns): Approach NACK; cited CI issues and opposed default changes, suggesting an opt-in instead.
Devs Involved in Closing the Fix PR:
• Andrew Chow (achow101): Closed PR #28408 as maintainer, citing controversy and lack of consensus; locked the conversation due to heat.
https://blossom.primal.net/312260f43988745eae05fb3df0bfc06685f88d6f15c1d0d3c6a514924898726a.jpg

2025-09-29 01:29:15 UTC

- reply

I agree with everything here except waiting 6-12 months. I don’t see the point in waiting that long.

2025-09-28 21:22:34 UTC

- reply

https://blossom.primal.net/fcfcb49bcdfb2785db03fea61eacd365f5f8024db6a354902751a14e7a7fbaa1.png

2025-09-28 18:45:21 UTC

Fuck Core Run Knots
https://youtu.be/s8ny5h01zbo?si=1xnnnpuq0g6egavI

2025-09-28 15:31:36 UTC

- reply

https://blossom.primal.net/c3aeb8405713fdebebe2e847533fe6183855d3760874620bdc427ab90221ea05.jpg

2025-09-28 15:30:24 UTC

- reply

https://blossom.primal.net/d35ee6f68145501c781990b55023b6dda732da9db9350c14a31f3d6640735418.gif

2025-09-28 15:24:58 UTC

- reply

https://blossom.primal.net/fec71c216e620610927ac89d2d4d3bf58b0382c103b70eefbd1d0dfd5b69398e.jpg

2025-09-28 15:23:22 UTC

- reply

The all-or-nothing logical fallacy, also known as the false dichotomy or black-and-white fallacy, occurs when a situation is presented as having only two mutually exclusive options, ignoring any middle ground or alternative possibilities. It oversimplifies complex issues by framing them as an either/or choice, often to manipulate or persuade.
For example:
• “You’re either with us or against us.” This statement ignores the possibility of neutrality or partial agreement.
• “If you don’t support this policy, you must hate progress.” This overlooks nuanced positions or alternative solutions.
This fallacy is problematic because it limits critical thinking and dismisses valid alternatives, leading to flawed reasoning or polarized conclusions. Recognizing it involves identifying when someone presents a situation as having only two extremes without justifying why no other options exist.
https://blossom.primal.net/c18e768716e16e94127611d1f7cb8a7f78b80954d65d9a304ec69c9a38499a31.jpg

2025-09-28 04:57:41 UTC

Dump Core Run Knots
https://blossom.primal.net/fcccebd6b310a3b33b738eac223cdfa86cb1eafacd8523041a7915c4ef9aa193.jpg

2025-09-28 03:32:39 UTC

- reply

https://blossom.primal.net/fec71c216e620610927ac89d2d4d3bf58b0382c103b70eefbd1d0dfd5b69398e.jpg

2025-09-28 02:01:38 UTC

Dump Core Run Knots
https://blossom.primal.net/95e1d1e431127f294077517e3a88b41f536b6caa7bcf4e13b1e766ebd098dfe2.jpg

2025-09-28 00:38:47 UTC

- reply

It actually does. Luke merges prs that get nacked out of core. Most of the differences were proposed in core first. They just hate him because he doesn’t ask for their opinion.

2025-09-28 00:33:06 UTC

- reply

All of them

2025-09-27 23:54:18 UTC

- reply

To heal an infection you gotta make some pus.

2025-09-27 23:38:15 UTC

- reply

There’s nothing cypherpunk about conflating jpegs with hard money and censorship with spam filtering.
It’s a category error. Treating the technical act of filtering data as equivalent to the socio-political act of censorship misattributes properties across distinct categories.

2025-09-27 23:04:11 UTC

- reply

The statement commits the noncentral fallacy (also known as the category error or the worst argument in the world). It labels the act of filtering certain Bitcoin transactions as “censorship,” invoking the strong negative connotations of that term (typically associated with authoritarian suppression of free speech or ideas), even though the action in question is atypical of the category—more akin to spam filtering or network moderation by decentralized participants rather than centralized control over expression. The premise that “all Bitcoin transactions are data” is used to blur distinctions and amplify the loaded term, but it doesn’t logically establish the conclusion.

2025-09-27 22:45:15 UTC

- reply

The term you’re struggling to avoid is “access journalism”. Bad attention is better than no attention I guess.
The label “influencer” would infer that you actually influence ppl.

2025-09-27 21:27:36 UTC

- reply

The statement commits the fallacy of equivocation by ambiguously shifting the meaning of “monetary transaction.” In the context of Bitcoin, this term typically refers to transfers of value (e.g., sending BTC between parties as a form of payment or exchange). However, the statement redefines it to include any transaction that incurs a fee paid to miners for inclusion in a block, even if the primary purpose is non-monetary, such as embedding arbitrary data without value transfer. This equivocal use of the term makes the argument appear valid when it isn’t.

2025-09-27 21:23:19 UTC

- reply

https://blossom.primal.net/db1792d44f59eb59e7cee60c27970c2dabf9949774731de647971f822f121bf0.jpg

2025-09-27 20:15:42 UTC

- reply

2025-09-26 23:25:20 UTC

- reply

https://blossom.primal.net/f781bfe1425513d1bba9f568ad314f060fc8e3b0b23710eb9c76fac2db28973d.jpg

2025-09-26 20:04:39 UTC

Recap of the op_return controversy…
https://blossom.primal.net/00cb0dd608379ca61bb37d0269ab4c59bd1ff93c865a1d5922a2eb253a5481fe.jpg

2025-09-26 12:53:18 UTC

- reply

Conflating neutral, censorship resistant & permissionless money, with neutral, censorship resistant & permissionless jpeg storage is where you fall on your face.
Just pointing out the precise reason nobody takes you serious.

2025-09-26 12:34:12 UTC

- reply

i read the luke dashjr hit piece.
it's wrong. basically the entire article is wrong.
i'm (obviously) not on luke's side, but guys this is just a sloppy low quality propaganda piece.
first of all: sharing private messages is not cool. for many obvious ethical reasons. but one reason that is often overlooked is that sharing private messages often puts them out of context and makes it easy to construct a false narrative without understanding the conversation
with that, let's look deeper into the article published by "the rage":
the rage: "dashjr... proposes the implementation of a multisig quorum on bitcoin that grants a designated group of people the ability to retroactively alter data that is hosted on the blockchain"
there is no discussion of "altering the data that is stored on the blockchain" anywhere in the screenshots provided.
luke discusses a hypothetical mechanism that would allow knots node operators to avoid downloading "spam" that's already in blocks.
imagine a hypothetical knots client that syncs blocks with a delay of eg 1 hour. when it downloads a block (late, on purpose), it pings luke's server and asks, "hey, is there any spam in this 1 hour old block?".
luke's server responds with a list of transaction IDs that contain "spam", and provides a "zero knowledge proof" that proves to knots nodes that those "spam" transactions are valid, without having to download them.
this is the magic of zk proofs and we don't need to get into how it works. suffice to say that the reason bitcoin nodes download transactions is to verify that they're valid, and if there's a way to verify without downloading them then the node can continue functioning without having to download the "spam".
so now knots have a mechanism to avoid "spam" on their computer while still validating the chain. this doesn't remove the "spam" for the chain. it is still available on clients that don't run knots (70%+ of the network). core nodes continue to function as normal, with "spam" and with no issues, and continue to be in sync with knots nodes. the only difference is that the knots nodes can avoid ever downloading "spam", while staying on the same network
the rage: "luke dashjr plans hard fork"
this isn't true and it's a misunderstanding of what luke is saying. his messages do not describe a plan to hard fork bitcoin. he's referring to a technicality, saying that whenever knots nodes use a mechanism like the hypothetical knots node i described above, every time they avoid downloading a transaction they technically hard fork. but just technically, not really. it doesn't split the network, and those hypothetical knots nodes remain fully compatible with core nodes. core nodes can continue to verify, their chain is not censored, and they're fully synced with knots nodes.
the rage: “right now the only options would be bitcoin dies or we have to trust someone,” dashjr writes. The proposed solution would require a consensus change, activating a bitcoin hardfork.
the quote about "we have to trust someone" is taken out of context. luke is literally saying in the convo that thanks to zk proofs and his proposed solution, they would NOT need to trust anyone.
the second part about a consensus change is made up. nothing in the screenshots suggests a consensus change. and i explained above that the "hard fork" bit is just a technicality. in this hypothetical design, there would be no chain split, and core nodes would remain compatible and uncensored.
the rage: dashjr reveals that public letters are being drafted by third parties to seemingly support the sanctioning of illegal content on the entire Bitcoin network.
the leaked conversation does not AT ALL mention a public letter that supports sanctioning illegal content "on the entire bitcoin network". luke is asked by his conversation partner a legal question, whether or not an op_return relay network will be perceived by authorities as illegal. luke replies that he can't answer that question because he's not a lawyer, but his understanding is that a group is working on a formal letter that addresses that legal question.
as far as I can tell that hypothetical letter is a simple "legal opinion", not a letter that calls for sanctioning transactions on bitcoin.
🔸🔸🔸🔸
fyi, they hypothetical design of a knots node that i provide above is just that: hypothetical. the leaked dms don't go into implementation details at all so i had to fill in the blanks. luke might've had some other design in mind. but my description is conceptually correct, and the article's isn't.
you can go back to the leaked screenshots and re-read them and tell me if anything there contradicts the hypothetical design I offered (nothing does).
also, an important point is that the entire leaked convo is hypothetical. people are allowed to have hypothetical conversations. that doesn't mean there's some conspiracy. everyone I know that discusses this issue in private has brought up all kinds of weird ideas to me that doesn't mean they actually plan to implement them.
🔸🔸🔸🔸
my conclusion is that this article is a hit piece, and not a particularly good one.
the most charitable explanation i can come up with is that the author misunderstood the leaked messages and wrote the incorrect article based on that misunderstanding
but honestly it really seems that this isn't the case, it seems like the author was employing a lot of motivated reasoning to arrive at the conclusions in the article. the goal was to make luke bad, and his words were manipulated for maximum effect
this isn't the first time "the rage" is doing this. last time it was a fake news article claiming that google is about to ban self-custody wallets from the android app store. it was based on the author's borderline malicious interpretation of the google store rules, to make them look like they're against self-custody.
that was incorrect, but the fake news article got so viral that google itself had to issue a clarification saying that they have not and will not ban self-custody wallets from the android store.
🔸🔸🔸🔸
perhaps most disappointing was seeing many big names from the "anti-knots" camp jumping on this and declaring that luke is working on a hard fork, that "they knew it" and that soon we will be getting "airdrop fork coins" to sell. all of those things are false.
this is, as always, a nothing burger. it's pretty obvious to me that this proposal never gets implemented, and even if it did, it does not censor the network and does not split the network, and remains fully compatible with core.
it's actually, dare i say it, a pretty good hypothetical solution (to a problem that doesn't matter). i wish they'd implement it. but they probably won't.
do better everyone.

2025-09-26 12:13:34 UTC

- reply

He says that the article is an intentional misunderstanding and it’s actually a legit way to remove illicit data from the chain without forking

2025-09-26 11:54:54 UTC

- reply

Even Taproot Wizards are calling you piece of shit at this point. Hang it up. You’re credibility has disintegrated
https://blossom.primal.net/dc23d4fba6d6f967fce378d65cba3e98330f98b48cf0fcc8c0769bce0d5958b6.jpg

2025-09-26 11:49:07 UTC

Even the Taproot Wizards are defending Luke now.
Bitcoin Core is disaster
https://blossom.primal.net/dc23d4fba6d6f967fce378d65cba3e98330f98b48cf0fcc8c0769bce0d5958b6.jpg

2025-09-26 11:44:23 UTC

- reply

Even the wizards are calling you a piece of shit now.
RIP jb55s credibility
https://blossom.primal.net/d87b34d7c827277eb2e44590f88af49366075bd18ed08a4e7438c99c8eccb2ce.jpg

2025-09-26 02:16:16 UTC

Fuck Core Run Knots
https://blossom.primal.net/a360036fc105812dcf13368e5cb3fc6d02d7dc7d46fe60adcad68f4626b369df.jpg
https://blossom.primal.net/1306f61346b99b90d770846879a2e142c49a22dc4215596a3963f101a97cbab6.jpg

2025-09-26 01:54:56 UTC

- reply

https://blossom.primal.net/984b8a635686e27b9ead0a2c203ac450d57f4d2db4277c9ecd1659c11a7bb885.jpg

2025-09-26 01:28:42 UTC

- reply

Prepare your anus
https://blossom.primal.net/312260f43988745eae05fb3df0bfc06685f88d6f15c1d0d3c6a514924898726a.jpg

2025-09-26 01:26:51 UTC

- reply

Nobody gives a shit about convincing you of anything. Get over it

2025-09-26 00:53:22 UTC

- reply

*were

2025-09-26 00:51:09 UTC

- reply

Journalism?
https://blossom.primal.net/d35ee6f68145501c781990b55023b6dda732da9db9350c14a31f3d6640735418.gif

2025-09-25 22:20:22 UTC

- reply

https://blossom.primal.net/984b8a635686e27b9ead0a2c203ac450d57f4d2db4277c9ecd1659c11a7bb885.jpg

2025-09-25 22:19:19 UTC

- reply

https://blossom.primal.net/4c1bdcebd69a8803c2d00e242215d5eb945d5a1311edd1f5dd04e92c5ee8d5f8.jpg

2025-09-25 22:10:54 UTC

- reply

Now that these clowns have trashed their reputations there’s nothing holding them back from desperate smear campaign.
https://blossom.primal.net/3a8ddc1f22d2dfd1f94ca39ec5ba8835321359bfe7355f50a6668efba6360afb.jpg

2025-09-25 21:38:21 UTC

- reply

You should’ve kept pretending to be unbiased. You’re now full cringe. No going back now.
https://blossom.primal.net/190b3ef7ccb3abb8f61bf36a14b0c6fe4fddcd7d124b05a0b46c968e93121988.jpg

2025-09-25 20:01:43 UTC

- reply

https://blossom.primal.net/73080f361e0de5394ea0be6cb4005ce8a7d90d3824e3b08435874e9ddf56b87b.jpg

2025-09-25 19:02:19 UTC

Dump Core Run Knots
https://blossom.primal.net/73080f361e0de5394ea0be6cb4005ce8a7d90d3824e3b08435874e9ddf56b87b.jpg

2025-09-25 14:05:24 UTC

Dump Core Run Knots
https://blossom.primal.net/4ada86724d3da8f7d30235524e82ef218a748ed55cdeaef088133f7fbf160326.jpg

2025-09-25 03:44:09 UTC

Bitcoin Core getting absolutely eviscerated on twitter
https://blossom.primal.net/c0c0e857aa7843d825127153c00a7b2da37a0846ff25636f9c4688b3138355bf.jpg

2025-09-25 02:03:24 UTC

Dump Core Run Knots
https://blossom.primal.net/f73904f647d663c015bfde5bf24c67cb4ee96ac1f9c0672914bd9e1994ace756.jpg

2025-09-25 01:15:46 UTC

- reply

https://blossom.primal.net/ff8200adf4316160b4e98e5f5ef560cb8ce1cd8a6c426dba62d20a482b7616b5.jpg

2025-09-25 01:10:58 UTC

Dump Core Run Knots
https://blossom.primal.net/d6156a080193c5d687802166e1a559a2ba47556a4c7bfd373b21e56fb1a6fbd0.jpg

2025-09-24 22:41:55 UTC

Dump Core Run Knots
https://blossom.primal.net/5cd852ec2e188e6ad1924ac65c99415f17ff397db1fd2c26c9326bccf7c0482c.jpg

2025-09-24 17:18:06 UTC

- reply

I’m sure you’ll be an excellent uber driver.
https://blossom.primal.net/f781bfe1425513d1bba9f568ad314f060fc8e3b0b23710eb9c76fac2db28973d.jpg

2025-09-24 17:16:57 UTC

- reply

https://blossom.primal.net/def329211776a4d45094009a916c4e3e60cbaff54c5f4f4d24b0d5000816fa96.jpg

2025-09-24 16:02:33 UTC

- reply

https://blossom.primal.net/2d1480cab6bdcd0fe1b9ceb57a366dd9e15e97b91daa274f7a20b56b0a86cacd.jpg

2025-09-24 01:50:34 UTC

- reply

Home mining. Micro scale. For now.

2025-09-24 01:18:44 UTC

- reply

Hard pass

2025-09-24 01:06:51 UTC

- reply

https://blossom.primal.net/f781bfe1425513d1bba9f568ad314f060fc8e3b0b23710eb9c76fac2db28973d.jpg

2025-09-24 01:05:31 UTC

- reply

Lopp sounds like a politician. This kind of smear price just shows his desperation.
https://blossom.primal.net/312260f43988745eae05fb3df0bfc06685f88d6f15c1d0d3c6a514924898726a.jpg

2025-09-24 00:55:16 UTC

Dump Core Run Knots
https://blossom.primal.net/2d1480cab6bdcd0fe1b9ceb57a366dd9e15e97b91daa274f7a20b56b0a86cacd.jpg

2025-09-23 22:50:32 UTC

- reply

https://blossom.primal.net/2d1480cab6bdcd0fe1b9ceb57a366dd9e15e97b91daa274f7a20b56b0a86cacd.jpg

2025-09-23 22:43:38 UTC

- reply

https://blossom.primal.net/f781bfe1425513d1bba9f568ad314f060fc8e3b0b23710eb9c76fac2db28973d.jpg

2025-09-23 21:52:32 UTC

- reply

https://blossom.primal.net/8c4aefed3c3618af488172a0d099ce59aa1865f8d453de6d2b009e79d8a8c714.jpg

2025-09-23 21:50:20 UTC

- reply

https://blossom.primal.net/984b8a635686e27b9ead0a2c203ac450d57f4d2db4277c9ecd1659c11a7bb885.jpg

2025-09-23 21:48:27 UTC

- reply

This clown weighing in on the “seriousness” of anything is the most ironic thing I’ve witnessed in 2025. So far…
https://blossom.primal.net/1c92bd319a56dc299a8264a6066ac9a164308eb3cab9b6ca9162b15bdcb63115.jpg

2025-09-23 21:42:37 UTC

- reply

I’ll take an honest eccentric zealot over a flock of lying grifters all day.
https://blossom.primal.net/1dbfb48a2ad081e6d466bb06f36f3f2c8629bb912f029590115188c6a8f0e684.jpg

2025-09-22 21:45:56 UTC

- reply

You just need an external housing for the new drive. Clone. Swap. Done.
https://blossom.primal.net/5542851a445a07a5ab34e27647255ad6b5965975e4070b2d85630786d950d235.jpg

2025-09-22 21:10:25 UTC

- reply

https://blossom.primal.net/8c4aefed3c3618af488172a0d099ce59aa1865f8d453de6d2b009e79d8a8c714.jpg

2025-09-21 21:21:39 UTC

- reply

https://blossom.primal.net/1064ce69e43e57d11fe26526ed8e525a9f4671b852ac449373736624136d0a56.jpg

2025-09-21 01:30:09 UTC

- reply

https://blossom.primal.net/438acb7d8255d4f4dbf1456d9d224156efe6a9ee06c26e41881dc449dbead2e9.jpg

2025-09-20 18:43:15 UTC

- reply

Ending Core is the only solution
https://blossom.primal.net/f781bfe1425513d1bba9f568ad314f060fc8e3b0b23710eb9c76fac2db28973d.jpg

2025-09-20 11:43:58 UTC

- reply

https://blossom.primal.net/59298b7946cc4d38ef127b0ff00f7fd760d47dc1c56a0473043d5ba07e349670.jpg

2025-09-19 23:04:36 UTC

- reply

It makes really cool force field doors
https://blossom.primal.net/288b881acce1432e3a854c7973c0cb0fde1ed041851c382cccd38dd2b92465d2.jpg

2025-09-19 18:12:43 UTC

- reply

https://blossom.primal.net/f781bfe1425513d1bba9f568ad314f060fc8e3b0b23710eb9c76fac2db28973d.jpg

2025-09-19 16:50:26 UTC

- reply

https://blossom.primal.net/f781bfe1425513d1bba9f568ad314f060fc8e3b0b23710eb9c76fac2db28973d.jpg

2025-09-19 16:47:17 UTC

- reply

https://blossom.primal.net/c598a5cc099e4fb2caa6b92bd7be71195f7b307f192249ea84ab5d121fea4942.png

2025-09-19 16:45:22 UTC

- reply

https://blossom.primal.net/f781bfe1425513d1bba9f568ad314f060fc8e3b0b23710eb9c76fac2db28973d.jpg

2025-09-19 16:28:01 UTC

Dump Core Run Knots
https://blossom.primal.net/c598a5cc099e4fb2caa6b92bd7be71195f7b307f192249ea84ab5d121fea4942.png