> For the complete documentation index, see [llms.txt](https://docs.itheum.io/product-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.itheum.io/product-docs/pre-aithra/pre-aithra-integrators/data-dex-guides/astar-network/guide-1-get-started-with-the-data-dex-on-astar-network/section-1-setting-up-wallets-on-astar-network-shibuya-testnet.md).

# Section 1: Setting up wallets on Astar Network - Shibuya Testnet

**Step 1)** Install MetaMask and connect to the Astar Network Shibuya Network

Here are the details you can use to add the new network to MetaMask:<br>

* Network Name : **Shibuya Network**
* New RPC URL : [**https://evm.shibuya.astar.network/**](https://evm.shibuya.astar.network/)
* Chain ID : 81
* Currency Symbol : **SBY**
* Block Explorer URL : [**https://shibuya.subscan.io**](https://shibuya.subscan.io)

There are some details [provided here as well one this.](https://docs.adaotop.com/guides/shibuya-test/how-to-add-and-connect-shibuya-network)

Now, your MetaMask wallet is ready to be used in the Shibuya Network.

\
**Step 2)** In Metamask, you should have two accounts set up to simulate a Data Seller and Data Buyer workflow.

\
Follow the official instructions here:

<https://support.metamask.io/hc/en-us/articles/360015289452-How-to-create-an-additional-account-in-your-wallet>

\
For easy reference, we can name the accounts:

* Data Seller
* Data Buyer

\
**Step 3)** You will need some  SBY (Astar Shibuya) tokens to pay gas for transactions.

The quickest way we found to get some SBY from the Faucet is via the chaindrop faucet located here : <https://chaindrop.org/?chainid=81&token=0xeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeeee>

There are also other faucet options detailed here: <https://docs.astar.network/docs/build/environment/faucet/>

\
Use the faucet to get some SBY into your Data Seller and Data Buyer MetaMask Accounts.

\
**Step 4)** After completing the above steps, you should have your MetaMask state looking similar to the image below.

<figure><img src="https://lh3.googleusercontent.com/o0KFawK9VnOgps8QA2O6KZNN5jNMDLqCYEvIgawTRNTaZ8zw6i0fySFyHDLNt54t-wCbkkqBEanBsSXcX_Ot91SKdi5X3e-upVU5P38SrEMDwXB9tuh147S5yMzA9fUvVOC_ZtV8ZpmgNAcoHTPUNmY" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.itheum.io/product-docs/pre-aithra/pre-aithra-integrators/data-dex-guides/astar-network/guide-1-get-started-with-the-data-dex-on-astar-network/section-1-setting-up-wallets-on-astar-network-shibuya-testnet.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.