Overview

Here are the most important things you need to know about the NFT Kit:

  • It is written in Kotlin/Java. It can be directly integrated (Maven/Gradle dependency) or run as RESTful web-service. A CLI tool allows you to run all functions manually.

  • It is open source (Apache 2). You can use the code for free and without strings attached.

  • It is a holistic solution that allows you to build use cases “end-to-end”. There is no need to research, combine or tweak different libraries to build pilots or production systems.

  • It abstracts complexity such as low-level functionality related to key handling, data storage, minting operations and interactions with third party systems.

  • It is customizable in a sense that you can build NFTs in all kinds of variations based on different smart contracts (e.g. ERC-721, ERC-1155) using various configurations (e.g. supply size, metadata storage).

  • It gives you advanced features like "soulbound" or "dynamic" NFTs or royalties.

  • It is modular, composable and built on open standards allowing you to customize and extend functionality with your own or third party implementations and to preventing lock-in.

  • It is flexible in a sense that you can deploy and run it on-premise, in your (multi) cloud environment or as a library in your application.

  • It enables you to use different blockchains / ecosystems - starting with EVM-compatible blockchains (e.g. Ethereum, Polygon, Binance Smart Chain, Avalanche).

  • Metadata is one of the core components of a NFT. We have a flexible and an abstract system to manage metadata. It can be on-chain (struct in smart contract, base64 string) or off-chain (IPFS, Arweave, centralized server).

Last updated