From 645b6badd4fa4bec915534b420045c2e40bc71ed Mon Sep 17 00:00:00 2001 From: ymekuria Date: Thu, 11 Jul 2024 18:27:22 -0700 Subject: [PATCH] feat(custom-tokens.mdx): remove duplicate copy --- .../writing-a-zkapp/feature-overview/custom-tokens.mdx | 5 +++-- 1 file changed, 3 insertions(+), 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 76577a60c..80105636e 100644 --- a/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx +++ b/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx @@ -45,8 +45,9 @@ 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) standard 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. 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. + 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: