# 6 : Wrap a token from Stellar Classic to Soroban.

## Token Playground Chapter 6 : Wrap a token from Stellar Classic to Soroban.

* Check this guide in <https://token-playground.gitbook.io/>
* Edit this guide in it's repo: <https://github.com/esteblock/token-playground/>
* Contribute to this guide in the [./docs folder](https://github.com/esteblock/token-playground/tree/main/docs) of the repo

### 1. Introduction

In the previous chapters we have managed to issue a (classic) Stellar Assets in the (classic) Stellar blockchain. In this chapter we will **wrap** that **Stellar Asset** into a **Stellar Asset Contract (SAC)** token inside **Soroban**.

### 2. Setting up your soroban-cli

Before using the `soroban-cli`, we need to configure it by telling which account will be executing and signing the transactions. In order to do this, we will call the `soroban config identity` command and we will provide it with the account's private key.

Here we will suppose that our user is the token admin of the asset, so we will call it `token-admin`, but you can choose another name for this.

1. Setup your `.soroban/identity` folder

First create the folder if it does not exist yet

```bash
mkdir -p ./soroban/identity
```

`soroban-cli` will read from here your identity. Inside this folder you'll need to create one file with `.toml` for every identity you want to have. If you want to have `user-name-1`, `user-name-2` and `user-name-3`. Your `.soroban/identity` folder should have 3 files and should look like this

```
.soroban/identity/user-name-1.toml
.soroban/identity/user-name-2.toml
.soroban/identity/user-name-3.toml
```

Where each `user-name-X` is a text file with the following structure:

```
secret_key=SBBSXWIML25UV46X3MPC7P4UZISJ2RCCTHHD6PUGRRVHPYLKNXXW2N4I
```

In this Playground we have our secrets in the `./settings.json` file, hence we will do:

```bash
TOKEN_ADMIN_SECRET=$(cat ./settings.json | jq -r '.issuerSecret' )
mkdir -p ".soroban/identity"
echo "secret_key = \"$TOKEN_ADMIN_SECRET\"" > ".soroban/identity/token-admin.toml"
```

2. Configure your soroban-cli to use the `token-admin` identity Next, every time that we want to call soroban-cli using our `token-admin` identity, we should add into our args: `--source token-admin`

### 3. Wrap your Stellar Asset into Soroban

For this you'll need the full Stellar Asset identification [read our chapter about Basic Concepts](/guide/index/2_basic_concepts.md). The asset identification is built by:

* The asset code (example: `USDC`)
* The issuer address (example: `GCUA5RTRR4N4ILSMORG3XFXJZB6KRG4QB22Z45BUNO5LIBCOYYPZ6TPZ`)

In order to wrap an asset you'll need to use the `soroban lab token wrap` command as follows:

```bash
soroban lab token wrap --network standalone --source token-admin --asset "ASSET_CODE:ISSUER_ADDRESS"
```

where the `token-admin` source is the identity of the user that will sign the transaction. We will see in a further chapter that this source does not necessary needs to be the token admin itself. This command will return the `address` of the SAC smart contract that will manage the wrapped token.

```
GAM5XOXRUWPMKENBGOEAKMLRQ4ENHLHDSU2L2J7TVJ34ZI7S6PHMYIGI
```

This correspond to the contract address.

### 4. Save the contract address for further use!

The contract address of this Stellar Asset Contract that is wrapping your Stellar Asset is crucial in order to use the token inside Soroban, so be sure to save it in a safe place!

In order to do this, you can do:

```bash
TOKEN_ADDRESS=$(soroban lab token wrap $ARGS --asset "$ASSET_CODE:$ISSUER_ADDRESS")
echo "Token wrapped succesfully with TOKEN_ADDRESS: $TOKEN_ADDRESS"
echo -n "$TOKEN_ADDRESS" > .soroban/token_address
```

What happens if you did not saved the contract id? Don't worry, in [Chapter 9](broken://pages/h1KYCoeKrFVajG8M2xTp) we will show how to recover the contract id of an already wrapped Stellar Asset.

Here, you'll find a fragmet of the code that includes all steps and exemplifies how to wrap a Stellar Asset:

```bash
NETWORK="standalone"
ASSET_CODE="MY_ASSET"
TOKEN_ADMIN_ADDRESS="GCUA5RTRR4N4ILSMORG3XFXJZB6KRG4QB22Z45BUNO5LIBCOYYPZ6TPZ"

ARGS="--network $NETWORK --source token-admin"
TOKEN_ID=$(soroban lab token wrap $ARGS --asset "$ASSET_CODE:$TOKEN_ADMIN_ADDRESS")
echo "Token wrapped succesfully with TOKEN_ID: $TOKEN_ID"

mkdir -p .soroban
echo -n "$TOKEN_ID" > .soroban/token_id
```

Another example, without the usage of `source` can be:

```bash
soroban lab token wrap --asset="AstroDollar:GAM5XOXRUWPMKENBGOEAKMLRQ4ENHLHDSU2L2J7TVJ34ZI7S6PHMYIGI" --secret-key SAHC723FQTC3MARBNUZLUFEIYI62VQDQH7FHLD2FGV6GROQQ7ULMHQGH --rpc-url https://horizon-futurenet.stellar.cash:443/soroban/rpc --network-passphrase 'Test SDF Future Network ; October 2022'
```

### 5. Use our code

If you want to use our **code** in the [Token Playground's Repo](https://github.com/esteblock/token-playground/), you can just call our script with the `soroban-preview-10` docker containter

You can run it by:

```bash
docker exec soroban-preview-10 ./src/wrap.sh standalone using_docker
```

Check all the code of our `wrap.sh` script [here](https://github.com/esteblock/token-playground/blob/main/src/wrap.sh)

## Next?

In the next two chapters we will mint tokens inside Soroban from an already wrapped Stellar Asset using its SAC's contract id. Are you ready?

***

This Playground has been developed by [@esteblock](https://github.com/esteblock/) in collaboration with [@marcos74](https://github.com/marcos74) from [@Dogstarcoin](https://github.com/Dogstarcoin)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://token-playground.gitbook.io/guide/index/6_wrap_a_token_from_classic_to_soroban.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.