From 2ab6d4040c06c7e0d1211a4351626a152e7cb5b8 Mon Sep 17 00:00:00 2001 From: ymekuria Date: Thu, 11 Jul 2024 18:21:05 -0700 Subject: [PATCH] feat(custom-tokens.mdx): update link to fungible token standard in TokenContract class section --- docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 fa30f77c6..76577a60c 100644 --- a/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx +++ b/docs/zkapps/writing-a-zkapp/feature-overview/custom-tokens.mdx @@ -45,7 +45,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](https://github.com/MinaFoundation/mina-fungible-token/blob/main/documentation/SUMMARY.md) standard which is built on top of the +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 . 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: