Restrictions

[casey]

A hard requirement before launching on mainnet is that we can make future changes in such a way that we avoid breaking existing inscriptions.

One way to do this is to create restrictions which narrow down the set of inscriptions that we accept, so that we can add features and simultaneously relax those restrictions.

Looking at our future features, these restrictions could be:

• Only one inscription per sat. Inscriptions applied to already inscribed sat are invalid.
• Only one inscription per transaction. If there is more than one inscription in a transaction's inputs, all of them are ignored.
• Only taproot witnesses are checked for inscriptions. All other witnesses are ignored
• Only witnesses that do not contain OP_SUCCESS are checked for inscriptions.
• Disallow empty data pushes in the inscription body. An empty data push in the inscription body serves no purpose, and disallowing it could allow it to be used in the future.

There are a lot of restrictions here, but each is pretty simple to implement, so this would get us a path to launching on mainnet before too long.

[casey]

Closing this in favor of individual issues.