Nostr notes by Amber

## Amber 6.6.8 - Fix a crash on some devices when opening Amber ...

2026-10-12T11:12:38Z

## Amber 6.6.8

- Fix a crash on some devices when opening Amber from another app or after rejecting a request, caused by the system failing to read the referring app

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.8)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.6.8.txt` and `manifest-v6.6.8.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.8.txt.sig manifest-v6.6.8.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.6.8.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

## Amber 6.6.7 - Fix relays staying disconnected until the app ...

2026-10-05T13:37:19Z

## Amber 6.6.7

- Fix relays staying disconnected until the app was force closed: relays marked dead after a stretch of bad connectivity now get another chance after a 15 minute cooldown, and failed connection attempts are no longer counted twice
- Reset relay connections when a VPN comes up or goes down, or when the device regains internet access, the same way switching between Wi-Fi and mobile data does; network changes now drop stale sockets and clear the reconnect backoff so relays come back immediately
- Detect web requests from browsers other than Chrome (such as DuckDuckGo), which previously failed with "Unknown signer type"
- Fix a crash when a permission was saved for an application that had just been deleted or reset

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.7)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.6.7.txt` and `manifest-v6.6.7.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.7.txt.sig manifest-v6.6.7.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.6.7.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

## Amber 6.6.5 - Harden application backups: backup events ...

2026-09-21T17:36:04Z

## Amber 6.6.5

- Harden application backups: backup events published to relays are now encrypted with a dedicated key derived from your account key (via HKDF, outside the NIP-44 derive-key namespace) instead of your main identity key, so apps holding a remembered `nip44_decrypt` permission can no longer fetch the kind 30078 backup and read its payload, including per-app NIP-46 secrets and local keys; existing identity-encrypted backups still restore through a fallback until the next publish overwrites them
- Fix the backup restore prompt never appearing after logging out and back in when backup publishing is disabled — the exact case restore exists for

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.5)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.6.5.txt` and `manifest-v6.6.5.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.5.txt.sig manifest-v6.6.5.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.6.5.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

# Changelog ## Amber 6.6.3 - Fix the "start service on ...

2026-09-09T22:35:48Z

# Changelog

## Amber 6.6.3

- Fix the "start service on boot" setting not being respected after an app update
- Fix a crash on the offline flavor caused by a `SecurityException` from WorkManager network tracking left over from an upgrade
- Fix the Russian translation of the "Amber is a free and open source project" string
- Fix a release build failure caused by an AGP 9.4.0 regression

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.3)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.6.3.txt` and `manifest-v6.6.3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.3.txt.sig manifest-v6.6.3.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.6.3.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

# Changelog ## Amber 6.6.1 - Fix parsing of incoming permission ...

2026-09-04T11:43:42Z

# Changelog

## Amber 6.6.1

