# Setup LiquidOps on Voltage nodes (API based - pull)

### Setup in Voltage

After logging into your Voltage account, navigate the left side menu and click on "Settings". Scroll down to the "Connect Settings" section&#x20;

* Ensure that gRPC is enabled.
* If you are using the IP Whitelist feature, include the following IP addresses:
  * 34.170.53.37
  * 34.70.20.229

<figure><img src="/files/oK5VoY0uqPX1VQ7RAoYK" alt=""><figcaption><p>LiquidOps on Voltage node: <strong>Readonly Macaroon (hex)</strong> </p></figcaption></figure>

Next, navigate to the **Connect** page from the left side menu.&#x20;

In the **Application** menu, choose **Manual** option. You are invited to copy **API Endpoint**, **Readonly Macaroon (hex)** and **TLS Certificate:**

#### **API Endpoint**&#x20;

In this example, the API Endpoint is "**demo.m.voltageapp.io**". Make a note of this value.

#### **Readonly Macaroon (hex)**

&#x20;Copy the entire content of the field. In our case, the readonly macaroon starts with "0201."

<figure><img src="/files/xPaHe5qOnJ3IqBSthqqX" alt=""><figcaption><p>LiquidOps on Voltage node: <strong>Readonly Macaroon (hex)</strong> </p></figcaption></figure>

#### **TLS Certificate**&#x20;

Scroll down the page and locate the TLS Certificate section. Select the option to "Show base64" and make a copy of the value. In our case the TLS certificate starts with "LS0..."

<figure><img src="/files/LlHGoHUUwsIHzfd7f4pg" alt=""><figcaption></figcaption></figure>

### Setup in Bolt.Observer

Log into your account at [bolt.observer](https://bolt.observer/), and add your Voltage node to the **Node page** either by entering the alias or the pubkey. Read [Getting started](/readme/liquidops/getting-started.md) for more details on how add your first node.

{% hint style="info" %}
When adding a new node to bolt.observer, please ensure that you wait for a duration of 10 minutes after its creation in Voltage. This waiting period is necessary to allow the node to be visible on the graph and successfully added to the platform.
{% endhint %}

Then click on Go to Node as shown below

<figure><img src="/files/1IODISZ4lhaJAAX7FTxl" alt=""><figcaption><p>Setup LiquidOps </p></figcaption></figure>

On your node page, setup LiquidOps by clicking on "Enroll in LiquidOps"

<figure><img src="/files/99CTjNNcHivVLb2UBZmL" alt=""><figcaption></figcaption></figure>

In the subsequent menu, click **CONTINUE** under LND Node.

<figure><img src="/files/uIZl51Dn26ouabLk2wqQ" alt="" width="337"><figcaption></figcaption></figure>

Now, you need to provide the following values obtained earlier:

* In the field **Address,** paste the [#api-endpoint](#api-endpoint "mention")and add ":10009" in the end. In our example, he Address should have the following format demo.m.voltageapp.io:10009
* In the field **Macaroon(hex)**, paste the [#readonly-macaroon-hex](#readonly-macaroon-hex "mention")
* In the field **Certificate,** paste the [#tls-certificate](#tls-certificate "mention")
* In the field **Certificate verification type,** select the option **Allow when public key is the same.**  Voltage uses a short-lived Let's Encrypt certificate, by selecting this option you will avoid manual updates of the TLS certificate.

<figure><img src="/files/W50yjmLc7DCcfp9Ye9PP" alt=""><figcaption></figcaption></figure>

Once macaroons are configured, you will get the confirmation that LiquidOps is enabled as follows: &#x20;

<figure><img src="/files/pk3RxTwpEQcb4i5sr2hc" alt=""><figcaption></figcaption></figure>


---

# 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.bolt.observer/readme/guides/setup-liquidops-on-voltage-nodes-api-based-pull.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.
