Config
This page goes over the `blocked.config.ts` file in detail. The app regularly references the rules inside the config, so understanding this part is important.
Creating config
The file's name and location can be altered.
Begin by creating a block3d.config.ts
file at your project's root. Next, create a block3dConfig
object and make sure to export it.
Configuring page restriction
Now that we have our block3dConfig
object, we need to populate it with 3 things:
publicRoutes
is an array of strings representing page routes that are marked as public, meaning that any configuredrules
don't apply to the pages listed inside it.strict
is a boolean. When markedtrue
, all existing rule criteria must be met. When markedfalse
, the user may view restricted pages as long as they meet the criteria for at least one rule.rules
is an array ofRule
objects. This is where you can control exactly which users may view your app.
Creating rules
The Rule
type is defined like so:
type
type
There are three different types of rules:
simple
rules are the most basic type and allow you to essentially whitelist any set of addresses that can then view your restricted pages. These rules consist of atitle
,type
, andaddresses
field.token
rules allow you to restrict pages based on addresses that hold aminimumBal
of any specified token. These rules consist of atitle
,type
,contracts
, and at least one globalminimumBal
OR at least oneminimumBal
for eachContract
object.nft
rules are identical totoken
rules except that they pertain to ERC-721 instead of ERC-20.
title
title
This can be any arbitrary string but should be short and describe its corresponding rule since it may be exposed to users on the front end.
addresses
addresses
This is an array of Ethereum addresses in string form and is only used in simple
rules.
minimumBal
minimumBal
This is a string representation of the minimum number of tokens/nfts that must be held by users to meet the rule criteria. Used only in token
and nft
rules. Remember to account for decimals.
contracts
contracts
Used only in token
and nft
rules, this is an array of Contract
objects that includes details about the token/nft smart contract.
address
is the smart contract address in string form. If using a chain's native currency, set this to the 0 address.chainId
is the blockchain chain ID that the smart contract exists on as type number.minimumBal
is the same as theminimumBal
that lives outside of theContract
object. This field exists solely to allow developers to have different minimum balances depending on the chain and isn't necessary if the other exists.
strict
strict
Used only in token
and nft
rules, this behaves similarly to the strict
field that lives directly inside the block3dConfig
object. It is a boolean that when set to true
, means every Contract
inside the contracts
array is included when deciding if a user can view the page. If set to false
, a minimum of one contract must meet the rule criteria. Defaults to false
.
For example, a developer using token
rule type with strict
set to false
, could have 3 separate Contract
objects in the contracts
array all representing the same token but on different chains. This way users can still view your app as long as they hold the minimumBal
on one of the chains.
Examples
Here are predefined config files for each rule type.
Simple
This file is configured to block users that aren't listed in the "Original Gangsters"
(everyone except Vitalik).
Token
This file is configured to block users that don't own 1 ETH and 500 USDC on mainnet
Nft
This file is configured to block users that don't own at least 1 of these NFTs: Milady, Remelio, Bonkler.
Last updated