Merge branch 'main' into cooking/planetora

Lift the Planetora event panel off the background
The panel was bg-background/40 + backdrop-blur — a fogged version of the same hue as the warm dawn-toned page background, which on mobile made the bottom sheet visually merge with the globe area underneath. Now: - Surface fill bumped to bg-background/85 so the panel reads as a distinct surface instead of a tinted overlay (backdrop-blur is retained so a hint of the globe still glows through). - Border tightened to border-border/70 plus a hairline foreground ring to crisp the edge against any backdrop colour. - Mobile sheet gets an explicit two-direction shadow (top + bottom) rather than shadow-2xl, which only casts downward — for a sheet pinned to the bottom of the viewport that downward cast falls off screen and leaves no visible separation. The new top-edge shadow is what actually lifts the sheet off the globe. Co-authored-by: Cursor <cursoragent@cursor.com>
2026-05-23 11:21:31 +07:00 · 2026-05-21 19:58:41 +07:00 · 2026-05-21 19:56:20 +07:00 · 2026-05-21 19:53:17 +07:00 · 2026-05-21 19:36:51 +07:00 · 2026-05-21 19:16:58 +07:00
885 changed files with 91259 additions and 73891 deletions
@@ -7,8 +7,5 @@ VITE_NOSTR_PUSH_PUBKEY=""
 # Primarily useful for native (Capacitor) builds, where window.location.origin is capacitor://localhost.
 # Example: VITE_SHARE_ORIGIN="https://agora.spot"
 VITE_SHARE_ORIGIN=""
-# DeepL-backed translation worker for user-generated content.
-# Example: VITE_TRANSLATE_WORKER_URL="https://agora-translate.<your-subdomain>.workers.dev"
-VITE_TRANSLATE_WORKER_URL="https://agora-translate.lemonknowsall.workers.dev/"
 # Set to "*" to allow any host in the Vite dev server (eg. when proxying through a custom domain)
-# ALLOWED_HOSTS="*"
+# ALLOWED_HOSTS="*"
@@ -37,12 +37,6 @@ deploy-web:
    - if: $CI_COMMIT_TAG
      when: never
    - if: $CI_COMMIT_REF_NAME == $CI_DEFAULT_BRANCH && $DEPLOY_SSH_KEY && $DEPLOY_TARGET
-  # Vite inlines VITE_* env vars at build time. These are sourced directly from
-  # project-level CI/CD variables, which are already present in the job
-  # environment — do NOT re-declare them here as `KEY: $KEY`. That self-reference
-  # overwrites the real value with the literal string "$KEY" whenever the source
-  # variable is out of scope (e.g. a Protected variable on an unprotected ref),
-  # which is how "$VITE_TRANSLATE_WORKER_URL" leaked into the built app.
  script:
    # Build the web app
    - npm ci
@@ -167,33 +161,23 @@ build-apk:
    # Write local.properties for Gradle
    - echo "sdk.dir=$ANDROID_SDK_ROOT" > android/local.properties

-    # Decode signing keystore and migrate JKS -> PKCS12 for Gradle compatibility.
-    # PKCS12 conceptually uses one password for the store and every entry; if the
-    # store and key passwords differ, keytool protects the migrated entry with the
-    # STORE password regardless of -destkeypass, so Gradle's later read with the
-    # key password fails ("Given final block not properly padded"). Unlock the
-    # source key with its own password ($KEY_PASSWORD), then write the PKCS12 with
-    # a single uniform password ($KEY_PASSWORD) for both store and entry so the
-    # key.properties below is internally consistent.
+    # Decode signing keystore and migrate JKS -> PKCS12 for Gradle compatibility
    - echo "$ANDROID_KEYSTORE_BASE64" | base64 -d > android/app/my-upload-key.jks
    - keytool -importkeystore
        -srckeystore android/app/my-upload-key.jks
        -destkeystore android/app/my-upload-key.keystore
        -deststoretype pkcs12
        -srcstorepass "$KEYSTORE_PASSWORD"
+        -deststorepass "$KEYSTORE_PASSWORD"
        -srcalias upload
        -destalias upload
-        -srckeypass "$KEY_PASSWORD"
-        -deststorepass "$KEY_PASSWORD"
-        -destkeypass "$KEY_PASSWORD"
        -noprompt
    - rm android/app/my-upload-key.jks

-    # Write key.properties from CI/CD variables. The PKCS12 above uses
-    # $KEY_PASSWORD uniformly, so both storePassword and keyPassword point to it.
+    # Write key.properties from CI/CD variables
    - |
      cat > android/key.properties << EOF
-      storePassword=$KEY_PASSWORD
+      storePassword=$KEYSTORE_PASSWORD
      keyPassword=$KEY_PASSWORD
      keyAlias=upload
      storeFile=my-upload-key.keystore
@@ -1,10 +1,6 @@
 # Project Overview

-Agora is a peer-to-peer crowdfunding Nostr client built with React 19.x, TailwindCSS 3.x, Vite, shadcn/ui, and Nostrify, wrapped as a native iOS/Android app via Capacitor.
-
-Donations are **on-chain Bitcoin** — donors pay a campaign's Bitcoin address directly. Agora ships an integrated **non-custodial HD Bitcoin wallet** (deterministically derived from the user's Nostr key) with BIP-86 Taproot and **BIP-352 silent-payment** support. The app never custodies or converts funds; it is a non-custodial UI that connects donors and campaigns peer-to-peer.
-
-**This is not a Lightning project.** Lightning (`useZaps`, `useWallet`, `useNWC`, LNURL/NWC/WebLN) survives only as a secondary *tipping* path for notes/profiles and a deprecated Breez/Spark wallet in recovery-only mode — never for campaign donations. The crowdfunding core is strictly on-chain.
+Agora is a Nostr client built with React 19.x, TailwindCSS 3.x, Vite, shadcn/ui, and Nostrify, wrapped as a native iOS/Android app via Capacitor.

 ## Technology Stack

@@ -21,7 +17,7 @@ Donations are **on-chain Bitcoin** — donors pay a campaign's Bitcoin address d
 ## Project Structure

 - `/src/components/` — UI components. `ui/` holds shadcn primitives; `auth/` holds login components.
- `/src/hooks/` — custom hooks. Discover the full set with `ls src/hooks/`. Core Nostr: `useNostr`, `useAuthor`, `useCurrentUser`, `useNostrPublish`, `useUploadFile`, `useAppContext`, `useTheme`, `useToast`, `useLoggedInAccounts`, `useLoginActions`, `useIsMobile`. **On-chain wallet & crowdfunding (the headline feature):** `useHdWallet`, `useHdWalletSp` (BIP-352 silent payments), `useBitcoinSigner`, `useDonateCampaign`, `useCampaign`/`useCampaigns`, `useCampaignDonations`, `useOnchainZap`. **Lightning (secondary tipping only, not campaigns):** `useZaps`, `useWallet` (NWC/WebLN status — *not* the on-chain wallet), `useNWC`.
+- `/src/hooks/` — custom hooks. Discover the full set with `ls src/hooks/`. Key ones: `useNostr`, `useAuthor`, `useCurrentUser`, `useNostrPublish`, `useUploadFile`, `useAppContext`, `useTheme`, `useToast`, `useLoggedInAccounts`, `useLoginActions`, `useIsMobile`, `useZaps`, `useWallet`, `useNWC`, `useShakespeare`.
 - `/src/pages/` — page components wired into `AppRouter.tsx`. The catch-all `/:nip19` route is handled by `NIP19Page.tsx` (see the `nip19-routing` skill).
 - `/src/lib/` — utility functions and shared logic.
 - `/src/contexts/` — React context providers (`AppContext`, `NWCContext`).
@@ -264,21 +260,6 @@ Routes live in `AppRouter.tsx`. To add one:

 The router provides automatic scroll-to-top on navigation and a 404 `NotFound` page.

-## Internationalization
-
-All user-facing strings live in `src/locales/<lang>.json`. `en.json` is the source of truth; fifteen other locales ship alongside it: `ar`, `es`, `fa`, `fr`, `hi`, `id`, `km`, `ps`, `pt`, `ru`, `sn`, `sw`, `tr`, `zh`, `zh-Hant`.
-
-**When you edit, add, or remove a translated string, update every locale in the same change — not just `en.json`.** Leaving the other locales stale ships an inconsistent app: users in other languages either see outdated copy or get an English fallback in the middle of a localized screen. This applies to FAQ entries, guide bodies, button labels, error messages — every value reachable through `t()`.
-
-Concrete rules:
-
- **Edits to an existing key** — change the value in `en.json` first, then update the corresponding key in all fifteen other locales. Translate the new content into each language; don't paste English. Preserve `{{interpolation}}` placeholders, markdown links, and technical tokens (`sp1…`, `BIP-352`, kind numbers, etc.) verbatim.
- **New keys** — add to `en.json` first, then add the same key with a translated value in every other locale. `src/test/locales.test.ts` fails the build if any locale ships a key that doesn't exist in `en.json`, but the inverse (a key missing from a non-English locale) is allowed and falls back to English at runtime — which is exactly the user-visible mess you're trying to avoid.
- **Removed keys** — delete from `en.json` and every other locale together. Leftover keys are dead translations and clutter future diffs.
- **Parallelize the translation work** — when updating one English string across all fifteen locales, dispatch the per-language edits to subagents in parallel rather than translating fifteen files sequentially. Provide each subagent the new English source, the existing translation snippet (so it matches established voice), and explicit instructions to preserve placeholders and technical tokens.
-
-Always run `npm run test` after locale changes — `locales.test.ts` catches structural drift, and the wider suite catches any `t()` calls that referenced a key you renamed.
-
 ## Development Practices

 - React Query for data fetching and caching
@@ -1,125 +1,5 @@
 # Changelog

-## [2.9.1] - 2026-06-27
-
-The Venezuela earthquake relief appeal now rallies behind every campaign on the ground, not just one. The home banner and relief page showcase a live, swipeable carousel of all Venezuelan relief efforts, with a running total of everything raised so far — so you can pick exactly who to help.
-
-### Changed
-
- The Venezuela relief appeal now showcases every Venezuelan relief campaign in a live, auto-scrolling carousel you can swipe through, with a combined raised total across all of them, instead of featuring a single campaign.
-
-## [2.9.0] - 2026-06-25
-
-A big one. Private messaging arrives with a fast, searchable inbox you can reply to in your own language. Campaign organizers can now get verified by trusted reviewers through a guided sign-up, and verified badges appear right on campaigns. There's a new Venezuela earthquake relief appeal that takes you straight to donations, plus optional Tor routing on Android, separate Public and Private wallets, faster donation scanning, and refreshed profiles, settings, and login.
-
-### Added
-
- Private direct messages: a dedicated inbox you can search by name, start new chats with inline recipient lookup, page back through old conversations, and read incoming messages translated into your language.
- Get verified: a guided sign-up for trusted reviewers to set up a verifier profile, publish a public "how we verify" statement, and vouch for campaigns. Verified badges now show on campaign pages, and a short tutorial walks you through it.
- A Venezuela earthquake relief appeal — a home-page banner, a one-time popup, and a shareable page that bakes in the relief campaign so you can read its story and donate without leaving.
- Optional Tor routing on Android for added privacy.
- Separate Public and Private wallets, keeping your spending and your private silent-payment funds cleanly apart.
- A "Don't have Bitcoin?" prompt on campaign pages that points first-time donors to Cash App.
- An always-visible language switcher in the top navigation, and a corporate sponsorship page.
-
-### Changed
-
- Redesigned profiles with cleaner stats, a merged campaigns view, and a themed raised total.
- Redesigned Settings into an Apple-style grouped layout.
- Reworked the login and onboarding flow, including a new welcome screen built around the Agora brand.
- Silent-payment donations now scan faster and keep working in the background, with a progress bar on the private wallet.
- The home page now shows every featured campaign instead of capping the list.
-
-### Fixed
-
- The audio, music, and podcast pages no longer crash.
- Backfilled and corrected translations across all sixteen languages.
-
-## [2.8.9] - 2026-06-02
-
-Adds an in-app prompt to grab the Android app from Zapstore, makes it easier to start or explore campaigns right from the home page, and irons out a batch of language and display fixes.
-
-### Added
-
- A prompt to download the Android app from Zapstore, shown to mobile web visitors on the home page, in the account menu, and in the slide-out menu.
- A "Start a campaign" button alongside "Browse all" in the middle of the home page.
-
-### Changed
-
- The "Explore campaigns" button now appears for everyone, not just logged-out visitors.
-
-### Fixed
-
- Switching languages now takes effect immediately instead of showing stale text.
- The reply box and the replies heading on a post now show up in your chosen language.
- Account balances keep their Latin numerals regardless of display language.
- Filled in missing translations on the "Why Agora" screen.
-
-## [2.8.8] - 2026-06-02
-
-Fixes the app icon proportions and updates the loading splash to the Agora bolt.
-
-### Fixed
-
- App icon no longer appears squashed.
- Loading splash now shows the Agora bolt instead of the old logo.
-
-## [2.8.7] - 2026-06-02
-
-Fixes the top navigation bar rendering behind the status bar on Android.
-
-### Fixed
-
- Top navigation bar now clears the system status bar on Android.
-
-## [2.8.6] - 2026-06-02
-
-Refreshes the app icon to the orange Agora bolt mark across Android, iOS, and the web.
-
-### Changed
-
- Update the app icon to the current Agora bolt on a brand-orange background.
-
-## [2.8.5] - 2026-06-02
-
-A maintenance release that fixes the Android build so signed releases publish correctly. No user-facing changes.
-
-## [2.8.4] - 2026-06-02
-
-A maintenance release that fixes the Android build so signed releases publish correctly. No user-facing changes.
-
-## [2.8.3] - 2026-06-02
-
-A maintenance release that fixes the Android build so signed releases publish correctly. No user-facing changes.
-
-## [2.8.2] - 2026-06-02
-
-A maintenance release that fixes the Android build pipeline so signed releases publish correctly. No user-facing changes.
-
-## [2.8.1] - 2026-06-02
-
-Agora becomes a home for putting your money where your heart is. Launch and back fundraising campaigns, rally around organizations with their own events and pledges, and send support straight from a built-in Bitcoin and Lightning wallet. Explore the world through immersive country pages, chat with a new AI agent, and move through a faster, cleaner app with a fresh look throughout.
-
-### Added
-
- Fundraising campaigns as the new home surface — create, edit, and back campaigns, set goals, add beneficiaries, and follow progress.
- Organizations with their own events, pledges, members, and moderation tools.
- Built-in wallet for sending Bitcoin and Lightning payments, with transaction history and balances shown in USD.
- One-tap support: zap posts, profiles, campaigns, and organizations.
- AI agent chat with a model selector, tool-calling, and slash commands.
- Immersive country pages with anthems, flags, weather, and a country-scoped feed, plus a new Discover square for exploring the world.
- Comments and reactions on campaigns, and donation receipts shown inline.
-
-### Changed
-
- Refreshed Agora branding, navigation, and app icons throughout.
- Streamlined onboarding with country and people follows.
- Polished campaign, organization, and donation flows end to end.
-
-### Removed
-
- Direct messaging and ephemeral geo chat.
-
 ## [1.0.0] - 2026-04-30

 ### Added
@@ -15,7 +15,6 @@
 | 33863 | Campaign                   | Self-authored fundraising campaign with a single Bitcoin wallet endpoint (`bc1...` or `sp1...`) |
 | 30385 | Community Stats Snapshot   | Pre-computed per-country / global community leaderboards       |
 | 36639 | Pledge                     | Donor pledge for concrete submissions, stored as sats           |
-| 14672 | Verifier Statement         | Self-authored statement describing how the author verifies campaigns (one per user) |

 ### Agora Protocols

@@ -23,9 +22,7 @@
 |--------------------------|-----------------------------------------|-----------------------------------------------------------------|
 | Flat Communities | 34550, 30009, 8, 1111, 1984 | One-level badge membership with explicit moderators (NIP-72 ext) |
 | Community Chat | 34550, 1311 | Realtime member chat scoped to a NIP-72 community |
-| Campaign Moderation | 33863, 34550, 36639, 1985, 39089 | Discovery curation (hidden + featured axes) via moderator-signed labels in the `agora.moderation` namespace, gated by a follow-pack moderator roster. Covers campaigns, organizations, and pledges identically. |
-| Campaign Verification | 33863, 1985 | Positive trust signal: moderator-signed NIP-32 labels in the `agora.verified` namespace (value `verified`) vouching for a campaign. Gated by the same moderator pack as hide/feature; retracted via kind 5 deletion. |
-| HD Wallet Derivation | — | BIP-39 mnemonic deterministically derived from the user's nsec via HKDF; seeds a BIP-86 Taproot + BIP-352 silent-payment wallet importable into any BIP-39-compatible wallet (see [Agora HD Wallet](#agora-hd-wallet-derivation) below). |
+| Campaign Moderation | 33863, 1985, 39089 | Homepage curation (approved / hidden / featured axes) via moderator-signed labels in the `agora.moderation` namespace, gated by a follow-pack moderator roster |

 ### Agora Content Marker

@@ -72,7 +69,7 @@ Clients filter both case variants (`agora` and `Agora`) because Nostr `t` tags a

 #### Backward compatibility

-Events published before this marker was adopted do not carry `t:agora` and therefore do not appear in the Agora activity feed. They remain reachable by direct link and via kind-specific directories (e.g. the moderator-curated `/campaigns`). Authors who wish to surface a legacy event in the feed can republish it (any edit through the Agora UI will add the marker automatically).
+Events published before this marker was adopted do not carry `t:agora` and therefore do not appear in the Agora activity feed. They remain reachable by direct link and via kind-specific directories (e.g. the moderator-curated `/campaigns/all`). Authors who wish to surface a legacy event in the feed can republish it (any edit through the Agora UI will add the marker automatically).

 ### Community Chat

@@ -284,11 +281,11 @@ The two zap kinds are complementary. Clients SHOULD sum verified amounts from bo

 ### Summary

