# Test bridge

Let's test by sending some tokens.

```bash
export FROM=$KYLIN_TEST_ACCOUNT
export TO=$KYLIN_BRIDGE_ACCOUNT
export QUANTITY="1.0000 TKN"
# user address, not token/tokenpeg account/contract, third account you created
export MEMO="0xE60dEdC13Ee13D563034dF75Acce5C58CB60ab12"
cleos -u $KYLIN_ENDPOINT push action $KYLIN_TOKEN_ACCOUNT transfer "[\"$FROM\",\"$TO\",\"$QUANTITY\",\"$MEMO\"]" -p $KYLIN_TEST_ACCOUNT@active  
```

Now let's see if the tokens make it! Navigate to your user account's address

{% embed url="<https://testnet.bscscan.com/address/0xE60dEdC13Ee13D563034dF75Acce5C58CB60ab12#tokentxns>" %}

![](/files/-Ma0T8WtWugQ68Er2XAq)

Now let's send it back!

Navigate to your tokenpeg contract on the EVM side, click on the contract tab, go to Write Contract, and connect using your user's account.

![](/files/-Ma0TdbSNev9qQKBocsL)

Scroll to #4.  We're going to send 1 token back `10000`. And to determine the destination address we're going to use a helper function on our bridge contract.

```bash
cleos -u $EOS_ENDPOINT push action $KYLIN_BRIDGE_ACCOUNT getdest '["YOUR EOSIO USER ACCOUNT HERE"]' -p $KYLIN_BRIDGE_ACCOUNT@active
```

The assertion error will relay the `uint64_t` for the account specified, and you said EOSIO assertion messages weren't good for anything, pish posh, we move on!

`Destination EOSIO Account Name Value: 11075078730411234672`

![](/files/-Ma0UNd0B7fY_qAn7Yq7)

Fire. [Example trx](https://testnet.bscscan.com/tx/0x301dddac2349b7b1c4fd73d11145f28ff015a2b8209d820df45e987360d46a8a)

And shazam you've got tokens! <https://kylin.eosq.app/tx/cbc1bd2591efc7311358ce1ee17c95e8da2dfbf895c00051f401afc794013be0>


---

# 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://docs.liquidapps.io/liquidapps-documentation/cross-chain-bridges/getting-started-with-liquidbridge/eosio-less-than-greater-than-evm/test-bridge.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.