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

Integrate IBC burn rate and send commission. #489

Merged
merged 9 commits into from
May 17, 2023

Conversation

dzmitryhil
Copy link
Contributor

@dzmitryhil dzmitryhil commented May 16, 2023

This change is Reviewable

* Fetch address prefix, chainID, and denom form the chain VIA GRPC.
* Instantiate multiple chains for the testing (coreum, gaia).
* Update the testing utils to support the submission of the TXs using the sdk.Account with different prefixes.
* Integrate the faucet for the gaia chain.
* Refactor IBC helpers and add 2-way integration tests.
Use correct channels for the denom building.
# Conflicts:
#	integration-tests/chain.go
#	integration-tests/faucet.go
#	integration-tests/ibc/transfer_test.go
#	integration-tests/init.go
#	integration-tests/tx.go
#	integration-tests/upgrade/upgrade_test.go
Copy link
Collaborator

@wojtek-coreum wojtek-coreum left a comment

Choose a reason for hiding this comment

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

Reviewed 8 of 9 files at r1, all commit messages.
Reviewable status: 8 of 9 files reviewed, 1 unresolved discussion (waiting on @dzmitryhil, @miladz68, @silverspase, and @ysv)


app/app.go line 342 at r1 (raw file):

	originalBankKeeper := bankkeeper.NewBaseKeeper(appCodec, keys[banktypes.StoreKey], app.AccountKeeper, app.GetSubspace(banktypes.ModuleName), app.ModuleAccountAddrs())
	var ibcChannelKeeper ibcchannelkeeper.Keeper
	assetFTKeeper := assetftkeeper.NewKeeper(

can't it be done after initializing ibc keeper to avoid the trick with pointer to predclared ibcChannelKeeper?

Copy link
Contributor Author

@dzmitryhil dzmitryhil left a comment

Choose a reason for hiding this comment

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

Reviewable status: 8 of 9 files reviewed, 1 unresolved discussion (waiting on @miladz68, @silverspase, @wojtek-coreum, and @ysv)


app/app.go line 342 at r1 (raw file):

Previously, wojtek-coreum (Wojtek) wrote…

can't it be done after initializing ibc keeper to avoid the trick with pointer to predclared ibcChannelKeeper?

Nope. The IBC keeper uses the staking keeper in the New function and checks whether it's nill, and the bank module is used in the staking keeper. So I've not found a better approach.

Copy link
Contributor

@miladz68 miladz68 left a comment

Choose a reason for hiding this comment

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

:lgtm:

Reviewed 8 of 9 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @dzmitryhil, @silverspase, @wojtek-coreum, and @ysv)


.github/workflows/ci.yml line 83 at r2 (raw file):

          repository: CoreumFoundation/crust
          path: crust
          ref: dzmitryhil/add-osmosis-testing-flags # FIXME remove once merged

you can define the flags here, and use the correct default values to pass the tests.

Copy link
Contributor Author

@dzmitryhil dzmitryhil left a comment

Choose a reason for hiding this comment

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

Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @miladz68, @silverspase, @wojtek-coreum, and @ysv)


.github/workflows/ci.yml line 83 at r2 (raw file):

Previously, miladz68 (milad) wrote…

you can define the flags here, and use the correct default values to pass the tests.

I wanted to be sure the with the new flags wich the crust intoduces it will pass.

Copy link
Contributor

@miladz68 miladz68 left a comment

Choose a reason for hiding this comment

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

Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @dzmitryhil, @silverspase, @wojtek-coreum, and @ysv)


.github/workflows/ci.yml line 83 at r2 (raw file):

Previously, dzmitryhil (Dzmitry Hil) wrote…

I wanted to be sure the with the new flags wich the crust intoduces it will pass.

well now that you do, you can remove the branch name right ? there is not need to merge it into master with a FIXME

Copy link
Contributor Author

@dzmitryhil dzmitryhil left a comment

Choose a reason for hiding this comment

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

Reviewable status: all files reviewed, 2 unresolved discussions (waiting on @miladz68, @silverspase, @wojtek-coreum, and @ysv)


.github/workflows/ci.yml line 83 at r2 (raw file):

Previously, miladz68 (milad) wrote…

well now that you do, you can remove the branch name right ? there is not need to merge it into master with a FIXME

The osmosis IBC on the crust master doesn't work so that branch also contains the changes to fix it.

Copy link
Contributor

@miladz68 miladz68 left a comment

Choose a reason for hiding this comment

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

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @silverspase, @wojtek-coreum, and @ysv)

Copy link
Collaborator

@wojtek-coreum wojtek-coreum left a comment

Choose a reason for hiding this comment

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

Reviewed 1 of 9 files at r1, 1 of 1 files at r2, all commit messages.
Reviewable status: :shipit: complete! all files reviewed, all discussions resolved (waiting on @silverspase and @ysv)

@dzmitryhil dzmitryhil merged commit 1544ab4 into master May 17, 2023
@dzmitryhil dzmitryhil deleted the dzmitryhil/burn-send-rate-ibc branch May 17, 2023 09:38
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.

3 participants