Explore gas cost modifications for memo field

[rootulp]

Context

CIAS is a project that applied inscriptions to Celestia. Instead of using blob data, they used the memo field.

For example, this tx has a memo field that base64 decodes to

data:,{"op":"cancel","amt":3230000,"tick":"cias","p":"cia-20"}

Problem

The gas cost of bytes in the memo field may be mis-priced relative to blobs. Ideally Celestia should enable use cases like inscriptions but encourage them to use blobs rather than memos.

Proposal

We've discussed three concrete gas modifications to encourage users to use blobs instead of memos.

1. Consider decreasing auth.MaxMemoCharacters from 256 bytes => 16 or 32 bytes
2. Consider adding a fixed cost for txs that contain memos
3. Consider increasing auth.TxSizeCostPerByte from 10 to something higher

Write a short doc that explores these 3 options.

cc: @nashqueue @cmwaters

[rootulp]

https://hackmd.io/@rootulp/gas-repricing