- Fix parsing of incoming permission lists when a permission has no `kind` field in its JSON, so the whole list no longer fails to load
- Fix rejected signer requests not returning the request id in the result, leaving calling apps unable to match the rejection to their request
- Update the default signer relays to `auth.nostr1.com`, `bucket.coracle.social`, `nrs.primal.net` and `relay.nip46.com`, and add `indexer.coracle.social` to the default indexer relays (#518)
- Add missing translations for Marmot protocol event kinds

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.6.1.txt` and `manifest-v6.6.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.1.txt.sig manifest-v6.6.1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.6.1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

## Amber 6.6.0 - New: pre-approve individual permissions when ...

2026-08-31T11:26:05Z

## Amber 6.6.0

- New: pre-approve individual permissions when connecting an app under the "Manually approve each permission" policy — an "Add permission" button lets you pick from the full permission catalog (searchable, including custom sign-event kinds) so those requests are approved automatically while everything else still asks
- New: when a NIP-46 connect request arrives while the kill switch is enabled, Amber now asks whether to disable it so the request can be answered, and the kill switch gained a toggle in the Settings network section
- Toggling the "Enable biometrics" setting now requires biometric authentication first, so the setting cannot be deactivated without authorization and broken sensors are caught before activation
- Toggling "require unlocked device" now shows a progress indicator with a do-not-close warning while every stored secret is re-encrypted, instead of silently freezing
- Fix the account picker not scrolling and its title not being visible
- Fix a crash in profile feed subscriptions when an account is removed while its events are being processed
- Trim the image and trust-score caches when the system reports memory pressure, so the 32 MB bitmap cache no longer stays fully resident while the app is in the background
- Performance: cache decrypted application lists so periodic relay refreshes stop re-decrypting every application row through the Keystore (the dominant native memory user on populated accounts), and warm up timezone data off the main thread to remove a ~170 ms disk read during the Applications screen's first composition
- Update Kotlin to 2.4.10, Gradle to 9.7.1, Quartz to 1.14.0 and the rest of the dependency stack

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.6.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.6.0.txt` and `manifest-v6.6.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.6.0.txt.sig manifest-v6.6.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.6.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

# Changelog ## Amber 6.5.2 - Fix the Applications screen taking ...

2026-08-18T13:43:14Z

# Changelog

## Amber 6.5.2

- Fix the Applications screen taking several seconds to load on populated accounts: the list no longer decrypts the encrypted `secret`/`localKey` columns it doesn't render, and the Keystore key handle is cached instead of re-fetched for every decryption
- Warm the account cache at app start so the switch-accounts button lists all accounts again instead of only the current one
- Fix a crash when scrolling the activity history screens caused by the same row appearing in two loaded pages at once
- Debounce relay status-counter notification updates so the status notification no longer freezes on stale text during bursts of relay traffic

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.5.2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.5.2.txt` and `manifest-v6.5.2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.5.2.txt.sig manifest-v6.5.2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.5.2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

# Changelog ## Amber 6.5.1 - Re-encrypt NIP-46 connection secrets ...

2026-08-14T17:31:11Z

# Changelog

## Amber 6.5.1

- Re-encrypt NIP-46 connection secrets stored in the per-account database during Keystore key rotation, so toggling "require unlocked device for key access" no longer leaves connections undecryptable
- Fix crash in EditPermission due to an invalid localKey

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.5.1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.5.1.txt` and `manifest-v6.5.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.5.1.txt.sig manifest-v6.5.1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.5.1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

# Changelog ## Amber 6.5.0 - Fix relay-auth whitelist authorizing ...

2026-08-14T11:53:30Z

# Changelog

## Amber 6.5.0

- Fix relay-auth whitelist authorizing any requester (GHSA-vx4h-56qj-wcp7)
- Fix NIP-46 freshness and replay protection (GHSA-h9fv-9247-3582)
- Envelope-encrypt NIP-46 connection secrets at rest (GHSA-5fjp-ghh8-wch8)
- Add opt-in unlocked-device requirement for Keystore key (GHSA-8844)
- Authorize before decrypt in SignerProviderQuery (GHSA-8844)
- Redact key material from logs and crash reports (GHSA-8844)
- Set FLAG_SECURE on sensitive QR surfaces (GHSA-8844)
- Warn on insecure ws:// connections to non-onion relays (GHSA-8844)
- Parse unknown permission remember types as NEVER to fail closed (GHSA-8844)
- Lazy-load account keys on cache miss and properly zeroize them on logout (GHSA-8844)
- Update translations for new string resources
- Fix CI test failures and linter violations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.5.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.5.0.txt` and `manifest-v6.5.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.5.0.txt.sig manifest-v6.5.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.5.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

## Amber 6.4.0 - Redesign the multi-request approval screen with ...

2026-08-07T10:41:26Z

## Amber 6.4.0

- Redesign the multi-request approval screen with explicit Approve/Deny toggles per request and per group, replacing the select-and-confirm flow, with proper error responses for denied bunker requests
- Add support for 113 more event kinds with localized labels across all shipped locales, including the Concord kinds, NIP-51 git repository bookmarks and NIP-53 room presence
- Add light/dark Compose previews for the multi-event approval screens
- Ignore platform finalizer-watchdog TimeoutExceptions in crash reports
- Fix a NegativeArraySizeException crash in relay subscriptions by guarding shared maps for concurrent access
- Translate the new approval strings (approve, confirm, remember my choice for) in all supported locales
- Update translations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.4.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.4.0.txt` and `manifest-v6.4.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.4.0.txt.sig manifest-v6.4.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.4.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

# Changelog ## Amber 6.3.0 - Group multi-request approval lists ...

2026-07-20T13:46:16Z

# Changelog

## Amber 6.3.0

- Group multi-request approval lists by type and kind, with collapsible groups and per-group remember and scope options
- Only use the fullscreen layout when there is a single bunker request
- Add support for Expert List (kind 12022) and Expert Pack (kind 32022) events
- Add a privacy mode setting to disable logs and activity stats
- Add a setting to disable relay trust scores
- Add a restart action and live status to the built-in Tor notification
- Fetch the user's NIP-65 relay list before fetching profile metadata
- Remove relay.damus.io from the default relay lists
- Fix the event date shown as Jan 1970 in the Show Details modals
- Fix all Android Lint warnings and enforce lint in the git hooks
- Upgrade Gradle to 9.6.1 and AGP to 9.3.0
- Move older release notes to per-version files under docs/changelogs
- Update translations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.3.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.3.0.txt` and `manifest-v6.3.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.3.0.txt.sig manifest-v6.3.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.3.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Older versions

Release notes for previous versions live in [docs/changelogs](docs/changelogs/README.md).

## Amber 6.2.3 - Add a configurable profile fetch interval ...

2026-07-01T16:36:12Z

## Amber 6.2.3

- Add a configurable profile fetch interval setting with never/always options
- Show a profile picture in the account switch bottom sheet
- Scope profile subscriptions by the current account, driven by composables
- Add error handling to bunker permission parsing
- Trim the shipped languages to the curated set of locales
- Set the benchmark build app name to "Amber Benchmark"
- Fix a StrictMode DiskReadViolation in Coil onSuccess logging
- Load the account off the main thread to fix a StrictMode keystore violation
- Read account name and picture off the main thread in the account switch sheet
- Avoid eager KeyPair() on the main thread in the login/signup screens
- Fix the settings section header contrast in the light theme
- Fix an unescaped apostrophe in the Turkish profile fetch interval string
- Update translations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.2.3)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.2.3.txt` and `manifest-v6.2.3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.2.3.txt.sig manifest-v6.2.3.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.2.3.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