-Addressable event representing a **self-authored fundraising campaign**. A campaign carries marketing-style metadata (title, summary, banner image, markdown story, optional goal, optional country) and one or two Bitcoin wallet endpoints declared in `w` tags. Each wallet endpoint is either a public on-chain bech32(m) address (`bc1q…`, `bc1p…`) or a silent-payment code (`sp1…`, per BIP-352). The mode of each endpoint is inferred from the prefix — the client renders a QR code that combines the present endpoints and adjusts the donation-progress UI accordingly. A campaign MAY declare **at most one** endpoint per mode (at most one on-chain address and at most one silent-payment code).
+Addressable event representing a **self-authored fundraising campaign**. A campaign carries marketing-style metadata (title, summary, banner image, markdown story, optional goal, optional deadline, optional country) and exactly one Bitcoin wallet endpoint declared in a `w` tag. The wallet endpoint is either a public on-chain bech32(m) address (`bc1q…`, `bc1p…`) or a silent-payment code (`sp1…`, per BIP-352). The mode is inferred from the prefix — the client renders the corresponding QR code and adjusts the donation-progress UI accordingly.

 The author of the event is also the beneficiary. Campaigns are never authored on behalf of someone else; the event creator owns the wallet declared in `w` and receives the donations. To stop accepting donations, the creator publishes a NIP-09 kind 5 deletion request referencing the campaign's `a` coordinate.

-The kind is addressable so the creator can edit the story, banner, goal, and wallet over the life of the campaign without minting new identifiers. The `d` tag is the campaign's slug.
+The kind is addressable so the creator can edit the story, banner, goal, deadline, and wallet over the life of the campaign without minting new identifiers. The `d` tag is the campaign's slug.

 ### Event Structure

@@ -314,30 +311,22 @@ The kind is addressable so the creator can edit the story, banner, goal, and wal
    ["alt", "Fundraising campaign: Save the Last Bookstore"],

    ["w", "bc1p7w2k3xq9...xyz"],
-    ["w", "sp1qq...verylongsilentpaymentcode..."],

    ["goal", "25000"],
+    ["deadline", "1735689600"],

-    ["i", "iso3166:US"],
-    ["k", "iso3166"],
-    ["t", "legal-defense"],
-    ["t", "mutual-aid"]
+    ["i", "iso3166-1:US"],
+    ["k", "iso3166-1"]
  ]
 }
 ```

-A silent-payment-only campaign omits the `bc1…` `w` tag and carries only the `sp1…`:
+A silent-payment campaign is identical except the `w` tag carries an `sp1…` code:

 ```json
 ["w", "sp1qq...verylongsilentpaymentcode..."]
 ```

-An on-chain-only campaign omits the `sp1…` `w` tag and carries only the `bc1…`:
-
-```json
-["w", "bc1p7w2k3xq9...xyz"]
-```
-
 ### Content

 The `content` field is the **campaign story**, formatted as Markdown. Clients SHOULD render it with the same Markdown renderer they use for NIP-23 long-form content. Empty content is permitted (e.g. for a campaign that lives entirely in its summary).
@@ -348,52 +337,40 @@ The `content` field is the **campaign story**, formatted as Markdown. Clients SH
 |-----------|----------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
 | `d`       | Yes      | Campaign slug, unique per author. Forms the addressable coordinate `33863:<pubkey>:<d>`.                                                                                                                                     |
 | `title`   | Yes      | Display title of the campaign (plain text, max ~200 chars).                                                                                                                                                                  |
-| `w`       | Yes      | Bitcoin wallet endpoint. The 2nd element is a single bech32(m) string: a mainnet on-chain address starting with `bc1q` (P2WPKH/P2WSH) or `bc1p` (P2TR), **or** a silent-payment code starting with `sp1` per BIP-352. A campaign MUST carry at least one `w` tag and MAY carry up to two — at most one per mode (on-chain and silent payment). |
+| `w`       | Yes      | Bitcoin wallet endpoint. The 2nd element is a single bech32(m) string: a mainnet on-chain address starting with `bc1q` (P2WPKH/P2WSH) or `bc1p` (P2TR), **or** a silent-payment code starting with `sp1` per BIP-352. Exactly one `w` tag per campaign. |
 | `summary` | Recommended | Short one-paragraph tagline shown in feed cards and previews.                                                                                                                                                              |
 | `banner`  | Recommended | HTTPS URL of the wide banner image. Clients MUST sanitize the URL (see `sanitizeUrl()` in `nostr-security`) before rendering, and SHOULD pair the URL with a NIP-92 `imeta` tag for dimensions, blurhash, MIME type, and SHA-256. |
 | `imeta`   | Recommended | NIP-92 media metadata for the banner. The first `url <value>` pair MUST match the `banner` URL; clients SHOULD ignore an `imeta` whose URL does not match.                                                                  |
 | `goal`    | Optional | Fundraising goal in **integer US Dollars** (no unit suffix, no decimals). Clients MAY display an estimated sat-equivalent at view time using a live exchange rate.                                                          |
-| `i`       | Recommended | NIP-73 country identifier. SHOULD be `iso3166:<code>` with an uppercase ISO 3166-1 alpha-2 country code (e.g. `iso3166:VE`).                                                                                          |
-| `k`       | Recommended if `i` is present | NIP-73 external content kind. For country identifiers this SHOULD be `iso3166`.                                                                                                              |
-| `t`       | Optional | User-entered discovery/category tags. Agora also adds `t:agora` as the app marker; other `t` values are freeform topics such as `legal-defense` or `mutual-aid`. |
+| `deadline`| Optional | Unix timestamp (seconds) at which the campaign closes for new donations. After the deadline, clients SHOULD show the campaign as ended but MAY still accept donations.                                                       |
+| `i`       | Recommended | NIP-73 country identifier. SHOULD be `iso3166-1:<code>` with an uppercase ISO 3166-1 alpha-2 country code (e.g. `iso3166-1:VE`).                                                                                          |
+| `k`       | Recommended if `i` is present | NIP-73 external content kind. For country identifiers this SHOULD be `iso3166-1`.                                                                                                              |
 | `alt`     | Recommended | NIP-31 human-readable fallback.                                                                                                                                                                                            |

 ### Wallet Modes

-The prefix of each `w` value selects one of two donation modes. Clients MUST detect the mode from the prefix; the event carries no other mode discriminator. When a campaign carries both an on-chain and a silent-payment endpoint, the client SHOULD present a single combined QR (see "Combined QR" below) so a scan offers the donor's wallet whichever endpoint it supports, while still rendering on-chain aggregate UI from the on-chain endpoint and the silent-payment privacy notice from the silent-payment endpoint.
+The prefix of the `w` value selects one of two donation modes. Clients MUST detect the mode from the prefix; the event carries no other mode discriminator.

 | Prefix              | Mode      | Description                                                                                                                              |
 |---------------------|-----------|------------------------------------------------------------------------------------------------------------------------------------------|
 | `bc1q…` / `bc1p…`   | On-chain  | Public mainnet bech32(m) address. Donations are traceable; clients show a progress bar, total raised, and donation list.                |
 | `sp1…`              | Silent payment | BIP-352 silent-payment code. Donations are **unlinkable by design**. Clients MUST hide all aggregate totals and progress UI (see below). |

-Other prefixes (`tb1…`, `bcrt1…`, `tsp1…`, lightning invoices, etc.) MUST be rejected at parse time; the campaign does not render. A campaign carrying two `w` tags of the same mode (e.g., two `bc1…` addresses) is invalid and MUST NOT render — only one endpoint per mode is permitted.
+Other prefixes (`tb1…`, `bcrt1…`, `tsp1…`, lightning invoices, etc.) MUST be rejected at parse time; the campaign does not render.

-Clients SHOULD validate the bech32(m) checksum of each `w` value, not just its prefix.
-
-### Combined QR
-
-When a campaign declares both endpoints, clients SHOULD render a single BIP-21 URI that combines them:
-
-```
-bitcoin:<bc1-address>?sp=<sp1-code>
-```
-
-BIP-352-aware wallets pick the `sp=` parameter and use the silent-payment flow; legacy wallets fall back to the on-chain address. Clients MAY also surface each endpoint's raw string as a copyable affordance so donors who prefer one over the other can choose explicitly. A single-endpoint campaign uses the standard form: `bitcoin:<bc1-address>` (on-chain only) or `bitcoin:?sp=<sp1-code>` (silent payment only).
+Clients SHOULD validate the bech32(m) checksum of the `w` value, not just its prefix.

 ### Client Behavior by Mode

-Each endpoint type drives its own UI elements independently. A dual-endpoint campaign shows the on-chain aggregate UI (computed from the on-chain endpoint) **and** the silent-payment privacy notice (because at least some donations may flow through the SP endpoint and not be visible in any aggregate).
-
-| UI element                  | On-chain (`bc1`) present                                        | Silent payment (`sp1`) present                        |
+| UI element                  | On-chain (`bc1`)                                                | Silent payment (`sp1`)                                |
 |-----------------------------|-----------------------------------------------------------------|-------------------------------------------------------|
-| QR code                     | bech32(m) address in BIP-21 `bitcoin:` URI                      | SP code in BIP-21 `?sp=` extension (combined with on-chain address when both are present) |
-| "Raised X" / progress bar   | Shown, computed from cumulative `chain_stats.funded_txo_sum` on the on-chain `w` address via an Esplora endpoint (default mempool.space). Kind 8333 receipts are **not** the source of this total — donors paying the BIP-21 QR with a native wallet would otherwise be missed. | **Not contributed.** When the on-chain endpoint is absent, aggregate UI is hidden entirely. |
-| Donor / recent-donation list| Shown, populated from verified kind 8333 receipts against the on-chain address (attribution only — these do not feed the headline total). | **Not contributed.**                                   |
-| Goal display                | Shown as USD target with optional sat-equivalent estimate       | Shown as USD target; no progress computation when on-chain endpoint is absent |
-| Donation receipt published  | Donor's client publishes a kind 8333 receipt against the on-chain endpoint (see below) | **No receipt published.** Publishing one would defeat SP unlinkability and is forbidden. |
+| QR code                     | bech32(m) address QR (or BIP-21 `bitcoin:` URI)                 | SP code QR (BIP-352 / BIP-21 SP extension)             |
+| "Raised X" / progress bar   | Shown, computed from verified kind 8333 receipts                | **Hidden.** Replaced with a "Private campaign — totals are not public" notice. |
+| Donor / recent-donation list| Shown                                                           | **Hidden.**                                            |
+| Goal display                | Shown as USD target with optional sat-equivalent estimate       | Shown as USD target; no progress computation           |
+| Donation receipt published  | Donor's client publishes a kind 8333 receipt (see below)        | **No receipt published.** Publishing one would defeat SP unlinkability and is forbidden. |

-For campaigns with **only** a silent-payment endpoint (no on-chain endpoint), clients MUST NOT attempt to scan the chain, MUST NOT publish receipts, and MUST NOT display any aggregate that could leak donation activity. For dual-endpoint campaigns, the on-chain aggregate UI is permitted but clients SHOULD render a privacy notice indicating that silent-payment donations are not reflected in the totals.
+For silent-payment campaigns, clients MUST NOT attempt to scan the chain, MUST NOT publish receipts, and MUST NOT display any aggregate that could leak donation activity. The only signal the public sees is the campaign event itself.

 ### Donation Flow — On-chain (`bc1`)

@@ -438,28 +415,18 @@ Silent-payment unlinkability is the entire point of this mode. Clients MUST NOT
 { "kinds": [33863], "authors": ["<creator-pubkey>"], "#d": ["<slug>"], "limit": 1 }
 ```

-**Compute the "raised" total:**
-
-The headline "raised" amount for an on-chain campaign MUST be sourced **directly from the campaign's on-chain `w` address**, not by aggregating kind 8333 receipts. Specifically, clients SHOULD query a mempool.space-compatible Esplora endpoint for the address and use the cumulative `chain_stats.funded_txo_sum` (plus `mempool_stats.funded_txo_sum` if surfacing pending donations) as the total raised.
-
-This is the source of truth for three reasons:
-
-1. **Completeness.** Donors who pay the BIP-21 QR with a native wallet do not publish a kind 8333 receipt. Aggregating receipts would undercount the campaign.
-2. **Forgery resistance.** A single Esplora `GET /address/<addr>` call cannot be spoofed by Nostr publishers, whereas verifying 500+ receipts against the chain is slower and more brittle (relay availability, pagination, replay attempts).
-3. **Stability.** `funded_txo_sum` is cumulative — it does not regress when the beneficiary spends from the address.
-
-**List individual donations (for the recent-donations sidebar):**
+**Aggregate donations for an on-chain campaign:**

 ```json
 { "kinds": [8333], "#a": ["33863:<creator-pubkey>:<slug>"], "limit": 500 }
 ```

-Kind 8333 receipts are used **only** to attribute individual donations to Nostr identities (donor pubkey, comment, timestamp) — not to compute the campaign total. Clients MUST still verify each receipt on-chain per the *Campaign-wallet mode* verification rules in the kind 8333 section before displaying it.
+Clients MUST verify each kind 8333 event on-chain before counting it toward the campaign total, per the *Campaign-wallet mode* verification rules in the kind 8333 section.

 **Filter by country:**

 ```json
-{ "kinds": [33863], "#i": ["iso3166:VE"], "limit": 50 }
+{ "kinds": [33863], "#i": ["iso3166-1:VE"], "limit": 50 }
 ```

 **Fetch pinned event comments:**
@@ -490,23 +457,22 @@ The `pinnedEvents` array is ordered newest pin first. Pinning an already-pinned

 ### Client Behavior

- **Wallet validity:** clients MUST reject events that carry no `w` tag, that carry more than one `w` tag of the same mode (e.g., two `bc1…` addresses), or whose `w` values fail bech32(m) checksum validation for one of the supported prefixes. Invalid campaigns do not render.
+- **Wallet validity:** clients MUST reject events whose `w` tag is missing, present more than once, or whose value does not pass bech32(m) checksum validation for one of the supported prefixes. Invalid campaigns do not render.
 - **Editability:** the creator MAY republish the same `(33863, pubkey, d)` triple to update any field, including the `w` wallet endpoint. Clients SHOULD keep `published_at` from the first publish on subsequent edits (NIP-23 convention).
 - **Closing a campaign:** there is no `status` tag. To stop accepting donations, the creator publishes a NIP-09 kind 5 deletion request referencing the campaign's `a` coordinate. Clients SHOULD honor the deletion by removing the campaign from discovery feeds. Historical kind 8333 receipts MAY still be rendered against the (now-deleted) campaign coordinate so donors can find their past donations.
- **Categories:** clients MAY use user-entered `t` tags for topic filtering and discovery. Agora reserves `t:agora` as its app marker but does not reserve any other topic namespace.
+- **No category, no topics:** kind 33863 events MUST NOT carry `t` tags or NIP-32 category labels in any `agora.*` namespace. Campaigns are individual stories; discovery happens via search (NIP-50 against title/summary/content), country (`#i`), and moderator curation (below).
 - **Migration:** kind 33863 has no relationship to any earlier campaign kind. Clients MUST NOT read, merge, or migrate events of any other kind into the kind 33863 namespace.

 ### Agora Moderation Labels

-Agora curates which kind 33863 campaigns appear on the homepage (`/`) and on the Support directory (`/campaigns`), which kind 34550 organizations appear in the Featured shelf on `/communities`, and which kind 36639 pledges appear in the discovery surfaces on `/pledges`, via moderator-signed NIP-32 label events (kind 1985) in a dedicated label namespace. The labeled event itself is never modified — surfacing is purely a client-side rollup of label events.
+Agora curates which kind 33863 campaigns appear on the homepage (`/`) and on the Support directory (`/campaigns/all`), and which kind 34550 organizations appear in the Featured shelf on `/communities`, via moderator-signed NIP-32 label events (kind 1985) in a dedicated label namespace. The labeled event itself is never modified — surfacing is purely a client-side rollup of label events.

-Campaigns, organizations, and pledges share a single label namespace and a single moderator pack (Team Soapbox); the only thing distinguishing the three streams is the kind prefix on the `a` tag of each label:
+Campaigns and organizations share a single label namespace and a single moderator pack (Team Soapbox); the only thing distinguishing the two streams is the kind prefix on the `a` tag of each label:

 - `33863:<author-pubkey>:<d>` — campaign (kind 33863, see "Open Campaigns" above).
 - `34550:<author-pubkey>:<d>` — organization (kind 34550, NIP-72 community definition).
- `36639:<author-pubkey>:<d>` — pledge (kind 36639, see "Pledge" below).

-A client surfacing campaigns MUST filter folded labels to those whose `a` tag starts with `33863:`. A client surfacing organizations MUST filter to `34550:`. A client surfacing pledges MUST filter to `36639:`. Mixing the streams would let a moderator's `featured` label on a campaign appear to feature an unrelated pledge with the same `d` tag, or any other cross-surface bleed.
+A client surfacing campaigns MUST filter folded labels to those whose `a` tag starts with `33863:`. A client surfacing organizations MUST filter to `34550:`. Mixing the two streams would let a moderator's `featured` label on a campaign appear to feature an unrelated organization with the same `d` tag, or vice versa.

 #### Namespace

@@ -521,60 +487,32 @@ Each label event carries the namespace twice, per NIP-32:

 #### Label values

-Two independent axes are defined; the newest moderator-signed label per axis per coordinate wins. All three surfaces (campaigns, organizations, pledges) use the same two axes — every Agora-tagged entity is publicly visible by default, and moderation reduces to suppressing unwanted entries (`hide`) and lifting curated ones into a featured row (`featured`).
+Three independent axes are defined; the newest moderator-signed label per axis per coordinate wins. **Campaigns** use all three axes (`approval`, `hide`, `featured`). **Organizations** use only two — `hide` and `featured` — because every Agora-tagged organization is publicly visible by default; there is no approval gate for orgs. Moderators MUST NOT publish `approved` or `unapproved` labels against kind 34550 coordinates, and clients MUST ignore any such labels they receive.

