feat(hypecli): add HIP-4 outcome commands - #78
Merged
Merged
Conversation
…question, negate)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds a new
hypecli outcomecommand group for HIP-4 outcome tokens:outcome list [--chain]: prints outcomes (ID, name, sides, description) and questions (ID, name, outcome IDs, settled IDs, fallback) from theoutcomeMetainfo endpoint, so users can discover the integer IDs the write commands need.outcome split --outcome --amount: split the quote token into one share of each side.outcome merge --outcome [--amount]: merge matching shares back into the quote token; omitting--amountmerges the maximum available.outcome merge-question --question [--amount]: merge a full set of mutually-exclusive outcomes within a question.outcome negate --question --outcome --amount: convert shares of one outcome into the complementary basket.Write commands reuse the shared
SignerArgsand follow thevault.rspattern (find_signer_sync+HttpClient+NonceHandler), passingNoneforvault_address/expires_afterlike the other write commands. SinceuserOutcomeis an L1 agent-signed action, agent (API wallet) keys work out of the box; this is now documented in--agent-helpand the--private-keyflag help.Verified: clean build, no new clippy warnings, help output for all subcommands, and
outcome listagainst live mainnet and testnet. Write paths are thin wrappers over the SDK methods exercised byexamples/hypercore/split_merge_outcome.rs; not yet exercised with a funded key from the CLI.