# Getting started

The Oasis Network is a high-performance and privacy-first blockchain network. It is operated by a group of independent and decentralized nodes. Each node is free to run its own software and to provide computing services to the public, as long as the network can reach a consensus on the computational results.

Second State has created the Oasis Ethereum runtime that supports both EVM and Ewasm smart contracts and dapps (decentralized applications). A network of Oasis validator nodes will deploy the Second State runtime and provide Ethereum services to the public. With BUIDL, it is a breeze to develop dapps on Oasis Network's Ethereum runtime nodes.

## Step1 Configure BUIDL for Oasis Ethereum

The easy way is to just click the link below to launch BUIDL in your browser. It pre-loads all the configurations for you.

{% embed url="<http://oasiseth.org/dev>" %}

![](/files/-MF6fX_7tCpxVLbI_8ID)

## Step 2 Get some Oasis ETH tokens for gas

In the **Accounts** tab, you will see 5 auto-generated addresses, and you can set any of them as default. The default address is used to sign transactions. Because of that, you will need to send a little Oasis ETH into that account to pay for gas fees.

![](/files/-MF6fdipeHO3vJR4c12C)

Go to the faucet website, enter your default address from BUIDL and give yourself some gas.

{% embed url="<http://faucet.oasiseth.org>" %}

![](/files/-MVvrfspEF_gWJgi6vpr)

Now, go back to BUILD's Accounts tab and you should see 0.01 OETH (or 10^18 wei) in your default address.

![](/files/-MF6g2V3uYCHlORcRshL)

## Step 3 Compile and deploy a smart contract

Click on the **Compile** button to compile the contract. A sidebar will open to show you the compiled ABI and bytecode of the contract.

![](/files/-Ljvt0TCDNmMVAyWB7Ap)

Next, you can press the **Deploy to the chain** button on the left panel to instantiate and deploy the contract to Oasis Network Ethereum runtime nodes. You can interact with deployed contracts by calling its public methods from inside [BUIDL](http://buidl.secondstate.io/) -- you can **set** its value and click on the **Transact** button to save the value onto the blockchain, and then click on the **Call** button to see the value in the **LOG** panel.

![](/files/-LjvtBzOEBmrEDsKAX9G)

## Step 4 Create an HTML Dapp

Once deployed, click on the **dapp** button on the left bar to work on your DApp.

![](/files/-LjvtS5gzcg150d5Y5yC)

The HTML tab above shows a simple HTML page with two buttons.

Next, go to the JS tab. It shows JavaScript on how to interact with the smart contract. It provides event handlers for the buttons. When a user clicks on the button, the JavaScript calls the smart contract functions via the web3 library.

![](/files/-MF6j7TcNY0EfPe9kMI0)

Finally, click on the **Run** button to run the DApp. You will see the DApp UI in the right panel. You can click on the **Set Data** button to store a number, and **Get Data** button to retrieve the stored number.

![](/files/-LjvviN3FlXf14V8PpSB)

Congratulations. You now have a complete DApp deployed on the Oasis Network!

Next, you can go through our tutorials to create and publish a [decentralized social media app](/oasis-network-ethereum-runtime/tutorial-oasistweet.md) or your own [ERC-20 tokens to be traded on Uniswap](/oasis-network-ethereum-runtime/tutorial-erc20.md)!


---

# 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.secondstate.io/oasis-network-ethereum-runtime/getting-started.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.