ordinally

Hey @cberner, @casey thought this might be a redb issue and we just should just throw it your way without any further analysis🤣

@casey now thinks ALL of them may have been spent as fees. Will follow that route later.

@casey seems to be right. This is inscriptions being sent to the coinbase. We do not decode this correctly. Encoding is this in `inscription_updater.rs:169` ```if is_coinbase { for flotsam in...

@cberner Yep, no redb issue.

Casey's initial take was he wanted to set the location like we do on purpose, but what's missing is a small piece of logic when decoding inscriptions to catch this....

Thanks, @gmart7t2 - this sounds very clear. Agree that your approach sounds right. Will take a look at the PR tomorrow. Thanks!

`ord wallet inscribe` is still broken with this PR: ``` error: Failed to send reveal transaction because: JSON-RPC error: RPC error response: RpcError { code: -26, message: "non-mandatory-script-verify-flag (Invalid Schnorr...

After some deep-diving on decoding the partially signed and fully signed reveal TXs when inscribing with a parent, I found that `sign_raw_transaction_with_wallet` apparently removes our inscription data from the witness...

Making progress. For anyone watching, this code does NOT meet our usual quality criteria yet, by far - lots of tests missing and some places are just held together by...

For casey, this was -txindex missing. Fix confirmed in https://www.youtube.com/watch?v=LXrUu8WOrHo Closing this issue.