|
2 ヶ月 前 | |
---|---|---|
.. | ||
anchor | 2 ヶ月 前 | |
public | 2 ヶ月 前 | |
scripts | 2 ヶ月 前 | |
src | 2 ヶ月 前 | |
.gitignore | 2 ヶ月 前 | |
.prettierignore | 2 ヶ月 前 | |
.prettierrc | 2 ヶ月 前 | |
README.md | 2 ヶ月 前 | |
components.json | 2 ヶ月 前 | |
eslint.config.mjs | 2 ヶ月 前 | |
next.config.ts | 2 ヶ月 前 | |
package.json | 2 ヶ月 前 | |
postcss.config.mjs | 2 ヶ月 前 | |
tsconfig.json | 2 ヶ月 前 |
An example of a allow / block list token using token extensions.
Allows the creation of an allow block list with a list authority. The allow/block list is then consumed by a transfer-hook.
The list is managed by a single authority and can be used by several token mints. This enables a separation of concerns between token management and allow/block list management, ideal for scenarios where an issuer wants a 3rd party managed allow/block list or wants to share the same list across a group of assets.
Initializes new tokens with several configuration options:
The issuer can configure the allow and block list with 3 distinct configurations:
These configurations are saved in the token mint metadata.
This repo includes a UI to manage the allow/block list based on the legacy-next-tailwind-basic
template. It also allows creating new token mints on the spot with transfer-hook enabled along with token transfers given that most wallets fail to fetch transfer-hook dependencies on devnet and locally.
Install dependencies:
yarn install
Compile the program:
anchor build
Compile the UI:
yarn run build
Serve the UI:
yarn run dev
There are a couple scripts to manage the local validator and deployment.
To start the local validator and deploy the program:
./scripts/start.sh
To stop the local validator:
./scripts/stop.sh