# SDK Updates

## Version 1.3.0

#### New Features:

1. **Signer-Based Provider:** In a move to increase flexibility and user trust, we've updated the setProvider function. Now, it accepts an ethers.Signer instead of a private key or web3connection. This change not only makes integration more flexible but also adds a layer of trust as users are no longer required to pass in private keys to the SDK.
2. **Batch Payment Functionality:** We've added a new function, "sendBatchPayment," designed to facilitate payments to multiple recipients using different tokens. It significantly simplifies mass payouts, making our SDK more robust and versatile.

## Version 1.2.1

**Bug Fixes:**

* Resolved an issue with setting an inspector for the escrow module. This fix ensures smooth integration and operation of this crucial module, enhancing overall system reliability.

### Version 1.2.0

**New Features:**

1. The SDK now supports direct metadata input, including notes and files. This simplifies the process as users can now bypass IPFS and input data directly into the SDK. Prior to this, only IPFS hashes could be utilized.
2. The setProvider function is now more versatile, accepting not just a browser web3 connection but also a private key and chainId. This allows the SDK to be employed in backend/custodial products, thus broadening its applicability and usability. Previously, setProvider was limited to use in the browser.


---

# 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://denota.gitbook.io/denota/release-notes/sdk-updates.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.