No, a client can't request the nsec

2026-06-12T15:31:29Z

In reply to nevent1q…hufl
_________________________

No, a client can't request the nsec

## Amber 6.2.1 - Reduce battery drain from relay reconnects and ...

2026-06-12T15:30:49Z

## Amber 6.2.1

- Reduce battery drain from relay reconnects and websocket pings
- Drop dead relays from the subscription pool instead of only backing off reconnects
- Do not wake the device when updating the relay notification
- Modernize the settings screen with grouped Material 3 cards and distinct icons
- Fix navigation crash when opening application permissions
- Fix a crash when writing the Bunker connect screen state off the main thread
- Reply with an error for invalid bunker request methods
- Add NIP-46 logout method support
- Add support for event kind 39701 (Public web bookmark)
- Fix a per-account database connection leak by building databases atomically
- Refresh app bar titles when the language changes
- Update Kotlin to 2.4.0 and Gradle to 9.5.1
- Update translations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.2.1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.2.1.txt` and `manifest-v6.2.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.2.1.txt.sig manifest-v6.2.1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.2.1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.2.0 - Add NIP-44 v3 encryption support, including a ...

2026-06-01T17:52:07Z

## Amber 6.2.0

- Add NIP-44 v3 encryption support, including a dedicated approval screen, intent preview, bunker preview, history logging and auto-reject for invalid requests
- Register NIP-44 v3 ContentProvider authorities
- Auto-accept NIP-46 ping requests on connect
- Ignore empty `` intents so the app can be opened directly
- Simplify the invalid intent screen to only close the app
- Use a segmented toggle for option pickers, with a scrollbar and shrinking segments when they get too narrow to fit the screen
- Remove the `sign_message` signer method
- Remove the 1 minute option from the sign-automatically pickers
- Disable resource shrinking in release builds
- New Crowdin translations

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.2.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.2.0.txt` and `manifest-v6.2.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.2.0.txt.sig manifest-v6.2.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.2.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

I'll see if I can have a better ui for this, I changed it ...

2026-05-26T09:43:47Z

In reply to nevent1q…6qd6
_________________________

I'll see if I can have a better ui for this, I changed it because it doesn't fit the screen when there's more than 4 options

## Amber 6.1.0 - Better layout when connecting a new app - Fix ...

2026-05-25T13:07:04Z

## Amber 6.1.0

- Better layout when connecting a new app
- Fix some reported crashes
- Fix signer dialog not closing after accepting a bunker request
- Show name and npub when showing your account
- Add a select/deselect all option in the permissions screen when connecting a new app
- Show a invalid request screen when receiving a invalid request
- Preview missing translation report before sending it
- Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once)
- Some optimizations when accepting/rejecting intent requests
- Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications
- Added a option to disable the service start on boot
- Only start the profile subscription for the current account
- Always return hex key when logging in to an app to comply with nip 55
- Added a close button in the empty requests screen
- Added loading state to the report screens
- Support for beta releases for the auto updater
- Add a reset button for bunkers
- Fix a connection issue when connecting to a new bunker by Alex Gleason (nprofile…ae9u)
- Fix app starting on boot when not enabled
- Support for sign psbt method
- Fix relay auth whitelist when the relay contains port number
- Change selectable options to be a bottom sheet
- Added more options to the automatically sign this for
- Add an encrypted applications backup that can be restored on a new device

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.1.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.1.0.txt` and `manifest-v6.1.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.1.0.txt.sig manifest-v6.1.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.1.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.1.0-pre3 - Better layout when connecting a new app - ...

2026-05-18T18:00:28Z

## Amber 6.1.0-pre3

- Better layout when connecting a new app
- Fix some reported crashes
- Fix signer dialog not closing after accepting a bunker request
- Show name and npub when showing your account
- Add a select/deselect all option in the permissions screen when connecting a new app
- Show a invalid request screen when receiving a invalid request
- Preview missing translation report before sending it
- Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once)
- Some optimizations when accepting/rejecting intent requests
- Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications
- Added a option to disable the service start on boot
- Only start the profile subscription for the current account
- Always return hex key when logging in to an app to comply with nip 55
- Added a close button in the empty requests screen
- Added loading state to the report screens
- Support for beta releases for the auto updater
- Add a reset button for bunkers
- Fix a connection issue when connecting to a new bunker by Alex Gleason (nprofile…ae9u)
- Fix app starting on boot when not enabled
- Support for sign psbt method
- Fix relay auth whitelist when the relay contains port number
- Change selectable options to be a bottom sheet
- Added more options to the automatically sign this for

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.1.0-pre3)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.1.0-pre3.txt` and `manifest-v6.1.0-pre3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.1.0-pre3.txt.sig manifest-v6.1.0-pre3.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.1.0-pre3.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.1.0-pre2 - Better layout when connecting a new app - ...

2026-05-08T13:52:29Z

## Amber 6.1.0-pre2

