You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Having a CLI available to do various operations in Mithril would be helpful for documenting, explaining and experimenting. Every language and environment can easily spawn processes or run shell commands so this would be provide a crude but simple integration point.
The text was updated successfully, but these errors were encountered:
Yes, this sounds helpful for experimenting. First thought for the CLI would be as follows (nothing set in stone):
./stm parameters -k 3 -m 10 -phi 1 <path-for-params># This must be run for different players
./stm stm-init -id <ID> -stake <STAKE><path-for-params><path-for-initialiser><path-for-broadcastable-data># This must be run for different players
./stm key-reg <path-for-broadcastable-data> [of all parties] <path-for-key-registration># This must be run for different players
./stm init-signer <path-for-initialiser><path-for-key-registration><path-for-signer># This must be run for different players
./stm try-signatures -m <MESSAGE><path-for-signer><path-for-parameters><path-to-store-valid-sigs># This needs to be performed a single time
./stm aggregate -m <MESSAGE><path-for-parameters><path-to-store-valid-sigs> [for all sigs] <path-for-aggregate-msig>
./stm verify-msig -m <MESSAGE><path-for-parameters><path-for-aggregate-msig>
All these calls can have the option of verbose where all the values will be printed to terminal. Maybe we want to allow for the CLI to take as input the serialised data as well?
Having a CLI available to do various operations in Mithril would be helpful for documenting, explaining and experimenting. Every language and environment can easily spawn processes or run shell commands so this would be provide a crude but simple integration point.
The text was updated successfully, but these errors were encountered: