Currently the block3dConfig allows you to determine if you want every rule criterion to be met, or at least one, before being allowed to view restricted pages. This is done through the strict field inside the config.
This is limiting per dapp since the rules are applied throughout the site with the exception of pages listed in the publicRoutes array.
Solution
Add a new field to each rule that marks what pages it should be applied to. Maybe we should also add an inverse rule that can only be used if the other new field isn't used, this way it works like a blacklist/whitelist.
For example, consider the new field terms enabled and disabled.
enabled - this rule will only work on the pages listed in this array.
disabled - this rule will work on all pages except the ones listed in this array.
Overview
Currently the
block3dConfig
allows you to determine if you want every rule criterion to be met, or at least one, before being allowed to view restricted pages. This is done through thestrict
field inside the config.This is limiting per dapp since the rules are applied throughout the site with the exception of pages listed in the
publicRoutes
array.Solution
Add a new field to each rule that marks what pages it should be applied to. Maybe we should also add an inverse rule that can only be used if the other new field isn't used, this way it works like a blacklist/whitelist.
For example, consider the new field terms
enabled
anddisabled
.enabled
- this rule will only work on the pages listed in this array.disabled
- this rule will work on all pages except the ones listed in this array.In the example above, the
/OGs
page is restricted only by theOriginal Gangsters
simple
rule.USDC
rule restricts every other pageOriginal Gangsters
rule only restricts the/OGs
page.