# Introduction

The BTFS TestNet allows developers to access the full functionality of BTFS in a controlled test environment. The following guide will guide the user through connecting to the test net, storing files, and retrieving files. For each new BTFS node, follow the process below to use the TestNet. Start up in the same manner as inside the Install&Run BTFS2.0 Node, including topping up BTT to BTTC ADDRESS,and topping up WBTT to VAULT ADDRESS ; the current top-ups are run in the TestNet environment.

# Install BTFS2.0

Install BTFS by following the [Install & Run BTFS2.0 Node ](🔗) . Once BTFS is installed, initialize the daemon



# Testnet Configuration

Apply the testnet configuration profile.



# Start the daemon



At this point, it is necessary to charge the BTTC ADDRESS 0x7Cf4B71017F0312037D53fe966CE625BF98FFff6, and it is recommended that 1000 BTT to complete the node contract deployment; then it will run to completion.

# VAULT ADDRESS Recharge

Although it runs successfully, you need to recharge the VAULT ADDRESS to upload the file. In the node startup log, the VAULT ADDRESS is found as follows. `self vault: 0x47813456f0951493347010a4f27aafbdcca61025 ` You can top up to the VAULT ADDRESS through your own wallet before you can upload the file.

# File Upload

Store a file to the BTFS network.

Warning

Files uploaded to the testnet will be purged periodically. Do not use the testnet for persistent storage.



Query the storage process by running `btfs storage upload <ID> status | jq`. Storage upload process is complete once all shards show complete and the file level storage shows complete.



# File Retrieval

Retrieve the file from the BTFS network by first removing the file from your local node, and then running `btfs get`.



# Replenish Testnet BTT

If you ever run out of testnet BTT balance, in order to replenish, you will need to generate a new BTFS key-pair. This can be achieved by shutting down BTFS, removing the `~/.btfs` directory, re-initializing BTFS, applying the storage-client-testnet profile, and finally re-starting the daemon.

Warning

Removing the .btfs directory results in:

  1. Removal of your existing BTFS node ID.

  2. Removal of files uploaded to your local go-btfs node only. Therefore, make sure you back up the .btfs directory and the necessary copies of the files you need, elsewhere.