Ord ignores valid 4-byte deploy inscriptions with invalid self-mint fields #61
Description
OKX-ORD ignores the following Signet inscription:
https://mempool.space/signet/tx/a2c59a69a75e619000e95679eeda3e1f3a7a5cfb696ba4a6bf7e5c631ef2f332
It's because the self_mint field isn't a valid string field (refer to the inscription content below) it fails to deserialize, but as per BRC20 rules, the field should be ignored and set to false when it's invalid.
Also, for 4 byte tickers, self_mint is always false and should be ignored.
{
"p": "brc-20",
"op": "deploy",
"tick": "TRIO",
"max": "21000000",
"lim": "21000000",
"self_mint": true
}
It's a valid deploy according to Unisat https://uniscan.cc/signet/brc20/trio and BiS OPI https://signet.bestinslot.xyz/ordinals/brc20/trio
Similar inscriptions can show up in mainnet too, so I'll fix this in a PR.