Claude e93202958d Fix relays staying disconnected and reset them on VPN changes
Relays could stay down until the app was force closed:

- RelayHealthTracker marked a relay dead permanently, and every failed
  dial was counted twice (onCannotConnect + onDisconnected), so ~5 failed
  attempts during a bad-connectivity stretch dropped every relay from the
  subscriptions. Only an OS network change or a manual reconnect cleared
  it. Dead relays now get another chance after a 15 minute cooldown, and
  only failed dials count.
- After onLost, the next network never cleared the dead list (lastNetwork
  was null), and resets that did happen never re-added dead relays to the
  subscriptions until the 5 minute safety tick.
- Network changes reconnected with Quartz's retry backoff still in place
  (up to 5 minutes, set at once on an unresolved host while offline), and
  kept sockets from the old network that only fail on ping timeout.

Network changes are now detected by NetworkChangeDetector (default
network, transports including VPN, regaining internet access) and handled
by Amber.resetRelayConnections, which drops all sockets, clears the dead
list and backoff, redials and refreshes the subscriptions. A VPN coming up
or going down, or moving between Wi-Fi and mobile, now resets relays the
same way switching Wi-Fi <-> mobile does. Manual reconnect uses the same
path.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Sr7iw4HfVgyBCrdsCxSVAX
2026-10-03 17:32:42 +00:00
2026-09-14 08:03:40 -03:00
2026-05-15 13:21:54 -03:00
2025-07-12 07:29:27 -03:00
2025-01-06 07:58:39 -03:00
2026-09-28 07:49:54 -03:00
2024-05-08 08:13:46 -03:00
2026-09-09 09:27:09 -03:00
2025-09-15 13:28:01 -03:00
2024-10-30 17:46:57 -03:00
2026-09-28 07:49:54 -03:00
2026-09-09 09:27:09 -03:00
2025-09-17 07:25:51 -03:00
2023-07-26 16:36:23 -03:00
2025-11-28 12:13:44 -03:00

Amber: Nostr event signer for Android

Amber is a nostr event signer for Android. It allows users to keep their nsec segregated in a single, dedicated app. The goal of Amber is to have your smartphone act as a NIP-46 signing device without any need for servers or additional hardware. "Private keys should be exposed to as few systems as possible as each system adds to the attack surface," as the rationale of said NIP states. In addition to native apps, Amber aims to support all current nostr web applications without requiring any extensions or web servers.

GitHub downloads Last Version CI License: Apache-2.0

Current Features

  • Offline
  • Use nip-46 or make an addendum in nip-46
  • Improve the ui (currently its showing a text with the raw json of the event)
  • Check if we can use Amber to sign the events of web applications
  • Change the sign button to just copy the signature of the event
  • Use content provider to sign events in background when you checked the remember my choice option on android
  • Support for multiple accounts

Download and Install

Get it on Zap Store Get it on Obtaininum Get it on GitHub Get it on F-Droid

Contributing

Issues can be logged on: https://gitworkshop.dev/greenart7c3@greenart7c3.com/Amber

GitHub issues and pull requests here are also welcome. Translations can be provided by editing the strings.xml files under app/src/main/res/values-<locale>/ and opening a pull request.

You can also send patches through Nostr using GitStr to this nostr address

By contributing to this repository, you agree to license your work under the MIT license. Any work contributed where you are not the original author must contain its license header with the original author(s) and source.

Development with Codex Web

This repository includes reusable Codex Web environment scripts so cloud tasks can bootstrap the Android build without manual setup. In the Codex Web environment settings, use:

bash .codex/setup.sh

as the setup script, and optionally use:

bash .codex/maintenance.sh

as the maintenance script for cached containers. The setup script installs or verifies Java 21, bootstraps the Android command-line SDK, installs Android API 36/build-tools 36.0.0, accepts SDK licenses, and warms Gradle dependencies for the default free debug unit-test sources.

Security and Verification

🔐 All releases are cryptographically signed with GPG for your security.

Before installing any APK from our releases, we strongly recommend verifying its authenticity to ensure it hasn't been tampered with.

📋 View Release Verification Guide

The verification process involves:

  1. Importing our GPG public key
  2. Verifying the release manifest signature
  3. Checking file integrity with SHA256 hashes

GPG Key Details:

  • Key ID: 44F0AAEB77F373747E3D5444885822EED3A26A6D
  • Fingerprint: 44F0 AAEB 77F3 7374 7E3D 5444 8858 22EE D3A2 6A6D
  • User ID: greenart7c3 <greenart7c3@proton.me>

Quick verification:

# Import the signing key
gpg --keyserver hkps://keys.openpgp.org --recv-keys 44F0AAEB77F373747E3D5444885822EED3A26A6D

# Verify a release (example for v1.0.0)
gpg --verify manifest-v1.0.0.txt.sig manifest-v1.0.0.txt

⚠️ Security Notice: Only download releases from this official GitHub repository. If GPG verification fails, do not install the APK and report it as a security issue.

Verifying Reproducibility of Amber

To confirm that the Amber build is reproducible, follow these steps:

  1. Run the following command to build the image with no cache and specified version:
docker build -t amber-repro --progress=plain --no-cache --build-arg VERSION=v4.0.2 --build-arg APK_TYPE=free-arm64-v8a .
  1. After the image is built, run the container:
docker run --rm amber-repro
  1. You should see the following message indicating success:
APKs match!

Certificate fingerprint for AppVerifier

com.greenart7c3.nostrsigner
E8:AB:8C:69:33:3B:68:63:6D:D4:6C:E2:42:40:8C:79:55:3A:7F:D9:05:5D:05:4D:61:DA:AB:AB:AD:A5:3B:BF

fdroid

com.greenart7c3.nostrsigner
56:DC:63:19:96:A5:5C:22:84:79:04:48:C7:DC:9F:1D:D0:5D:F5:96:B2:CE:48:82:31:36:33:F5:60:2E:5F:E4

Usage

Check NIP 55 and NIP 46 for more information.

Contributors

S
Description
No description provided
Readme MIT
17 MiB
Languages
Kotlin 93.4%
DM 5.5%
Shell 0.7%
Dockerfile 0.2%
Python 0.2%