Bitcoin recorded its largest mined block at the time when Luxor mining pool produced block #774,628 at roughly 3.96 MB. The block contained only 63 transactions, but one of them dominated the discussion: a massive 3.94 MB Ordinal inscription featuring a “Taproot Wizard” image. The event quickly became a flashpoint in the growing debate over what should be stored on the Bitcoin blockchain and whether blockspace should primarily serve monetary transfers or broader forms of data publication.
How a Near-4 MB Bitcoin Block Became Possible
The record block did not emerge in a vacuum. Its technical backdrop lies in Taproot, the Bitcoin upgrade activated in November 2021, and in the way users later combined Taproot with the witness structure introduced by Segregated Witness, or Segwit. Taproot was designed to improve transaction efficiency and privacy by enabling more flexible scripting and signature aggregation. However, developers and users discovered that these features could also be used to insert large amounts of arbitrary data into witness fields at a discounted weight cost.
That combination made it possible for a Bitcoin block to approach 4 MB in effective size, even though Bitcoin’s historic block size limit is commonly discussed as 1 MB. Prior to Luxor’s block, the largest known block had been around 2.765 MB, mined in August 2022. The new record therefore represented a meaningful jump and demonstrated in practical terms how inscriptions could consume a large share of available blockspace.
Luxor acknowledged the event publicly and framed it playfully on social media, saying it had used “magic energy” to free an ancient wizard from a cosmic cage. The mining pool attached the image known as “Taproot Wizard,” listed as Ordinal inscription #652, and presented the block as a novel moment in Bitcoin’s history. For supporters of inscriptions, the episode was proof of Bitcoin’s expanding expressive capacity. For critics, it was evidence that the network was being pushed in an undesirable direction.
Why the Ordinals Debate Escalated
Ordinals were already controversial among parts of the Bitcoin community before the record block appeared. The protocol allows users to assign unique data to individual satoshis, enabling forms of Bitcoin-native collectibles often described as NFTs on Bitcoin. Supporters view the trend as an innovative use of Bitcoin’s security and permanence. Critics argue that it is a poor fit for a system whose main purpose is censorship-resistant money.
The fact that the block held only 63 transactions amplified the backlash. To some Bitcoin advocates, a nearly full block should ideally process a large number of financial transfers rather than archive a single oversized JPEG. In online discussions, critics argued that the blockspace consumed by the wizard image could have been used by thousands of ordinary users making monetary transactions. This concern goes beyond aesthetics or ideology: blockspace is scarce, and when one type of activity uses more of it, the economics of fees and access may shift for everyone else.
One widely shared criticism was that there was nothing technologically revolutionary about stuffing a large image into a block. Detractors argued that the same image could have been stored in a much smaller form and accused the creators of inflating its size simply to make a point or provoke the community. The criticism reflected a broader discomfort with the idea that Bitcoin’s limited blockspace could be used for spectacle rather than payments.
Developers Warn About Spam and Filtering
The controversy deepened when longtime Bitcoin developer Luke Dashjr described Ordinals as an “attack.” In response, he quickly produced a node patch intended to filter or censor what he characterized as Ordinal “spam.” Dashjr also clarified that the patch was not a protocol change, soft fork, or hard fork, but rather a temporary filtering measure. Even so, the move illustrated how seriously some participants viewed the issue.
That distinction matters. A protocol-level change would require broad consensus and would alter Bitcoin’s rules. A node-level filter, by contrast, is a local operational response that can be adopted or ignored by node operators. Still, the emergence of such a patch signals that the debate is no longer only philosophical. It now extends into software behavior, policy enforcement, and the practical question of how much discretion infrastructure operators should exercise over transaction relay and acceptance.
For critics of inscriptions, filtering appears to be a defensive measure against the misuse of blockspace. For supporters, such proposals risk undermining Bitcoin’s neutrality by introducing subjective judgments about which transactions are legitimate. That tension sits at the center of the dispute: if Bitcoin is open and permissionless, who gets to decide what counts as acceptable use?
Immutable Content and the Problem of Permanence
Another major concern raised by the record block was the immutable nature of Bitcoin data. Once controversial or offensive material is inscribed and confirmed on-chain, it cannot simply be removed from the blockchain itself. This property is part of what gives Bitcoin credibility as an incorruptible ledger, but it also creates a challenge when the network is used to store non-financial content.
The report noted that, aside from the wizard image, inscription #668 contained an unsavory image. Although that image was reportedly removed from the Ordinals website, it remained on the Bitcoin blockchain and could not be deleted at the ledger level. The same report also pointed to inscription #466, where the game DOOM had been uploaded to the blockchain. These examples sharpened concerns among Bitcoin’s small-block supporters, who warned that once arbitrary data storage becomes normalized, the chain could end up preserving material that many users find objectionable or dangerous.
Critics described a future in which one malicious actor, or even one automated miner willing to prioritize such transactions, could repeatedly lock disturbing content into a globally distributed and effectively uncensorable database. That scenario has alarmed people who view Bitcoin as a monetary system first and foremost. Their concern is not simply that undesirable content exists, but that Bitcoin’s own guarantees of permanence and replication become the mechanism that preserves it.
A Renewed Blocksize War, or a Passing Shock?
The appearance of a nearly 4 MB block led some observers to ask whether Bitcoin was entering a new kind of “blocksize war.” Historically, Bitcoin has experienced deep disagreements over how much data blocks should carry and whether scaling should happen on-chain or through additional layers. The new controversy is different in form but similar in spirit. This time, the argument is less about changing protocol limits directly and more about how existing rules can be used in ways some participants consider contrary to Bitcoin’s original purpose.
Supporters of small blocks tend to see the event as a warning sign. In their view, if blockspace is increasingly captured by large inscriptions, the result could be higher fees, heavier burdens on nodes, and a cultural shift away from peer-to-peer money toward generalized data storage. They also worry that the social legitimacy of Bitcoin could be tested if more offensive or legally contentious content is preserved on-chain.
On the other side, defenders of inscriptions can point out that the record block did not break Bitcoin’s consensus rules. It used features already available under the network’s current design. From that perspective, the block was not an exploit in the sense of violating consensus, but an emergent use case enabled by previous upgrades. If Bitcoin is truly permissionless, they argue, then users should be free to compete for blockspace, and miners should be free to include the transactions that pay for it.
What the Record Block Means for Bitcoin
Luxor’s block #774,628 may ultimately be remembered less for its wizard image than for what it revealed about Bitcoin’s unresolved identity questions. Is Bitcoin a narrowly focused settlement network optimized for monetary transfers, or is it a more open platform where users can publish durable data if they are willing to pay for blockspace? The technology does not settle that question by itself; the answer will emerge from the interaction of miners, developers, node operators, wallet providers, and users.
What is clear is that the record block intensified an already heated discussion. It highlighted the practical effects of Taproot-era transaction design, demonstrated that very large inscriptions were viable on-chain, and forced the community to confront the trade-offs of immutability in a broader data environment. Whether the event becomes the start of a lasting policy shift or remains a symbolic episode, it has already reshaped the conversation around Bitcoin blockspace, neutrality, and the limits of acceptable on-chain expression.