Welcome to the official GitHub repository for the Tarsier Token ($TARS), the meme token with a mission to protect the Philippine Tarsier and its habitat!
$TARS is more than just a meme token; it's a community-driven movement that combines the fun of crypto with a passion for conservation. Built on the Internet Computer Protocol (ICP), $TARS aims to:
- Protect the Philippine Tarsier: A portion of every $TARS transaction and NFT sale is dedicated to Tarsier conservation efforts.
- Empower the Community: $TARS holders will have a say in the project's future through decentralized governance.
- Innovate with NFTs: We're creating unique Tarsier-themed NFTs with utility and collectability.
- Reward Staking: Earn passive income by holding and staking $TARS.
- Join the Community: Connect with us on Twitter-X and Twitter-X Community, Telegram and Discord.
- Learn More: Visit our website or ICP-website to learn about our mission, roadmap, and team.
- Get $TARS: You can acquire $TARS through airdrops, staking rewards, or on decentralized exchanges.
- Add TARS Token: If you want add TARS using ICRC-2 Token standard and its Canister: i5xtb-aaaaa-aaaam-acrja-cai
- Participate: Contribute to the community, collect NFTs, and help us protect the Tarsier! Click here for ZEALY
-
Smart Contracts: The core $TARS token smart contracts.
-
Frontend: ReactJS, Typescript
-
Documentation: Whitepaper, technical documentation, and other resources. Visit our Pitchdeck
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 TARSIER-TOKEN
, 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 Tarsier-Token/
dfx help
dfx canister --help
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.
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:
- set
DFX_NETWORK
toic
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
indfx.json
will replaceprocess.env.DFX_NETWORK
with the string in the autogenerated declarations
- Setting
- Write your own
createActor
constructor
We welcome contributions from the community! If you'd like to get involved, please check our CONTRIBUTING.md file for guidelines.
This project is licensed under the MIT License.
Crypto investments carry risk. Please do your own research and invest responsibly.
For any inquiries, please reach out to us through our social media channels or email us at [tarsierian@gmail.com].
Let's make a difference together!