- Better layout when connecting a new app
- Fix some reported crashes
- Fix signer dialog not closing after accepting a bunker request
- Show name and npub when showing your account
- Add a select/deselect all option in the permissions screen when connecting a new app
- Show a invalid request screen when receiving a invalid request
- Preview missing translation report before sending it
- Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once)
- Some optimizations when accepting/rejecting intent requests
- Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications
- Added a option to disable the service start on boot
- Only start the profile subscription for the current account
- Always return hex key when logging in to an app to comply with nip 55
- Added a close button in the empty requests screen
- Added loading state to the report screens
- Support for beta releases for the auto updater
- Add a reset button for bunkers
- Fix a connection issue when connecting to a new bunker by Alex Gleason (nprofile…ae9u)
- Fix app starting on boot when not enabled

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.1.0-pre2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.1.0-pre2.txt` and `manifest-v6.1.0-pre2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.1.0-pre2.txt.sig manifest-v6.1.0-pre2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.1.0-pre2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.1.0-pre1 - Better layout when connecting a new app - ...

2026-04-29T12:03:06Z

## Amber 6.1.0-pre1

- Better layout when connecting a new app
- Fix some reported crashes
- Fix signer dialog not closing after accepting a bunker request
- Show name and npub when showing your account
- Add a select/deselect all option in the permissions screen when connecting a new app
- Show a invalid request screen when receiving a invalid request
- Preview missing translation report before sending it
- Add a rate limiting for intents based on app/type/event kind (rate limiting only applies to apps that don't implement sending multiple requests at once)
- Some optimizations when accepting/rejecting intent requests
- Added a stop service in the notification, this force closes the app and you have to manually open it again before using bunker applications
- Added a option to disable the service start on boot
- Only start the profile subscription for the current account
- Always return hex key when logging in to an app to comply with nip 55

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.1.0-pre1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.1.0-pre1.txt` and `manifest-v6.1.0-pre1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.1.0-pre1.txt.sig manifest-v6.1.0-pre1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.1.0-pre1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.0.3 - Fix racing condition when receiving intents - ...

2026-04-15T13:17:54Z

## Amber 6.0.3

- Fix racing condition when receiving intents
- Upgrade gradle and agp
- Add account index option when using seed words
- Fix relay reconnection on startup if the relay is offline
- Add missing periodic worker for app updates
- Check for empty request ids when receiving intents

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.0.3)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.0.3.txt` and `manifest-v6.0.3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.0.3.txt.sig manifest-v6.0.3.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.0.3.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.0.2 - Fix racing condition when receiving intents - ...

2026-04-15T12:28:07Z

## Amber 6.0.2

- Fix racing condition when receiving intents
- Upgrade gradle and agp
- Add account index option when using seed words
- Fix relay reconnection on startup if the relay is offline
- Add missing periodic worker for app updates

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.0.2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.0.2.txt` and `manifest-v6.0.2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.0.2.txt.sig manifest-v6.0.2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.0.2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.0.1 - Fix missing event validation when checking for ...

2026-04-10T15:58:07Z

## Amber 6.0.1

- Fix missing event validation when checking for app updates and profile events
- Fix racing condition when receiving intents
- Fix subscriptions never closing when removing an app
- Remove richtext dependency
- Update Quartz library to 1.08.0
- Add two new backup options, webdav and share to google drive
- Implement exponential backoff for relay reconnections

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.0.1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.0.1.txt` and `manifest-v6.0.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.0.1.txt.sig manifest-v6.0.1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.0.1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.0.0 - Add per-connection signing keys for NIP-46 ...

2026-04-08T11:16:40Z

## Amber 6.0.0

- Add per-connection signing keys for NIP-46 bunker protocol
- Add NIP-42 relay auth whitelist settings
- Add mnemonic recovery phrase login support
- Fix a crash when receiving duplicated events
- Optimize performance in content resolvers, intents and activity screen
- Optimized logs and activities to reduce the size of the database
- Fix a crash when pasting from clipboard
- Make relays notifications minimized by default
- Fix a database migration error
- Warn the user when their device has a broken KeyStore
- Add a self updater

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.0.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.0.0.txt` and `manifest-v6.0.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.0.0.txt.sig manifest-v6.0.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.0.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 6.0.0-pre1 - Add per-connection signing keys for NIP-46 ...

2026-04-01T19:24:54Z

## Amber 6.0.0-pre1

- Add per-connection signing keys for NIP-46 bunker protocol
- Add NIP-42 relay auth whitelist settings
- Add mnemonic recovery phrase login screen
- Fix a crash when receiving duplicated events
- Optimize performance in content resolvers, intents and activity screen
- Optimized logs and activities to reduce the size of the database

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v6.0.0-pre1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v6.0.0-pre1.txt` and `manifest-v6.0.0-pre1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v6.0.0-pre1.txt.sig manifest-v6.0.0-pre1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v6.0.0-pre1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 5.0.4 - Do not start service, tor or notifications when ...

2026-03-27T21:01:19Z

## Amber 5.0.4

- Do not start service, tor or notifications when using the offline version
- Do not re-add bunker requests when failed to send response
- Better performance when receiving multiple requests
- Add a 30 second timeout for profile subscriptions
- Remove the tabs from the connect screen
- Fix rejection not respecting the scoped encrypt/decrypt
- Show alt tags when there's no translation for a event kind
- use a boolean for the intent rejection
- Fix the accept/reject button not showing when scanning a nostrconnect qrcode

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v5.0.4)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v5.0.4.txt` and `manifest-v5.0.4.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v5.0.4.txt.sig manifest-v5.0.4.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v5.0.4.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 5.0.2 - Do not start service, tor or notifications when ...

