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

chore: add begin block deployments to mock mainnet #1189

Closed
wants to merge 6 commits into from

Conversation

kingpinXD
Copy link
Contributor

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.

Closes:

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Include instructions and any relevant details so others can reproduce.

  • Tested CCTX in localnet
  • Tested in development environment
  • Go unit tests
  • Go integration tests
  • Tested via GitHub Actions

Checklist:

  • I have added unit tests that prove my fix feature works

@kingpinXD kingpinXD changed the title add begin blocked deployemnts for mock mainent chore: add begin block deployemtns to mock mainnet Sep 25, 2023
@kingpinXD kingpinXD changed the title chore: add begin block deployemtns to mock mainnet chore: add begin block deployments to mock mainnet Sep 25, 2023
// setup uniswap v2 factory
uniswapV2Factory, err := k.DeployUniswapV2Factory(ctx)
if err != nil {
return sdkerrors.Wrapf(err, "failed to DeployUniswapV2Factory")
Copy link
Member

Choose a reason for hiding this comment

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

We still sdkerrors with errorsmod some places

}
_, err = k.SetupChainGasCoinAndPool(ctx, common.EthChain().ChainId, "ETH", "ETH", 18)
if err != nil {
return errorsmod.Wrapf(err, fmt.Sprintf("failed to setupChainGasCoinAndPool for %s", common.EthChain().ChainName))
Copy link
Member

Choose a reason for hiding this comment

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

You don't need fmt.Sprintf since Wrapf can already format strings

return sdkerrors.Wrapf(err, "failed to DeployUniswapV2Factory")
}
ctx.EventManager().EmitEvent(
sdk.NewEvent(sdk.EventTypeMessage,
Copy link
Member

Choose a reason for hiding this comment

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

We're using sdk.EventTypeMessage but this is not a message event
Same below

Comment on lines +76 to +79
//err = k.SetGasPrice(ctx, big.NewInt(1337), big.NewInt(1))
if err != nil {
return err
}
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
//err = k.SetGasPrice(ctx, big.NewInt(1337), big.NewInt(1))
if err != nil {
return err
}

We're handling the error but the method is commented out

)

func (k Keeper) BlockOneDeploySystemContracts(_ context.Context) error {
func (k Keeper) BlockOneDeploySystemContracts(goCtx context.Context) error {
Copy link
Member

Choose a reason for hiding this comment

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

It looks like there are code we could factorize with the other networks privnet, testnet.

I think we would benefit of having a single function BlockOneSetup that group the setup operations logic common to all network and implement tests for this function since an error here or an inconsistency can prevent the network from working.

Could be another PR

@github-actions
Copy link

github-actions bot commented Oct 9, 2023

!!!WARNING!!!
nosec detected in the following files: zetaclient/bitcoin_client.go

Be very careful about using #nosec in code. It can be a quick way to suppress security warnings and move forward with development, it should be employed with caution. Suppressing warnings with #nosec can hide potentially serious vulnerabilities. Only use #nosec when you're absolutely certain that the security issue is either a false positive or has been mitigated in another way.

Only suppress a single rule (or a specific set of rules) within a section of code, while continuing to scan for other problems. To do this, you can list the rule(s) to be suppressed within the #nosec annotation, e.g: /* #nosec G401 */ or //#nosec G201 G202 G203
Broad #nosec annotations should be avoided, as they can hide other vulnerabilities. The CI will block you from merging this PR until you remove #nosec annotations that do not target specific rules.

Pay extra attention to the way #nosec is being used in the files listed above.

@github-actions github-actions bot added the nosec label Oct 9, 2023
brewmaster012 and others added 2 commits October 9, 2023 11:03
…1259)

* special handling to avoid duplicate payment on bitcoin outbound nonce 0

* use cctx amount instead of txResult's amount because it's not available in bitcoin mainnet

---------

Co-authored-by: charliec <[email protected]>
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