Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Axelar with main merged, fixes, upgrade updates #236

Merged
merged 127 commits into from
Dec 10, 2023
Merged

Conversation

EricBolten
Copy link
Contributor

Cleanly merge main into Axelar, fix some bugs, update the v7 upgrade handler.

We're long since past v4 and it breaks on the new Cosmos SDK. Was only
here for historical reasons.
-----END CERTIFICATE-----
`

const FrenchChocolatineSubscriberCA = `-----BEGIN CERTIFICATE-----
Copy link
Member

Choose a reason for hiding this comment

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

Probably fine for this PR but I know at least this validator has dropped from the active set. Would it be worth culling inactive validators from this list? I can go through the list if you need me to.

Copy link
Contributor Author

@EricBolten EricBolten Dec 10, 2023

Choose a reason for hiding this comment

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

I double-checked all the validators in the upgrade against steward-registry and left in the inactive ones, just to have this mirror the current state we're working with. If you want to spend the time to verify which ones we should remove, go for it, although there isn't really a method for scrubbing dead subscribers post-upgrade unless they delete their subscriber themselves, I don't think. So there will likely be cruft no matter what.

Copy link
Member

Choose a reason for hiding this comment

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

Ah, probably needed then

Copy link
Member

@cbrit cbrit left a comment

Choose a reason for hiding this comment

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

LGTM

@@ -49,38 +49,73 @@ func auctionInitGenesis(ctx sdk.Context, auctionKeeper auctionkeeper.Keeper) {
genesisState := auctiontypes.DefaultGenesisState()

usomm52WeekLow := sdk.MustNewDecFromStr("0.079151")
eth52WeekHigh := sdk.MustNewDecFromStr("2359.89")
Copy link
Contributor

Choose a reason for hiding this comment

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

I am wondering if we about multiply these prices by 1.5 given market conditions

Copy link
Contributor Author

Choose a reason for hiding this comment

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

We could, 52 week high is an arbitrary choice. At the same time, since prices are denominated in SOMM and we are choosing SOMM's 52 week low, it should have the effect of overpricing in most market conditions. But perhaps adding a flat multiplier on top of it as a param or something would be a good move. We can also control when these prices time out with that auction parameter so they'll have to be updated every N blocks.

@EricBolten EricBolten merged commit 10451f0 into main Dec 10, 2023
9 checks passed
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.

4 participants