Starter template for a Jetton project
This project contains everything you need to deploy a new token (Jetton contract) to TON blockchain. This project is free and open source and was created for educational purposes.
This is by far the simpler option if you want to use the standard Jetton code. You will not need to install any tools on your machine, just open up your web browser, fill-in some data about your token in the HTML form and click deploy.
Make sure you have a TON wallet with at least 0.25 TON balance. Supported wallets include TonHub and Chrome Extension.
Use your web browser to open the site of the deploy form: https://jetton.live
Safety Notice: The form is open source and served from GitHub Pages
Fill in the information about your Jetton in the form - choose a name, ticker and image.
Click the "Connect Wallet" button to connect your wallet.
Deploy and approve the deploy transaction in your wallet.
Once the token is deployed, the deploying wallet will receive all the tokens that were minted.
This is much more complicated and will allow you to change the actual behavior of the Jetton to any custom behavior you want to program with the FunC language. For example, let's say you want a special Jetton that pays a 1% fee to some address every time it's transferred between users. Since this behavior is different from the standard, for this option you will need to install the FunC compiler on your machine.
Note: This project is based on the tonstarter-contracts repo, consult it if you need more help.
Make sure you have all "Dependencies and Requirements" as described in tonstarter-contracts repo.
Git clone the repo locally and rename the directory to your own project name.
In the root repo dir, run in terminal npm install
Edit the smart contract source files to implement your new custom behavior, they're here: contracts/*.fc
Once you finish coding, build the project by running in the root repo dir npm run build
If you want to test your code locally, implement TypeScript unit tests here: test/*.spec.ts
Once your tests are ready, run them by running in the root repo dir npm run test
Edit your token metadata (like name and ticker) in jettonParams in build/jetton-minter.deploy.ts
Prepare at least 0.25 TON for deployment fees.
To deploy the token, run in the root repo dir npm run deploy and follow the on-screen instructions.
Jetton Name - For example: Bitcoin Cash
Usually 1-3 words, unabbreviated project name with spaces with each word capitalized. Our running example will be the bitcoincash.org project which is a fork of the Bitcoin token.
Jetton Symbol - For example: BCH
Usually 3-5 uppercase characters, the currency symbol for the token. This would usually appear next to the amount when the token balance is displayed. This would also appear in exchanges where the token is listed as the ticker.
Decimals - For example: 9
The decimal precision of your token (9 is TON default). Blockchains store floating point numbers (like 1.2345) as integers with a given precision. Under 9 decimals precision the balance 1.2345 BCH will be encoded as 1234500000 and the smallest balance possible to encode is 0.000000001 BCH which is encoded as 1. The balance 1 BCH is encoded as 1000000000.
Tokens to Mint - For example: 21,000,000
Number of initial tokens to mint and send to your wallet address (float). In our example, let's mint the entire supply as in Bitcoin, 21 million coins. Notice that the value here is a float number and is not encoded according to the decimal precision in the previous field. So for 21,000,000 BCH we will input 21000000 and not 21000000000000000.
Description - For example: Low fee peer-to-peer electronic cash alternative to Bitcoin
Optional freeform sentence explaining about your project. This can be left empty. Its purpose is to give a little more background detail about the project beyond the name. Don't make this part too long (longer than one sentence) because it's stored on-chain and can get costly.
Jetton Logo URI - For example: https://bitcoincash-example.github.io/website/logo.png
URL of 256x256 pixel PNG image of the token logo with transparent background. Notice that this logo is not immutable (unlike the rest of the fields) and can be changed in the future of the project as its update poses no security risks to users. It should be placed on hosting where multiple maintainers can be given easy access, which makes GitHub Pages a good solution since it can support multiple community contributors and PRs. The best practice would be this:
Create a new free GitHub organization for your project, you can follow the instructions here. In our example we created the organization bitcoincash-example which you can see here.
Under this new organization, create a new public repository with the name website, you can follow the instructions here. In our example you can see the repo here.
Upload your PNG image to this repository and enable GitHub Pages on it, you can follow the instructions here and then here. The result should be a live website like https://bitcoincash-example.github.io/website/logo.png where your image is hosted.
If you can afford it, we recommend to buy a custom domain for your project like bitcoincash.org. Use any domain seller like Google Domains or GoDaddy. Then, connect your custom domain to the repository in the previous step, you can follow the instructions here.
If you have a custom domain, your image URL should be https://bitcoincash.org/logo.png instead of the github.io one. This will remove any future dependency on GitHub and allow you to switch hosting in the future which is a good option to keep.
Where is this metadata stored? - The Jetton standard supports storing metadata either on-chain or in an off-chain URL (a JSON file hosted somewhere). It is our belief that the best practice is storing metadata on-chain. Why? Let's explore the alternatives:
On-chain - On-chain data is immutable, users can be guaranteed that important fields like the symbol will not change without their consent. On-chain data is also guaranteed to always be available. This deployer always stores metadata on-chain.
Off-chain IPFS (ipfs:// URL) - IPFS data is immutable so it's safe like on-chain. But IPFS data is not guaranteed to always be available. Availability depends if someone is willing to pin the data (similar to seeding in torrents). If this someone goes out of business or suffers downtime, token metadata will disappear. This is an unnecessary risk in our eyes.
Off-chain website (https:// URL) - This is by far the worst option. The owner of the website could change the metadata without user consent (not necessarily on purpose if the website is hacked). The website can also be taken down and the metadata will disappear. Users should never invest money in tokens that have their metadata stored this way.
What about the Jetton Logo URI, if it's stored on a website, can't it change? Yes, it can change and this is a feature. We believe that logos can go through rebranding without putting users at risk. Satoshi Nakamoto didn't design the current logo of Bitcoin when he wrote the initial code.
I don't see the metadata in a wallet or block explorer, why? Some tools don't support yet the secure on-chain metadata standard. Please open issues with these tools to fix and display on-chain metadata which is supported by the official standard and is the secure way to publish Jettons.
Don't forget that we're dealing with programmable money here. Jettons are tradable and users may end up paying real money for them. It is our responsibility as a community to keep everybody safe.
Never deploy smart contract code that you are unable to review
Make sure you understand what you deploy. We went into a lot of effort to make sure everything is open source. The smart contract code that is deployed is available in this repo, you should review it and see that it's compatible with the official standard version. The HTML form that performs the deployment is open source as well and served from GitHub Pages so you can have confidence the source you see is what actually being served. By deploying your Jetton, you are taking full responsibility over what you deploy. This repo is aimed for educational purposes only and provides no guarantees.
The Jetton code allows a special admin role (the deployer wallet address) to mint new tokens for themselves and change token metadata. This functionality is necessary for the initial launch because that's how new Jettons enter circulation. Once you're finished with minting you must revoke your admin permissions by changing the admin to an empty address. A blockchain ecosystem is designed to be trustless. You should never take responsibility for your users' funds, you don't want a misplaced key on your behalf to permit theft from other people! Revoking the admin role will guarantee that nobody will ever be able to mint new tokens in the future and crush your Jetton price. Please only revoke after you finished doing QA and made sure all the metadata fields are correct! After revoking admin you will not be able to change any of the metadata fields anymore.
Yes! Contract deployers that look like this are the safest you can get. This is actually the reason we implemented this deployer, to prevent people from getting hurt. Let's go over all the questions that you should ask yourself before using any deployer:
Are you making any money from this deployer? What's your business model? Why did you make it?
No. This is a community project that is 100% open source. It's completely free to use and there is no business model. Because it's open source anyone can copy it. The reason we made it is to keep people safe. We are TON ecosystem contributors that want TON to succeed.
Do you have access to my token? Will you be able to mint my tokens to yourself and sell them?
No. This deployer uses the standard Jetton code published by TON foundation. The standard code has only one special admin address that can mint tokens. This admin address is your deployer wallet address (your wallet that pays the deploy fees).
How can I check that you're actually using the standard Jetton smart contract code in this deployer?
This deployer is open source so you can compare the code yourself. The standard Jetton code is here - notice the TON blockchain repo. The code in this deployer is here.
I'm using the HTML form to deploy from my browser, how can I be sure it's deploying the contract source code in the repo?
The HTML form is also open source, you can see the compiled smart contract bytecode that it is deploying here. You can build the FunC source code by yourself by cloning the contract repo and building it by running npm install and then npm run build. Then compare the build output in the /build directory.
How can I be sure that the website I visit in my browser is actually serving the HTML source code in the repo?
If you use the website to deploy, notice that the website is served by GitHub Pages - a cool service by GitHub that allows to serve websites directly from open source repos. The GitHub Actions that build the website are here and you can see that the repo name leads to the custom domain - https://ton-defi-org.github.io/jetton-deployer-webclient
Does this deployer use any hidden backend servers that I don't have access to and the community can't audit?
No. We went into a lot of effort to make this tool as trustless as possible. There are no backend services. The entire deployer runs client side in your browser so the community can audit every aspect of it.
I'm not technical enough to understand all the answers here, how can I still be confident you're telling the truth?
If you can't audit everything by yourself, rely on other people in your community. Since this deployer is fully open source, anyone has access to it. We encourage technical people in the community to verify every aspect and let the community know if we missed anything by accident. The best way to feel confident that someone is telling the truth is that they offer 100% transparency.
What happens if somebody hacks my wallet in the future, would this hacker be able to steal from users of my token?
No, if you follow our advice. The best practice is to deploy a token that even you can't control. This means that even if you make a mistake in the future and your personal wallet gets hacked, your token users will still be safe. The first thing we're doing is storing all token metadata (like name and ticker) on-chain. Some deployers host this info in a JSON file on an external URL. This is very dangerous because if somebody ever hacks the website that holds the JSON - they would be able to change the ticker and destroy the token. Storing the metadata on-chain guarantees that it could never change. Second, after you finish minting the initial supply of your token, we encourage you to revoke the admin account to prevent any future minting. This means that even if your deployer wallet gets hacked, the hacker will not be able to mint and harm your token users.
I didn't write down my new Jetton's contract address and forgot what it was!
Don't worry, we can find your Jetton in a block explorer like tonscan.org. Open https://tonscan.org and go to the address page of the wallet you used to deploy the Jetton (this is the wallet that paid the 0.25 TON deploy fees). We assume that you minted some tokens to this address. In the explorer UI click on the tab named "JETTONS". This will now show you all the Jettons you hold, your new Jetton should be in the list. If you didn't mint any tokens, then just throw this Jetton away and deploy a new one.
I made a mistake with the metadata! I want to change one of the fields
You can only change metadata fields until you revoke the admin role. If you didn't revoke the admin yet, open the minter UI and search for your Jetton by address. Once found, connect the wallet that you deployed with. You should have the ability to edit metadata fields in the UI. If you revoked the admin and must change one of the metadata fields due to a mistake, your best course of action is to throw this Jetton away and deploy a new one.
Can there be multiple Jettons with the same metadata fields like name, logo and symbol?
Yes! Anyone can deploy as many duplicate Jettons as they want with similar metadata. Every Jetton will be deployed on a different address. Jettons are not unique and are very easy to fake. To make sure you're working with the correct Jetton, always compare the address to the official address. If you deployed a Jetton and made a mistake that cannot be recovered, you can always deploy a new one and forget about the old.
I don't see my Jetton's image, it doesn't show!
Your Jetton's logo URI is probably invalid. To make sure the URI is working, paste it in your browser. Make sure the URI is not a web page but the URI of the image directly. The URI should end with a .PNG or .JPG extension. If this is not the case, open the website in your browser, right click on the image and select "Copy Image Address". You should now have the correct URI in your clipboard.
My Jetton displays in some wallets/explorers but not in others
Some wallets and some explorers don't support the latest standard of Jettons that store metadata securely on-chain. Wallets like TonKeeper and TonHub should be ok and explorers like tonscan.org should be ok. If your Jettons works well in these but doesn't show up in a different wallet/explorer, please open an issue for this developer and ask them to add support for Jettons storing metadata on-chain (this is part of the official standard).
I have a different problem and I don't know what to do
We have a friendly community on Telegram that will be happy to help you. Visit https://t.me/ton_minter and ask for help.
MIT