Tracker: Icepick configuration file #15
Labels
No Label
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: public/icepick#15
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We needed a good way to be able to quickly define trustable but arbitrary derivation paths and a way to say what modules are supported. A configuration format is a good way to achieve this.
Because the
icepick
CLI is defined by the module, this file must be defined without using CLI arguments. I have created theICEPICK_CONFIG_FILE
variable that offers the ability to specify an external file if necessary.Added
command_name
to allow custom commands... Maybe this system can also allowcommand_args
to allow passing in command-line arguments for custom coin transfer.For example, PYTH may call:
which then exports a CLI for PYTH.
This would work in contrast to my original example which was to define multiple binaries.
The first part of this is implemented and has been a part of my work in implementing IPDBG transfer.
Had to include an algorithm field for derived accounts.
Closing as this is now extended by #22, Icepick Workflows.