2026-03-27T10:51:46Z

## Amber 5.0.2

- Do not start service, tor or notifications when using the offline version
- Do not re-add bunker requests when failed to send response
- Better performance when receiving multiple requests
- Add a 30 second timeout for profile subscriptions
- Remove the tabs from the connect screen
- Fix rejection not respecting the scoped encrypt/decrypt
- Show alt tags when there's no translation for a event kind
- use a boolean for the intent rejection

Download it with [Zapstore](https://zapstore.dev/apps/com.greenart7c3.nostrsigner), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v5.0.2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v5.0.2.txt` and `manifest-v5.0.2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v5.0.2.txt.sig manifest-v5.0.2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v5.0.2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 5.0.1 - Always remove internet permissions from offline ...

2026-03-18T16:56:33Z

## Amber 5.0.1

- Always remove internet permissions from offline build to avoid dependencies adding them
- Add a CI check for the internet permissions in the offline build
- Option for built in tor
- Search the content in the activities screen
- Granular encryption/decryption based on data type
- Migrate PIN storage from SharedPreferences to encrypted DataStore
- Fix crash on offline build
- Show the crash report content before sending

Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v5.0.1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v5.0.1.txt` and `manifest-v5.0.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v5.0.1.txt.sig manifest-v5.0.1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v5.0.1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 5.0.0 - Always remove internet permissions from offline ...

2026-03-18T12:59:52Z

## Amber 5.0.0

- Always remove internet permissions from offline build to avoid dependencies adding them
- Add a CI check for the internet permissions in the offline build
- Option for built in tor
- Search the content in the activities screen
- Granular encryption/decryption based on data type
- Migrate PIN storage from SharedPreferences to encrypted DataStore

Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v5.0.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v5.0.0.txt` and `manifest-v5.0.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v5.0.0.txt.sig manifest-v5.0.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v5.0.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.3 - Profile relays: Remove relay.nostr.band. Add ...

2026-03-11T18:14:21Z

## Amber 4.1.3

- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me
- Better relay notification text
- Fix relay icon when more than 10 relays
- Hide icon and relay notification if not using apps that connect to relays
- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec
- Do not use strongBox when it's a mediatek device, it's breaking all the time
- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press
- Remove relay.nsec.app from defaults (it's not working properly sometimes)
- Close profile subscriptions once receiving EOSE from relays
- Fix icon size and themed icon
- Show the account that is signing the event
- Show a button to report unknown event kinds
- Better relay connection management
- Refactor start service
- Use bottom sheet for requests instead of showing the full application
- Display the "Sign as" widget in the multi event screen
- Decrease the timeout of sending response to relays
- Show request content in the activities screen
- Client auth permissions by relay
- Fix a crash when loading profile image
- Do not group events when receiving multiple events

Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.3)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.3.txt` and `manifest-v4.1.3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.3.txt.sig manifest-v4.1.3.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.3.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.3-pre4 - Profile relays: Remove relay.nostr.band. ...

2026-03-09T19:31:17Z

## Amber 4.1.3-pre4

- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me
- Better relay notification text
- Fix relay icon when more than 10 relays
- Hide icon and relay notification if not using apps that connect to relays
- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec
- Do not use strongBox when it's a mediatek device, it's breaking all the time
- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press
- Remove relay.nsec.app from defaults (it's not working properly sometimes)
- Close profile subscriptions once receiving EOSE from relays
- Fix icon size and themed icon
- Show the account that is signing the event
- Show a button to report unknown event kinds
- Better relay connection management
- Refactor start service
- Use bottom sheet for requests instead of showing the full application
- Display the "Sign as" widget in the multi event screen
- Decrease the timeout of sending response to relays
- Show rquest content in the activities screen
- Client auth permissions by relay
- Fix a crash when loading profile image
- Do not group events when receiving multiple events

Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.3-pre4)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.3-pre4.txt` and `manifest-v4.1.3-pre4.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.3-pre4.txt.sig manifest-v4.1.3-pre4.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.3-pre4.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.3-pre3 - Profile relays: Remove relay.nostr.band. ...

2026-03-09T16:43:18Z

## Amber 4.1.3-pre3

- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me
- Better relay notification text
- Fix relay icon when more than 10 relays
- Hide icon and relay notification if not using apps that connect to relays
- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec
- Do not use strongBox when it's a mediatek device, it's breaking all the time
- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press
- Remove relay.nsec.app from defaults (it's not working properly sometimes)
- Close profile subscriptions once receiving EOSE from relays
- Fix icon size and themed icon
- Show the account that is signing the event
- Show a button to report unknown event kinds
- Better relay connection management
- Refactor start service
- Use bottom sheet for requests instead of showing the full application
- Display the "Sign as" widget in the multi event screen
- Decrease the timeout of sending response to relays
- Show rquest content in the activities screen
- Client auth permissions by relay
- Fix a crash when loading profile image

Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.3-pre3)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.3-pre3.txt` and `manifest-v4.1.3-pre3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.3-pre3.txt.sig manifest-v4.1.3-pre3.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.3-pre3.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.3-pre2 - Profile relays: Remove relay.nostr.band. ...

2026-03-06T10:06:36Z

## Amber 4.1.3-pre2

- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me
- Better relay notification text
- Fix relay icon when more than 10 relays
- Hide icon and relay notification if not using apps that connect to relays
- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec
- Do not use strongBox when it's a mediatek device, it's breaking all the time
- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press
- Remove relay.nsec.app from defaults (it's not working properly sometimes)
- Close profile subscriptions once receiving EOSE from relays
- Fix icon size and themed icon
- Show the account that is signing the event
- Show a button to report unknown event kinds
- Better relay connection management
- Refactor start service
- Use bottom sheet for requests instead of showing the full application
- Display the "Sign as" widget in the multi event screen
- Decrease the timeout of sending response to relays

Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.3-pre2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.3-pre2.txt` and `manifest-v4.1.3-pre2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.3-pre2.txt.sig manifest-v4.1.3-pre2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.3-pre2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.3-pre1 - Profile relays: Remove relay.nostr.band. ...

2026-02-25T17:27:37Z

## Amber 4.1.3-pre1

- Profile relays: Remove relay.nostr.band. Add user.kindpag.es, profiles.nostr1.com, directory.yabu.me
- Better relay notification text
- Fix relay icon when more than 10 relays
- Hide icon and relay notification if not using apps that connect to relays
- Change backup screen from icon buttons to text buttons to avoid confusion when using ncryptsec
- Do not use strongBox when it's a mediatek device, it's breaking all the time
- Use AlarmManager to start the service to see if it fixes the crash on graphene os restart app button press
- Remove relay.nsec.app from defaults (it's not working properly sometimes)
- Close profile subscriptions once receiving EOSE from relays
- Fix icon size and themed icon

Download it with [Zapstore](https://zapstore.dev/apps/naddr1qvzqqqr7pvpzqateqake4lc2fn77lflzq30jfpk8uhvtccalc66989er8cdmljceqqdkxmmd9enhyet9deshyaphvvejumn0wd68yumfvahx2usx8zmj2), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.3-pre1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.3-pre1.txt` and `manifest-v4.1.3-pre1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.3-pre1.txt.sig manifest-v4.1.3-pre1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.3-pre1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.2 - Fix some missing Relay trusted score in some ...

2026-02-09T10:42:13Z

## Amber 4.1.2

- Fix some missing Relay trusted score in some screens
- Move some components to it's own file
- Use full uuid for bunker secrets
- Remove some unused dependencies
- Migrate from LiveData to Flow in the account Model
- Upgrade to gradle plugin 9
- Fix json parsing error for encrypt/decrypt requests when they are not nostr events
- Fix a crash when receiving a auth event without relay tags

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.2.txt` and `manifest-v4.1.2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.2.txt.sig manifest-v4.1.2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.2-pre1 - Fix some missing Relay trusted score in ...

2026-02-04T11:41:09Z

## Amber 4.1.2-pre1

- Fix some missing Relay trusted score in some screens
- Move some components to it's own file
- Use full uuid for bunker secrets
- Remove some unused dependencies
- Migrate from LiveData to Flow in the account Model
- Upgrade to gradle plugin 9
- Fix json parsing error for encrypt/decrypt requests when they are not nostr events

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.2-pre1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.2-pre1.txt` and `manifest-v4.1.2-pre1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.2-pre1.txt.sig manifest-v4.1.2-pre1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.2-pre1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.1 - New ui for login, events and permissions screen ...

2026-01-26T14:52:58Z

## Amber 4.1.1

- New ui for login, events and permissions screen
- Refactor relay counters to use the updated method from quartz library
- Fix relay connection not closing when trying to add a unsupported relay
- Expose datastore errors
- Fix connection not being deleted when it fails when using bunker
- Add a loading indicator when login in
- Let the app crash when it fails to read the intent
- Use application wide scope for the datastore
- Remove migration code from old encrypted shared preferences
- Throw a error if could not find the private keys inside the keystore
- Cache keystore and signer (some 'old' devices are taking 20+ seconds to load the keystore)
- Relay trusted score by Geek (nprofile…x2te)
- Verify if account exists before trying to load the keys
- Support for `switch_relays` method

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.1.txt` and `manifest-v4.1.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.1.txt.sig manifest-v4.1.1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.0 - New ui for login, events and permissions screen ...

2026-01-26T13:36:18Z

## Amber 4.1.0

- New ui for login, events and permissions screen
- Refactor relay counters to use the updated method from quartz library
- Fix relay connection not closing when trying to add a unsupported relay
- Expose datastore errors
- Fix connection not being deleted when it fails when using bunker
- Add a loading indicator when login in
- Let the app crash when it fails to read the intent
- Use application wide scope for the datastore
- Remove migration code from old encrypted shared preferences
- Throw a error if could not find the private keys inside the keystore
- Cache keystore and signer (some 'old' devices are taking 20+ seconds to load the keystore)

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.0.txt` and `manifest-v4.1.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.0.txt.sig manifest-v4.1.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Não, a versão fdroid tem o certificado diferente

2026-01-21T13:44:40Z

In reply to nevent1q…psqc
_________________________

Não, a versão fdroid tem o certificado diferente

## Amber 4.1.0-pre3 - New ui for login, events and permissions ...

2026-01-21T12:58:22Z

## Amber 4.1.0-pre3

- New ui for login, events and permissions screen
- Refactor relay counters to use the updated method from quartz library
- Fix relay connection not closing when trying to add a unsupported relay
- Expose datastore errors
- Fix connection not being deleted when it fails when using bunker
- Add a loading indicator when login in
- Let the app crash when it fails to read the intent
- Use application wide scope for the datastore
- Remove migration code from old encrypted shared preferences
- Throw a error if could not find the private keys inside the keystore

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.0-pre3)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.0-pre3.txt` and `manifest-v4.1.0-pre3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.0-pre3.txt.sig manifest-v4.1.0-pre3.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.0-pre3.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.1.0-pre1 - New ui for login, events and permissions ...

2026-01-16T09:48:40Z

## Amber 4.1.0-pre1

- New ui for login, events and permissions screen
- Refactor relay counters to use the updated method from quartz library
- Fix relay connection not closing when trying to add a unsupported relay

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.1.0-pre1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.1.0-pre1.txt` and `manifest-v4.1.0-pre1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.1.0-pre1.txt.sig manifest-v4.1.0-pre1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.1.0-pre1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.0.7 - Fix some crashes - Separate relay and service ...

2026-01-07T12:03:11Z

## Amber 4.0.7

- Fix some crashes
- Separate relay and service notifications
- Save screen state in the login screen

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.7)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.7.txt` and `manifest-v4.0.7.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.7.txt.sig manifest-v4.0.7.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.7.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.0.6 - Remove `get_public_key` from content provider - ...

2025-12-22T11:32:16Z

## Amber 4.0.6

- Remove `get_public_key` from content provider
- Handle parsing errors when trying to decrypt content to show the content for the user
- Fix a crash on edit app the permission screen
- Add a cache to the signer to improve performance
- Use finishAndRemoveTask instead of finish
- Fix screen recomposition
- Fix crash when reading a invalid nostrconnect URI
- Retry sending connect event on failure when adding a relay

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.6)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.6.txt` and `manifest-v4.0.6.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.6.txt.sig manifest-v4.0.6.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.6.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

I think you can, never tried it to see if it breaks anything ...

2025-12-16T21:00:27Z

In reply to nevent1q…g5f4
_________________________

I think you can, never tried it to see if it breaks anything after a while

## Amber 4.0.5 - Implemented pagination in the application, logs ...

2025-12-15T11:19:30Z

## Amber 4.0.5

- Implemented pagination in the application, logs and activities screen
- Fix database size calculation inside the settings screen
- Optimize `getSavedRelays` to query unique relay lists directly
- Remove application name pre-loading in `IncomingRequestScreen`
- Use direct `DELETE` queries for clearing old logs and history instead of iterative deletion

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.5)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.5.txt` and `manifest-v4.0.5.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.5.txt.sig manifest-v4.0.5.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.5.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

