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

Support encryptor allowlist #306

Closed

Conversation

piotr-roslaniec
Copy link
Contributor

@piotr-roslaniec piotr-roslaniec commented Oct 4, 2023

Type of PR:

  • Feature

Required reviews:

  • 2

What this does:

High-level idea of the changes introduced in this PR.
List relevant API changes (if any), as well as related PRs and issues.

Issues fixed/closed:

Why it's needed:

Explain how this PR fits in the greater context of the NuCypher Network.
E.g., if this PR address a nucypher/productdev issue, let reviewers know!

Notes for reviewers:

@codecov-commenter
Copy link

codecov-commenter commented Oct 4, 2023

Codecov Report

Merging #306 (fac82b6) into monorepo (80018e5) will decrease coverage by 0.40%.
The diff coverage is 51.72%.

@@             Coverage Diff              @@
##           monorepo     #306      +/-   ##
============================================
- Coverage     88.25%   87.86%   -0.40%     
============================================
  Files            33       33              
  Lines          2409     2430      +21     
  Branches        205      205              
============================================
+ Hits           2126     2135       +9     
- Misses          254      266      +12     
  Partials         29       29              
Files Coverage Δ
packages/pre/src/characters/bob.ts 85.61% <100.00%> (ø)
packages/pre/src/cohort.ts 89.28% <100.00%> (ø)
packages/taco/src/conditions/const.ts 100.00% <100.00%> (ø)
packages/pre/src/kits/retrieval.ts 77.27% <0.00%> (ø)
packages/pre/src/policy.ts 83.13% <50.00%> (+0.09%) ⬆️
packages/taco/src/taco.ts 86.99% <42.85%> (-9.13%) ⬇️

GlobalAllowListInterface,
} from "../GlobalAllowList";

const _abi = [
Copy link
Contributor

Choose a reason for hiding this comment

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

is there a difference between this _abi and packages/shared/abis/GlobalAllowList.json?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is code generated by typechain, the difference includes generated (inferred) types.

Copy link
Contributor

Choose a reason for hiding this comment

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

ok cool, so as one changes, the other will be automatically kept up to date by typechain

Copy link
Member

@KPrasch KPrasch left a comment

Choose a reason for hiding this comment

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

Looking good, although if there's an incoming PR that will integrate nucypher-contracts >= v0.5.0 do we want to wait for that first?

@piotr-roslaniec
Copy link
Contributor Author

(...) there's an incoming PR that will integrate nucypher-contracts v0.5.0 do we want to wait for that first?

Yes, I will add this information to the PR description.

};

const MUMBAI: Contracts = {
SUBSCRIPTION_MANAGER: '0xb9015d7b35ce7c81dde38ef7136baa3b1044f313',
COORDINATOR: '0x8E49989F9D3aD89c8ab0de21FbA2E00C67ca872F',
GLOBAL_ALLOW_LIST: '0x7b521E78CFaf55fa01433181d1D636E7e4b73243',
Copy link
Member

Choose a reason for hiding this comment

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

We should be careful here. Both tapir and lynx use Mumbai but have different GlobalAllowList contracts:

  • Lynx: 0x7b521E78CFaf55fa01433181d1D636E7e4b73243
  • Tapir: 0x5Ff235481bbDBF5dFCC908d987506FA6a8696678

How would this resolution work currently? Keying by "domain" is better than solely by blockchain/chain_id.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Will address post #314 changes

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
do not merge Open for review but do not merge please
Projects
Status: Completed
Development

Successfully merging this pull request may close these issues.

5 participants