Skip to content

zoro-onepiece/Crypto-Token

Repository files navigation

Notes by Author of the Repo

For successfully running this code ,in main.mo(backend) ,put your principal where I have highlighted in my code .You can get your principal from terminal using

dfx identity get-principal

Be sure to install all dependencies using

npm i

Also be sure you are using latest and compatible versions of both dfx and all other dependencies. I used Map data structure from motoko core library.Configure it in your project by following instructions from the docs:

Command for adding core using Mops package manager is :

mops add core

Note: This project is configured to use II(internet identity).I used nns to set up my local II so that i could login with II then be directed to app. If you want to follow my way : Open two terminals: Terminal 1:

dfx extension install nns

After it's done ,run

dfx start --clean --background

Terminal 2:

dfx nns install

After it is done run :

dfx deploy

after that run:

npm start

Note:

I have only tested my project locally .Haven't deployed on playground or mainnet .If you took course 'Full stack web development by Angla Yu ' and got stuck coz that course is very outdated for web 3 ,then this repo is perfect for you coz I have updated the code to new version etc.I have given my project,my token and my app the names I wanted ,so don't get confused.you can name yours whatever you want. PR's, issues and github discussions are welcome!

tokenc

Welcome to your new tokenc project and to the Internet Computer development community. By default, creating a new project adds this README and some template files to your project directory. You can edit these template files to customize your project and to include your own code to speed up the development cycle.

To get started, you might want to explore the project directory structure and the default configuration file. Working with this project in your development environment will not affect any production deployment or identity tokens.

To learn more before you start working with tokenc, see the following documentation available online:

If you want to start working on your project right away, you might want to try the following commands:

cd tokenc/
dfx help
dfx canister --help

Running the project locally

If you want to test your project locally, you can use the following commands:

# Starts the replica, running in the background
dfx start --background

# Deploys your canisters to the replica and generates your candid interface
dfx deploy

Once the job completes, your application will be available at http://localhost:4943?canisterId={asset_canister_id}.

If you have made changes to your backend canister, you can generate a new candid interface with

npm run generate

at any time. This is recommended before starting the frontend development server, and will be run automatically any time you run dfx deploy.

If you are making frontend changes, you can start a development server with

npm start

Which will start a server at http://localhost:8080, proxying API requests to the replica at port 4943.

Note on frontend environment variables

If you are hosting frontend code somewhere without using DFX, you may need to make one of the following adjustments to ensure your project does not fetch the root key in production:

  • setDFX_NETWORK to ic if you are using Webpack
  • use your own preferred method to replace process.env.DFX_NETWORK in the autogenerated declarations
    • Setting canisters -> {asset_canister_id} -> declarations -> env_override to a string in dfx.json will replace process.env.DFX_NETWORK with the string in the autogenerated declarations
  • Write your own createActor constructor

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published