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

Initialize fees for (nearly) all transactions #250

Merged
merged 3 commits into from
Feb 24, 2024
Merged

Initialize fees for (nearly) all transactions #250

merged 3 commits into from
Feb 24, 2024

Conversation

AArnott
Copy link
Collaborator

@AArnott AArnott commented Feb 24, 2024

The only transactions that appear to be left with a null fee are the unshielded incoming (transparent->transparent), which is a lower priority since wallets don't typically need to display that to the user.

Closes #248

The only transactions that appear to be left with a null fee are the unshielded incoming (transparent->transparent), which is a lower priority since wallets don't typically need to display that to the user.
@AArnott AArnott merged commit f0ae7c3 into main Feb 24, 2024
6 checks passed
@AArnott AArnott deleted the fix248 branch February 24, 2024 15:24
AArnott pushed a commit that referenced this pull request Mar 2, 2024
Bumps [dotnet-coverage](https://github.com/microsoft/codecoverage) from 17.10.1 to 17.10.2.
- [Commits](https://github.com/microsoft/codecoverage/commits)

---
updated-dependencies:
- dependency-name: dotnet-coverage
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
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.

Report fees accurately
1 participant