> For the complete documentation index, see [llms.txt](https://docs.shadowcipher.in/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.shadowcipher.in/changelog/readme.md).

# Changelog

New features, improvements and fixes in BSA Signer.

Changes to BSA Signer, newest first.

| Date        | Release                                                                                                              | Highlights                                                 |
| ----------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------- |
| 13 Nov 2026 | [Mobile signing improvements](https://docs.shadowcipher.in/changelog/2026/2026-11-13-mobile-signing.md)              | Signing and simulator work on phones; touch placement      |
| 21 Oct 2026 | [eSign, DSC token signing and timestamps](https://docs.shadowcipher.in/changelog/2026/2026-10-21-signing-options.md) | New ways to sign, OpenAPI spec                             |
| 20 Oct 2026 | [Signing API, templates, e-Stamp merge and stock](https://docs.shadowcipher.in/changelog/2026/2026-10-20-phase-2.md) | OAuth signing API, templates, merge, counters, rate limits |
| 11 Aug 2026 | [Platform and security updates](https://docs.shadowcipher.in/changelog/2026/2026-08-11-platform-updates.md)          | Java 17, library and security policy updates               |
| 9 Feb 2026  | [Version 6.1](https://docs.shadowcipher.in/changelog/2026/2026-02-09-version-6-1.md)                                 | Two new authentication types, viewer fixes                 |
| 8 Feb 2026  | [Version 6](https://docs.shadowcipher.in/changelog/2026/2026-02-08-version-6.md)                                     | Transactions, stock checks, signing engine rework          |
| 28 Jan 2026 | [Version 5](https://docs.shadowcipher.in/changelog/2026/2026-01-28-version-5.md)                                     | New look, better PDF viewer, client signature styles       |
| 14 Jan 2026 | [V3 release](https://docs.shadowcipher.in/changelog/2026/2026-01-14-v3-release.md)                                   | Clients, OAuth 2.0, Google sign-in, certificate sessions   |
| 11 Jan 2026 | [New landing page and sign-in](https://docs.shadowcipher.in/changelog/2026/2026-01-11-landing-page.md)               | Landing page, sign-in, clearer signing layout              |
| 24 Aug 2024 | [Version 4.0](https://docs.shadowcipher.in/changelog/2024/2024-08-24-version-4.md)                                   | Configurable signature appearances, validation             |
| 23 Aug 2024 | [Version 3.0](https://docs.shadowcipher.in/changelog/2024/2024-08-23-version-3.md)                                   | Users and stock                                            |
| 11 Aug 2024 | [First release](https://docs.shadowcipher.in/changelog/2024/2024-08-11-first-release.md)                             | BSA Signer signing page                                    |


---

# 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.shadowcipher.in/changelog/readme.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.
