Skip to content

Force Nova pool for Asset Hub and lock Novasama validators in selection#2268

Open
Leemo94 wants to merge 2 commits intonovasamatech:developfrom
Leemo94:feature/staking-nova-pool-locked-validators
Open

Force Nova pool for Asset Hub and lock Novasama validators in selection#2268
Leemo94 wants to merge 2 commits intonovasamatech:developfrom
Leemo94:feature/staking-nova-pool-locked-validators

Conversation

@Leemo94
Copy link
Copy Markdown

@Leemo94 Leemo94 commented Mar 20, 2026

  • Bypass pool selection screen for Polkadot/Kusama Asset Hub chains; recommendation system selects Nova pool and user cannot change it
  • Pool name hidden on staking type screen; "Recommended" label persists
  • Preferred (Nova) validators locked at bottom of custom validator list with greyed-out checkboxes; cannot be deselected via tap, search, edit-mode delete, or "Deselect All"
  • Selection count reflects community-only available slots

- Bypass pool selection screen for Polkadot/Kusama Asset Hub chains;
  recommendation system selects Nova pool and user cannot change it
- Pool name hidden on staking type screen; "Recommended" label persists
- Preferred (Nova) validators locked at bottom of custom validator list
  with greyed-out checkboxes; cannot be deselected via tap, search,
  edit-mode delete, or "Deselect All"
- Selection count reflects community-only available slots

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
- Move FORCED_NOVA_POOL_CHAIN_IDS from top-level val to forcedPoolChainIds
  property on the KnownNovaPools interface; implement on FixedKnownNovaPools
- Inject KnownNovaPools into EditableStakingTypeItemFormatter via
  SetupStakingTypeModule so the forced-chain check goes through DI instead
  of directly importing the constant
- Use injected knownNovaPools.forcedPoolChainIds in SetupPoolStakingFlowExecutor
  (dependency was already wired) instead of the top-level constant
- Fix import ordering in SetupStakingTypeModule

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@Leemo94
Copy link
Copy Markdown
Author

Leemo94 commented Apr 18, 2026

CI failures here seem to be the standard fork-secrets restriction (scaleway/action-scw-secret can't authenticate without the access key, which GitHub doesn't expose to fork PRs).

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.

1 participant