Skip to content

Always demand a key in a command #4643

@hMsats

Description

@hMsats

As an example, it's possible to fund a channel like this:

fundchannel 03854fa7f2babfe819c8f745c8fee50a15762236823328f61707519ec6e5e09fb5 100000 10000perkb 10

I find this very dangerous, hard to read and it must be really hard for the software to check the correctness and return a clear error message. Also, how would future versions add fixed order keys in between older keys and still be valid/understandable for non-upgraded node owners? I would suggest to always enforce the key=value. The above would then become:

fundchannel id=03854fa7f2babfe819c8f745c8fee50a15762236823328f61707519ec6e5e09fb5 amount=100000 feerate=10000perkb minconf=10

Much more readable according to me and I guess also for the software plus less dangerous for the user. I really don't understand why this is optional.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions