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.