Casey Rodarmor

Let's add a `Wallet` struct that can only be constructed by loading the wallet: ```rust struct Wallet { foo: (), } impl Wallet { fn load(options: &Options) -> Result {...

Ahh, nice, maybe I was looking at an old tweet when we weren't using screenshots. Screenshots FTW!

This indicates that you already have a bitcoin core wallet named `ord`, so you might have already created an ord wallet.

> Hello! Impressive work done here. Thank you! > I'm interested in the inscription functionality by itself, decoupled from ordinals. I think this is interesting too, and I'd like to...

> I'm thinking these don't need functionality related to transferring them, they will just be "publications" of data. These would be the equivalent to Counterparty broadcasts, which are separate from...

This is my proposal: 1. Add a command to ord that doesn't require the index to be synced and which can make an inscription on a UTXO in the wallet....

> @casey, the changes proposed should work, but I still find them too coupled to ordinals. This burning you describe can still be done as ordinal's specific use cases though....

> I believe that the need to burn (and the disclaimer) already shows tight coupling. Maybe a separate non-ordinals-aware wallet is more appropriate for publishing... Maybe so! Let me know...

I honestly just haven't been convinced there is a real need not to just improve inscriptions here. So this should be turned into issues with specific asks (burn on inscribe,...

Leaving open, since a lot of those specific asks were covered in this issue's comments, and don't want to lose them.