> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/id/panduan-pengembang/websocket-subscriptions.md).

# Langganan WebSocket

Endpoint EVM Rome mendukung langganan Ethereum WebSocket (`eth_subscribe` / `eth_unsubscribe`) melalui `wss://`. Sambungkan ke host yang sama seperti RPC HTTPS, dengan `wss://` skema:

```
wss://<chain>.<network>.romeprotocol.xyz/
```

Inilah yang `ethers` / `viem` `WebSocketProvider` digunakan di balik layar, jadi `.on('block')`, `contract.on(event)`, dan `viem`'s `watchEvent` / `watchBlocks` berfungsi langsung tanpa konfigurasi.

## Jenis langganan

| Tipe                     | Dipicu pada                                         | Digunakan untuk                                                               |
| ------------------------ | --------------------------------------------------- | ----------------------------------------------------------------------------- |
| `newHeads`               | setiap blok baru                                    | pemantau blok, menyegarkan saldo/nonce, bot per-blok, pengindeks              |
| `logs`                   | event yang cocok (berdasarkan `address` / `topics`) | bereaksi terhadap event kontrak Anda, relayer/jembatan, bot trading           |
| `newPendingTransactions` | —                                                   | diterima tetapi tidak pernah memancarkan (Rome tidak memiliki mempool publik) |

## ethers (v6)

```javascript
import { ethers } from "ethers";

const provider = new ethers.WebSocketProvider(
  "wss://martius.testnet.romeprotocol.xyz/"
);

// newHeads
provider.on("block", (blockNumber) => {
  console.log("blok baru", blockNumber);
});

// logs — bereaksi terhadap event kontrak
const contract = new ethers.Contract(address, abi, provider);
contract.on("Transfer", (from, to, value) => {
  console.log("Transfer", from, to, value.toString());
});
```

## viem

```javascript
import { createPublicClient, webSocket } from "viem";

const client = createPublicClient({
  transport: webSocket("wss://martius.testnet.romeprotocol.xyz/"),
});

const unwatch = client.watchBlocks({
  onBlock: (block) => console.log("blok baru", block.number),
});

client.watchEvent({
  address,
  onLogs: (logs) => console.log(logs),
});
```

## JSON-RPC mentah

```json
→ {"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["newHeads"]}
← {"jsonrpc":"2.0","id":1,"result":"0x…"}                       // id langganan
← {"jsonrpc":"2.0","method":"eth_subscription","params":{"subscription":"0x…","result":{…block…}}}
```

Untuk `logs`, berikan objek filter sebagai parameter kedua:

```json
{"jsonrpc":"2.0","id":1,"method":"eth_subscribe","params":["logs",{"address":"0x…","topics":["0x…"]}]}
```

## Catatan

* Langganan mendorong pembaruan saat blok baru dibuat (latensinya berada pada kisaran waktu satu blok).
* Untuk koneksi yang berumur panjang, tangani penyambungan ulang di klien Anda — standar untuk RPC WebSocket apa pun.


---

# 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.rome.builders/id/panduan-pengembang/websocket-subscriptions.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.