> For the complete documentation index, see [llms.txt](https://docs.stacks.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stacks.co/reference/stacks.js/stacks-connect/methods/stx_signstructuredmessage.md).

# stx\_signStructuredMessage

Requests the connected wallet to sign a structured Clarity value message (SIP-018 compliant). This is used for domain-separated, typed data signing.

***

### Usage

```ts
import { request } from '@stacks/connect';
import { Cl } from '@stacks/transactions';

const result = await request('stx_signStructuredMessage', {
  message: Cl.stringAscii('Hello, Stacks!'),
  domain: Cl.tuple({
    name: Cl.stringAscii('My App'),
    version: Cl.stringAscii('1.0.0'),
    'chain-id': Cl.uint(1),
  }),
});

console.log('Signature:', result.signature);
console.log('Public Key:', result.publicKey);
```

#### Notes

* The `message` must be a `ClarityValue` object (constructed using `Cl` helpers from `@stacks/transactions`).
* The `domain` must be a `TupleCV` containing domain separation fields. This follows the SIP-018 standard for structured data signing.
* Clarity values are automatically serialized to hex strings before being sent to the wallet.
* For signing simple plaintext messages, use [`stx_signMessage`](/reference/stacks.js/stacks-connect/methods/stx_signmessage.md) instead.

[**Reference Link**](https://github.com/stx-labs/connect/blob/main/packages/connect/src/methods.ts#L113)

***

### Signature

```ts
function request(
  'stx_signStructuredMessage',
  params: SignStructuredMessageParams
): Promise<SignMessageResult>
```

***

### Returns

`SignMessageResult`

```ts
interface SignMessageResult {
  signature: string;
  publicKey: string;
}
```

| Property    | Type     | Description                                  |
| ----------- | -------- | -------------------------------------------- |
| `signature` | `string` | The hex-encoded DER signature.               |
| `publicKey` | `string` | The hex-encoded public key used for signing. |

***

### Parameters

#### message (required)

* **Type**: `ClarityValue`

The Clarity value to sign. Can be any valid Clarity type (e.g. `Cl.stringAscii(...)`, `Cl.uint(...)`, `Cl.tuple(...)`).

#### domain (required)

* **Type**: `TupleCV`

A Clarity tuple value containing domain separation fields. Standard fields include:

| Field      | Type          | Description                                               |
| ---------- | ------------- | --------------------------------------------------------- |
| `name`     | `StringASCII` | The name of the application.                              |
| `version`  | `StringASCII` | The version of the application.                           |
| `chain-id` | `UInt`        | The chain ID (`1` for mainnet, `2147483648` for testnet). |


---

# 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.stacks.co/reference/stacks.js/stacks-connect/methods/stx_signstructuredmessage.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.