Considerations re: enriched Deposits workflow

[NiloCK]

OP-stack deposits allow for depositing of transactions, which are executed on the L2, not simply value, which is minted on the L2.

Monomer's support for deposits is currently limited to value minting. This has implications for an AppChain's censorship resistance.

The workflow for including deposits is that all L1 user initiated deposits are bundled with the L1Attributes deposit tx as a single cosmos-sdk.types.tx transaction with a custom message body.

Current planning for processing the L1 deposits is to bypass (or alter) some standard checks (AnteHandler), but passing arbitrary user-defined transactions through reduced checks is a security hazard.

Potentially: the minting portion of the user initiated deposits could be decoupled from the transaction execution portion. Then, minting could remain bundled with the L1Attributes deposit for guaranteed execution, and the associated transaction data could be packaged processed as regular sdk transactions to succeed or fail according to the normal logic of the AppChain.