# syncing

### REQUEST

```
POST https://mainnet-slice-rpc.com
```

#### HEADERS

```
Content-Type: application/json
```

#### EXAMPLE

```
## JSON-RPC over HTTPS POST
curl https://mainnet-slice-rpc.com \
    -X POST \
    -H "Content-Type: application/json" \
    -d '{"jsonrpc":"2.0","method":"eth_syncing","params": [],"id":1}'

## JSON-RPC over WSS
wscat -c ws://mainnet-slice-rpc.com
>{"jsonrpc":"2.0","method":"eth_syncing","params": [],"id":1}
```

### RESPONSE

#### RESULT FIELDS

* `SYNC STATUS` - a boolean as false **only** when not syncing
* `SYNC BLOCKS` i. `startingBlock` - a hexcode of the integer indicating the block at which the import started (will only be reset, after the sync reached his head) ii. `currentBlock` - a hexcode of the integer indicating the current block, same as eth\_blockNumber iii. `highestBlock` - a hexcode of the integer indicating the highest block

#### BODY

```js
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": false
}
```


---

# 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://slice-ledger.gitbook.io/sliceledger/api/syncing.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.