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

feat (l2): hard fork #591

Open
wants to merge 18 commits into
base: main
Choose a base branch
from
Open

feat (l2): hard fork #591

wants to merge 18 commits into from

Conversation

faultytolly
Copy link
Contributor

Description


Closes #XXX

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow-up issues.

PR review checkboxes:

I have...

  • Added a relevant changelog entry to the Unreleased section in CHANGELOG.md
  • Targeted PR against the correct branch
  • included the correct type prefix in the PR title
  • Linked to the GitHub issue with discussion and accepted design
  • Targets only one GitHub issue
  • Wrote unit and integration tests
  • Wrote relevant migration scripts if necessary
  • All CI checks have passed
  • Added relevant godoc comments
  • Add an issue in the e2e-tests repo if necessary

SDK Checklist

  • Import/Export Genesis
  • Registered Invariants
  • Registered Events
  • Updated openapi.yaml
  • No usage of go map
  • No usage of time.Now()
  • Used fixed point arithmetic and not float arithmetic
  • Avoid panicking in Begin/End block as much as possible
  • No unexpected math Overflow
  • Used sendCoin and not SendCoins
  • Out-of-block compute is bounded
  • No serialized ID at the end of store keys
  • UInt to byte conversion should use BigEndian

Full security checklist here


For Reviewer:

  • Confirmed the correct type prefix in the PR title
  • Reviewers assigned
  • Confirmed all author checklist items have been addressed

After reviewer approval:

  • In case the PR targets the main branch, PR should not be squash merge in order to keep meaningful git history.
  • In case the PR targets a release branch, PR must be rebased.

@faultytolly faultytolly requested a review from a team as a code owner November 5, 2024 13:39
proto.MessageName(&vestingtypes.PermanentLockedAccount{}): {},
}

const BumpSequence = 1_000_000_000
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
const BumpSequence = 1_000_000_000
const BumpSequence = 10_000_000_000


ctx := sdk.UnwrapSDKContext(goCtx)

var allErrors error
Copy link
Contributor

Choose a reason for hiding this comment

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

This is weird, you're making a stack of errors
You should only call Join once

Comment on lines +147 to +161
err := m.bumpAccountSequence(ctx, account)
allErrors = errors.Join(allErrors, err)
} else {
// check if it can be handled by something custom
for _, f := range m.accountBumpFilters {
toBump, err := f(accType, account)
if err != nil {
allErrors = errors.Join(allErrors, fmt.Errorf("filter account: %w", err))
return false
}
if toBump {
err := m.bumpAccountSequence(ctx, account)
allErrors = errors.Join(allErrors, err)
break
}
Copy link
Contributor

Choose a reason for hiding this comment

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

Can refac to only call bump once


err := m.upgradeKeeper.ScheduleUpgrade(ctx, upgradetypes.Plan{
Name: fmt.Sprintf("upgrade-drs-%d", drs.DrsVersion),
Height: ctx.BlockHeight() + 1,
Copy link
Contributor

Choose a reason for hiding this comment

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

+1?

Copy link
Contributor

Choose a reason for hiding this comment

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

agree, not sure why the upgrade is scheduled in the next block and not the same..

Comment on lines 197 to 201
func (m msgServer) updateDrsVersion(ctx sdk.Context, drsVersion uint64) {
oldParams := m.rollapParamsKeeper.GetParams(ctx)
oldParams.DrsVersion = uint32(drsVersion)
m.rollapParamsKeeper.SetParams(ctx, oldParams)
}
Copy link
Contributor

Choose a reason for hiding this comment

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

is it easier to just leave this to the upgrade?

Copy link
Contributor

Choose a reason for hiding this comment

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

no need to do it here imo

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I think is better here, the upgrade handler I think is responsability of the rollapp, as it kind of case by case and it can't be generic?

@danwt
Copy link
Contributor

danwt commented Nov 11, 2024

+1 height is a blocker

Copy link
Contributor

@srene srene left a comment

Choose a reason for hiding this comment

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

why do we have two separate consensus messages for the upgrade? bump account sequencers + updateDRS? couldnt we do it with a unique upgradedrs message and include the drs update version and bumpsequences logic in the necssary upgrade handler?


err := m.upgradeKeeper.ScheduleUpgrade(ctx, upgradetypes.Plan{
Name: fmt.Sprintf("upgrade-drs-%d", drs.DrsVersion),
Height: ctx.BlockHeight() + 1,
Copy link
Contributor

Choose a reason for hiding this comment

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

agree, not sure why the upgrade is scheduled in the next block and not the same..


m.updateDrsVersion(ctx, drs.DrsVersion)

err := m.upgradeKeeper.ScheduleUpgrade(ctx, upgradetypes.Plan{
Copy link
Contributor

Choose a reason for hiding this comment

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

i think besides the scheduleupgrade we need to call the SetUpgradeHandler, otherwise it the node stops necause it does not find an upgraded handler for the scheduled upgrade.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

but we dont have a way to setup a generic handler

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The way it works is that it uses the upgrade name to get the handler, I understand when the fork happens there will be a consensus on the next version of the app to use. And this version should include a handler.

@danwt
Copy link
Contributor

danwt commented Nov 12, 2024

@srene

why do we have two separate consensus messages for the upgrade? bump account sequencers + updateDRS? couldnt we do it with a unique upgradedrs message and include the drs update version and bumpsequences logic in the necssary upgrade handler?

Hey sergi

-Not all upgrades will require sequence bump
-Sometimes you want to sequence bump without upgrade

ctx := sdk.UnwrapSDKContext(goCtx)

var allErrors error
m.accountKeeper.IterateAccounts(ctx, func(account authtypes.AccountI) bool {
Copy link
Collaborator

Choose a reason for hiding this comment

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

why u not breaking with error on the first error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants