feat: add HIP-4 userOutcome actions (split/merge/negate/mergeQuestion)#3
Conversation
HIP-4 added explicit userOutcome L1 actions after this repo's initial commit; the Python SDK (through 0.24.0) has no helpers for them. Add hand-signed wrappers and an example, and correct the docs that claimed no split/merge primitive existed. - hl4/outcome_actions.py: split_outcome, merge_outcome, negate_outcome, merge_question — signed via sign_l1_action + _post_action. - examples/13_split_merge.py: CLI for all four. - examples/11_mint_burn_demo.py, README.md: split explicit-actions vs engine classification; fees now zero; document fallback restrictions and that negate is unidirectional (mergeQuestion is its unwind). - pyproject.toml/uv.lock: bump hyperliquid-python-sdk floor to >=0.24.0. All four actions verified live on testnet (split/merge/negate/mergeQuestion round-trip returns to the exact starting balance).
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (6)
📝 WalkthroughWalkthroughAdds a new ChangesHIP-4 Explicit Outcome Actions
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
HIP-4 added explicit userOutcome L1 actions after this repo's initial commit; the Python SDK (through 0.24.0) has no helpers for them. Add hand-signed wrappers and an example, and correct the docs that claimed no split/merge primitive existed.
All four actions verified live on testnet (split/merge/negate/mergeQuestion round-trip returns to the exact starting balance).
Summary by CodeRabbit
New Features
Documentation
Chores