I improved the performance and will release a new version on ...

2025-12-14T09:15:14Z

In reply to nevent1q…quse
_________________________

I improved the performance and will release a new version on monday

Never seen this one before. I'll try to find out what is ...

2025-12-14T09:14:28Z

In reply to nevent1q…fffy
_________________________

Never seen this one before. I'll try to find out what is happening, maybe its some relay misconfiguration

## Amber 4.0.4 - Fix NullPointerException - Improve activity ...

2025-12-11T22:34:31Z

## Amber 4.0.4

- Fix NullPointerException
- Improve activity screen performance
- Add some event kinds translations

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.4)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.4.txt` and `manifest-v4.0.4.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.4.txt.sig manifest-v4.0.4.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.4.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.0.3 - Fix close application logic for bunkers - Add a ...

2025-12-08T12:11:20Z

## Amber 4.0.3

- Fix close application logic for bunkers
- Add a Export/Import accounts method by Kylesantiago (nprofile…h2yp)
- Separate relay reqs per account
- Update relay reqs when adding an account
- New encryption/decryption ui
- Support for ping requests when using bunker
- Fix encryption type by elsat (nprofile…kqly)
- Separate logs and history tables in it's own databases
- Add crash reporting
- Try to get the saved account in the get public key of the content provider
- Use quartz from maven
- Save logs when there's a error using content provider
- Add a text to the relays page floating button
- Show the relays used by apps

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.3)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.3.txt` and `manifest-v4.0.3.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.3.txt.sig manifest-v4.0.3.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.3.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.0.3-pre2 - Fix close application logic for bunkers - ...

