Skip to content

feat: Gigahdx liquidations#1460

Draft
enthusiastmartin wants to merge 15 commits into
gigahdx-lockfrom
gigahdx-liquidations
Draft

feat: Gigahdx liquidations#1460
enthusiastmartin wants to merge 15 commits into
gigahdx-lockfrom
gigahdx-liquidations

Conversation

@enthusiastmartin
Copy link
Copy Markdown
Member

No description provided.

@github-actions
Copy link
Copy Markdown

Crate versions that have not been updated:

  • runtime-integration-tests: v1.85.0
  • pallet-gigahdx-rewards: v0.1.0
  • hydradx-runtime: v422.0.0

Crate versions that have been updated:

  • pallet-gigahdx: v0.1.1 -> v0.1.3
  • pallet-liquidation: v2.4.2 -> v2.5.0
  • hydradx-traits: v4.8.0 -> v4.9.0

hydradx-runtime: cargo and spec versions don't match.

Runtime version has been increased.

fn clear_conflicting_votes(who: &AccountId, max_remaining_hdx: Balance) -> Result<u32, DispatchError>;

/// Saturating reduction of the `pyconvot` lock by `amount`.
fn force_release_vote_lock(who: &AccountId, amount: Balance) -> Result<(), DispatchError>;
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i dont see this used in any prod code, is it intentional or we have some missing usage?

/// Emits `Liquidated` event when successful.
///
#[pallet::call_index(0)]
// Worst case is the gigahdx branch: up to 3 full-gas EVM calls
Copy link
Copy Markdown
Contributor

@dmoka dmoka May 29, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure if this is the best way to handle the benchmark of worst case.

In the current liqudate benchmark test, we use collateral asset hdx.

I see 2 options:

  • either we use gigahdx as collateral asset so we properly have the worst case here
  • or we introduce a new benchmark test for gigahdx branch, then in the weight macro we switch to it if collateral asset is gigahdx.

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.

2 participants