-| Axis     | Values                    | Surfaces                           | Meaning                                                                 |
-|----------|---------------------------|------------------------------------|-------------------------------------------------------------------------|
-| hide     | `hidden`, `unhidden`      | campaigns, organizations, pledges  | `hidden` suppresses the target everywhere it would otherwise appear. `unhidden` retracts a previous hide. |
-| featured | `featured`, `unfeatured`  | campaigns, organizations, pledges  | `featured` places the target in a hand-picked Featured row. `unfeatured` retracts. |
-
-> **Legacy `approved` / `unapproved` labels.** A previous revision of this spec defined a third axis ("approval") used only by campaigns to gate which campaigns appeared on the home page. The axis was retired once `featured` became the single positive-curation mechanism on the home page. Clients MUST ignore `approved` / `unapproved` labels and SHOULD NOT publish new ones. Existing labels in relay archives are dead data.
+| Axis     | Values                    | Surfaces       | Meaning                                                                 |
+|----------|---------------------------|----------------|-------------------------------------------------------------------------|
+| approval | `approved`, `unapproved`  | campaigns only | `approved` allows the campaign on its discovery surfaces. `unapproved` retracts a previous approval. |
+| hide     | `hidden`, `unhidden`      | both           | `hidden` suppresses the campaign/organization everywhere it would otherwise appear. `unhidden` retracts a previous hide. |
+| featured | `featured`, `unfeatured`  | both           | `featured` places the campaign in the hand-picked Featured row on `/`, or the organization in the Featured shelf on `/communities`. `unfeatured` retracts. |

 Surfacing rules (hide always wins):

 **Campaigns**

- **Featured row on `/`** — iff the latest featured label is `featured` AND the latest hide label is not `hidden`. Ordered by the featured label's effective rank (see Moderator-driven Ordering), descending.
- **Discover shelf on `/campaigns`** — iff the latest hide label is not `hidden`. Every non-hidden campaign on the network is enumerable here; the home page's Featured row is a curated subset, not a gate.
- **Moderator-only "Hidden"** — iff hidden. Surfaces the suppressed set so moderators can unhide.
+- **Featured row on `/`** — iff the latest featured label is `featured` AND the latest hide label is not `hidden`. Ordered newest-`created_at`-of-`featured`-label first. Featured is independent of Approved at the protocol level; a campaign may be featured without being approved (the home page treats Featured and Approved as deduplicated bins, with Featured taking precedence).
+- **Community Campaigns grid on `/`** — iff approved, not hidden, and not featured (featured campaigns get their own row above).
+- **Discover shelf** — iff approved AND not hidden.
+- **Moderator-only "Pending"** — iff neither approved nor hidden.
+- **Moderator-only "Hidden"** — iff hidden.

 **Organizations**

- **Featured shelf on `/communities`** — iff the latest featured label is `featured` AND the latest hide label is not `hidden`. Ordered by the featured label's effective rank, descending (see Moderator-driven Ordering).
+- **Featured shelf on `/communities`** — iff the latest featured label is `featured` AND the latest hide label is not `hidden`. Ordered newest-`created_at`-of-`featured`-label first.
 - **"My organizations" shelf on `/communities`** — intentionally ignores all moderation labels. A user's own founded, moderated, or followed organizations always render regardless of label state.
 - **Moderator-only "Needs review"** — iff `t:agora` AND not featured AND not hidden. Surfaces orgs minted through Agora's create flow that haven't been triaged into Featured or Hidden yet.
 - **Moderator-only "Hidden"** — iff hidden.
 - **Hide enforcement on other organization discovery surfaces** — clients SHOULD suppress `hidden` organizations from any future "All organizations" / browse surface for non-moderators. Moderators MAY see hidden organizations with a "Hidden" treatment so they can unhide.

-**Pledges**
-
- **Discovery surfaces on `/pledges`** — non-moderators MUST NOT see `hidden` pledges in the active / upcoming / past sections, the search results grid, or any future browse surface. Moderators MAY opt-in to seeing hidden pledges via a Show-hidden toggle so they can unhide.
- **Author-own surfaces** — a pledge author's own pledges in their profile always render regardless of moderation state. Moderation governs public discovery, not authorship.
- **Direct-URL access** — a pledge's detail page (`/<naddr>`) renders regardless of moderation state. Hidden pledges remain reachable by anyone who has the link; moderation only governs which surfaces enumerate them.
- **Featured** — reserved for a future curated pledge shelf. The `featured` axis is defined for symmetry with campaigns/organizations, and clients MAY use it when implementing such a shelf.
-
-#### Moderator-driven Ordering
-
-The Featured row is sorted by the **effective rank** of the moderator's latest `featured` label per campaign coordinate, descending.
-
-A label's effective rank is the numeric value of its `["rank", "<number>"]` tag if present, falling back to the label's `created_at` when no rank tag is set. Labels published before this feature existed — and any normal hide / feature actions that don't carry a rank — surface with their `created_at` as the effective rank, so newer feature actions naturally float to the top.
-
-The fold rule per `(coord, axis)` is unchanged: the newest event by `created_at` wins. Encoding order in the `created_at` itself would conflict with that rule the moment a moderator tried to lower a campaign's position — the new label would have an older `created_at` than the existing one and lose the fold. The rank tag decouples sort key from event recency so reorder publishes always use `created_at = now` and the fold always picks them up.
-
-A moderator MAY reorder the row by republishing the `featured` label for a campaign with a `rank` tag carrying a chosen integer. Three operations cover the common cases:
-
- **Move to top** — publish with `rank = max(freshRank, currentTopRank + 1)`, where `freshRank` is a strictly-monotonic integer the client SHOULD source from current wall-clock time at sub-second resolution (Agora uses `Date.now() * 1000`). The `max` guard handles a (rare) clock-skewed existing rank that's already above `freshRank`.
- **Move up by one** — publish with `rank = neighborAbove.rank + 1`, where `neighborAbove` is the label sorted directly above the campaign being moved.
- **Move down by one** — publish with `rank = neighborBelow.rank - 1`. Only the moved campaign's label is republished; the neighbor below is untouched.
-
-A general "drop at index `j`" (e.g. drag-and-drop in a moderator UI) is implemented by computing the two new neighbors of the moved campaign in the rearranged list and choosing any integer rank strictly between their ranks. When the gap is too tight (`prev.rank - next.rank < 2`), clients SHOULD pick `next.rank + 1` and accept that the rendered list may briefly be off by one until the next reorder leaves a wider gap. Using a sub-second-resolution `freshRank` keeps inter-rank gaps wide enough for many midpoint inserts before any renumbering is needed.
-
-The conflict model matches the rest of the moderation namespace: the newest label per `(coord, axis)` from any moderator wins. Concurrent reorders by two moderators resolve to whoever's publish lands later; clients SHOULD refetch labels after a reorder publish to surface the authoritative order.
-
-Reorder labels remain valid moderation labels in every other respect. Clients that don't recognize the `rank` tag simply read the label's axis state and ignore the rank — the labels are not a separate kind, not a separate namespace, and not a new tag namespace. Non-Agora clients see exactly the same hide / feature state they always have.
-
-The featured row is the only Agora surface that uses moderator-driven ordering today. The same mechanism MAY be applied to the organization or pledge featured shelves if those grow a curation UI; until then, those shelves sort by `created_at` (the legacy behavior, identical to using a missing rank tag).
-
 #### Event Structure

 ```json
@@ -583,9 +521,9 @@ The featured row is the only Agora surface that uses moderator-driven ordering t
  "content": "",
  "tags": [
    ["L", "agora.moderation"],
-    ["l", "featured", "agora.moderation"],
+    ["l", "approved", "agora.moderation"],
    ["a", "33863:<author-pubkey>:<campaign-d-tag>"],
-    ["alt", "Campaign moderation: featured"]
+    ["alt", "Campaign moderation: approved"]
  ]
 }
 ```
