All Collections
Wallet Services
Information about infrastructure migration and new crypto wallet addresses
Information about infrastructure migration and new crypto wallet addresses
Kriptomat Support Team avatar
Written by Kriptomat Support Team
Updated over a week ago

Kriptomat has migrated to a completely new infrastructure. This process was ongoing from 25 January to 17 June 2021.

This new infrastructure boasts some truly incredible security and scaling improvements, allowing us to provide an enterprise-grade platform for trading, moving, and storing digital assets.

With our new overhaul, when making a crypto withdrawal, you are now able to see the exact amount of coins that the receiving wallet will get. This should offer a greatly improved experience over our previous system, which calculated network and transaction fees in the background─leaving you guessing how much would actually be sent.

***

WHAT THIS MEANS FOR YOU AS A USER OF OUR SERVICE:

Your old Kriptomat crypto wallet addresses will change! If you want to send cryptocurrencies to your Kriptomat wallet, you need to double-check the wallet address inside your Kriptomat account. See how to do this.

This is especially important if you have recurring transfers coming in to, or going out of your account, so you’ll need to make sure you inform the counterparty that your wallet has changed.

To make this transition easier, for the next 12 months you’ll still receive payments sent to your old crypto wallet addresses. However these transfers may take longer to complete as we will be re-routing them to your new addresses, and this may incur additional transfer fees.

Please keep in mind that the old crypto wallet addresses will phase out on 11th July 2022, of which you will receive periodic reminders until the date. After this date, we will no longer provide support for these addresses so kindly make sure you switch to your new address on time.

***

Do you have any questions? Use the support chat to contact our support team or send us an email at [email protected]

Did this answer your question?