Contract Procedure

Phase 1 - Sending tokens to SXPSwap Contract (BSC/ETH)¶

In order to facilitate a successful migration, the Swipe (SXP) tokens on BEP20/ERC20 are meant to enter a contract and never leave the contract ever again.
This is facilitated by a contract on BEP20 and ERC20.

The process consists on 2 main functions.
1. The first function "approve", which exists on the Swipe (SXP) token contract, this serves for the purpose of approving the SXPSwap contract to move the Swipe tokens over the new SXPSwap Contract.
2. The second function "transferTokenToContract", this serves for the purpose of sending the tokens that were previously approved to SXPSwap.

Functions on the new contract.
The function "transferTokenToContract" is only accepted if the following parameters are included.

These parameters are:

1. Address of Swipe token.
   
2. Amount of tokens to be transferred.
   
3. A valid SXP mainnet address to be entered in string format.
   
   If these parameters are missing, the transaction will fail.
   

Validation¶

New wallet address validation¶

There are 4 validation controls for the SXP mainnet address that check for a 34 character address with the S prefix.
1. Validation on the frontend for Metamask users that are using the official SXPSwap tool.
2. Validation on the smart contract to only allow addresses with a certain prefix.
3. Validation on the backend program that sends the mainnet SXP to the new address.
4. Validation by the forging nodes that accept or deny the transaction created by the backend tool.

Interacting with the contract directly and entering a wrong address by accident or on purpose will result in loss of funds.
There is no way to recover the tokens from a contract and sending new SXP tokens on mainnet is impossible without a valid transaction on the contract side.

Notes¶

Other tokens can be sent to the SXPSwap contract.
These tokens can not be recovered and will not be accepted by the backend program that broadcasts the swap to the forging delegates.
Due to the validation by the backend program and the validation from the forging delegates, trying to send "fake" SXP tokens with a correct SXP mainnet address will have no impact on the swap procedure.