2025-12-05T09:34:04Z

## Amber 4.0.3-pre2

- Fix close application logic for bunkers
- Add a Export/Import accounts method by Kylesantiago (nprofile…h2yp)
- Separate relay reqs per account
- Update relay reqs when adding an account
- New encryption/decryption ui
- Support for ping requests when using bunker
- Fix encryption type by elsat (nprofile…kqly)
- Separate logs and history tables in it's own databases
- Add crash reporting
- Try to get the saved account in the get public key of the content provider
- Use quartz from maven
- Save logs when there's a error using content provider
- Add a text to the relays page floating button
- Show the relays used by apps
- Fix export account
- Clear account cache on logout
- Only load private keys on demand
- Remove nip11 fetch when adding a new relay since we don't verify anything anymore
- Update relay requests when deleting an app

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.3-pre2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.3-pre2.txt` and `manifest-v4.0.3-pre2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.3-pre2.txt.sig manifest-v4.0.3-pre2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.3-pre2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

jumble.social

2025-11-28T22:58:11Z

In reply to nevent1q…3qmr
_________________________

jumble.social

Added it

2025-11-28T21:41:05Z

In reply to nevent1q…s038
_________________________

Added it

Sure, I'll add it later

2025-11-28T20:17:23Z

In reply to nevent1q…s038
_________________________

