> For the complete documentation index, see [llms.txt](https://docs.param.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.param.network/the-protocol/multi-signature-state-recording.md).

# Multi signature state recording

Commerce transactions has more states as compared to typical financial transaction. Any state change would involve minimum two parties to fulfil the associated contractual obligations. In order to bring this into universal commerce blockchain, where most of the contracts can be build seamlessly on a single chain, ⦃param⦄ records the transaction states and transitions on the ledger natively.

![](/files/-L_zjsM_jVswq9p45BxC)

⦃param⦄ protocol records states after necessary validations such as:

* Quotations are always initiated by party-Seller to a party-Buyer, which serves as the base for rest of the state-change validations
* Create Purchase Order transaction can only be initiated by Buyer
* Create Invoice transaction can only be initiated by Seller
* Create Record Payment  transaction can only be initiated by Buyer
* Create Digital Receipt transaction can only be initiated by Seller
* Only Buyer or Seller can add subscribers to the transaction, which is detailed in [later](/the-protocol/param-node.md) section.

Although the network is permissioned, for spam protection, the creating Quotation on the network would come at a stake or a cost.

> Its worthwhile to note, a single "*commerce transaction"* is equal to multiple ⦃param⦄ transaction on the chain


---

# 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.param.network/the-protocol/multi-signature-state-recording.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.