Findora SDKcontains a
Triple MaskingAPI, which enables developers to have access to the latest
Findoraprivacy features, such as a fully secured transfer with zero visibility and full privacy.
User can transfer funds from its normal wallet to the anonymous wallet. This process is called
bar to abar.
bar to abarprocess is completed, then only the person, who has access to the keys of that anonymous wallet as well as to the special hash with the transfer information (a.k.a a commitment), would be able to decode the information related to that transfer, to see its balance and to use funds from it, like to transfer it back to the normal wallet and so on.
After funds are converted (using
bar to abar), they are fully secured and hidden under full privacy protection, which basically means, that nobody can trace neither the sender normal wallet information, nor the amount or type of the asset whatever. It is fully secured and the only way to retrieve that iformation, as well as to use those funds, is to have both the commitment and the anonymous wallet information.
It is critically important to secure and protect this information, otherwise funds would be completely lost without any option to recover it.
To receive funds from the anonymous walllet, user needs to perform the opposite (reversed) operation, which is called
abar to bar. For that user needs to provide the commitment and some pieces of the anonymous wallet information, as well as the information about the normal wallet (where the funds should be tansfered to).
Both operations (and a few others, such as
abar to abar transfer) are available in the
Findora SDKvia its
Triple MaskingAPI, please see the examples in the next chapters.