- Sync now pulls every BTC Map place worldwide (~29k live), not just
Madeira — dropped BTCMAP_CENTER_LAT/LON/RADIUS_KM entirely.
- Incremental via a stored watermark (settings.btcmap_synced_since):
only fetches what changed since the last sync, not the whole dataset
every time. Handles deletions too (BTC Map delistings correctly evict
the local place + cascade its claim/links, not just go unclaimed).
- Real bug caught and fixed before it shipped: tried BTC Map's own
recommended updated_since+limit pagination first, but their timestamps
mix millisecond and whole-second precision, and naive string comparison
across that isn't chronologically safe — silently truncated a real
sync to ~4,000 of ~42,000 records with no error. Measured the
alternative (single unpaginated request) instead: 2-3s for the full
dataset, simpler and actually correct. Full writeup in
services/btcmap.ts, regression test for the specific bug in
services/btcmap.test.ts.
- @fastify/compress added — the places list is now tens of thousands of
rows, gzip/br/zstd auto-negotiated.
- Also fixed while touching dependencies: @fastify/static had a real
high-severity path-traversal/auth-bypass advisory (GHSA-pr96-94w5-mx2h
et al) affecting the version we were pinned to — bumped to the patched
10.1.2.
- Frontend: leaflet.markercluster (raw per-marker rendering doesn't scale
to tens of thousands of points), cyberpunk-themed cluster icons to
match the existing HUD styling, batch marker insertion (addLayers, not
a per-marker addLayer loop) since that's dramatically faster at this
scale. Default map view is now world-scale, recentering on the
player's location if geolocation is available.
- 60 backend tests passing throughout (7 new for the sync rewrite).
- MAX_LINK_DISTANCE_KM (default 500): flat cap on link length. Real
Ingress scales this off portal/resonator level (up to ~655km); Regress
has no leveling system to scale off of, so this is a single ceiling.
- PORTAL_TIMEOUT_BLOCKS (default 2100): claims stamp the current Bitcoin
block height (claimed_at_block, new migration) and expire back to
neutral after this many blocks — the game's clock is block height, not
wall-clock. Current height comes from mempool.space (BlockHeightService,
60s cache), same trust model as the BTC Map dependency. A background
sweep actively reverts timed-out claims (tearing down their links, same
as a normal recapture); claim/link routes also check inline so
correctness doesn't depend on sweep timing between runs.
- Pre-existing claims (already live in production) get backfilled with
the real current block height once at startup rather than a guessed
historical value — dry-run verified against an actual copy of the live
production database before deploying.
- Score now reports link count per team alongside places/fields/area
(backend already computed this; only the frontend display was missing).
22 new tests (53 total): pure expiry-logic unit tests plus full
claim/link/sweep integration tests using a network-free fake block-height
provider (BlockHeightProvider interface + FakeBlockHeight test double).
Regress needs to live at podsteadr.atobitcoin.io/regress/ since / is
already podsteadr. Two coordinated pieces:
- VITE_BASE build arg (frontend asset/script paths, %BASE_URL% in
index.html for the nostr-provider.js script tag)
- ROUTE_PREFIX runtime env (backend routes registered under the prefix
via Fastify's plugin-encapsulation, including /api/health)
The nginx location must forward the prefix unstripped (proxy_pass with
no trailing path) — NIP-98 login signs the exact URL it calls, so a
stripped prefix makes the backend reconstruct a different URL than what
was signed and every login fails. Caught this with a real nginx+docker
integration test locally before it could break the live migration, then
fixed a matching bug in auth.ts (it was signing the unprefixed URL while
api.ts fetched the prefixed one). New routePrefix.test.ts proves the
prefix is actually enforced, including a negative case. 40 tests passing.
Also fixes a latent bug: import.meta.env usage had no vite/client type
reference, so it only ever passed typecheck by accident in earlier local
runs — added the standard vite-env.d.ts.
A new link can no longer cross any existing link from either team —
segmentsIntersect() does a standard orientation-based segment test,
and routes/links.ts excludes shared-endpoint pairs (fanning multiple
links out of the same portal is fine, that's not a crossing). 6 new
tests; 37 total passing.
- Server: NIP-98 nostr auth (session cookies), BTC Map sync, claim/link/field
routes, physical-presence checks via geolocation distance. 31 tests passing.
- Frontend: Leaflet map, team pick, claim/link UI, Archipelago identity
bridge vendored (nostr-provider.js) for dashboard launch support.
- Verified end-to-end against the live BTC Map API (167 real Madeira places)
and via genuine NIP-98-signed HTTP requests against the built app.
ssmithx