# accounts

### 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_accounts","params":[],"id":1}'

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

### RESPONSE

#### RESULT FIELDS

* `ADDRESSES` - arrays of hex codes as strings representing the addresses owned by the client

NOTE: While this JSON-RPC method is supported by SliceLedger, it will *not* return any accounts. SliceLedger does not support "unlocking" accounts. Instead, users should send already signed raw transactions using `eth_sendRawTransaction`.

#### BODY

```
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": []
}
```


---

# 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/accounts.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.