Skip to content

fix: thread --announce-only through stake/liquidity/crowd submission paths#899

Open
bitloi wants to merge 1 commit intolatent-to:stagingfrom
bitloi:fix/issue-2-announce-only-stake-liquidity-crowd
Open

fix: thread --announce-only through stake/liquidity/crowd submission paths#899
bitloi wants to merge 1 commit intolatent-to:stagingfrom
bitloi:fix/issue-2-announce-only-stake-liquidity-crowd

Conversation

@bitloi
Copy link
Copy Markdown
Contributor

@bitloi bitloi commented Apr 3, 2026

Closes #898

--announce-only was accepted at the CLI layer but dropped on multiple stake/liquidity/crowd paths before extrinsic submission.

This change:

  • threads announce_only from CLI handlers into downstream command functions
  • passes announce_only to sign_and_send_extrinsic / sign_and_send_batch_extrinsic
  • fixes the interactive unstake -> unstake_all path to forward proxy + announce_only
  • keeps announce-only behavior consistent by disabling MEV shielding when announcing
  • adds regression tests for CLI forwarding and command-level forwarding across stake, liquidity, and crowd flows

@bitloi bitloi changed the base branch from main to staging April 3, 2026 00:36
@bitloi bitloi force-pushed the fix/issue-2-announce-only-stake-liquidity-crowd branch 2 times, most recently from ca5ba97 to 30fc840 Compare April 3, 2026 01:04
@bitloi bitloi force-pushed the fix/issue-2-announce-only-stake-liquidity-crowd branch from b4807ac to c420a37 Compare April 3, 2026 02:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

bug: --announce-only is silently dropped in stake/liquidity/crowd commands

1 participant