Frequently asked questions
Practical answers about activation, native KAD vaults, trading and withdrawals.
When does KADDEX activate?
KADDEX activates on Kadikama mainnet at block 16,000. The Trade page remains blurred and unavailable before that height. Its counter follows the live Kadikama network height.
Why is the Trade page blurred?
The mainnet consensus rules required by KADDEX are not active yet. The blur is removed automatically after the network reaches block 16,000; reloading the page is not required.
Does the activation affect existing coins or transactions?
No. Existing KAD, wallet balances, addresses and confirmed transactions remain unchanged. The upgrade adds validation rules for new KADDEX witness-v2 outputs and their spends.
Which wallet version is required?
Use Kadikama Core 1.0.2 or later for KADDEX mainnet deposits and withdrawals. Keep the wallet fully synchronized before approving a request.
What is a KADDEX vault?
It is a native Kadikama witness-v2 output committed to an owner public key. Spending it requires a valid signature from the corresponding owner key stored in the Qt wallet that created the deposit.
Does the exchange receive my KAD private key?
No. Kadikama Qt creates the owner key locally. The exchange receives public deposit metadata needed to identify and validate the vault, but it does not receive the owner private key or wallet seed.
Why are Web3 and Kadikama Qt both used?
Web3 identifies the Ethereum account used for USDT. Kadikama Qt identifies the KAD wallet and holds the owner key for KADDEX vaults. They are bound to one exchange account without sharing either wallet's private key.
Does connecting either wallet move funds?
No. Connection and browser authorization do not transfer KAD or USDT. A deposit or withdrawal is a separate action with an amount and wallet confirmation.
How do I deposit KAD?
Open Funds, choose Deposit from Qt, enter an amount and approve the request in Kadikama Core 1.0.2. Qt creates the owner-controlled vault, registers its public metadata and broadcasts the transaction. The balance is credited after two Kadikama confirmations.
Where is deposited KAD held?
It is held on the Kadikama blockchain in the KADDEX vault output created by Qt. The owner key remains in the user's wallet; it is not a server vault key.
How quickly do orders execute?
Confirmed deposits become credited balances. Matching compatible limit orders changes available and locked balances without waiting for a new blockchain confirmation for every fill. Entry and exit still wait for their respective networks.
What happens to funds in an open order?
A sell order moves its KAD amount from Available to Locked. A buy order locks the required USDT. Fills consume the matched portion, and cancellation returns only the unfilled remainder to Available.
How do I withdraw KAD?
Select an active deposit and amount in Funds, then approve the request in the same Qt wallet that created it. Qt verifies the funding output, creates a fresh destination in that wallet and signs the complete transaction locally.
Can I withdraw only part of a KAD deposit?
Yes. The requested amount is paid to a fresh address in the Qt wallet and the remainder returns to the same owner-controlled vault. After the 0.00001000 KAD fee, a non-zero remainder must be at least 0.01 KAD.
Can the website change my KAD withdrawal destination?
Not after Qt signs it. KADDEX withdrawals use SIGHASH_ALL, so changing the destination, amount, inputs or outputs invalidates the owner signature.
What if the exchange website is temporarily unavailable?
Confirmed KAD remains in its on-chain owner-controlled vault, but the normal order book and assisted withdrawal workflow are unavailable until the service returns. Keep the original Qt wallet and its backup because it contains the owner key and local recovery metadata.
Does KADDEX also hold USDT?
No. KADDEX is the native Kadikama settlement layer. USDT remains on Ethereum Mainnet and uses the Ethereum settlement contract and the connected Web3 wallet.
What are the native swap rules?
KADDEX also defines a hash-locked swap output. The buyer claim path needs the buyer signature and correct 32-byte secret; the seller refund path needs the seller signature after the encoded block-height locktime.
Do miners and pools need to upgrade?
Miners, pools and validating services that intend to accept KADDEX transactions should run Kadikama Core 1.0.2 before block 16,000. Ordinary historical transactions and previously mined balances are not rewritten.
What should I verify before confirming?
Verify the domain trade.kaddex.space, the network, amount, wallet address, expiry and fee. Never enter a seed phrase or private key into the website.