From bbab8228f4a3f20b559f1b46a1de6cfd8afa467d Mon Sep 17 00:00:00 2001 From: ymekuria Date: Fri, 12 Jul 2024 10:54:52 -0700 Subject: [PATCH] refactor(custom-tokens.mdx): remove unnecessary reference redundant copy --- docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx b/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx index b903a0753..3a0a1a620 100644 --- a/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx +++ b/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx @@ -53,8 +53,7 @@ A token manager smart contract sets the rules around minting, burning, and sendi ## TokenContract class -Use the `TokenContract` class to perform common token operations, such as minting, burning, and sending tokens. In o1js, the `TokenContract` class is your blueprint for custom token implementations. If you want to create a fungible token you can use the -[fungible token standard](https://github.com/MinaFoundation/mina-fungible-token/blob/main/documentation/SUMMARY.md) which is built on top of the `TokenContract` class. +Use the `TokenContract` class to perform common token operations, such as minting, burning, and sending tokens. In o1js, the `TokenContract` class is your blueprint for custom token implementations. As shown in this [example code](https://github.com/o1-labs/o1js/blob/main/src/lib/mina/token/token-contract.unit-test.ts#L13), you inherit from the `TokenContract` class: