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

Why is whitelist in faucet an option? #340

Closed
clangenb opened this issue Aug 10, 2023 · 3 comments
Closed

Why is whitelist in faucet an option? #340

clangenb opened this issue Aug 10, 2023 · 3 comments

Comments

@clangenb
Copy link
Member

It would be much easier to just have an empty array. Otherwise, I need to do some extra null handling on all frontends.

@brenzi
Copy link
Member

brenzi commented Aug 11, 2023

the idea is that None means that every community can drip (unlike no one can).
I wanted this to be explicit, not implicit in an empty vec. But I admit that "explicit" would have been an enum like this:

WhitelistType::AnyCommunity
WhitelistType::Restricted(Vec)

We may want to diversify further due to BeeDance and LoCoFlex. I guess that due to the different security assumptions we may even want:

WhitelistType::AnyCommunity
WhitelistType::AnyCommunityWithRules(Vec)
WhitelistType::Restricted(Vec)

assuming that CommunityIdentifier is the overarching type for communities of all rule types

TBD further

@clangenb
Copy link
Member Author

Alright, this makes sense. I did not get that part of the logic, and I already saw your commit in the wallet fixing my misunderstanding that null == empty vec. ;)

@clangenb
Copy link
Member Author

As my question has been answered, I will close this issue and we can continue the discussion in #344

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

No branches or pull requests

2 participants