# Kangal Docs 📖 Source of truth for all things Kangal ## 🔖 Litepaper {% content-ref url="/pages/-MXroxoArGl\_DIHdtzl5" %} [Litepaper](/litepaper/litepaper) {% endcontent-ref %} ## 📜 Community Foundation Document {% content-ref url="/pages/-MWBYQRZas0qxg1Kv97z" %} [CFD-1: Number of Kangals to hold to be able to create visible proposals](/community-foundation-document/cfd-1-number-of-kangals-to-hold-to-be-able-to-create-visible-proposals) {% endcontent-ref %} {% content-ref url="/pages/-MWFvgItZxRYzzOMeTls" %} [Community Treasury](/community-foundation-document/community-treasury) {% endcontent-ref %} ## ❓FAQ {% content-ref url="/pages/-MUUVwMhFsHFR6qqcPnx" %} [How KANGAL supply is always limited to 100 Billion](/faq/how-kangal-supply-is-always-limited-to-100-billion) {% endcontent-ref %} # Litepaper \ 📖 See the [whitepaper](https://whitepaper.kangaltoken.com/) for a more in-depth view of the Kangal Ecosystem. ## What is KANGAL? KANGAL is the governance and value token of the Kangal dApps ecosystem. KANGAL holders are the stakeholders of the Kangal DAO and can create and vote on proposals that shape up the future of the project. KANGAL staking will be the only way to mint the Utility Token $TEAK which will power the dApps ecosystem which will start out with dApps built by the core team and eventually the platform will turn into a dAppStore where other developers, teams, or companies will be able to submit and publish their dApps. One of the first dApps of the platform will be an NFT drops platform which will eventually turn into a full-fledged NFT marketplace. ## Technical Background and Tokenomics * KANGAL is an ERC-20 & BEP-20 token running on Ethereum & BSC and Polygon mainnet. * Max total supply is 100,000,000,000 & all in circulation. There was no presale or special allocations. * Starting liquidity is locked via [Unicrypt](https://unicrypt.network/amm/uni/pair/0x0Bc4428491010DfEAa97E48C70bF4940fa783b40) for 10 years. #### Contracts ETH: BSC: Polygon: ## DAO Kangal Core Team's one of main responsibilities is bootstrapping the DAO. This is an ongoing process that will get moving faster as there are more stakeholders active in the process. Below is the current situation: Kangal DAO stakeholders are able to discuss ideas on any aspect of the project and initiate new proposals on the [community forum](https://kangaltoken.community/). Voting for proposals take place on projects snapshot spaces, available for both [ETH](https://snapshot.page/#/kangal.eth) and [BSC](https://snapshot.org/#/kangal-bsc.eth) side. The project aims not only to give Kangal DAO stakeholders the ability to create proposals and vote on them but also to give control of the main parameters of the ecosystem itself by making them configurable. The first example of this ecosystem configuribility will be the stakeholders naming the Utility Token, and the APR rate for staking KANGAL and KANGAL LPs. ## Initial Projects #### Utility Token and Staking Deployment A Utility Token that will be powering the dApps ecosystem will be deployed. This token's supply & circulation will be 100% controlled by the DAO. The name will be decided by the DAO stakeholders as well. Emissions will only occur by staking KANGAL and KANGAL LPs. Kangal’s price will display the whole Kangal ecosystem’s value, and the Utility Token's price will be driven by the return percentage rate for staking, burns, and fees gathered which will be driven by the transaction volume on the ecosystem usage. #### dApps Ecosystem Below are some of the initial plans related to what the ecosystem will get started with: * NFT dApp that will start with special drops, and then turn into an NFT minting and a marketplace. * Holders board, where you can define a handle for your wallet by burning some amount of Utility Token. * BURN board, where the messages left are sorted by the amount of Utility Token you burned for it. * AD board, use Utility Token to promote anything. * Various lotteries. * Games. # CFD-1: Number of Kangals to hold to be able to create visible proposals Proposal Result Summary: Proposal on deciding the number of Kangals required to hold for creating visible proposals on Kangal's snapshot spaces. Result: 20M KANGAL or bKANGAL tokens. Details:\ # Community Treasury **Summary** Community treasury was implemented after the result of the following proposal:\ \ Wallet address on ETH, BSC and Polygon: 0x1C1433cB0995338F5aF5F4312B553f95D10d0c24 All expenses require approval from the community through a proposal creation and vote on snapshot spaces. Since these decisions need to be taken swiftly, the voting on these proposals will be completed in 24 hours. **Allowance proposals** **ETH ->** [**https://snapshot.org/#/kangal.eth**](https://snapshot.org/#/kangal.eth) **BSC ->** [**https://snapshot.org/#/kangal-bsc.eth/**](https://snapshot.org/#/kangal-bsc.eth/) **Staking treasury multisig addresses** **BSC:** [**https://bscscan.com/address/0xa77d3754428edda3760438f9c25b9bd25dc23b6a**](https://bscscan.com/address/0xa77d3754428edda3760438f9c25b9bd25dc23b6a) **Polygon:** [**https://polygonscan.com/address/0xb64b3026e904c0a1645bd4adb10e883d73adaa20**](https://polygonscan.com/address/0xb64b3026e904c0a1645bd4adb10e883d73adaa20) # Addresses **KANGAL on ETH**\ [0x6e765d26388a17a6e86c49a8e41df3f58abcd337](https://etherscan.io/token/0x6e765d26388a17a6e86c49a8e41df3f58abcd337) **KANGAL on BSC**\ [0xd632bd021a07af70592ce1e18717ab9aa126decb](https://bscscan.com/token/0xd632bd021a07af70592ce1e18717ab9aa126decb) **KANGAL on Polygon**\ [0x34f380a4e3389e99c0369264453523bbe5af7fab](https://polygonscan.com/token/0x34f380a4e3389e99c0369264453523bbe5af7fab) **$TEAK on BSC**\ [0xba0f58179f5441d81d22402bd0183ffff130e243](https://bscscan.com/token/0xba0f58179f5441d81d22402bd0183ffff130e243) **$TEAK on Polygon**\ [0x3d50f9543cdb83ec867f491787c65d14631ba50f](https://polygonscan.com/token/0x3d50f9543cdb83ec867f491787c65d14631ba50f) **Staking contract (KANGAL -> $TEAK) on BSC**\ [0x222dc5cbc4d5082ac181532c01a57cc897ea4f15](https://bscscan.com/address/0x222dc5cbc4d5082ac181532c01a57cc897ea4f15) **Staking contract (KANGAL -> $TEAK) on Polygon**\ [0x68a37C1cbBD49f693029F5749CA0b1D7c6d85A74](https://polygonscan.com/address/0x68a37c1cbbd49f693029f5749ca0b1d7c6d85a74) # How KANGAL supply is always limited to 100 Billion The total maximum and circulating supply of ERC20 KANGAL and its BEP20 version bKANGAL token is 100 billion, which you can see by checking the contract source code of the ERC20 token on [etherscan](https://etherscan.io/address/0x6e765d26388a17a6e86c49a8e41df3f58abcd337#code). There are no burn or mint functions in this contract, which means there is no way to change the supply. Kangal uses the bridging feature of burgerswap.org to bridge into Binance Smart Chain, which works by creating BEP20 bKANGAL tokens on BSC and locking the bridged ERC20 tokens. Check [this contract](https://etherscan.io/token/0x6e765d26388a17a6e86c49a8e41df3f58abcd337?a=0xc8c1b41713761281a520b7ad81544197bc85a4ce) to see the amount ERC20 tokens that are locked, and this [bscscan page](https://www.bscscan.com/token/0xd632Bd021a07AF70592CE1E18717Ab9aA126DECB) to see the amount of bKANGAL tokens. When bKANGAL tokens are converted back into KANGAL tokens, BEP20 version of the tokens are burned and the amount that was locked on the Ethereum contract is unlocked. Note that there can be a difference in the number of locked KANGAL's in the contract and the bKANGAL supply shown on bscscan in case anyone using burgerswap.org bridge does not claim the tokens they have converted.