Kapd.app

Kapd.app lets you create crypto baskets and mint them as NFTs. A basket can hold multiple on-chain assets and can be used as a programmable crypto gift card or as a tradable basket NFT.

Each basket can contain up to 9 assets. This is also explained in the Create Basket section and reflected in the Basket Details area.

You need a connected wallet for minting, editing, depositing and withdrawing. Reading and loading basket data is more flexible, but write actions require a connected wallet on Cronos.

Kapd.app is configured here for Cronos. If the wallet is connected to the wrong network, the interface warns the user and prevents write actions until Cronos is selected.

Actions depend on basket status, ownership, maturity, deposit settings and network state. The interface only shows or enables actions when the current basket and connected wallet are actually allowed to perform them.

The Kapd.app marketplace is where users can browse, list, buy and manage tradable Crypto Basket NFTs. It is designed to show baskets as transparent on-chain products with visible holdings, valuation and basket facts.

Yes. If your basket is eligible for listing, you can offer it for sale on the Kapd.app marketplace. Buyers can then purchase the basket NFT together with the on-chain assets and rules attached to it.

The marketplace compares the ask price of a basket NFT with its indexed basket value. This makes it possible to show whether a basket is offered at a premium, discount, or close to fair basket value.

A listing can become invalid if the basket NFT is transferred outside the marketplace flow. In that case, the marketplace can detect the invalid state and the basket owner can cancel or resolve the outdated listing.

The Kapd.app marketplace is specialized for basket NFTs. It can show live basket-specific information such as holdings, indexed value, maturity profile, listing validity and basket facts that generic NFT marketplaces usually do not support.

Creating a basket mints a new NFT in Draft status. After that, you can open Basket Details, enter edit mode, add tokens, configure rules, and later activate the basket.

Draft means the basket exists, but is not yet active. In this phase you can still define the token set and configure basket behavior before activation.

Activate finalizes the basket setup on-chain. Depending on the basket state, Kapd.app first ensures the token set and settings are completed, then activates the NFT so it can operate under its defined rules.

Gift Card mode is a basket flag intended for gifting workflows. It is reflected in the metadata and user interface and helps position the basket as a crypto gift card experience.

Limit Mode controls whether deposits are open-ended or capped. Open mode allows flexible deposits, while Capped mode is used when per-token caps must be respected.

Maturity is an optional lock timestamp. If it is set, the basket is treated as locked until that local date and time has been reached.

Yes, if deposits are open for that basket. Deposits can be configured as Open or Closed. If deposits are closed, the UI will block deposit actions and explain why.

Yes. Kapd.app supports native CRO deposits for CRO slots and ERC-20 deposits for token slots. The deposit flow reads the basket assets and shows only valid choices for the selected basket.

Yes. Kapd.app applies a 0.5% deposit fee, and the deposit modal shows the estimated net amount to be added to the basket. However, some tokens also charge their own buy tax, sell tax, transfer tax, or a combination of these. In those cases, the actual amount received can be lower than the estimate shown by Kapd.app.

Withdraw becomes available only when the basket rules allow it. In the current flow, that generally means the basket must be active, owned by the connected wallet, and mature if a maturity timestamp was configured.

Load Baskets searches the registered basket contracts for baskets belonging to the entered owner address and then shows them in the list so one can be selected for detailed viewing.

Load Baskets works for any owner address you enter manually. My Baskets is a convenience action that automatically uses the currently connected wallet address.

The preview helps users immediately see the visual representation of the selected basket NFT. Clicking the NFT opens a larger lightbox view for easier reading on desktop and mobile.

Kapd.app basket NFTs are dynamic. The image reflects the actual assets stored in the basket contract. However, many wallets and NFT marketplaces cache metadata and images for performance reasons. Because of this caching, the displayed NFT image may not immediately update after deposits or withdrawals.

It depends on the platform. Some wallets refresh metadata automatically within minutes, while others may cache NFT images for hours or even longer. The underlying basket data on-chain is always correct, even if the displayed image is temporarily outdated.

Many NFT platforms provide a refresh or “reload metadata” option. If available, using this feature will force the platform to fetch the latest metadata and image from the Kapd.app API.

The most reliable source is the Kapd.app interface itself. The dApp reads the basket contract directly from the blockchain, ensuring the displayed balances and basket contents always match the current on-chain state.

No. The NFT image is generated dynamically based on the basket contract data. The actual token balances are stored on-chain inside the basket contract, not inside the NFT image or metadata.

The flow is designed around on-chain basket ownership and wallet-controlled actions. Users interact with the basket contracts directly through their own wallet instead of handing assets to a centralized account.

Yes. Kapd.app can show the current Manager contract together with the basket contracts and the Cronos Oracle Hub smart contract from the public config. Open the popup below and use the explorer links to inspect verified contract source code.

No. The basket contract is designed so basket assets cannot be arbitrarily withdrawn by an owner/admin role. Basket assets are intended to leave the basket only through the normal withdrawAll flow by the current NFT owner, and only when the basket rules allow it, such as after maturity if a maturity lock was set.

The manager/admin side is meant for protocol configuration, such as mint settings, allowed tokens, metadata settings, approved routers/adapters, and sweeping protocol fees. It is not intended as a backdoor to drain the assets stored inside user baskets.

Only protocol-owned fees. Kapd.app uses protocol fees on deposits and withdrawals. Those accrued fee balances can be swept by the manager. That is different from the basket assets that belong to the NFT holder.

Your assets are held on-chain inside the basket contract that belongs to your basket NFT. Ownership and withdrawal rights are tied to the NFT owner and the basket rules, not to a centralized Kapd.app account.

No smart contract system can honestly promise zero risk. Kapd.app is designed to reduce admin custody risk and make behavior verifiable on-chain, but users should still review the contracts, verify addresses, and only use amounts they are comfortable managing on-chain.

The basket contract is intended to be immutable in the sense that it has no normal owner role that can arbitrarily pull user assets out. Manager-related changes are about protocol configuration and contract routing, not about granting an admin the right to seize basket balances.

Your basket assets remain safe on the blockchain. The Kapd.app website is only a user interface that interacts with the smart contracts. Even if the website is unavailable, the basket contracts and NFTs continue to exist on-chain and can still be accessed through blockchain tools such as Cronos Explorer.

Your assets are stored in the basket contracts on the Cronos blockchain, not on Kapd.app servers. If the project were ever abandoned, the contracts would still function and basket owners could interact with them directly using blockchain tools or custom interfaces.

Yes. Because the basket contracts are deployed on-chain, you can interact with them directly using Cronos Explorer or other blockchain tools. By calling the withdrawal function from your wallet address (the NFT owner), you can retrieve the assets stored in your basket.

Open your basket contract on Cronos Explorer and connect your wallet. Then go to the contract's “Write Contract” section and call the withdrawal function (for example withdrawAll) from the address that owns the basket NFT. This sends all basket assets back to the NFT owner's wallet.

Yes. Because the contracts are public and deployed on-chain, any developer could build a new interface that interacts with the basket contracts. The website itself is not required for the contracts to continue functioning.