Optimize On-Chain Data Storage

[adamkrellenstein]

We can store a lot more data on-chain using modern methods.

Support up to 400kb description fields, like Ordinals.

cf. https://bitcoin.stackexchange.com/questions/121686/data-op-drop-vs-op-return/121687#121687

Replaces: #1225

[loon3]

should also consider adding data storage via p2wsh outputs, https://github.com/mikeinspace/stamps/blob/main/OLGA.md

this is very similar to existing p2pkh storage, which uses fake addresses to store data in unspendable outputs

the benefit over something like the "inscription envelope" method is that it only requires one transaction vs two

[adamkrellenstein]

we can also use this for storing the destination value...

[pinnate-modo]

Building on what @wasthatawolf said, could we in theory encode txs in spendable p2wsh addresses? The witness script would look like this: OP_FALSE OP_IF <counterparty_data> OP_ENDIF OP_ELSE <pubkey> OP_CHECKSIG.