Important
Since the launch of Kaia Blockchain, this repository has been parked in favour of the new open-source projects in Kaia's Github. Contributors have now moved there continuing with massive open-source contributions to our blockchain ecosystem. A big thank you to everyone who has contributed to this repository.
For future development and contributions, please refer to the new kaia-dapp-mono repository
More information about Klaytn's chain merge with Finschia blockchain, please refer to the launching of Kaia blockchain kaia.io.
Start your web3 journey on Klaytn with a complete DApp toolkit
Klaytn DApp Toolkit takes an unopinionated approach to DApp development. Instead of forcing you to adopt our tech stack of choice, we provide you with code snippets that you can use to copy and paste into whichever framework/technical stack that you are using. You can always refer to the original framework documentation for troubleshooting as well as our Troubleshooting section for each component.
The included smart contract templates and front-end sample codes aim to provide you with everything you need to run a web product, along with additional tools, documentation, and tricks for building onchain.
Whether you're a hackathon participant or an ambitious entrepreneur looking to establish the next successful project, this toolkit is designed with you in mind.
Read the docs in the repository for complete
Contains many complete smart contract implementations of various DApps
Contains implementation details of various frontend frameworks for EVM and guide to implement Klaytn specific features with copy/paste code samples
placeholder
Contains details of bounty program on Klaytn Ecosystem
Includes various information pieces for the reference
Contains workshop exercises
The idea behind this is to give you ownership and control over the code, allowing you to decide how the components of your DApp are built.
Start with some sensible defaults, then customize all the codes to your needs.
One of the drawback of other opinionated tools is that they often stick to one technical stack which might not fit for everyone.
Not at the moment.
You can use any development framework that supports EVM. For example, Hardhat, Foundry, Wagmi, Thirdweb. You can also use dedicated toolings released by the Klaytn Foundation here