Document config file

[hantuzun]

Ordinals and inscriptions are protocols running on Bitcoin just like HTTP or IPFS are protocols running on transport protocols like TCP/IP. Protocols are content agnostic. The nodes however, could have a say on the content they engage with.

Below are my opinions on blocklist and allowlist functionalities (blacklist, whitelist, i.e. censorship) for inscriptions.

For platforms supporting graphic content, the nodes should be able to censor content. I'd prefer @casey to be able to censor inscriptions he doesn't like on ordinals.com as I think this would improve the chances of Inscriptions making a big impact.

It's inevitable for Inscriptions nodes to have censorship ability. Some IPFS nodes [1], and Ethereum RPC providers [2] and validator nodes [3] censor content today.

The earlier we have censorship ability for inscriptions, the less nodes will need to opt-in to censorship. Because, the earlier we have this functionality, the less controversial content will be inscribed.

• First, knowing that they can be censored today, there will be less incentives to inscribe controversial content.
• Second, ordinal theory will become less controversial over time, as it will benefit Bitcoin. This will reduce the incentives to inscribe controversial content to hurt the project.

Therefore, I suggest we start designing blocklist and allowlist functionalities.