> 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-bitcoin-staking/types/multisigtxparams.md).

# MultiSigTxParams

Transaction parameters for an M-of-N multisig origin, such as a `bond-admin` held by a 2-of-3 multisig: the [TxParamsBase](/reference/stacks.js/stacks-bitcoin-staking/types/txparamsbase.md) fields plus `UnsignedMultiSigOptions` from `@stacks/transactions`. It is one side of the [TxParams](/reference/stacks.js/stacks-bitcoin-staking/types/txparams.md) union that every `build*` function accepts.

***

### Usage

```ts
import { buildSetBondAdmin } from '@stacks/bitcoin-staking';
import { TransactionSigner } from '@stacks/transactions';

const tx = await buildSetBondAdmin({
  newAdmin: 'SP2C2YFP12AJZB4MABJBAJ55XECVS7E4PMMZ89YZR',
  publicKeys: [pubKeyA, pubKeyB, pubKeyC],
  numSignatures: 2,
  fee: 10_000n,
  nonce,
  network: 'mainnet',
});

// Fields follow the order of publicKeys: sign with two keys, append the third.
const signer = new TransactionSigner(tx);
signer.signOrigin(privKeyA);
signer.signOrigin(privKeyB);
signer.appendOrigin(pubKeyC);
```

#### Notes

* Builders default `useNonSequentialMultiSig` to `true`, so the transaction uses the non-sequential multisig hashmode. Pass `useNonSequentialMultiSig: false` for the sequential one. `makeUnsignedContractCall` called directly does the reverse and uses the sequential hashmode unless the option is set.
* Without `address`, the public keys are used in the order given. With `address`, the given order is kept if it derives that address, the sorted order is used if that derives it instead, and otherwise the builder throws `Failed to find matching multi-sig address given public-keys.`
* The returned transaction is unsigned. Sign it with `numSignatures` keys through [TransactionSigner](/reference/stacks.js/stacks-transactions/signing/transactionsigner.md) `signOrigin`, and add each remaining public key with `appendOrigin`.

[**Reference Link**](https://github.com/stx-labs/stacks.js/blob/6101c99efe5a9616ce7e16cef68e28fd10676e7e/packages/bitcoin-staking/src/types.ts#L32-L40)

***

### Definition

```ts
export type MultiSigTxParams = TxParamsBase & UnsignedMultiSigOptions & { publicKey?: never };
```

***

### Properties

| Property                   | Type                 | Description                                                                                                                                                             |
| -------------------------- | -------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `publicKeys`               | `PublicKey[]`        | All N public keys of the multisig, hex string or bytes each                                                                                                             |
| `numSignatures`            | `number`             | Signatures required, M in M-of-N                                                                                                                                        |
| `address`                  | `string` (optional)  | Multisig Stacks address. When set, it decides the key order                                                                                                             |
| `useNonSequentialMultiSig` | `boolean` (optional) | Multisig hashmode. Builders in this package default it to `true`. `@stacks/transactions` marks the option `@experimental`                                               |
| `publicKey`                | `never`              | Must be absent. A defined `publicKey` makes the builder treat the params as [SingleSigTxParams](/reference/stacks.js/stacks-bitcoin-staking/types/singlesigtxparams.md) |

`fee`, `nonce`, `network`, `postConditions` and `postConditionMode` come from [TxParamsBase](/reference/stacks.js/stacks-bitcoin-staking/types/txparamsbase.md).


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stacks.co/reference/stacks.js/stacks-bitcoin-staking/types/multisigtxparams.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.