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

[ZCash] Add shardtree + zcash_client_backend crates #26474

Closed
wants to merge 1 commit into from

Conversation

cypt4
Copy link
Collaborator

@cypt4 cypt4 commented Nov 11, 2024

Resolves brave/brave-browser#40408

Previous pr : #25092
Audit : https://github.com/brave/reviews/issues/1724
zcash_client_backend audit: https://github.com/brave/reviews/issues/1799

Submitter Checklist:

  • I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally:
    • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
    • npm run presubmit wiki, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

@github-actions github-actions bot added CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) feature/web3/wallet feature/web3/wallet/core labels Nov 11, 2024
@cypt4 cypt4 changed the title Add shardtree crate [ZCash] Add shardtree crate Nov 11, 2024
@cypt4 cypt4 changed the title [ZCash] Add shardtree crate [ZCash] Add shardtree + zcash_client_backend crates Nov 13, 2024
@cypt4 cypt4 marked this pull request as ready for review November 19, 2024 10:37
@cypt4 cypt4 requested review from a team, fmarier and bridiver as code owners November 19, 2024 10:37
Copy link
Member

@fmarier fmarier left a comment

Choose a reason for hiding this comment

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

script/brave_license_helper.py changes 👍

@@ -0,0 +1,383 @@
# This file is automatically @generated by Cargo.
Copy link
Collaborator

Choose a reason for hiding this comment

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

this is odd, I wonder why this was added if bitflags is already vendored and no version changes. cc @cdesouza-chromium

Copy link
Collaborator

Choose a reason for hiding this comment

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

This file can be deleted. I've rebased this branch and ran gnrt and it seems to be all good. This PR needs to be rebased anyway, and gnrt has to be rerun, because otherwise we will have a dirty gnrt run tree in master. I would advise to delete this folder, and run gnrt with this PR on master.

@@ -242,3 +242,8 @@ package = "zerocopy"
[patch.crates-io.zerocopy_derive_v0_7]
path = "../../../../third_party/rust/chromium_crates_io/vendor/zerocopy-derive-0.7.35"
package = "zerocopy-derive"

[patch.crates-io.zcash_client_backend_v0_12]
path = "../../../components/brave_wallet/browser/zcash/rust/librustzcash/src/zcash_client_backend"
Copy link
Collaborator

@bridiver bridiver Nov 19, 2024

Choose a reason for hiding this comment

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

just leaving a placeholder for myself that I need to audit this code as well for any potential chromium concerns

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

@github-actions github-actions bot added the chromium-version-mismatch The Chromium version on the PR branch does not match the version on the target branch label Dec 2, 2024
@cypt4 cypt4 mentioned this pull request Dec 10, 2024
24 tasks
@cypt4
Copy link
Collaborator Author

cypt4 commented Dec 10, 2024

closed, reopened #26966

@cypt4 cypt4 closed this Dec 10, 2024
@cypt4
Copy link
Collaborator Author

cypt4 commented Dec 10, 2024

closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
chromium-version-mismatch The Chromium version on the PR branch does not match the version on the target branch CI/run-audit-deps Check for known npm/cargo vulnerabilities (audit_deps) feature/web3/wallet/core feature/web3/wallet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[ZCash] Add shardtree crate
4 participants