Sure, I'll add it later

## Amber 4.0.2 - Change Dockerfile to build from the local repo - ...

2025-09-19T15:46:39Z

## Amber 4.0.2

- Change Dockerfile to build from the local repo
- Show all accounts in the backup screen
- Show the backup dialog if any account needs backup
- Enable gradle configuration cache
- Fix migration from old version
- Fix 404 link in README by @npub1lczxedq435kkzvuhf04kpxh67alqs4sa4glv24xfy6nw5tvwnwxqhwwxyr

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.2.txt` and `manifest-v4.0.2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.2.txt.sig manifest-v4.0.2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.0.1 - Fix reproducibility and added instruction in the ...

2025-09-10T11:11:36Z

## Amber 4.0.1

- Fix reproducibility and added instruction in the README
- Fix the validation of the current logged in user when sending a event from another user
- When using intents send a reject response
- Fix the edit permissions screen not updating correctly the fields when rejecting/accepting a permission
- Update to gradle 9

Download it with [zapstore.dev](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.1.txt` and `manifest-v4.0.1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.1.txt.sig manifest-v4.0.1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

Thanks

2025-09-01T14:34:26Z

In reply to nevent1q…mxkv
_________________________

Thanks

## Amber 4.0.0 - Refactor everything to use the new quartz update ...

2025-08-29T14:26:31Z

## Amber 4.0.0

- Refactor everything to use the new quartz update
- Fix reconnection issues
- Kill switch feature

Download it with [zap.store](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.0.txt` and `manifest-v4.0.0.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.0.txt.sig manifest-v4.0.0.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.0.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.0.0-pre2 - Refactor everything to use the new quartz ...

2025-08-27T12:45:39Z

## Amber 4.0.0-pre2

- Refactor everything to use the new quartz update
- Fix reconnection issues
- Kill switch feature

Download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0-pre2)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.0-pre2.txt` and `manifest-v4.0.0-pre2.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.0-pre2.txt.sig manifest-v4.0.0-pre2.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.0-pre2.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 4.0.0-pre1 - Refactor everything to use the new quartz ...

2025-08-22T10:36:36Z

## Amber 4.0.0-pre1

- Refactor everything to use the new quartz update

Download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v4.0.0-pre1)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v4.0.0-pre1.txt` and `manifest-v4.0.0-pre1.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v4.0.0-pre1.txt.sig manifest-v4.0.0-pre1.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v4.0.0-pre1.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.

## Amber 3.4.5 - Added a button in notifications and AppBar to ...

2025-08-11T11:00:38Z

## Amber 3.4.5

- Added a button in notifications and AppBar to restart connection to relays
- When connecting to relay try sending the subscription again
- If there’s a error sending a message to the relay try restarting it and sending again
- Check for encryption type again (not every app has support for nip44 yet)
- Revert QrCode reader support for multi-window (it was not reading inverted QrCodes)
- Generate a new event when there’s an error instead of trying to send the same event to avoid receiving duplicated messages from relays
- Send a error notification if it was not possible to send the event to the relays
- Close the app first and then try to send the event to the relays

Download it with [zap.store](https://zapstore.dev/download), [Obtainium](https://github.com/ImranR98/Obtainium), [f-droid](https://f-droid.org/packages/com.greenart7c3.nostrsigner) or download it directly in the [releases page](https://github.com/greenart7c3/Amber/releases/tag/v3.4.5)

If you like my work consider making a [donation](https://greenart7c3.com)

## Verifying the release

In order to verify the release, you'll need to have `gpg` or `gpg2` installed on your system. Once you've obtained a copy (and hopefully verified that as well), you'll first need to import the keys that have signed this release if you haven't done so already:

``` bash
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D
```

Once you have his PGP key you can verify the release (assuming `manifest-v3.4.5.txt` and `manifest-v3.4.5.txt.sig` are in the current directory) with:

``` bash
gpg --verify manifest-v3.4.5.txt.sig manifest-v3.4.5.txt
```

You should see the following if the verification was successful:

``` bash
gpg: Signature made Fri 13 Sep 2024 08:06:52 AM -03
gpg: using RSA key 44F0AAEB77F373747E3D5444885822EED3A26A6D
gpg: Good signature from "greenart7c3 <greenart7c3@proton.me>"
```

That will verify the signature on the main manifest page which ensures integrity and authenticity of the binaries you've downloaded locally. Next, depending on your operating system you should then re-calculate the sha256 sum of the binary, and compare that with the following hashes:

``` bash
cat manifest-v3.4.5.txt
```

One can use the `shasum -a 256 <file name here>` tool in order to re-compute the `sha256` hash of the target binary for your operating system. The produced hash should be compared with the hashes listed above and they should match exactly.