Scribd
Upload
71 views2 pages

SSH CryptoHost Fund Transfer Guide

The document outlines the process for loading funds into a global server using a specific transmission type (MT103/202 COV FTP) and the necessary files generated during this process. It details the steps the receiver must take to decrypt, convert, and broadcast the transaction using an external server connected to both the global server and CRYPTOHOST. Additionally, it lists the required information needed to complete the transaction after uploading to the crypto host.

Uploaded by

xh24ttjc6q
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
71 views2 pages

SSH CryptoHost Fund Transfer Guide

The document outlines the process for loading funds into a global server using a specific transmission type (MT103/202 COV FTP) and the necessary files generated during this process. It details the steps the receiver must take to decrypt, convert, and broadcast the transaction using an external server connected to both the global server and CRYPTOHOST. Additionally, it lists the required information needed to complete the transaction after uploading to the crypto host.

Uploaded by

xh24ttjc6q
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

SSH CRYPTOHOST

LOADING

Funds are loaded into the global server with a MT103/202 COV FTP type of
transmission.
Type of funds: M1
Cloud type: CRYPTOHOST
Together with the loading the following files are generated: .fin, .cef, .dll, particular RSA
key and Blackscreen. The files come RAW and encrypted which will require the receiver
to decrypt and convert before actually moving on with transaction.

UPLOAD PACKAGE
Receiver provides the SSH login information.
Sender loads into the SSH following files:
1. .cef
2. .fin
3. .dll
4. RSA key
5. CIS
6. Black screen

STEPS that receiver has to :

While using an external server / external bank layer server connected to both Global
Server and CRYPTOHOST the receiver has to:
a. **Open .cef File***: USE the RSA key uploaded to decrypt the .cef file
b. **CONVERT FILE***: Utilize “[Link]” to convert the decrypted file
c. ***GENERATE JSON**: Upon successful conversion, a .json file will be
generated
d. ***BROADCAST**: Bind your cryptocurrency by broadcasting the
transaction on-chain. On this particular step, the funds are downloaded
and converted at the same time using the connection with the global
server and Cryptohost server, while being also sent toward the receiver
master wallet also connected to the Cryptohost.

After successfully uploading to our crypto host, we will need the following information to
complete the transaction:

►API Key
►Access Key
►App ID
►API Endpoint
►Wallet ID
►Network
MECHANISM

Funds uploaded to
1 GLOBAL SERVER
TYPE of funds: M1
CLOUD TYPE:
CRYPTOHOST
GLOBAL
CRYPTOHOST
SERVER

4
BROADCAST and bind your
SENDER cryptocurrency by
2 broadcasting the transaction
Sender uploads in on-chain.
receiver private On this step, based on
server via SSH the .json file, the funds are
connection the authomatically downloaded
PRIVATE
following files:
1. .cef
SERVER 3 and converted
into USDT in the RECEIVER
2. .fin 1. **Open .cef File***: USE same time with WALLET
3. .dll the RSA key uploaded to being transferred
4. RSA key decrypt the .cef file to receiver wallet.
6. Black screen 2. **CONVERT FILE***:
Utilize “[Link]” to
convert the decrypted file
3. ***GENERATE JSON**:
Upon successful
conversion, a .json file will
be generated
5 PAYOUT

After successfully uploading to our crypto host, we will need the following information to complete the
transaction:

►API Key
►Access Key
►App ID
►API Endpoint
►Wallet ID
►Network

You might also like