should inscriptions be optional in batchfile?

[rot13maxi]

Right now a batch file requires inscriptions . Since the interface for etching runes is through the inscribe command, should we allow this to be optional if you only want to etch runes and are not trying to inscribe something? I'm happy to write the PR, want to make sure there's not an intent here that I'm missing before I go make all the updates

[raphjaph]

I think this would be a great addition!

Since we use the inscription envelope for the commit/reveal of the rune name. It would have to create an inscription with no content. And then on the runes page, if the inscription has no content, it shouldn't be shown

[casey]

I think if we do this, the inscriptions field should still be present, but marked somehow as having no content, since creating a rune will still create an inscription, to store the commitment.

[GiantDole]

+1 on this feature :)

[0xprames]

+1

[raphjaph]

Closed by #3451

[gus4rs]

@raphjaph inscriptions are still required in the batch file

error: missing field `inscriptions` at line 23 column 1

ord --version
ord 0.18.1

[raphjaph]

you can do:

inscriptions:
-

It's a bit janky for now but works.

[gus4rs]

It creates an inscription s

you can do:

inscriptions:
-

It's a bit janky for now but works.

It actually creates an inscription without a file along with the etch, so no, it doesn't work

[ensfn]

you can do:

inscriptions:
-

It's a bit janky for now but works.

@raphjaph It doesn't work, still creates inscription with outrageous fees (at least for me for some reason). Can you provide guidance on how can I remove validations for that part of the code so I can do it at my own risk?

Thanks