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

txnbuild: Properly calculate claimable balance IDs with muxed accounts. #3678

Merged
merged 4 commits into from
Jun 9, 2021

Conversation

Shaptic
Copy link
Contributor

@Shaptic Shaptic commented Jun 8, 2021

PR Checklist

PR Structure

  • This PR has reasonably narrow scope (if not, break it down into smaller PRs).
  • This PR avoids mixing refactoring changes with feature changes (split into two PRs
    otherwise).
  • This PR's title starts with name of package that is most changed in the PR, ex.
    services/friendbot, or all or doc if the changes are broad or impact many
    packages.

Thoroughness

  • This PR adds tests for the most critical parts of the new functionality or fixes.
  • I've updated any docs (developer docs, .md
    files, etc... affected by this change). Take a look in the docs folder for a given service,
    like this one.

Release planning

  • I've updated the relevant CHANGELOG (here for Horizon) if
    needed with deprecations, added features, breaking changes, and DB schema changes.
  • I've decided if this PR requires a new major/minor version according to
    semver, or if it's mainly a patch change. The PR is targeted at the next
    release branch if it's not a patch change.

What

Uses the unmuxed transaction source account when calculating claimable balance IDs.

Why

Fixes #3676.

Known limitations

n/a

@Shaptic Shaptic requested a review from a team June 8, 2021 22:07
@Shaptic Shaptic added the bug label Jun 8, 2021
@Shaptic Shaptic self-assigned this Jun 8, 2021
@Shaptic Shaptic requested a review from jonjove June 8, 2021 22:07
Copy link
Contributor

@bartekn bartekn left a comment

Choose a reason for hiding this comment

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

Good catch!

@Shaptic Shaptic merged commit c1d3637 into stellar:master Jun 9, 2021
@Shaptic Shaptic deleted the fix-claimable-balances branch June 9, 2021 00:26
* `BaseFee` in `TransactionParams` when calling `NewTransaction` is allowed to be zero because the fee can be paid by wrapping a `Transaction` in a `FeeBumpTransaction`. ([#3622](https://github.com/stellar/go/pull/3622))
* `BaseFee` in `TransactionParams` when calling `NewTransaction` is allowed to be zero because the fee can be paid by wrapping a `Transaction` in a `FeeBumpTransaction` ([#3622](https://github.com/stellar/go/pull/3622))

* Claimable balance IDs are now precomputed correctly (``Transaction.ClaimableBalanceID(int)`) even when the transaction's source account is a fully-muxed account ([#3678](https://github.com/stellar/go/pull/3678)).
Copy link
Contributor

Choose a reason for hiding this comment

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

There is quoting typo:

``Transaction.ClaimableBalanceID(int)`

should be

`Transaction.ClaimableBalanceID(int)`

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yep, thank you! I fixed this in #3679.

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

Successfully merging this pull request may close these issues.

When using muxed accounts, claimable balance IDs aren't calculated correctly.
3 participants