40% of Bitcoin’s current transactions are non-monatarian, and in June the network was processed Approximately 3 million metaprocedural transactionsa term that includes activities such as creating non-difficult tokens (NFTs) through protocols such as ordinals and issuance of assets such as runes and alkanes.
Every day, about 350,000 Bitcoin transactions are recorded, according to data shared by analysts on June 30th.
Of that number, Approximately 150,000 is a non-financial nature (registration)Covers Runes, BRC-20 Standard Tokens, Standard Tokens, Standard Tokens, Standard Tokens, Standard Tokens, Standard Tokens, Standard Tokens, Standard Tokens, Standard Tokens, Alkanes as seen in the following image referring to the operation of June 29th.
Those data, They represent 40% of the daily volumeemphasizing the use of chains that go beyond their original function as payment systems.
Metaprocol works when using data from Op_return or Witness segments (Witness) of transactions.spam»They crowd the network.
Knot pre-determined policies limit OP_RETURN transactions to 42 bytes, but most non-unilateral activities are allowed if you comply with this limit or use an alternative method.
However, nodes with knots reject these transactions, but other nodes may be in another block. So the knot nodes can delay these transactions from being included in the accounting a bit.
In contrast, Bitcoin Core, a reference client with almost 86% of the active nodes, currently allows 83 bytes, extending the limit for the version released in October 2025 to 100,000 bytes (V.30).
Knot node inconsistencies?
Bitcoin Knot has established itself as a tool to mitigate this phenomenon. but, Analysts revealed sarcasm: Despite focusing on filtering unwanted transactions, most of these non-monatary operations (particularly around 120,000 runes and alkanes out of 350,000 transactions per day) are allowed by knot nodes by default.
This occurs because knots limit a given policy. 40 useful data byteswill be added to 2 bytes OPCODEtechnical instructions that separate the start and end of that information.
Many transactions eliminate filters by relying on alternative methods such as op_return (by adjusting to this limit or relying on alternative methods such as using witness fields), such as storing data instead of op_return.
This situation Knot users may not notice,Analysts say that values and nodal sovereignty (individual control of nodes) above strict filtration must be that the node analyzes and rejects transactions directly from the mempool.
“I’m sure most knot users don’t know what’s actually going to happen with Bitcoin, and this could be a novelty for them,” he said.
The function of knots and their meaning
The knot manipulation allows operators to adjust the space dedicated to Op_return and provide flexibility.
By default, 40 bytes and 2 bytes OPCODE They establish basic restrictions, but those who want to include up to 80 actual databys must configure the function Datacarrierize a DataCarrierSize = 83. here, DataCarriersize It’s an option Defines the maximum data size that a node acceptsadapts to the needs of the user.
However, filters containing a 40-byte limit, Applies by default, but not requiredOperators can change them to prefer and allow transactions that respect established restrictions.
This design aims to reduce calls in some way.spam«, acts as a configurable filter as an order or non-financial data creation.
When 14% of nodes perform a knot, we expect transactions to be filtered, but the default policy does not block 40% of non-monatary operations. Because many people are following the rules or overlooked..
In that case, the validity depends on the user Initiatives to Strengthen the Configurationa step that many people don’t seem to give, directly linking the flexibility of the knot and the inability to fulfill its declared purpose.