@@ -605,47 +543,12 @@ An organization label has the same shape with a kind 34550 `a` tag:
 }
 ```

-A pledge label has the same shape with a kind 36639 `a` tag:
-
-```json
-{
-  "kind": 1985,
-  "content": "",
-  "tags": [
-    ["L", "agora.moderation"],
-    ["l", "hidden", "agora.moderation"],
-    ["a", "36639:<author-pubkey>:<pledge-d-tag>"],
-    ["alt", "Pledge moderation: hidden"]
-  ]
-}
-```
-
 Required tags:

 - `L` set to `agora.moderation`.
 - `l` with the label value as the 2nd element and `agora.moderation` as the 3rd.
- `a` referencing the target coordinate (`33863:<pubkey>:<d>` for a campaign, `34550:<pubkey>:<d>` for an organization, `36639:<pubkey>:<d>` for a pledge).
- `alt` (NIP-31) — clients without label support will display this string. The `alt` value SHOULD identify the surface (e.g. `Campaign moderation: featured`, `Organization moderation: featured`, or `Pledge moderation: hidden`) so non-Agora clients can read it.
-
-Optional tags:
-
- `rank` — single string element parsed as an integer. Used on `featured` labels to position the target within the moderator-curated Featured row; see Moderator-driven Ordering above. Labels without this tag sort by `created_at` (descending), which is the correct behavior for all non-reorder uses.
-
-A label with a rank tag looks like:
-
-```json
-{
-  "kind": 1985,
-  "content": "",
-  "tags": [
-    ["L", "agora.moderation"],
-    ["l", "featured", "agora.moderation"],
-    ["a", "33863:<author-pubkey>:<campaign-d-tag>"],
-    ["rank", "1700000000123000"],
-    ["alt", "Campaign moderation: featured"]
-  ]
-}
-```
+- `a` referencing the target coordinate (`33863:<pubkey>:<d>` for a campaign, `34550:<pubkey>:<d>` for an organization).
+- `alt` (NIP-31) — clients without label support will display this string. The `alt` value SHOULD identify the surface (e.g. `Campaign moderation: featured` or `Organization moderation: featured`) so non-Agora clients can read it.

 #### Trust Model

@@ -659,8 +562,8 @@ d-tag:      k4p5w0n22suf

 The pack `p` tags are the authoritative moderator list. Clients MUST pin `authors:` on their label REQ to the pack `p` tags; events from non-pack authors MUST be ignored. This means:

- Self-promotion is impossible unless the pack author has added you.
- A moderator removed from the pack immediately loses moderation authority — campaigns kept alive on the Featured row only by their labels fall off the row until another moderator features them.
+- Self-approval is impossible unless the pack author has added you.
+- A moderator removed from the pack immediately loses moderation authority — campaigns/organizations kept alive only by their labels return to "pending" until another moderator approves them.
 - The pack author (single signer) can reset the entire moderator roster by republishing the pack.

 The same moderator set governs both campaign and organization labels. Carving out per-surface moderator subsets is out of scope; clients that need that distinction would have to introduce a second follow pack and a second label namespace.
@@ -693,111 +596,13 @@ Step 3 — fold by `(coord, axis)`, latest-`created_at`-wins, filtering to the r

 #### Client Behavior

- Clients SHOULD render hide/feature controls only for users whose pubkey appears in the pack.
- Clients MAY display "Hidden" badges on hidden campaigns/organizations/pledges when viewed by a moderator, and SHOULD NOT render them at all to non-moderators.
- Authors' own campaigns, organizations, and pledges are visible at their NIP-19 routes regardless of moderation state. The campaign URL remains live and donatable even when the campaign is not on the home page's Featured row.
-
-#### Campaign Verification Labels (`agora.verified`)
-
-Separately from the hide/feature moderation axes above, Agora supports a positive **verification** signal: a campaign moderator vouches for a specific campaign. Verification is a distinct NIP-32 label namespace, `agora.verified`, with a single value `verified`. It rides the same kind 1985 label kind and the **same moderator pack** as the hide/feature labels, but is otherwise independent of `agora.moderation` — no axes, no rank, purely additive.
-
-A verification label points at one campaign coordinate (`33863:<pubkey>:<d>`):
-
-```json
-{
-  "kind": 1985,
-  "content": "",
-  "tags": [
-    ["L", "agora.verified"],
-    ["l", "verified", "agora.verified"],
-    ["a", "33863:<campaign-pubkey>:<campaign-d>"],
-    ["alt", "Campaign verification"]
-  ]
-}
-```
-
-**Trust model.** The set of pubkeys whose `agora.verified` labels are honored is the campaign moderator pack — the same allowlist that governs hide/feature labels (the Team Soapbox follow pack `p` tags). Clients MUST filter the read query by `authors: <moderators>` — a `verified` label signed by any pubkey outside the pack MUST be ignored, otherwise the badge is forgeable by anyone. As with moderation labels, clients MUST NOT run the query with an empty `authors:` filter.
-
-**Reading.** One filter fetches every verification across all moderators:
-
-```json
-{
-  "kinds": [1985],
-  "authors": ["<moderator-1>", "<moderator-2>"],
-  "#L": ["agora.verified"],
-  "#l": ["verified"],
-  "limit": 2000
-}
-```
-
-Fold by `(coord, moderator)`, keeping the newest label per pair. A campaign is "verified by" the set of moderators with a surviving label; clients SHOULD render the moderators' avatars stacked as a badge, with multiple moderators forming a stack.
-
-**Retraction.** There is no `unverified` value. A moderator retracts a verification by publishing a NIP-09 kind 5 deletion of their own label event (referenced by `e` tag plus `k: 1985`). A kind 5 only takes effect on events authored by the signer, so a moderator can only remove their own verification.
-
-**Client behavior.**
- Verification is a moderator action: clients SHOULD render the verify / remove-verification control inside the campaign moderator menu (alongside hide / add-to-list), gated on moderator membership.
- Verification is purely additive — it never hides or promotes a campaign on its own. It is a trust hint layered over whatever moderation/discovery state already applies.
- The label kind 1985 read is routed to Agora's search relays (`relay.ditto.pub`, `relay.dreamith.to`) where these labels are published.
+- Clients SHOULD render approve/hide/feature controls only for users whose pubkey appears in the pack.
+- Clients MAY display "Hidden" badges on hidden campaigns/organizations when viewed by a moderator, and SHOULD NOT render them at all to non-moderators.
+- Non-moderator authors viewing the homepage SHOULD see their own pending campaigns in a separate explained section so they understand why their campaign isn't yet on the homepage. The campaign URL remains live and donatable regardless of moderation state.
+- Organization authors are not shown an equivalent "pending" surface today — organizations are visible at their NIP-19 route regardless of moderation, and the only moderation surface is the Featured shelf.

 ---

-## Kind 14672: Verifier Statement
-
-### Summary
-
-Replaceable event kind for a **self-authored statement describing how the author verifies campaigns**. Anyone can "become a verifier" simply by publishing one of these events — there is no gatekeeper. The statement is a public, freeform explanation of the diligence process the author applies before vouching for a campaign, so donors can judge whether to trust that author's judgement.
-
-Exactly one statement per user (replaceable, no `d` tag): publishing a new event replaces the previous one. Clients surface the statement prominently on the author's profile page.
-
-This kind is **distinct from** the `agora.verified` campaign-verification labels (kind 1985, see Kind 33863 above). Those are moderator-signed, gated by the Team Soapbox follow pack, and vouch for one specific campaign. A kind 14672 statement is an open, self-published description of an author's *general* verification methodology and confers no special authority — it is a reputation signal donors read, not an access-control mechanism.
-
-### Event Structure
-
-```json
-{
-  "kind": 14672,
-  "pubkey": "<author-pubkey>",
-  "content": "I personally visit each campaign organizer over video call, confirm their identity against a government ID, and cross-check the cause with at least two independent local sources before I vouch for it. ...",
-  "tags": [
-    ["alt", "Verifier statement: how this account verifies campaigns"],
-    ["t", "agora"]
-  ]
-}
-```
-
-### Content
-
-The `content` field is the verifier statement, formatted as **Markdown**. Clients SHOULD render it with the same Markdown renderer they use for other long-form Agora content (campaign stories, policy pages). Empty or whitespace-only content means the author has **withdrawn** their verifier statement — clients MUST treat an empty-content event the same as no event (the author is no longer a verifier) and MUST NOT render a verifier section for it.
-
-### Tags
-
-| Tag   | Required    | Description                                                                 |
-|-------|-------------|-----------------------------------------------------------------------------|
-| `alt` | Recommended | NIP-31 human-readable fallback describing the event's purpose.              |
-| `t`   | Optional    | Agora content marker (`t:agora`). Added at publish time via `withAgoraTag`. |
-
-The statement carries no queryable fields beyond the author and kind — it is identified entirely by `(14672, pubkey)`.
-
-### Querying
-
-**Fetch a user's verifier statement:**
-
-```json
-{ "kinds": [14672], "authors": ["<pubkey>"], "limit": 1 }
-```
-
-Clients MUST filter by `authors` — a verifier statement only describes the diligence of the pubkey that signed it, so an unfiltered query would be meaningless (and would let anyone's statement be attributed to anyone).
-
-### Client Behavior
-
- **Becoming a verifier:** a user publishes a kind 14672 event with their statement in `content`. No approval, allowlist, or moderation gate applies.
- **Withdrawing:** a user republishes the event with empty `content`, or publishes a NIP-09 kind 5 deletion referencing the event. Either way clients stop rendering the verifier section.
- **Rendering:** clients SHOULD surface the statement prominently on the author's profile (e.g. a dedicated "Verifier" section in the profile overview), rendering the Markdown content sanitized.
- **Editing:** because the kind is replaceable, the latest event per `(14672, pubkey)` wins. Clients performing an edit SHOULD pass the previous event as `prev` so `published_at` is preserved (NIP-23 convention).
-
---
-
-
 ## Kind 16769: Profile Tabs

 ### Summary
@@ -1167,9 +972,6 @@ A kind `34550` event defines the community, extending [NIP-72](https://github.co
 | `image` | No | Image URL. |
 | `a` | Yes (1) | Member badge definition reference with role marker `"member"`. |
 | `p` | No | Moderator pubkeys. The 4th element SHOULD be `"moderator"`. |
-| `i` | No | Agora extension: NIP-73 country identifier (`iso3166:XX`) for country-scoped group discovery. This is not part of NIP-72. |
-| `k` | Recommended if `i` is present | Agora extension: external content kind hint. Use `iso3166` for country identifiers. |
-| `t` | No | Agora extension: user-entered discovery/category tags. Agora also adds `t:agora` as the app marker. |
 | `relay` | No | Recommended relay URL for community content (per [NIP-72](https://github.com/nostr-protocol/nips/blob/master/72.md)). |
 | `alt` | No | [NIP-31](https://github.com/nostr-protocol/nips/blob/master/31.md) description. |

@@ -1195,10 +997,6 @@ The fourth element is a strict protocol marker, not a display label. Communities
    ["image", "https://example.com/clan-banner.jpg"],
    ["a", "30009:<founder-pubkey>:a1b2c3d4-...-member", "", "member"],
    ["p", "<co-moderator-pubkey>", "", "moderator"],
-    ["i", "iso3166:US"],
-    ["k", "iso3166"],
-    ["t", "local-news"],
-    ["t", "mutual-aid"],
    ["relay", "wss://relay.example.com"],
    ["alt", "Community: The Arbiter's Guard"]
  ]
@@ -1686,85 +1484,3 @@ Albums are represented as kind 34139 playlist events with a `["t", "album"]` tag
 - Albums display release date and label information when available
 - Track ordering follows the order of `a` tags in the event
 - The same detail view, playback, and commenting features apply to both albums and playlists
-
---
-
-## Agora HD Wallet Derivation
-
-### Summary
-
-Agora's Bitcoin wallet is hierarchical-deterministic and derived from the user's Nostr secret key (`nsec`). The user backs up either the nsec or the 24-word BIP-39 mnemonic — the mnemonic is a deterministic, one-way function of the nsec, so anyone with the nsec can regenerate the mnemonic at will.
-
-This specification covers two derivation generations:
-
- **v2 (current)** — nsec → HKDF → BIP-39 24-word mnemonic → PBKDF2 → BIP-32 master seed. The resulting mnemonic imports into any BIP-39-compatible wallet (Sparrow, Electrum, Trezor, Ledger, BlueWallet, Phoenix, …) at the standard BIP-86 / BIP-352 paths.
- **v1 (legacy, migration-only)** — nsec used directly as the BIP-32 master seed (`HDKey.fromMasterSeed(nsec_bytes)`). v1 and v2 produce different addresses for the same nsec.
-
-### v2 Derivation
-
-The v2 pipeline turns a 32-byte nsec into a 64-byte BIP-32 master seed in three steps:
-
-```
-entropy  = HKDF-SHA256(ikm = nsec_bytes,
-                       salt = "" (default per RFC 5869),
-                       info = "agora/v1",
-                       length = 32 bytes)
-mnemonic = BIP-39 encoding of (entropy || SHA256(entropy)[0])      // 24 words
-seed     = PBKDF2-HMAC-SHA512(password = mnemonic,
-                              salt = "mnemonic",
-                              iterations = 2048,
-                              dkLen = 64)
-master   = HDKey.fromMasterSeed(seed)                              // BIP-32 root
-```
-
-The `"agora/v1"` HKDF info string is a versioning hook: changing it would derive a completely independent wallet from the same nsec. The `"mnemonic"` PBKDF2 salt is the literal BIP-39 default (no user passphrase).
-
-#### Properties
-
- **Deterministic** — the same nsec always produces the same mnemonic, seed, and BIP-32 master.
- **One-way** — the mnemonic is a hash of the nsec; an attacker who learns the mnemonic learns only the wallet, not the Nostr identity.
- **Interoperable** — the resulting 24-word phrase is a standard BIP-39 mnemonic. Any BIP-39-compatible wallet can import it at the BIP-86 / BIP-352 paths and recover the same on-chain addresses.
-
-### Address Derivation
-
-Once the BIP-32 master is in hand, addresses derive at the standard paths:
-
-#### BIP-86 (Taproot single-key, key-path-only)
-
-```
-m/86'/0'/0'/<chain>/<index>
-```
-
- `chain ∈ {0, 1}` — `0` = receive, `1` = change.
- `index` — advanced per receive (no address reuse).
-
-Output script is P2TR with the derived x-only pubkey as `internalPubkey` (no tapscript tree).
-
-#### BIP-352 (Silent Payments)
-
-```
-m/352'/0'/0'/0'/0    // spend keypair
-m/352'/0'/0'/1'/0    // scan keypair
-```
-
-The silent-payment address (`sp1q…`) is the bech32m encoding of `(scan_pubkey || spend_pubkey)` with version `0` and HRP `sp`. The address is **static** — a user publishes one `sp1q…` and reuses it; each sender derives a fresh, unlinkable Taproot output per payment.
-
-### v1 → v2 Migration
-
-The v1 derivation (`HDKey.fromMasterSeed(nsec_bytes)`) produces a different BIP-32 master than v2 for the same nsec, so a user upgrading from v1 to v2 has funds at addresses that the v2 wallet never scans. Agora ships a one-shot migration page (`/wallet/migrate-v1`) that:
-
-1. Detects v1 funds by scanning the v1 xpub against the configured Blockbook indexer and reading the v1 silent-payment UTXO doc from the user's relays (NIP-78 d-tag `${appId}/hdwallet/sp-utxos`).
-2. If any v1 funds exist, builds a single sweep PSBT consuming every v1 BIP-86 UTXO + every v1 SP UTXO, with one output (`total − fee`) at the v2 wallet's first BIP-86 receive address.
-3. Signs every input using v1-derived keys (`HDKey.fromMasterSeed(nsec_bytes)`) and broadcasts via Blockbook.
-
-The v1 derivation code is retained indefinitely so users can migrate at any time. New scans, sends, and receives always run against v2.
-
-### NIP-78 Storage
-
-Agora stores per-wallet auxiliary state as a NIP-78 encrypted addressable event (kind 30078, NIP-44 to the user's own pubkey). The v2 d-tag suffix is `hdwallet/sp-utxos/v2`; the legacy v1 d-tag is `hdwallet/sp-utxos`. The two are independent: v2 never writes to the v1 tag, and the v1 tag is read only by the migration sweep.
-
-### Security Notes
-
- The nsec is both the Nostr identity secret and the wallet seed source. Anyone with the nsec controls both. The 24-word mnemonic is the wallet half of that secret and is safer to share with Bitcoin-side tools (it can't impersonate the user on Nostr).
- The wallet is gated to nsec logins. Browser-extension (NIP-07) and remote-signer (NIP-46) logins do not expose the raw secret key, so the wallet cannot derive child keys and surfaces an "unsupported" state.
- Spend signing happens locally in the browser using the derived BIP-32 leaves. The nsec never leaves the device.
@@ -0,0 +1,116 @@
+NIP-DC
+======
+
+Nostr Webxdc
+------------
+
+`draft` `optional`
+
+This NIP defines how to share and run [webxdc](https://webxdc.org/) apps over Nostr. Webxdc apps are `.xdc` (ZIP) files containing sandboxed HTML5 applications. They are attached to regular Nostr events using `imeta` tags (NIP-92), and state is coordinated through a unique identifier.
+
+This spec covers public webxdc communication only. Private communication may be addressed in a future update.
+
+## Attachment
+
+A webxdc app is attached to any event by including the `.xdc` file URL in the content and an `imeta` tag with MIME type `application/x-webxdc`.
+
+The `imeta` tag SHOULD include a `webxdc` property with a randomly generated unique string. This serves as the coordination identifier for state updates and realtime channels. If omitted, the app can still run but state won't work.
+
+```json
+{
+  "kind": 1,
+  "content": "Let's play chess! https://blossom.example.com/abc123.xdc",
+  "tags": [
+    ["imeta",
+      "url https://blossom.example.com/abc123.xdc",
+      "m application/x-webxdc",
+      "x a1b2c3d4e5f6...",
+      "webxdc 9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d"
+    ]
+  ]
+}
+```
+
+A webxdc MAY also be published as a kind `1063` (NIP-94) file metadata event:
+
+```json
+{
+  "kind": 1063,
+  "content": "A collaborative chess game. Play with friends over Nostr!",
+  "tags": [
+    ["url", "https://blossom.example.com/abc123.xdc"],
+    ["m", "application/x-webxdc"],
+    ["x", "a1b2c3d4e5f6..."],
+    ["alt", "Webxdc app: Chess"],
+    ["webxdc", "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d"]
+  ]
+}
+```
+
+## Kind `4932`: State Update
+
+A regular event carrying a state update, mapping to the webxdc [`sendUpdate()`](https://webxdc.org/docs/spec/sendUpdate.html) API. Updates are ordered by `created_at` and assigned serial numbers by the client.
+
+### Tags
+
+- `i`: The `webxdc` identifier from the originating event (required)
+- `alt`: NIP-31 human-readable description (required)
+- `info`: Short info message, max ~50 chars (optional)
+- `document`: Document name being edited (optional)
+- `summary`: Short summary text, e.g. "8 votes" (optional)
+
+The optional tags correspond to fields in the webxdc `sendUpdate()` API.
+
+### Content
+
+JSON-serialized payload from `sendUpdate()`.
+
+```json
+{
+  "kind": 4932,
+  "content": "{\"move\":\"e2e4\",\"player\":\"white\"}",
+  "tags": [
+    ["i", "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d"],
+    ["alt", "Webxdc update"],
+    ["info", "White played e2-e4"]
+  ]
+}
+```
+
+## Kind `20932`: Realtime Data (Ephemeral)
+
+An ephemeral event carrying realtime data, mapping to the webxdc [`joinRealtimeChannel`](https://webxdc.org/docs/spec/joinRealtimeChannel.html) API. Relays forward these to active subscribers but do not store them.
+
+### Tags
+
+- `i`: The `webxdc` identifier from the originating event (required)
+
+### Content
+
+Base64-encoded `Uint8Array` payload (max 128,000 bytes raw).
+
+```json
+{
+  "kind": 20932,
+  "content": "SGVsbG8gZnJvbSBucHViMWFiYy4uLg==",
+  "tags": [
+    ["i", "9b1deb4d-3b7d-4bad-9bdd-2b0d7b3dcb6d"]
+  ]
+}
+```
+
+## Flow
+
+1. A user uploads a `.xdc` file (e.g. to Blossom) and publishes an event with the URL in content and an `imeta` tag. The `imeta` SHOULD include a `webxdc` property.
+2. A client detects the `imeta` tag, downloads the `.xdc`, extracts it, and runs `index.html` in a sandboxed iframe or webview.
+3. `sendUpdate()` publishes a kind `4932` event with the `webxdc` identifier in an `i` tag.
+4. The client subscribes to kind `4932` events with `#i` matching the identifier and delivers them via `setUpdateListener()`.
+5. `joinRealtimeChannel()` subscribes to kind `20932` events with `#i` matching the identifier. `send()` publishes ephemeral kind `20932` events. `leave()` closes the subscription.
+6. `selfAddr` and `selfName` MAY map to the user's npub and display name, or any other values.
+
+## Security Considerations
+
+- Webxdc apps MUST be sandboxed with no network access, per the [webxdc spec](https://webxdc.org/docs/spec/messenger.html).
+- Clients SHOULD verify the `.xdc` file hash (`x` tag) before running it.
+- All communication in this spec is public. Webxdc apps designed for private chats or small groups may not work as expected.
+- Webxdc apps have no access to Nostr signatures or identity verification. Any participant can claim to be anyone within the app. Apps should not rely on `selfAddr` or `selfName` for trust decisions.
@@ -1,24 +1,22 @@
-# Eranos
+# Agora

 Power to the people.

-Eranos is a Nostr client focused on community ownership, expressive identity, and censorship resistance. This repository is the Eranos-branded app, a Grin-only fork of Agora (itself built from the Ditto codebase). It federates with the wider Nostr network - the search, labels, video, and zapstore routes are all live - with `relay.floonet.dev` as its home relay.
+Agora is a Nostr client focused on community ownership, expressive identity, and censorship resistance. This repository (`agora-3`) is the Agora-branded app built from the Ditto codebase.

-A mechanical Grin-only content policy runs at the edge: it drops the zap event kinds (9041, 9734, 9735) and redacts Lightning money-rail tokens (bolt11, lnurl, and `lightning:` URIs) from posts and DMs while keeping the rest of the message. Grin slatepacks and the Grin campaign kinds (33863, 36639, 3414) pass through untouched. Talking about bitcoin is never filtered - only the Lightning money rail is redacted. Web push is disabled.
-
-**[eranos.fund](https://eranos.fund)** | **Upstream: [Agora](https://gitlab.com/soapbox-pub/agora-3)**
+**[agora.spot](https://agora.spot)** | **[Source](https://gitlab.com/soapbox-pub/agora-3)**

 ## What This Repo Is

- Eranos product identity (name, theme, assets, native IDs)
+- Agora product identity (name, theme, assets, native IDs)
 - Ditto-derived implementation with broad Nostr feature coverage
- Configurable deployment defaults via `eranos.json`
+- Configurable deployment defaults via `agora.json`

 ## Features

 - **Community-first social client**: notes, articles, comments, reposts, reactions, and rich event rendering
- **Grin-only content policy**: federates with foreign relays but drops the Lightning zap kinds and redacts Lightning payment tokens, leaving Grin campaigns, slatepacks, and ordinary discussion (including talk about bitcoin) untouched
 - **Theming system**: built-in presets + custom color/font/background themes that can be shared as events
+- **Lightning support**: zaps with Nostr Wallet Connect and WebLN
 - **Private messaging**: NIP-04 and NIP-17 direct messages
 - **Mobile app shell**: Capacitor-powered Android/iOS wrappers
 - **Self-hostable**: static web build + configurable relay and upload infrastructure
@@ -33,8 +31,8 @@ A mechanical Grin-only content policy runs at the edge: it drops the zap event k
 ### Development

 ```sh
-git clone <this-repo>
-cd eranos
+git clone https://gitlab.com/soapbox-pub/agora-3.git
+cd agora-3
 npm install
 npm run dev
 ```
@@ -46,8 +44,8 @@ Development server: `http://localhost:8080`
 Use Docker Compose when you want the nginx reverse-proxy stack (necessary if you want decryptable media in messages - kind 15s of NIP 17):

 ```sh
-git clone <this-repo>
-cd eranos
+git clone https://gitlab.com/soapbox-pub/agora-3.git
+cd agora-3
 cp .env.example .env
 docker compose up --build
 ```
@@ -89,7 +87,7 @@ This runs type-checking, linting, unit tests, and production build checks.

 ## Configuration

-Build-time config is read from `eranos.json` (gitignored by default so each deployment can provide its own values).
+Build-time config is read from `agora.json` (gitignored by default so each deployment can provide its own values).

 ```jsonc
 {
@@ -111,7 +109,7 @@ Build-time config is read from `eranos.json` (gitignored by default so each depl
 Configuration priority (highest first):

 1. User settings (local storage)
-2. Build config (`eranos.json`)
+2. Build config (`agora.json`)
 3. Hardcoded app defaults

 Use a custom config path:
@@ -122,7 +120,7 @@ CONFIG_FILE=./my-config.json npm run build

 ## Deployment

-Eranos builds to static files and can be deployed to any static host.
+Agora builds to static files and can be deployed to any static host.

 - GitLab/GitHub Pages
 - Netlify/Vercel
@@ -157,5 +155,3 @@ Read [CONTRIBUTING.md](CONTRIBUTING.md) before opening a merge request.
 ## License

 [AGPL-3.0](LICENSE)
-
-🤖 Built with AI pair-programming assistance (Claude)
@@ -7,22 +7,15 @@ if (keystorePropertiesFile.exists()) {
 }

 android {
-    namespace = "fund.eranos.app"
+    namespace = "spot.agora.app"
    compileSdk = rootProject.ext.compileSdkVersion
    defaultConfig {
-        applicationId "fund.eranos.app"
+        applicationId "spot.agora.app"
        minSdkVersion rootProject.ext.minSdkVersion
        targetSdkVersion rootProject.ext.targetSdkVersion
        versionCode 1
-        versionName "2.9.1"
+        versionName "2.14.4"
        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
-        // The arti-mobile AAR bundles large native Rust libraries for every
-        // ABI (~45 MB total). Restrict to the ABIs we actually ship/test:
-        // arm64-v8a + armeabi-v7a (real devices) and x86_64 (emulators).
-        // Drop x86_64 here if you only ever test on physical devices.
-        ndk {
-            abiFilters 'arm64-v8a', 'armeabi-v7a', 'x86_64'
-        }
        aaptOptions {
             // Files and dirs to omit from the packaged assets dir, modified to accommodate modern web apps.
             // Default: https://android.googlesource.com/platform/frameworks/base/+/282e181b58cf72b6ca770dc7ca5f91f135444502/tools/aapt/AaptAssets.cpp#61
@@ -58,20 +51,10 @@ repositories {
 dependencies {
    implementation fileTree(include: ['*.jar'], dir: 'libs')
    implementation "androidx.appcompat:appcompat:$androidxAppCompatVersion"
-    implementation "androidx.core:core:$androidxCoreVersion"
    implementation "androidx.coordinatorlayout:coordinatorlayout:$androidxCoordinatorLayoutVersion"
    implementation "androidx.core:core-splashscreen:$coreSplashScreenVersion"
    implementation project(':capacitor-android')
    implementation 'com.squareup.okhttp3:okhttp:4.12.0'
-    // Tor in Rust (arti) — prebuilt AAR from Guardian Project's gpmaven repo
-    // (source pinned to an immutable commit in the root build.gradle).
-    // Provides org.torproject.arti.ArtiProxy used by TorController.
-    // The resolved AAR is checksum-verified below (verifyArtiChecksum).
-    implementation 'org.torproject:arti-mobile:1.7.0.1'
-    // arti pulls androidx.webkit in transitively but only at runtime; we
-    // compile against ProxyController/WebViewFeature in TorController, so
-    // declare it explicitly on the app's compile classpath.
-    implementation "androidx.webkit:webkit:$androidxWebkitVersion"
    testImplementation "junit:junit:$junitVersion"
    androidTestImplementation "androidx.test.ext:junit:$androidxJunitVersion"
    androidTestImplementation "androidx.test.espresso:espresso-core:$androidxEspressoCoreVersion"
@@ -80,49 +63,6 @@ dependencies {

 apply from: 'capacitor.build.gradle'

-// Supply-chain pin for the arti-mobile AAR. It carries a native library with
-// network-proxy privileges and is sourced from Guardian Project's gpmaven repo,
-// so we verify the resolved artifact's SHA-256 against a value pinned here.
-// A mismatch fails the build before any APK is assembled. To bump arti, update
-// the version + repo commit (root build.gradle) and replace this checksum after
-// re-verifying a fresh download.
-ext.artiMobileSha256 = 'cbdb34ce3cdb32f755f25f6dd05a2d1eb9a44025a17ec9202729816e2a3af05b'
-
-task verifyArtiChecksum {
-    doLast {
-        def artifact = configurations.releaseRuntimeClasspath
-            .resolvedConfiguration
-            .resolvedArtifacts
-            .find { it.moduleVersion.id.group == 'org.torproject' && it.moduleVersion.id.name == 'arti-mobile' }
-
-        if (artifact == null) {
-            throw new GradleException("arti-mobile artifact not found on the runtime classpath; cannot verify Tor native library.")
-        }
-
-        def actual = java.security.MessageDigest.getInstance("SHA-256")
-            .digest(artifact.file.bytes)
-            .collect { String.format('%02x', it) }
-            .join('')
-
-        if (actual != project.ext.artiMobileSha256) {
-            throw new GradleException(
-                "arti-mobile AAR checksum mismatch!\n" +
-                "  expected: ${project.ext.artiMobileSha256}\n" +
-                "  actual:   ${actual}\n" +
-                "  file:     ${artifact.file}\n" +
-                "Refusing to build a Tor proxy from an unverified native artifact."
-            )
-        }
-        logger.lifecycle("Verified arti-mobile AAR checksum (${actual}).")
-    }
-}
-
-afterEvaluate {
-    tasks.matching { it.name.startsWith('assemble') || it.name.startsWith('bundle') }.configureEach {
-        dependsOn verifyArtiChecksum
-    }
-}
-
 try {
    def servicesJSON = file('google-services.json')
    if (servicesJSON.text) {
@@ -7,7 +7,7 @@

 # Keep Capacitor classes (WebView JS bridge)
 -keep class com.getcapacitor.** { *; }
-keep class fund.eranos.app.** { *; }
+-keep class spot.agora.app.** { *; }

 # Keep WebView JS interfaces
 -keepclassmembers class * {
@@ -19,18 +19,6 @@
 -dontwarn okio.**
 -keep class okhttp3.** { *; }

-# Barcode scanner plugin (@capacitor/barcode-scanner -> OutSystems ionbarcode)
-# references Gson's @SerializedName, but Gson isn't on the release classpath.
-# Suppress the missing-class warning, keep the annotation attribute, and keep
-# the plugin's model classes so R8 doesn't strip/rename serialized fields.
-dontwarn com.google.gson.**
-keepattributes *Annotation*
-keep class com.outsystems.plugins.barcode.** { *; }
-
-# Keep arti (Tor) classes — ArtiJNI declares native methods invoked from the
-# Rust .so via JNI, so its names must not be obfuscated/stripped.
-keep class org.torproject.arti.** { *; }
-
 # Uncomment this to preserve the line number information for
 # debugging stack traces.
 #-keepattributes SourceFile,LineNumberTable
@@ -24,12 +24,12 @@
                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>

-            <!-- Deep links: open eranos.fund URLs in the app -->
+            <!-- Deep links: open agora.spot URLs in the app -->
            <intent-filter android:autoVerify="true">
                <action android:name="android.intent.action.VIEW" />
                <category android:name="android.intent.category.DEFAULT" />
                <category android:name="android.intent.category.BROWSABLE" />
-                <data android:scheme="https" android:host="eranos.fund" />
+                <data android:scheme="https" android:host="agora.spot" />
            </intent-filter>

        </activity>
@@ -60,6 +60,4 @@
    <uses-permission android:name="android.permission.WAKE_LOCK" />
    <uses-permission android:name="android.permission.RECORD_AUDIO" />
    <uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
-    <uses-permission android:name="android.permission.CAMERA" />
-    <uses-feature android:name="android.hardware.camera" android:required="false" />
 </manifest>
@@ -1,381 +0,0 @@
-package fund.eranos.app;
-
-import android.content.Context;
-import android.content.SharedPreferences;
-import android.util.Log;
-
-import androidx.annotation.Nullable;
-import androidx.webkit.ProxyConfig;
-import androidx.webkit.ProxyController;
-import androidx.webkit.WebViewFeature;
-
-import org.json.JSONException;
-import org.json.JSONObject;
-
-import java.net.InetSocketAddress;
-import java.net.Proxy;
-import java.util.concurrent.Executors;
-import java.util.concurrent.ScheduledExecutorService;
-import java.util.concurrent.TimeUnit;
-import java.util.concurrent.atomic.AtomicBoolean;
-import java.util.regex.Matcher;
-import java.util.regex.Pattern;
-
-import org.torproject.arti.ArtiProxy;
-
-import okhttp3.OkHttpClient;
-import okhttp3.Request;
-import okhttp3.Response;
-
-/**
- * Process-wide controller for the optional Tor (arti) mode on Android.
- *
- * <p>When enabled, this starts a local SOCKS5 proxy backed by arti (Tor in
- * Rust) and — via {@link ArtiProxy.ArtiProxyBuilder#setWrapWebView(boolean)} —
- * installs an Android {@code ProxyController} override so that <em>all</em>
- * Capacitor WebView traffic (every {@code fetch} and relay {@code WebSocket})
- * is routed through Tor. No changes to the TypeScript HTTP layer are needed.
- *
- * <p>The enabled flag is persisted to {@link SharedPreferences} by
- * {@link TorPlugin} and read here at startup from {@link MainActivity}, so arti
- * auto-starts on a cold launch <em>before</em> the WebView loads — there is no
- * pre-bootstrap leak window. Beyond that, activation is live: the settings
- * toggle calls {@link #start}/{@link #stop} (bridged through {@link TorPlugin}),
- * which start or stop arti immediately while also updating the persisted flag.
- *
- * <p>Pluggable transports (obfs4 via IPtProxy) are intentionally not wired up
- * yet — the builder already exposes {@code setObfs4Port}/{@code setBridgeLines}
- * for a future censorship-resistance layer.
- */
-public class TorController {
-
-    private static final String TAG = "TorController";
-
-    /** Local SOCKS5 port arti listens on (arti's own default). */
-    public static final int SOCKS_PORT = 9150;
-
-    static final String PREFS_NAME = "tor_config";
-    static final String KEY_ENABLED = "enabled";
-
-    /** Endpoint used to confirm a working Tor circuit (small JSON response). */
-    private static final String PROBE_URL = "https://check.torproject.org/api/ip";
-    // Re-verify continuously (gently) so the status reflects current reality.
-    private static final long PROBE_INTERVAL_SECONDS = 10;
-    /** After this long without a successful probe, surface a soft "failed". */
-    private static final long SOFT_TIMEOUT_SECONDS = 120;
-
-    // Status values mirrored to JS (see src/lib/tor.ts TorStatus).
-    public static final String STATUS_DISABLED = "disabled";
-    public static final String STATUS_CONNECTING = "connecting";
-    public static final String STATUS_CONNECTED = "connected";
-    public static final String STATUS_FAILED = "failed";
-
-    /** Receives status changes so the Capacitor plugin can forward them to JS. */
-    public interface StatusListener {
-        void onTorStatus(String status, int bootstrapPercent, @Nullable String error, @Nullable String exitIp);
-    }
-
-    private static volatile TorController instance;
-
-    private final Object lock = new Object();
-    private final AtomicBoolean started = new AtomicBoolean(false);
-
-    private ArtiProxy artiProxy;
-    private ScheduledExecutorService scheduler;
-
-    private volatile String status = STATUS_DISABLED;
-    private volatile int bootstrapPercent = 0;
-    @Nullable private volatile String error = null;
-    /** Tor exit-node IP from the last successful check (for verification UI). */
-    @Nullable private volatile String exitIp = null;
-    /** Consecutive failed probes; used to debounce CONNECTED -> reconnecting. */
-    private int consecutiveFailures = 0;
-    @Nullable private volatile StatusListener listener;
-    private volatile long startedAtMs = 0;
-
-    private TorController() {}
-
-    public static TorController getInstance() {
-        if (instance == null) {
-            synchronized (TorController.class) {
-                if (instance == null) {
-                    instance = new TorController();
-                }
-            }
-        }
-        return instance;
-    }
-
-    /** Whether Tor is enabled in persisted preferences (read at cold-launch startup). */
-    public static boolean isEnabled(Context context) {
-        SharedPreferences prefs = context.getSharedPreferences(PREFS_NAME, Context.MODE_PRIVATE);
-        return prefs.getBoolean(KEY_ENABLED, false);
-    }
-
-    /**
-     * Persist the enabled flag only. This controls whether arti auto-starts on
-     * the next cold launch; it does not start or stop arti now. For live
-     * activation call {@link #start}/{@link #stop}, which also persist the flag.
-     */
-    public static void setEnabled(Context context, boolean enabled) {
-        context.getSharedPreferences(PREFS_NAME, Context.MODE_PRIVATE)
-                .edit()
-                .putBoolean(KEY_ENABLED, enabled)
-                .apply();
-    }
-
-    public void setListener(@Nullable StatusListener listener) {
-        this.listener = listener;
-        // Replay the current status so a freshly-attached listener is in sync.
-        if (listener != null) {
-            listener.onTorStatus(status, bootstrapPercent, error, exitIp);
-        }
-    }
-
-    public String getStatus() {
-        return status;
-    }
-
-    public int getBootstrapPercent() {
-        return bootstrapPercent;
-    }
-
-    @Nullable
-    public String getError() {
-        return error;
-    }
-
-    @Nullable
-    public String getExitIp() {
-        return exitIp;
-    }
-
-    /**
-     * Start arti and install the WebView proxy override. Idempotent: a second
-     * call while already running is a no-op. Heavy work runs off the caller's
-     * thread so this is safe to invoke from {@code MainActivity.onCreate}.
-     */
-    public void start(Context context) {
-        if (!started.compareAndSet(false, true)) {
-            return;
-        }
-        final Context appContext = context.getApplicationContext();
-        exitIp = null;
-        consecutiveFailures = 0;
-        // Install the fail-closed WebView proxy override synchronously, BEFORE
-        // the WebView loads (start() is called from MainActivity.onCreate ahead
-        // of super.onCreate). With no direct fallback, any request that arti
-        // can't carry fails instead of leaking out directly — even during the
-        // bootstrap window when arti isn't connected yet.
-        applyWebViewProxy();
-        updateStatus(STATUS_CONNECTING, 0, null);
-        startedAtMs = System.currentTimeMillis();
-
-        Thread t = new Thread(() -> {
-            try {
-                synchronized (lock) {
-                    // NB: we do NOT use setWrapWebView(true) — arti's helper
-                    // appends a DIRECT fallback (fail-open). We set our own
-                    // fail-closed override in applyWebViewProxy() instead.
-                    artiProxy = ArtiProxy.Builder(appContext)
-                            .setSocksPort(SOCKS_PORT)
-                            .setLogListener(this::onArtiLog)
-                            .build();
-                    artiProxy.start();
-                }
-                Log.d(TAG, "arti started on socks://127.0.0.1:" + SOCKS_PORT);
-                beginConnectivityProbe();
-            } catch (Throwable e) {
-                Log.e(TAG, "Failed to start arti", e);
-                updateStatus(STATUS_FAILED, bootstrapPercent, String.valueOf(e.getMessage()));
-            }
-        }, "arti-start");
-        t.setDaemon(true);
-        t.start();
-    }
-
-    /** Stop arti and route the WebView back to a direct connection. Safe to
-     *  call live (toggle off) — clears the SOCKS proxy override so traffic
-     *  doesn't get stranded on the now-stopped proxy. */
-    public void stop() {
-        // Remove the WebView SOCKS override first so new requests go direct.
-        clearWebViewProxy();
-        synchronized (lock) {
-            if (scheduler != null) {
-                scheduler.shutdownNow();
-                scheduler = null;
-            }
-            if (artiProxy != null) {
-                try {
-                    artiProxy.stop();
-                } catch (Throwable e) {
-                    Log.w(TAG, "Error stopping arti", e);
-                }
-                artiProxy = null;
-            }
-        }
-        started.set(false);
-        exitIp = null;
-        updateStatus(STATUS_DISABLED, 0, null);
-    }
-
-    /** Re-run the connectivity probe (used by a "Retry" action in the gate). */
-    public void retry() {
-        if (!started.get()) {
-            return;
-        }
-        consecutiveFailures = 0;
-        startedAtMs = System.currentTimeMillis();
-        if (!STATUS_CONNECTED.equals(status)) {
-            updateStatus(STATUS_CONNECTING, bootstrapPercent, null);
-        }
-        beginConnectivityProbe();
-    }
-
-    // --- internals -------------------------------------------------------
-
-    /**
-     * Route the WebView through arti's SOCKS proxy, FAIL-CLOSED. There is no
-     * {@code addDirect()} fallback, so when Tor can't carry a request it fails
-     * rather than leaking to a direct connection. localhost is bypassed (it's
-     * the local Capacitor asset server, never remote traffic).
-     */
-    private void applyWebViewProxy() {
-        try {
-            if (WebViewFeature.isFeatureSupported(WebViewFeature.PROXY_OVERRIDE)) {
-                ProxyConfig config = new ProxyConfig.Builder()
-                        .addProxyRule("socks://127.0.0.1:" + SOCKS_PORT)
-                        // No addDirect() — fail closed.
-                        .addBypassRule("localhost")
-                        .addBypassRule("127.0.0.1")
-                        .build();
-                ProxyController.getInstance().setProxyOverride(config, Runnable::run, () -> {});
-            }
-        } catch (Throwable e) {
-            Log.w(TAG, "Error applying WebView proxy override", e);
-        }
-    }
-
-    /** Remove the app-wide WebView SOCKS proxy override so the WebView reverts
-     *  to a direct connection. */
-    private void clearWebViewProxy() {
-        try {
-            if (WebViewFeature.isFeatureSupported(WebViewFeature.PROXY_OVERRIDE)) {
-                ProxyController.getInstance().clearProxyOverride(Runnable::run, () -> {});
-            }
-        } catch (Throwable e) {
-            Log.w(TAG, "Error clearing WebView proxy override", e);
-        }
-    }
-
-    private static final Pattern PERCENT = Pattern.compile("(\\d{1,3})\\s*%");
-
-    private void onArtiLog(String line) {
-        if (line == null) return;
-        Log.d("artilog", line);
-        // Best-effort bootstrap progress for the UI. arti's log format isn't a
-        // stable API, so the connectivity probe (below) remains authoritative
-        // for the definitive "connected" signal.
-        Matcher m = PERCENT.matcher(line);
-        if (m.find()) {
-            try {
-                int pct = Integer.parseInt(m.group(1));
-                if (pct >= 0 && pct <= 100 && pct >= bootstrapPercent
-                        && !STATUS_CONNECTED.equals(status)) {
-                    updateStatus(STATUS_CONNECTING, pct, null);
-                }
-            } catch (NumberFormatException ignored) {
-            }
-        }
-    }
-
-    private void beginConnectivityProbe() {
-        synchronized (lock) {
-            if (scheduler != null) {
-                scheduler.shutdownNow();
-            }
-            scheduler = Executors.newSingleThreadScheduledExecutor(r -> {
-                Thread th = new Thread(r, "tor-probe");
-                th.setDaemon(true);
-                return th;
-            });
-            final ScheduledExecutorService s = scheduler;
-            final OkHttpClient client = new OkHttpClient.Builder()
-                    .proxy(new Proxy(Proxy.Type.SOCKS, new InetSocketAddress("127.0.0.1", SOCKS_PORT)))
-                    .connectTimeout(20, TimeUnit.SECONDS)
-                    .readTimeout(20, TimeUnit.SECONDS)
-                    .build();
-
-            // Probe continuously (no shutdown on success). check.torproject.org
-            // reports whether the request actually exited via Tor, so we only
-            // report CONNECTED when IsTor is true — and we keep re-verifying so a
-            // dropped circuit downgrades the status instead of lying.
-            s.scheduleWithFixedDelay(() -> {
-                Request req = new Request.Builder()
-                        .url(PROBE_URL)
-                        .header("Accept", "application/json")
-                        .build();
-                try (Response resp = client.newCall(req).execute()) {
-                    String body = resp.body() != null ? resp.body().string() : "";
-                    boolean isTor = false;
-                    String ip = null;
-                    try {
-                        JSONObject json = new JSONObject(body);
-                        isTor = json.optBoolean("IsTor", false);
-                        ip = json.has("IP") ? json.optString("IP", null) : null;
-                    } catch (JSONException ignored) {
-                        // Non-JSON response — treat as not-via-Tor below.
-                    }
-
-                    if (resp.isSuccessful() && isTor) {
-                        consecutiveFailures = 0;
-                        exitIp = ip;
-                        updateStatus(STATUS_CONNECTED, 100, null);
-                    } else if (resp.isSuccessful()) {
-                        // Reached the internet but NOT through Tor — a leak/bypass.
-                        // This should not happen with the SOCKS proxy, but report
-                        // it honestly rather than claiming a Tor connection.
-                        consecutiveFailures = 0;
-                        exitIp = ip;
-                        updateStatus(STATUS_FAILED, bootstrapPercent,
-                                "Connected to the internet, but not through Tor.");
-                    } else {
-                        handleProbeFailure();
-                    }
-                } catch (Exception e) {
-                    handleProbeFailure();
-                }
-            }, 0, PROBE_INTERVAL_SECONDS, TimeUnit.SECONDS);
-        }
-    }
-
-    /** A probe couldn't reach Tor. Debounce CONNECTED, surface FAILED after the
-     *  soft timeout while still connecting. */
-    private void handleProbeFailure() {
-        consecutiveFailures++;
-        if (STATUS_CONNECTED.equals(status)) {
-            // Tolerate a couple of transient blips before downgrading.
-            if (consecutiveFailures >= 3) {
-                exitIp = null;
-                updateStatus(STATUS_CONNECTING, bootstrapPercent,
-                        "Lost the Tor circuit; reconnecting…");
-            }
-            return;
-        }
-        long elapsed = (System.currentTimeMillis() - startedAtMs) / 1000;
-        if (elapsed >= SOFT_TIMEOUT_SECONDS && !STATUS_FAILED.equals(status)) {
-            updateStatus(STATUS_FAILED, bootstrapPercent,
-                    "Couldn't reach the Tor network. Your network may be blocking Tor.");
-        }
-    }
-
-    private void updateStatus(String newStatus, int percent, @Nullable String err) {
-        this.status = newStatus;
-        this.bootstrapPercent = percent;
-        this.error = err;
-        StatusListener l = this.listener;
-        if (l != null) {
-            l.onTorStatus(newStatus, percent, err, exitIp);
-        }
-    }
-}
@@ -1,102 +0,0 @@
-package fund.eranos.app;
-
-import com.getcapacitor.JSObject;
-import com.getcapacitor.Plugin;
-import com.getcapacitor.PluginCall;
-import com.getcapacitor.PluginMethod;
-import com.getcapacitor.annotation.CapacitorPlugin;
-
-/**
- * Capacitor bridge for the Tor (arti) mode.
- *
- * <p>Mirrors {@link DittoNotificationPlugin}'s pattern: JS configures native
- * state, native owns the work. On a cold launch arti auto-starts from
- * {@link MainActivity} based on the persisted flag. At runtime the settings
- * toggle activates Tor live via {@link #start}/{@link #stop}, which start or
- * stop arti immediately and update the persisted flag. ({@link #setEnabled}
- * persists the flag only, without touching the running proxy.) Live bootstrap
- * status is pushed to JS via the {@code torStatus} event.
- *
- * <p>JS interface: see {@code src/lib/tor.ts}.
- */
-@CapacitorPlugin(name = "Tor")
-public class TorPlugin extends Plugin {
-
-    private static final String EVENT_STATUS = "torStatus";
-
-    @Override
-    public void load() {
-        // Forward native status changes to JS listeners. Attaching also replays
-        // the current status, keeping a newly-mounted JS gate in sync.
-        TorController.getInstance().setListener((status, bootstrapPercent, error, exitIp) -> {
-            JSObject data = new JSObject();
-            data.put("status", status);
-            data.put("bootstrapPercent", bootstrapPercent);
-            data.put("error", error);
-            data.put("exitIp", exitIp);
-            notifyListeners(EVENT_STATUS, data);
-        });
-    }
-
-    /** Whether Tor is enabled in persisted preferences. */
-    @PluginMethod
-    public void isEnabled(PluginCall call) {
-        JSObject ret = new JSObject();
-        ret.put("enabled", TorController.isEnabled(getContext()));
-        call.resolve(ret);
-    }
-
-    /**
-     * Persist the enabled flag only, without starting or stopping arti now.
-     * Controls whether arti auto-starts on the next cold launch. For live
-     * activation use {@link #start}/{@link #stop}.
-     */
-    @PluginMethod
-    public void setEnabled(PluginCall call) {
-        Boolean enabled = call.getBoolean("enabled");
-        if (enabled == null) {
-            call.reject("Missing 'enabled' boolean");
-            return;
-        }
-        TorController.setEnabled(getContext(), enabled);
-        call.resolve();
-    }
-
-    /** Start arti now (live activation). Also persists enabled=true so it
-     *  auto-starts on the next cold launch. */
-    @PluginMethod
-    public void start(PluginCall call) {
-        TorController.setEnabled(getContext(), true);
-        TorController.getInstance().start(getContext());
-        call.resolve();
-    }
-
-    /** Stop arti now (live deactivation) and clear the WebView proxy. Also
-     *  persists enabled=false. */
-    @PluginMethod
-    public void stop(PluginCall call) {
-        TorController.setEnabled(getContext(), false);
-        TorController.getInstance().stop();
-        call.resolve();
-    }
-
-    /** Current connection status (synchronous snapshot). */
-    @PluginMethod
-    public void getStatus(PluginCall call) {
-        TorController controller = TorController.getInstance();
-        JSObject ret = new JSObject();
-        ret.put("enabled", TorController.isEnabled(getContext()));
-        ret.put("status", controller.getStatus());
-        ret.put("bootstrapPercent", controller.getBootstrapPercent());
-        ret.put("error", controller.getError());
-        ret.put("exitIp", controller.getExitIp());
-        call.resolve(ret);
-    }
-
-    /** Re-run the connectivity probe (for a "Retry" action in the gate). */
-    @PluginMethod
-    public void retry(PluginCall call) {
-        TorController.getInstance().retry();
-        call.resolve();
-    }
-}
@@ -1,4 +1,4 @@
-package fund.eranos.app;
+package spot.agora.app;

 import android.app.ForegroundServiceStartNotAllowedException;
 import android.content.Context;
@@ -1,4 +1,4 @@
-package fund.eranos.app;
+package spot.agora.app;

 import android.app.ForegroundServiceStartNotAllowedException;
 import android.content.Context;
@@ -8,12 +8,6 @@ import android.net.Uri;
 import android.os.Build;
 import android.os.Bundle;
 import android.util.Log;
-import android.view.View;
-import android.webkit.WebView;
-
-import androidx.core.graphics.Insets;
-import androidx.core.view.ViewCompat;
-import androidx.core.view.WindowInsetsCompat;

 import com.getcapacitor.BridgeActivity;

@@ -25,14 +19,6 @@ public class MainActivity extends BridgeActivity {
    protected void onCreate(Bundle savedInstanceState) {
        // Register native plugins before super.onCreate.
        registerPlugin(DittoNotificationPlugin.class);
-        registerPlugin(TorPlugin.class);
-
-        // If the user enabled Tor (apply on relaunch), start arti BEFORE
-        // super.onCreate so the WebView SOCKS proxy override is installed
-        // before the WebView issues any network request — no leak window.
-        if (TorController.isEnabled(this)) {
-            TorController.getInstance().start(getApplicationContext());
-        }

        super.onCreate(savedInstanceState);

@@ -61,35 +47,6 @@ public class MainActivity extends BridgeActivity {

        // Handle notification tap deep link
        handleNotificationIntent(getIntent());
-
-        // The Android WebView reports env(safe-area-inset-*) as 0, so inject the
-        // real system-bar insets as CSS variables (--safe-area-inset-top/bottom)
-        // that the web layer consumes (see src/index.css). Without this, the top
-        // nav renders behind the status bar in the APK.
-        applySafeAreaInsets();
-    }
-
-    /**
-     * Read the status-bar (top) and navigation-bar (bottom) insets and write
-     * them into the WebView as CSS pixel variables. Re-applies on every inset
-     * change (rotation, status-bar show/hide, etc.).
-     */
-    private void applySafeAreaInsets() {
-        final WebView webView = getBridge().getWebView();
-        if (webView == null) return;
-
-        ViewCompat.setOnApplyWindowInsetsListener(webView, (v, insets) -> {
-            Insets bars = insets.getInsets(WindowInsetsCompat.Type.systemBars());
-            float density = getResources().getDisplayMetrics().density;
-            int topPx = Math.round(bars.top / density);
-            int bottomPx = Math.round(bars.bottom / density);
-            String js =
-                "document.documentElement.style.setProperty('--safe-area-inset-top','" + topPx + "px');" +
-                "document.documentElement.style.setProperty('--safe-area-inset-bottom','" + bottomPx + "px');";
-            v.post(() -> webView.evaluateJavascript(js, null));
-            return insets;
-        });
-        ViewCompat.requestApplyInsets(webView);
    }

    @Override
@@ -106,7 +63,7 @@ public class MainActivity extends BridgeActivity {
    private void handleNotificationIntent(Intent intent) {
        if (intent == null) return;
        Uri data = intent.getData();
-        if (data != null && "eranos.fund".equals(data.getHost())) {
+        if (data != null && "agora.spot".equals(data.getHost())) {
            String path = data.getPath();
            if (path != null && !path.isEmpty()) {
                // Wait for WebView to be ready, then navigate
@@ -1,4 +1,4 @@
-package fund.eranos.app;
+package spot.agora.app;

 import android.app.NotificationChannel;
 import android.app.NotificationManager;
@@ -337,7 +337,7 @@ public class NostrPoller {
        if (manager == null) return;

        Intent intent = new Intent(context, MainActivity.class);
-        intent.setData(Uri.parse("https://eranos.fund/notifications"));
+        intent.setData(Uri.parse("https://agora.spot/notifications"));
        intent.setFlags(Intent.FLAG_ACTIVITY_SINGLE_TOP | Intent.FLAG_ACTIVITY_CLEAR_TOP);
        PendingIntent pendingIntent = PendingIntent.getActivity(
                context, id, intent,
@@ -1,4 +1,4 @@
-package fund.eranos.app;
+package spot.agora.app;

 import android.app.AlarmManager;
 import android.app.ForegroundServiceStartNotAllowedException;
@@ -83,7 +83,7 @@ public class NotificationRelayService extends Service {
    // + REQ + up to 5 events + EOSE + metadata fetch + disconnect.
    private static final long FETCH_WAKELOCK_TIMEOUT_MS = 30_000;

-    private static final String ACTION_FETCH = "fund.eranos.app.ACTION_FETCH";
+    private static final String ACTION_FETCH = "spot.agora.app.ACTION_FETCH";

    // Backoff bounds for relay connect failures (separate from alarm interval).
    private static final long INITIAL_BACKOFF_MS = 1_000;
@@ -0,0 +1,50 @@
+<vector xmlns:android="http://schemas.android.com/apk/res/android"
+    android:width="108dp"
+    android:height="108dp"
+    android:viewportWidth="100"
+    android:viewportHeight="100">
+
+    <!--
+      Ditto logo from public/logo.svg.
+      SVG viewBox is "-5 -10 100 100", so we shift all paths by (+5, +10)
+      to place the origin at (0,0) for the 100x100 viewport.
+      Then scale to 60% around the content center (50, 40) to fit within
+      Android's adaptive icon safe zone (66% of 108dp).
+    -->
+
+    <group
+        android:translateX="5"
+        android:translateY="10"
+        android:scaleX="0.7"
+        android:scaleY="0.7"
+        android:pivotX="50"
+        android:pivotY="40">
+
+        <!-- path1: bottom arc / bottom-right swash -->
+        <path
+            android:fillColor="#FFFFFF"
+            android:pathData="m 71.719615,49.36907 -0.62891,0.37109 c -0.12891,0.07031 -0.26172,0.14844 -0.39062,0.21875 -3.9883,10.309 -14.008,17.617 -25.699,17.617 -4.1211,0 -8.0312,-0.89844 -11.539,-2.5391 -0.12891,0.03906 -0.26172,0.07031 -0.39063,0.10156 l -0.35156,0.08984 h -0.02734 l -0.25,0.05859 -0.07813,0.01953 -0.10938,0.03125 c -0.55859,0.12891 -1.1289,0.26172 -1.6992,0.39062 -0.10156,0.03125 -0.19922,0.05078 -0.30078,0.07031 l -0.30078,0.10156 -0.18359,0.0078 c -0.26953,0.05859 -1.3086,0.26953 -1.3086,0.26953 -0.28906,0.05859 -0.55859,0.10937 -0.82813,0.17187 4.9805,3.3086 10.961,5.2305 17.371,5.2305 15.059,0 27.699,-10.602 30.828,-24.738 -0.75,0.48828 -1.5195,0.96875 -2.2891,1.4414 -0.59375,0.36328 -1.2031,0.72656 -1.8242,1.0859 z" />
+
+        <!-- path2: small left accent dot/arc -->
+        <path
+            android:fillColor="#FFFFFF"
+            android:pathData="m 30.926615,29.47807 c 0.36328,-0.48828 0.75,-0.95312 1.1523,-1.3828 0.75781,-0.80469 0.71484,-2.0703 -0.08984,-2.8281 -0.80469,-0.75781 -2.0703,-0.71484 -2.8281,0.08984 -0.50781,0.53906 -0.99219,1.125 -1.4492,1.7383 -0.65625,0.88672 -0.47266,2.1406 0.41406,2.7969 0.35938,0.26562 0.77344,0.39453 1.1875,0.39453 0.61719,0 1.2227,-0.27734 1.6133,-0.80859 z" />
+
+        <!-- path3: left vertical bar -->
+        <path
+            android:fillColor="#FFFFFF"
+            android:pathData="m 26.742615,32.67807 c -1.0586,-0.3125 -2.1719,0.29687 -2.4805,1.3594 -0.55859,1.9062 -0.83984,3.9141 -0.83984,5.9609 0,2.3789 0.39062,4.7227 1.1602,6.9609 0.28516,0.82812 1.0625,1.3516 1.8906,1.3516 0.21484,0 0.43359,-0.03516 0.64844,-0.10938 1.043,-0.35938 1.6016,-1.4961 1.2422,-2.543 -0.625,-1.8203 -0.94141,-3.7227 -0.94141,-5.6602 0,-1.668 0.22656,-3.2969 0.67969,-4.8398 0.30859,-1.0586 -0.30078,-2.168 -1.3594,-2.4805 z" />
+
+        <!-- path4: main ring arc -->
+        <path
+            android:fillColor="#FFFFFF"
+            android:pathData="m 14.691615,48.83807 c 0.10156,0.33984 0.19922,0.67969 0.32812,1.0195 0.42969,1.3516 0.94922,2.6484 1.5781,3.9102 0.10156,-0.01172 0.21094,-0.01172 0.32031,-0.01953 l 0.16016,-0.01172 0.80078,-0.07031 c 0.37109,-0.03906 0.67188,-0.07031 0.98047,-0.10156 0.51172,-0.05859 1.0195,-0.12109 1.5586,-0.19922 l 0.21875,-0.03125 c 0.07031,-0.01172 0.14062,-0.01953 0.21094,-0.03125 -1.2188,-2.2109 -2.1484,-4.6016 -2.7305,-7.1211 -0.16016,-0.71094 -0.30078,-1.4297 -0.39844,-2.1602 -0.19922,-1.3086 -0.30078,-2.6602 -0.30078,-4.0312 0,-0.89844 0.03906,-1.7812 0.12891,-2.6484 0.07031,-0.71094 0.16016,-1.4102 0.28906,-2.1016 2.25,-12.949 13.57,-22.828 27.16,-22.828 6.0508,0 11.648,1.9609 16.211,5.3008 0.57031,0.41016 1.1289,0.85938 1.6719,1.3203 1.6914,1.4219 3.2109,3.0703 4.5,4.8789 0.42969,0.60156 0.83984,1.2109 1.2188,1.8398 1.3203,2.1602 2.3398,4.5117 3.0195,7 0.23828,-0.17188 0.42969,-0.30859 0.62891,-0.46875 0.64844,-0.48047 1.2109,-0.92188 1.7383,-1.3398 0.28125,-0.23047 0.5,-0.41016 0.71094,-0.57812 0.10156,-0.07813 0.19141,-0.16016 0.28125,-0.23828 -0.42969,-1.3516 -0.96094,-2.6484 -1.5898,-3.8984 -0.14062,-0.32812 -0.30859,-0.64844 -0.48047,-0.96875 -0.32812,-0.64844 -0.69922,-1.2891 -1.0898,-1.9102 -1.6797,-2.7109 -3.7695,-5.1406 -6.1719,-7.2188 -0.57031,-0.48828 -1.1484,-0.96875 -1.7617,-1.4102 -0.55859,-0.42188 -1.1406,-0.82812 -1.7305,-1.2109 -4.9414,-3.2188 -10.852,-5.0898 -17.16,-5.0898 -14.961,0 -27.531,10.469 -30.75,24.469 -0.17188,0.67969 -0.30859,1.3711 -0.42188,2.0703 -0.12891,0.73828 -0.21875,1.5 -0.28906,2.2617 -0.07813,0.91016 -0.12109,1.8398 -0.12109,2.7812 0,2.3008 0.25,4.5508 0.71875,6.7109 0.17188,0.71484 0.35156,1.4258 0.5625,2.125 z" />
+
+        <!-- path5: top-right swash / outer arc with tail -->
+        <path
+            android:fillColor="#FFFFFF"
+            android:pathData="m 90.441615,21.60007 c -2.1797,-5.3398 -9.4102,-7.3984 -21,-6.0391 1.8906,1.8906 3.5391,3.9688 4.9297,6.2109 0.28906,0.46094 0.55859,0.92187 0.80859,1.3789 5.5391,-0.12109 7.6094,1.0391 7.8398,1.4492 0.12891,0.46875 -0.55078,2.7305 -4.5898,6.4805 -0.01953,0.01953 -0.03125,0.03125 -0.03906,0.03906 -0.26172,0.23828 -0.51953,0.48047 -0.80078,0.71875 -0.19922,0.17969 -0.41016,0.35938 -0.62891,0.53906 -0.10938,0.10156 -0.21875,0.19141 -0.33984,0.28906 -0.23828,0.19922 -0.5,0.41016 -0.76172,0.62109 -0.12891,0.10156 -0.26172,0.21094 -0.39844,0.32031 -0.42969,0.33984 -0.89063,0.69141 -1.3711,1.0508 -0.26953,0.21094 -0.53906,0.41016 -0.82812,0.60938 -0.32031,0.23047 -0.64062,0.46875 -0.98047,0.69922 0,0.01172 -0.01172,0.01172 -0.01172,0.01172 -0.26953,0.19141 -0.55078,0.37891 -0.82812,0.57031 -0.28125,0.19141 -0.55859,0.37109 -0.85156,0.55859 -0.25,0.16016 -0.5,0.32812 -0.76172,0.48828 -6,3.8984 -13.48,7.7188 -21.379,10.922 -8.0117,3.2383 -15.871,5.6602 -22.93,7.0391 -0.30078,0.05859 -0.60156,0.12109 -0.89062,0.17188 -0.60938,0.12109 -1.2188,0.21875 -1.8203,0.32031 -0.07031,0.01172 -0.12891,0.01953 -0.19922,0.03125 h -0.01953 c -0.28906,0.05078 -0.57031,0.08984 -0.83984,0.12891 -0.30859,0.05078 -0.60938,0.08984 -0.91016,0.12891 -0.57031,0.07813 -1.1094,0.14844 -1.6406,0.21094 -0.35156,0.03906 -0.69141,0.07031 -1.0195,0.10156 -0.30078,0.03125 -0.58984,0.05078 -0.87891,0.07813 -0.48047,0.03125 -0.92969,0.05859 -1.3711,0.07813 -0.39844,0.01953 -0.78125,0.03125 -1.1484,0.03906 -5.5116996,0.10938 -7.5702996,-1.0391 -7.8007996,-1.4492 -0.12891,-0.48047 0.55078,-2.7383 4.6093996,-6.5 -0.12891,-0.48828 -0.26172,-1 -0.37891,-1.5391 -0.51953,-2.4219 -0.78906,-4.8906 -0.78906,-7.3594 0,-0.17969 0,-0.37109 0.01172,-0.55078 -9.2733996,7.082 -13.0229996,13.59 -10.8749996,18.949 1.7383,4.2695 6.7188,6.4492 14.5899996,6.4492 2.8594,0 6.1016,-0.28906 9.7109,-0.87109 0.17188,-0.03125 0.33984,-0.05859 0.51953,-0.08984 0.17188,-0.03125 0.35156,-0.05859 0.51953,-0.08984 l 1.2188,-0.21875 c 0.57031,-0.10156 1.1484,-0.21875 1.7305,-0.33984 0.53125,-0.10938 1.0508,-0.21094 1.5781,-0.32812 0.01172,0 0.03125,-0.01172 0.03906,-0.01172 0.05078,-0.01172 0.08984,-0.01953 0.14062,-0.03125 0.07031,-0.01172 0.12891,-0.03125 0.19922,-0.05078 0.57812,-0.12891 1.1602,-0.26172 1.7383,-0.39844 0.05078,-0.01172 0.10156,-0.03125 0.14844,-0.03906 0.21094,-0.05078 0.42188,-0.10156 0.64062,-0.14844 h 0.01172 c 6.0898,-1.5117 12.559,-3.6406 19.102,-6.2891 6.5508,-2.6602 12.68,-5.6289 18.109,-8.7812 0.21875,-0.12891 0.44141,-0.26172 0.66016,-0.39062 0.58984,-0.33984 1.1797,-0.69141 1.7617,-1.0508 1.5703,-0.96094 3.0586,-1.9297 4.4805,-2.9102 0.12891,-0.08984 0.26172,-0.17969 0.39062,-0.26953 11.242,-7.8477 15.941,-15.09 13.594,-20.938 z" />
+
+    </group>
+
+</vector>
@@ -1,4 +1,4 @@
 <?xml version="1.0" encoding="utf-8"?>
 <resources>
-    <color name="ic_launcher_background">#e9673f</color>
+    <color name="ic_launcher_background">#ff6600</color>
 </resources>
@@ -1,7 +1,7 @@
 <?xml version='1.0' encoding='utf-8'?>
 <resources>
-    <string name="app_name">Eranos</string>
-    <string name="title_activity_main">Eranos</string>
-    <string name="package_name">fund.eranos.app</string>
-    <string name="custom_url_scheme">fund.eranos.app</string>
+    <string name="app_name">Agora</string>
+    <string name="title_activity_main">Agora</string>
+    <string name="package_name">spot.agora.app</string>
+    <string name="custom_url_scheme">spot.agora.app</string>
 </resources>
@@ -21,18 +21,6 @@ allprojects {
    repositories {
        google()
        mavenCentral()
-        // Guardian Project's experimental Maven repo, hosting the prebuilt
-        // org.torproject:arti-mobile AAR (Tor in Rust) used for the optional Tor mode.
-        //
-        // Pinned to an immutable commit SHA rather than the mutable `master`
-        // branch: this artifact ships a native library with network-proxy
-        // privileges, so we don't want a force-push or new commit to gpmaven
-        // silently changing what we resolve. To bump arti, update both the
-        // commit below and the checksum pin in `app/build.gradle`, and re-verify
-        // the SHA-256 against a fresh download.
-        //
-        // Commit: guardianproject/gpmaven@b3ee2a63eec4ce37ea22fcc6b1ff009f406f2b13
-        maven { url "https://raw.githubusercontent.com/guardianproject/gpmaven/b3ee2a63eec4ce37ea22fcc6b1ff009f406f2b13" }
    }
 }

@@ -1,5 +1,5 @@
 ext {
-    minSdkVersion = 26
+    minSdkVersion = 24
    compileSdkVersion = 36
    targetSdkVersion = 36
    androidxActivityVersion = '1.11.0'
@@ -1,8 +1,8 @@
 import type { CapacitorConfig } from '@capacitor/cli';

 const config: CapacitorConfig = {
-  appId: 'fund.eranos.app',
-  appName: 'Eranos',
+  appId: 'spot.agora.app',
+  appName: 'Agora',
  webDir: 'dist',
  server: {
    androidScheme: 'https',
@@ -16,7 +16,14 @@ const config: CapacitorConfig = {
  ios: {
    backgroundColor: '#14161f',
    contentInset: 'never',
-    scheme: 'Eranos'
+    scheme: 'Agora'
+  },
+  plugins: {
+    SystemBars: {
+      // Inject --safe-area-inset-* CSS variables on Android to work around
+      // a Chromium bug (<140) where env(safe-area-inset-*) reports 0.
+      insetsHandling: 'css',
+    },
  },
 };

@@ -10,7 +10,7 @@ services:
    depends_on:
      - vite
    networks:
-      - eranos-network
+      - agora-network

  vite:
    image: node:22-alpine
@@ -22,9 +22,9 @@ services:
    environment:
      - NODE_ENV=development
    networks:
-      - eranos-network
+      - agora-network
    restart: unless-stopped

 networks:
-  eranos-network:
+  agora-network:
    driver: bridge
@@ -1,35 +1,35 @@
 <!DOCTYPE html>
 <html lang="en" class="dark">
  <head>
-    <title>Eranos — Power to the people.</title>
+    <title>Agora — Power to the people.</title>
    <meta charset="UTF-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1.0, viewport-fit=cover, interactive-widget=resizes-content" />
-    <meta name="description" content="Eranos — a peer-to-peer crowdfunding app on Nostr. Fund campaigns directly with Grin, no middlemen." />
+    <meta name="description" content="Agora — a Nostr social client for communities, creativity, and ownership." />

    <!-- Open Graph -->
-    <meta property="og:title" content="Eranos" />
+    <meta property="og:title" content="Agora" />
    <meta property="og:description" content="Power to the people." />
-    <meta property="og:image" content="https://eranos.fund/og-image.jpg" />
+    <meta property="og:image" content="https://agora.spot/og-image.jpg" />
    <meta property="og:image:width" content="1200" />
    <meta property="og:image:height" content="630" />
    <meta property="og:image:type" content="image/jpeg" />
    <meta property="og:type" content="website" />
-    <meta property="og:url" content="https://eranos.fund" />
-    <meta property="og:site_name" content="Eranos" />
+    <meta property="og:url" content="https://agora.spot" />
+    <meta property="og:site_name" content="Agora" />

    <!-- Twitter / X -->
    <meta name="twitter:card" content="summary_large_image" />
-    <meta name="twitter:title" content="Eranos" />
+    <meta name="twitter:title" content="Agora" />
    <meta name="twitter:description" content="Power to the people." />
-    <meta name="twitter:image" content="https://eranos.fund/og-image.jpg" />
+    <meta name="twitter:image" content="https://agora.spot/og-image.jpg" />

-    <meta http-equiv="content-security-policy" content="default-src 'none'; script-src 'self' 'wasm-unsafe-eval'; worker-src 'self' blob:; child-src 'self' blob:; style-src 'self' 'unsafe-inline'; frame-src 'self' https:; font-src 'self' https:; base-uri 'self'; manifest-src 'self'; connect-src 'self' blob: https: wss:; img-src 'self' data: blob: https:; media-src 'self' blob: https:">
+    <meta http-equiv="content-security-policy" content="default-src 'none'; script-src 'self' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; frame-src 'self' https:; font-src 'self' https:; base-uri 'self'; manifest-src 'self'; connect-src 'self' blob: https: wss:; img-src 'self' data: blob: https:; media-src 'self' blob: https:">
    <link rel="icon" type="image/x-icon" href="/favicon.ico">
    <link rel="icon" type="image/png" sizes="16x16" href="/favicon-16.png">
    <link rel="icon" type="image/png" sizes="32x32" href="/favicon-32.png">
    <link rel="apple-touch-icon" sizes="180x180" href="/apple-touch-icon.png">
    <meta name="theme-color" content="#0a0c14" media="(prefers-color-scheme: dark)">
-    <meta name="theme-color" content="#faa805" media="(prefers-color-scheme: light)">
+    <meta name="theme-color" content="#ff6600" media="(prefers-color-scheme: light)">
    <link rel="manifest" href="/manifest.webmanifest">
    <style>@keyframes agora-spin{to{transform:rotate(360deg)}}</style>
  </head>
@@ -323,9 +323,9 @@
 					"$(inherited)",
 					"@executable_path/Frameworks",
 				);
-				MARKETING_VERSION = 2.9.1;
+				MARKETING_VERSION = 2.14.4;
 				OTHER_SWIFT_FLAGS = "$(inherited) \"-D\" \"COCOAPODS\" \"-DDEBUG\"";
-				PRODUCT_BUNDLE_IDENTIFIER = fund.eranos.app;
+				PRODUCT_BUNDLE_IDENTIFIER = spot.agora.app;
 				PRODUCT_NAME = "$(TARGET_NAME)";
 				SWIFT_ACTIVE_COMPILATION_CONDITIONS = DEBUG;
 				SWIFT_VERSION = 5.0;
@@ -347,8 +347,8 @@
 					"$(inherited)",
 					"@executable_path/Frameworks",
 				);
-				MARKETING_VERSION = 2.9.1;
-				PRODUCT_BUNDLE_IDENTIFIER = fund.eranos.app;
+				MARKETING_VERSION = 2.8.0;
+				PRODUCT_BUNDLE_IDENTIFIER = spot.agora.app;
 				PRODUCT_NAME = "$(TARGET_NAME)";
 				SWIFT_ACTIVE_COMPILATION_CONDITIONS = "";
 				SWIFT_VERSION = 5.0;
@@ -4,8 +4,8 @@
 <dict>
 	<key>com.apple.developer.associated-domains</key>
 	<array>
-		<string>webcredentials:eranos.fund</string>
-		<string>webcredentials:eranos.fund?mode=developer</string>
+		<string>webcredentials:agora.spot</string>
+		<string>webcredentials:agora.spot?mode=developer</string>
 	</array>
 </dict>
 </plist>
@@ -33,7 +33,7 @@ public class DittoNotificationPlugin: CAPPlugin, CAPBridgedPlugin {

    // MARK: - Constants

-    static let bgTaskIdentifier = "fund.eranos.app.notification-refresh"
+    static let bgTaskIdentifier = "spot.agora.app.notification-refresh"
    private static let prefsKey = "ditto_notification_config"

    // MARK: - Plugin Methods
@@ -7,7 +7,7 @@
 	<key>CFBundleDevelopmentRegion</key>
 	<string>en</string>
 	<key>CFBundleDisplayName</key>
-        <string>Eranos</string>
+        <string>Agora</string>
 	<key>CFBundleExecutable</key>
 	<string>$(EXECUTABLE_NAME)</string>
 	<key>CFBundleIdentifier</key>
@@ -48,11 +48,11 @@
 	<key>UIViewControllerBasedStatusBarAppearance</key>
 	<true/>
 	<key>NSPhotoLibraryUsageDescription</key>
-	<string>Eranos needs access to your photo library to upload images to your posts and profile.</string>
+	<string>Agora needs access to your photo library to upload images to your posts and profile.</string>
 	<key>NSCameraUsageDescription</key>
-	<string>Eranos needs camera access to take photos and videos for your posts, and to scan QR codes.</string>
+	<string>Agora needs camera access to take photos and videos for your posts.</string>
 	<key>NSMicrophoneUsageDescription</key>
-	<string>Eranos needs access to your microphone to record voice messages.</string>
+	<string>Agora needs access to your microphone to record voice messages.</string>
 	<key>ITSAppUsesNonExemptEncryption</key>
 	<false/>
 	<key>UIBackgroundModes</key>
@@ -61,7 +61,7 @@
 	</array>
 	<key>BGTaskSchedulerPermittedIdentifiers</key>
 	<array>
-		<string>fund.eranos.app.notification-refresh</string>
+		<string>spot.agora.app.notification-refresh</string>
 	</array>
 </dict>
 </plist>
@@ -1,2 +1,2 @@
-app_identifier("fund.eranos.app")
+app_identifier("spot.agora.app")
 team_id("GZLTTH5DLM")
@@ -3,7 +3,7 @@ default_platform(:ios)
 platform :ios do
  # ─── Lanes ────────────────────────────────────────────────────────────

-  desc "Build and sign the App Store IPA. Output at ../artifacts/Eranos.ipa."
+  desc "Build and sign the App Store IPA. Output at ../artifacts/Agora.ipa."
  lane :build_ipa do
    setup_lane_signing!
    build_release_ipa!
@@ -19,7 +19,7 @@ platform :ios do
    submit_release_for_review!(ipa_path)
  end

-  desc "Build, sign, and submit Eranos to the App Store for review (single-step convenience)."
+  desc "Build, sign, and submit Agora to the App Store for review (single-step convenience)."
  lane :release do
    setup_lane_signing!
    build_release_ipa!
@@ -83,7 +83,7 @@ platform :ios do
      configuration: "Release",
      export_method: "app-store",
      output_directory: "../artifacts",
-      output_name: "Eranos.ipa",
+      output_name: "Agora.ipa",
      clean: true,
      # Override the Xcode project's Automatic signing for this build only.
      # Match has already installed the AppStore cert + profile into the
@@ -93,7 +93,7 @@ platform :ios do
      xcargs: [
        "CODE_SIGN_STYLE=Manual",
        "CODE_SIGN_IDENTITY='Apple Distribution'",
-        "PROVISIONING_PROFILE_SPECIFIER='match AppStore fund.eranos.app'",
+        "PROVISIONING_PROFILE_SPECIFIER='match AppStore spot.agora.app'",
        "DEVELOPMENT_TEAM=GZLTTH5DLM",
      ].join(" "),
      export_options: {
@@ -101,7 +101,7 @@ platform :ios do
        signingStyle: "manual",
        teamID: "GZLTTH5DLM",
        provisioningProfiles: {
-          "fund.eranos.app" => "match AppStore fund.eranos.app",
+          "spot.agora.app" => "match AppStore spot.agora.app",
        },
      },
    )
@@ -1,5 +1,5 @@
 git_url("https://gitlab.com/soapbox-pub/certificates.git")
 storage_mode("git")
 type("appstore")
-app_identifier(["fund.eranos.app"])
+app_identifier(["spot.agora.app"])
 team_id("GZLTTH5DLM")
@@ -1,7 +1,7 @@
 {
-  "name": "eranos",
+  "name": "agora",
  "private": true,
-  "version": "2.9.1",
+  "version": "2.8.0",
  "type": "module",
  "scripts": {
    "dev": "npm i --silent && vite",
@@ -15,6 +15,7 @@
    "node": ">=22"
  },
  "dependencies": {
+    "@breeztech/breez-sdk-spark": "^0.10.0",
    "@capacitor/app": "^8.0.0",
    "@capacitor/barcode-scanner": "^3.0.2",
    "@capacitor/core": "^8.1.0",
@@ -29,20 +30,34 @@
    "@dnd-kit/utilities": "^3.2.2",
    "@emoji-mart/data": "^1.2.1",
    "@emoji-mart/react": "^1.1.1",
+    "@fontsource-variable/comfortaa": "^5.2.8",
+    "@fontsource-variable/dm-sans": "^5.2.8",
    "@fontsource-variable/fredoka": "^5.2.10",
    "@fontsource-variable/inter": "^5.2.6",
+    "@fontsource-variable/jetbrains-mono": "^5.2.8",
+    "@fontsource-variable/lora": "^5.2.8",
+    "@fontsource-variable/merriweather": "^5.2.6",
+    "@fontsource-variable/montserrat": "^5.2.8",
    "@fontsource-variable/nunito": "^5.2.7",
+    "@fontsource-variable/outfit": "^5.2.8",
    "@fontsource-variable/playfair-display": "^5.2.8",
    "@fontsource/bebas-neue": "^5.2.7",
+    "@fontsource/bungee-shade": "^5.2.7",
    "@fontsource/caveat": "^5.2.8",
+    "@fontsource/cherry-bomb-one": "^5.2.7",
+    "@fontsource/comic-neue": "^5.2.7",
+    "@fontsource/comic-relief": "^5.2.2",
+    "@fontsource/courier-prime": "^5.2.8",
    "@fontsource/creepster": "^5.2.7",
+    "@fontsource/luckiest-guy": "^5.2.8",
    "@fontsource/noto-sans-nushu": "^5.2.6",
-    "@fontsource/noto-sans-tc": "^5.2.9",
    "@fontsource/pacifico": "^5.2.7",
    "@fontsource/permanent-marker": "^5.2.7",
    "@fontsource/pirata-one": "^5.2.8",
+    "@fontsource/press-start-2p": "^5.2.7",
    "@fontsource/silkscreen": "^5.2.8",
    "@fontsource/special-elite": "^5.2.8",
+    "@getalby/sdk": "^5.1.1",
    "@hookform/resolvers": "^5.2.2",
    "@milkdown/core": "^7.20.0",
    "@milkdown/ctx": "^7.20.0",
@@ -55,22 +70,25 @@
    "@milkdown/prose": "^7.20.0",
    "@milkdown/react": "^7.20.0",
    "@milkdown/utils": "^7.20.0",
-    "@noble/curves": "^1.2.0",
+    "@noble/curves": "^2.2.0",
    "@noble/hashes": "^1.8.0",
-    "@scure/base": "^1.1.1",
-    "@nostrify/nostrify": "^0.53.0",
-    "@nostrify/react": "^0.6.3",
+    "@nostrify/nostrify": "^0.52.0",
+    "@nostrify/react": "^0.6.0",
    "@nostrify/types": "^0.37.0",
    "@plausible-analytics/tracker": "^0.4.4",
    "@radix-ui/react-accordion": "^1.2.0",
    "@radix-ui/react-alert-dialog": "^1.1.1",
+    "@radix-ui/react-aspect-ratio": "^1.1.0",
    "@radix-ui/react-avatar": "^1.1.0",
    "@radix-ui/react-checkbox": "^1.1.1",
    "@radix-ui/react-collapsible": "^1.1.0",
+    "@radix-ui/react-context-menu": "^2.2.16",
    "@radix-ui/react-dialog": "^1.1.2",
    "@radix-ui/react-dropdown-menu": "^2.1.16",
    "@radix-ui/react-hover-card": "^1.1.15",
    "@radix-ui/react-label": "^2.1.0",
+    "@radix-ui/react-menubar": "^1.1.16",
+    "@radix-ui/react-navigation-menu": "^1.2.14",
    "@radix-ui/react-popover": "^1.1.15",
    "@radix-ui/react-progress": "^1.1.0",
    "@radix-ui/react-radio-group": "^1.2.0",
@@ -85,8 +103,13 @@
    "@radix-ui/react-toggle": "^1.1.0",
    "@radix-ui/react-toggle-group": "^1.1.0",
    "@radix-ui/react-tooltip": "^1.2.8",
+    "@scure/base": "^1.1.1",
+    "@scure/bip32": "^2.2.0",
+    "@scure/bip39": "^1.6.0",
+    "@scure/btc-signer": "^2.2.0",
    "@sentry/react": "^10.42.0",
    "@tanstack/react-query": "^5.56.2",
+    "@types/d3-geo": "^3.1.0",
    "@unhead/addons": "^2.1.13",
    "@unhead/react": "^2.1.13",
    "blurhash": "^2.0.5",
@@ -95,33 +118,43 @@
    "clsx": "^2.1.1",
    "cmdk": "^1.0.0",
    "d3-celestial": "^0.7.35",
+    "d3-geo": "^3.1.1",
    "d3-scale": "^4.0.2",
    "date-fns": "^3.6.0",
    "dompurify": "^3.3.3",
    "embla-carousel-react": "^8.3.0",
    "emoji-mart": "^5.6.0",
+    "fflate": "^0.8.2",
    "hls.js": "^1.6.15",
+    "html-to-image": "^1.11.13",
    "i18next": "^26.0.5",
    "i18next-browser-languagedetector": "^8.2.1",
    "idb": "^8.0.3",
+    "input-otp": "^1.2.4",
+    "iso-3166": "^4.4.0",
+    "leaflet": "^1.9.4",
    "lucide-react": "^1.8.0",
    "nostr-tools": "^2.13.0",
-    "qr-scanner": "^1.4.2",
    "qrcode": "^1.5.4",
    "react": "^19.2.4",
    "react-blurhash": "^0.3.0",
+    "react-day-picker": "^9.14.0",
    "react-dom": "^19.2.4",
    "react-easy-crop": "^5.5.6",
    "react-hook-form": "^7.71.1",
    "react-i18next": "^17.0.4",
    "react-intersection-observer": "^9.16.0",
+    "react-leaflet": "^4.2.1",
    "react-markdown": "^10.1.0",
+    "react-resizable-panels": "^2.1.3",
    "react-router-dom": "^6.26.2",
    "recharts": "^2.12.7",
    "rehype-sanitize": "^6.0.0",
    "slugify": "^1.6.8",
+    "smol-toml": "^1.6.0",
    "tailwind-merge": "^2.5.2",
    "tailwindcss-animate": "^1.0.7",
+    "topojson-client": "^3.1.0",
    "uri-templates": "^0.2.0",
    "vaul": "^1.1.2",
    "zod": "^4.3.6"
@@ -139,17 +172,21 @@
    "@testing-library/react": "^16.3.2",
    "@types/d3-scale": "^4.0.9",
    "@types/dompurify": "^3.0.5",
+    "@types/leaflet": "^1.9.21",
    "@types/node": "^22.5.5",
    "@types/qrcode": "^1.5.5",
    "@types/react": "^19.2.14",
    "@types/react-dom": "^19.2.3",
+    "@types/topojson-client": "^3.1.5",
+    "@types/topojson-specification": "^1.0.5",
    "@vitejs/plugin-react": "^6.0.1",
+    "@webbtc/webln-types": "^3.0.0",
+    "@webxdc/types": "^2.1.2",
    "autoprefixer": "^10.4.20",
    "eslint": "^9.9.0",
    "eslint-plugin-react-hooks": "^5.1.0-rc.0",
    "eslint-plugin-react-refresh": "^0.4.9",
    "globals": "^15.9.0",
-    "iso-3166": "^4.4.0",
    "jsdom": "^26.1.0",
    "postcss": "^8.4.47",
    "rollup-plugin-visualizer": "^7.0.1",
@@ -157,7 +194,7 @@
    "typescript": "^5.5.3",
    "typescript-eslint": "^8.0.1",
    "vite": "^8.0.3",
-    "vitest": "^4.1.8"
+    "vitest": "^3.1.4"
  },
  "overrides": {
    "react": "$react",
@@ -1,125 +1,5 @@
 # Changelog

-## [2.9.1] - 2026-06-27
-
-The Venezuela earthquake relief appeal now rallies behind every campaign on the ground, not just one. The home banner and relief page showcase a live, swipeable carousel of all Venezuelan relief efforts, with a running total of everything raised so far — so you can pick exactly who to help.
-
-### Changed
-
- The Venezuela relief appeal now showcases every Venezuelan relief campaign in a live, auto-scrolling carousel you can swipe through, with a combined raised total across all of them, instead of featuring a single campaign.
-
-## [2.9.0] - 2026-06-25
-
-A big one. Private messaging arrives with a fast, searchable inbox you can reply to in your own language. Campaign organizers can now get verified by trusted reviewers through a guided sign-up, and verified badges appear right on campaigns. There's a new Venezuela earthquake relief appeal that takes you straight to donations, plus optional Tor routing on Android, separate Public and Private wallets, faster donation scanning, and refreshed profiles, settings, and login.
-
-### Added
-
- Private direct messages: a dedicated inbox you can search by name, start new chats with inline recipient lookup, page back through old conversations, and read incoming messages translated into your language.
- Get verified: a guided sign-up for trusted reviewers to set up a verifier profile, publish a public "how we verify" statement, and vouch for campaigns. Verified badges now show on campaign pages, and a short tutorial walks you through it.
- A Venezuela earthquake relief appeal — a home-page banner, a one-time popup, and a shareable page that bakes in the relief campaign so you can read its story and donate without leaving.
- Optional Tor routing on Android for added privacy.
- Separate Public and Private wallets, keeping your spending and your private silent-payment funds cleanly apart.
- A "Don't have Bitcoin?" prompt on campaign pages that points first-time donors to Cash App.
- An always-visible language switcher in the top navigation, and a corporate sponsorship page.
-
-### Changed
-
- Redesigned profiles with cleaner stats, a merged campaigns view, and a themed raised total.
- Redesigned Settings into an Apple-style grouped layout.
- Reworked the login and onboarding flow, including a new welcome screen built around the Agora brand.
- Silent-payment donations now scan faster and keep working in the background, with a progress bar on the private wallet.
- The home page now shows every featured campaign instead of capping the list.
-
-### Fixed
-
- The audio, music, and podcast pages no longer crash.
- Backfilled and corrected translations across all sixteen languages.
-
-## [2.8.9] - 2026-06-02
-
-Adds an in-app prompt to grab the Android app from Zapstore, makes it easier to start or explore campaigns right from the home page, and irons out a batch of language and display fixes.
-
-### Added
-
- A prompt to download the Android app from Zapstore, shown to mobile web visitors on the home page, in the account menu, and in the slide-out menu.
- A "Start a campaign" button alongside "Browse all" in the middle of the home page.
-
-### Changed
-
- The "Explore campaigns" button now appears for everyone, not just logged-out visitors.
-
-### Fixed
-
- Switching languages now takes effect immediately instead of showing stale text.
- The reply box and the replies heading on a post now show up in your chosen language.
- Account balances keep their Latin numerals regardless of display language.
- Filled in missing translations on the "Why Agora" screen.
-
-## [2.8.8] - 2026-06-02
-
-Fixes the app icon proportions and updates the loading splash to the Agora bolt.
-
-### Fixed
-
- App icon no longer appears squashed.
- Loading splash now shows the Agora bolt instead of the old logo.
-
-## [2.8.7] - 2026-06-02
-
-Fixes the top navigation bar rendering behind the status bar on Android.
-
-### Fixed
-
- Top navigation bar now clears the system status bar on Android.
-
-## [2.8.6] - 2026-06-02
-
-Refreshes the app icon to the orange Agora bolt mark across Android, iOS, and the web.
-
-### Changed
-
- Update the app icon to the current Agora bolt on a brand-orange background.
-
-## [2.8.5] - 2026-06-02
-
-A maintenance release that fixes the Android build so signed releases publish correctly. No user-facing changes.
-
-## [2.8.4] - 2026-06-02
-
-A maintenance release that fixes the Android build so signed releases publish correctly. No user-facing changes.
-
-## [2.8.3] - 2026-06-02
-
-A maintenance release that fixes the Android build so signed releases publish correctly. No user-facing changes.
-
-## [2.8.2] - 2026-06-02
-
-A maintenance release that fixes the Android build pipeline so signed releases publish correctly. No user-facing changes.
-
-## [2.8.1] - 2026-06-02
-
-Agora becomes a home for putting your money where your heart is. Launch and back fundraising campaigns, rally around organizations with their own events and pledges, and send support straight from a built-in Bitcoin and Lightning wallet. Explore the world through immersive country pages, chat with a new AI agent, and move through a faster, cleaner app with a fresh look throughout.
-
-### Added
-
- Fundraising campaigns as the new home surface — create, edit, and back campaigns, set goals, add beneficiaries, and follow progress.
- Organizations with their own events, pledges, members, and moderation tools.
- Built-in wallet for sending Bitcoin and Lightning payments, with transaction history and balances shown in USD.
- One-tap support: zap posts, profiles, campaigns, and organizations.
- AI agent chat with a model selector, tool-calling, and slash commands.
- Immersive country pages with anthems, flags, weather, and a country-scoped feed, plus a new Discover square for exploring the world.
- Comments and reactions on campaigns, and donation receipts shown inline.
-
-### Changed
-
- Refreshed Agora branding, navigation, and app icons throughout.
- Streamlined onboarding with country and people follows.
- Polished campaign, organization, and donation flows end to end.
-
-### Removed
-
- Direct messaging and ephemeral geo chat.
-
 ## [1.0.0] - 2026-04-30

 ### Added
--- a/Show More
+++ b/Show More
Author	SHA1	Message	Date
sam	53828741e1	Merge branch 'main' into cooking/planetora	2026-05-23 11:21:31 +07:00
sam	4cd2aadba2	Lift the Planetora event panel off the background The panel was bg-background/40 + backdrop-blur — a fogged version of the same hue as the warm dawn-toned page background, which on mobile made the bottom sheet visually merge with the globe area underneath. Now: - Surface fill bumped to bg-background/85 so the panel reads as a distinct surface instead of a tinted overlay (backdrop-blur is retained so a hint of the globe still glows through). - Border tightened to border-border/70 plus a hairline foreground ring to crisp the edge against any backdrop colour. - Mobile sheet gets an explicit two-direction shadow (top + bottom) rather than shadow-2xl, which only casts downward — for a sheet pinned to the bottom of the viewport that downward cast falls off screen and leaves no visible separation. The new top-edge shadow is what actually lifts the sheet off the globe. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 19:58:41 +07:00
sam	e57a3029f5	Track event latitude when focusing the camera The selected event eased toward lng=0 (centre of the visible hemisphere) but latitude stayed pinned at the resting tilt (VIEW_TILT_DEG = 20°). For events near the equator that pushed the marker well below the disc's centre — and on mobile, where the bottom sheet sits over the lower half of the screen, the focused location ended up partly behind the panel (e.g. a Venezuelan post sitting at ~8°N landed roughly 50 px below the globe's centre, right in the panel's overlap zone). Now both rotLng and rotLat ease toward the selected event's coords so the focal point lands at the centre of the disc, well clear of the mobile panel. With nothing selected the camera settles back to VIEW_TILT_DEG. The existing depth-based fading uses the same eased latitude so rings and the selected dot continue to fade correctly as the globe tumbles. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 19:56:20 +07:00
sam	7590af5a76	Drop the orphaned WebGL Planetora globe and its react-globe.gl dep PlanetoraGlobe.tsx hadn't been rendered since the SVG renderer landed — only its PlanetoraTheme type was still referenced. Move the type into PlanetoraSvgGlobe.tsx (next to the only renderer that consumes it), delete the legacy file, and trim WARM_THEME of the WebGL-only fields (countrySideFill, atmosphereColor, background) along with their now defunct comments. react-globe.gl (which pulled in three.js, ~280 kB gzip) drops out entirely — `npm uninstall react-globe.gl` cleans node_modules and the shipped bundle. Stale doc-comment references to PlanetoraGlobe in the playback / auto-pilot hooks are pointed at PlanetoraSvgGlobe. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 19:53:17 +07:00
sam	605e7f599f	Shift the Planetora globe up (not down) when the mobile panel opens When the bottom-sheet event panel was opened on mobile, the SVG canvas was extended off the bottom of the viewport — which centres the globe lower in screen space, sliding it down behind the panel. Flip the extension to the top edge instead so the globe centres in the panel-free band above the sheet, the way it does on desktop with the right-side panel. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 19:36:51 +07:00
sam	f5bc774aba	Hide the Planetora bottom HUD on mobile while an event panel is open The bottom-sheet event panel and the timeline / live-stat HUD both anchor to the bottom of the viewport on mobile, so they fight for the same pixels — the panel covers the HUD and the page reads as cluttered. Add a hideBottomHud flag and toggle it on whenever the mobile event panel is up; the HUD fades out so the panel is the unambiguous focus, and fades back in when the panel closes. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 19:16:58 +07:00
sam	3b125592d1	Layer the homepage's atmospheric backdrop behind Planetora Tracking bg-background was correct for theme awareness but left the page flat — solid cream in light mode, solid black in dark mode — which read as nothing like the homepage's hero. Layer in the same recipe: a warm/cool primary→secondary gradient wash, a directional dawn-gold scrim from the upper-left, a big radial sunrise glow brightened with mix-blend-screen, a thin top-edge sliver of sunrise light, and the homepage's fractal-noise film grain. Adds peach corners + a soft warm glow in light mode and a deep warm atmosphere around the globe in dark mode, matching the hero section's vibe without copying its content. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 15:38:02 +07:00
sam	e318ca0550	Have Planetora's page background follow the app's light/dark theme Pinning Planetora to a fixed dawn-sky gradient broke the visual contract with the rest of the app — the homepage tracks bg-background (cream in light mode, near-black in dark mode) and the warm globe already pops in either, so there's no reason for Planetora to pick its own background. The page now uses bg-background like everything else; the warm sphere palette stays fixed. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 15:31:28 +07:00
sam	af36a9c7d5	Lighten the Planetora page background to a dawn sky gradient Even with the warm globe palette in place, sitting it on a near-black slab still made the page feel heavy. Swap the solid dusk navy for a pale dawn sky — powder blue overhead easing into peach-cream near the horizon — so the cream globe sits in light instead of a void, and the honey-shaded limb naturally blends into the warmer lower band. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 15:27:53 +07:00
sam	d7729b705e	Recolour Planetora globe with the homepage's warm dawn palette A dark globe with bright orange splashes was reading as a surveillance / situation-room dashboard rather than a friendly community-activity visualiser. Planetora now uses the same warm "dawn earth" tones as the homepage HeroGlobe — a cream→honey radial sphere, sandy-amber inactive countries, terracotta active countries, cream pulse rings, and a soft dusk-navy page background — regardless of the surrounding app's light/dark mode. Adds three sphere-shading fields (sphereCentre / sphereMid / sphereEdge) to the shared PlanetoraTheme so the SVG renderer can paint a real lit sphere instead of stacking opacities of the page background. Drops the now-unused light/dark CSS-variable observer in the page (the palette is fixed) along with its hsl() helper. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 15:23:41 +07:00
sam	e04342668b	Add a continuous ping animation to the selected event marker The selected marker was just a static halo ring around a dot, which made the focused event read as a flat target. Two phase-offset pulse rings now expand outwards continuously while the marker is shown, matching the visual language of the per-event rings so a focused event still feels alive. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 15:16:08 +07:00
sam	80b56b3318	Render Planetora countries with d3-geo orthographic projection Drops the hand-rolled projection / hemisphere clipper for d3-geo's geoOrthographic + geoPath. The previous implementation cut a straight chord across the back of the disc when a polygon (Russia, Greenland, Antarctica…) crossed from front to back to front, leaving abrupt flat edges along the limb. d3 walks the limb arc properly via clipAngle(90), so the silhouette matches the sphere. Also drops the camera "zoom" by lowering RADIUS from 285 to 250, giving the globe ~17% more breathing room from the viewport edges. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 15:05:25 +07:00
sam	3ade1e8126	Cap Planetora event panel height to clear the bottom HUD The panel anchored at top-36 with max-h calc(100vh-10rem) could extend to within 16px of the bottom edge, overlapping the "now showing" summary that lives inset-x-0 bottom-0. Reserving 18rem (≈9rem top + 9rem bottom) instead keeps tall notes scrollable inside the panel body while leaving the timeline / live HUD visible underneath. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 14:55:41 +07:00
sam	279c8b914c	Drop the orange limb glow on the SVG globe The rim gradient was layering a thick atmosphere-coloured band onto the sphere's edge, which on the dark theme reads as a glowing orange halo ring. Sphere shading is fine without it — the base radial fill plus the highlight already give the disc enough depth. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 14:54:13 +07:00
sam	9313e9b1d7	Shift Planetora globe off-centre when the event panel is open Restores the layout the WebGL globe had: the SVG canvas now extends off the left edge (desktop) or bottom edge (mobile) by the panel's width or height, so the globe sits centred in the panel-free space and stops visually colliding with the opened note. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 14:45:14 +07:00
sam	9ca70dfcc2	Swap WebGL globe for a pure-SVG renderer in Planetora Drops the dependency on react-globe.gl / WebGL so the page works on machines and browsers that fall back to software rendering. Country polygons and pulse rings are projected each rAF tick and applied imperatively to ref'd SVG nodes, so the React tree stays quiet during animation. Co-authored-by: Cursor <cursoragent@cursor.com>	2026-05-21 14:34:31 +07:00
sam	4067904e09	Merge branch 'main' into cooking/planetora	2026-05-21 13:51:53 +07:00
sam	523235e043	live events from user relays too	2026-05-20 22:43:38 +07:00
sam	14ca8999ad	live mode	2026-05-20 22:16:10 +07:00
sam	9dcc183044	link in footer to planetora page	2026-05-20 20:35:17 +07:00
sam	7a519ba341	Merge branch 'main' into cooking/planetora	2026-05-20 20:18:22 +07:00
sam	aeb73e941b	transparency++	2026-05-15 14:47:12 +07:00
sam	9fed3bc0b7	edge case to avoid stale data getting stuck	2026-05-15 12:57:36 +07:00
sam	6555253224	perf	2026-05-15 12:43:36 +07:00
sam	4ad6feac5d	first draft - planetora; a visualisation/hub of agora activity	2026-05-15 12:23:07 +07:00