Bitcoin Core developer Luke Dashjr's proposal to limit inscriptions was not approved, and opinions among inscription developers are mixed

ChainCatcher news, the proposal "datacarriersize: Match more datacarrying #28408" initiated by Bitcoin Core developer Luke Dashjr discussed the issue of whether to restrict inscriptions. After discussions among several Bitcoin Core developers, it was not approved, and the proposal is currently marked as closed.

It is reported that Bitcoin Core developer Ava Chow summarized and closed this PR, stating that it is clear this proposal is controversial, and given the current situation, it is impossible to reach a conclusion that satisfies everyone, believing there is no need to continue the discussion.

Additionally, another Bitcoin Core code maintainer, gloria, summarized this PR.

Supporting Luke's viewpoint are:

1. Stop inscriptions; they are spam;
2. Inscriptions and embedded data can harm the network;
3. People want this: there is user demand and specific use cases that Bitcoin Core should provide; another option is for people to write and run patches, but this may be unsafe;
4. This is just fixing the data carrier size to work as intended;

Opposing Luke's viewpoint are:

1. This will not stop inscriptions; miners are unlikely to adopt this strategy as it is incompatible with incentives;
2. We cannot write code to detect all embedded data;
3. This PR changes the default mempool policy, posing potential harm to individual node operators and the network;

Other opposing viewpoints include:

1. Generally speaking, using mempool policies to block usage is ineffective;
2. Attempting to "review" transactions based on usage is inappropriate; the free market determines the use of Bitcoin;
3. This also changes the operation of -datacarriersize executed from underlying users.