🇩🇰 🇪🇺
ElderSafe

Eldersafe — 4-Month Build Plan

From seed capital to pilot launch. 16 weeks. 50,000 DKK. 10 founders.
The pilot is the onboarding — first 100 signups trigger the genesis Eldersafe–Ældre Sagen collaboration.
No MOU required to start. The verification emails are the partnership proposal.

Build
Test
Partner
Document
Risk
Total Duration
16 weeks
Seed Capital
50,000 DKK
Pilot Members
100
Checkpoints
4
ARR Target
40M DKK

Phase 1 — Foundation (Weeks 1–4)

Strategy shift: We don't wait for Ældre Sagen. The pilot is the partnership proposal. When a user signs up with their membership number, the system sends a verification email to Ældre Sagen's public contact address. Every verification request is a traceable, documented demonstration of the collaboration model. If they respond — we have proof the format works. If they don't — we have proof we tried. Either way, the system runs.

Week 1 — Infrastructure + Verification Design Goal: Stack running. Email-based membership verification designed.
  • Build Set up development environment on the current VPS. Git repo, venv, SQLite, Caddy.
  • Build Deploy Flask endpoint behind Caddy with auto-HTTPS on eldersafe.cloud. Prove the stack works.
  • Build Configure @eldersafe.dk email infrastructure — catch-all for {member_number}@eldersafe.dk addresses.
  • Docs Design the verification email template: Danish-language, clear subject line, explicit response options ("vi bekræfter" / "vi afviser at udtale os"), CC to membership-specific eldersafe address.
  • Docs Define reminder schedule: max 3 emails total (anti-spam). Deadlines. Timeout behavior.
  • Docs Create shared docs repo (all architecture docs live here).
  • Risk If eldersafe.dk email isn't deliverable, the verification loop breaks. Test DKIM/SPF immediately.
✓ End of Week 1: Dev environment running. eldersafe.cloud serves HTTPS. Verification email design complete. eldersafe.dk email tested.
Week 2 — Notary + Legal Groundwork Goal: Identify notary candidates. Confirm regulatory path.
  • Partner Identify 3+ Danish notary candidates (trust service providers, Nets, law firms with HSM capability). Send the identity revelation protocol spec.
  • Partner Request indicative pricing: air-gapped HSM, BSV chain monitoring, court order verification, annual retainer.
  • Risk If all three say "we don't do that" or quote >20 DKK/member — redesign the notary role or absorb the cost.
  • Docs Contact a Danish fintech/blockchain lawyer. One-hour consult: does the pilot trigger MiCA? Finanstilsynet? Datatilsynet?
  • Docs Start DPIA (Data Protection Impact Assessment) draft. Use the GDPR analysis from the architecture docs.
  • Build Set up BSV testnet wallet. Write and broadcast a test transaction from Python. Prove the BSV integration path works.
  • Test Measure: time from Python → broadcast → confirmation. Record baseline.
✓ End of Week 2: At least one notary has responded with indicative pricing. Lawyer consult completed. BSV testnet transaction confirmed.
Week 3 — Core Auth + Email Verification Goal: A member can sign up. Verification email fires. Status is tracked.
  • Build Auth system: member_number + email → JWT magic link. 10-minute expiry. Rate-limited.
  • Build Session management: HttpOnly, Secure, SameSite=Strict cookies. Session timeout.
  • Build Verification workflow: on signup → send templated email to Ældre Sagen (info@aeldresagen.dk) + CC {member_number}@eldersafe.dk. Email asks: confirm or refuse. Fully traceable.
  • Build Reminder engine: 3 emails max. Escalating interval (72h → 168h). Deadline cutoff. Status: pending → verified / refused / timeout.
  • Build Dashboard: shows verification status, email trail, next reminder date. Member understands where they are in the process.
  • Test Auth flow end-to-end: login → magic link → verify → dashboard.
  • Test Verification flow: signup → email sent → reminder schedule → response handling → status update. Test with both valid and invalid membership numbers.
  • Test Negative tests: wrong member number, wrong email, expired token, double-use token, rate limit.
✓ End of Week 3: Auth works. Verification emails fire automatically on signup. Reminder engine tracks state. Dashboard shows verification progress. Zero PII stored.
Week 4 — Life Signal MVP + CHECKPOINT #1 Goal: A logged-in member can fire a life signal. It gets recorded.
  • Build Life signal endpoint: POST /api/signal. Idempotent per 24h window. Records to PostgreSQL.
  • Build Signal streak tracking: count consecutive days. Display on dashboard.
  • Build Dashboard: shows last signal time, current streak, reward balance (placeholder).
  • Build PWA manifest + service worker. App is installable on mobile. Works offline (cached UI, no data).
  • Test 5 test members. Each fires a signal. Verify DB records. Verify dashboard updates.
  • Test Install PWA on Android + iOS. Verify it launches, auth works, signal fires.
  • Docs Write CHECKPOINT #1 report: auth works, signal works, PWA installable, verification emails firing.
★ CHECKPOINT #1 (Week 4): A Danish senior can sign up, receive a magic link, log in, and check in today. Email verification fires automatically on signup — the genesis Eldersafe–Ældre Sagen collaboration is live. Core loop functional. PWA installable. Notary pricing received. Legal opinion obtained.

Phase 2 — Blockchain + Contracts (Weeks 5–8)

The BSV integration moves from testnet to mainnet. Smart contract logic goes live. The treasury wallet exists.

Week 5 — BSV Mainnet Integration Goal: A life signal produces a real BSV transaction.
  • Build Whatsonchain API integration — broadcast raw transactions to BSV mainnet.
  • Build Wallet key management: generate and store BSV keypairs. Derive from salted member_number.
  • Build Signal → BSV tx pipeline: enqueue to Redis, batch worker picks up, broadcasts, records txid.
  • Test End-to-end: fire signal → txid appears in DB → txid verifiable on BSV block explorer.
  • Test Measure: latency from signal to on-chain confirmation. Cost per tx in satoshis.
  • Test Batch test: fire 100 signals rapidly → batch worker handles them → all confirmed.
Week 6 — Smart Contract: Life Signal + Breach Cascade Goal: Contract correctly tracks streaks and detects missed signals.
  • Build Contract state machine: active → breach_day_1 → breach_day_2 → … → breach_day_7 → terminated.
  • Build Cron job (every 30 min): check all active members. If last_signal > 24h, advance breach state.
  • Build 30-day streak bonus: after 30 consecutive days, credit 5 satoshis to member reward balance.
  • Build SMS escalation trigger: at breach_day_3, enqueue SMS to designated contacts. (Mock SMS for now.)
  • Test Simulate: member skips day 1 → breach state advances. Member resumes → state resets to active.
  • Test Simulate: member skips 7 consecutive days → contract terminates. SMS escalation fires.
  • Test Simulate: 30-day streak → bonus credited. Verify satoshi amount.
Week 7 — Treasury + 50 DKK Economics Goal: The 50 DKK split is operational. Treasury exists on-chain.
  • Build Eldersafe public fund wallet (BSV multisig address). Visible on block explorer.
  • Build BSV treasury wallet — receives 10 DKK per activation. Holds the 109 BSV from seed.
  • Build 50 DKK split accounting: payer rebate (10), BSV treasury (10), founder (2), SMS escrow (1.50), notary (5), ops (21.50).
  • Build Reward payout: 1 satoshi per signal, 5 satoshi per 30-day bonus. Deducted from treasury.
  • Test Simulate 100 member activations. Verify each split line reconciles. Verify treasury balance matches expected.
  • Docs Public treasury dashboard: a read-only page showing fund balance, inflows, outflows. Live on status.eldersafe.dk.
Week 8 — UX Polish + CHECKPOINT #2 Goal: Test with real elderly users. Fix everything they find confusing.
  • Test UX test session #1: 3–5 Danish seniors (65+). Silent observation. No instructions. Watch them try to log in, check in, read dashboard.
  • Test UX test session #2: incorporate fixes. Test again with 3 different seniors.
  • Build All UI text in Danish. Large fonts. High contrast. Minimal taps. Clear feedback after every action.
  • Build Accessibility: screen reader support, touch targets ≥ 48px, no tiny text, no jargon.
  • Docs UX findings report. What worked. What didn't. What changed. Share with Ældre Sagen.
  • Docs CHECKPOINT #2 report: blockchain live, contracts working, treasury visible, UX tested.
★ CHECKPOINT #2 (Week 8): Full system operational. BSV integration live. Contracts tested. Real elderly users have used it and not hated it.

Phase 3 — Pilot Preparation (Weeks 9–12)

From working prototype to production pilot. Infrastructure hardening, monitoring, onboarding flow.

Week 9 — Infrastructure Hardening Goal: Production-ready infrastructure. Nothing on "it works on my machine."
  • Build Migrate SQLite → PostgreSQL if not already done. Apply production schema from architecture doc.
  • Build Redis for signal queue (replace any in-memory queue).
  • Build Systemd units for all services: eldersafe (Gunicorn), caddy, eldersafe-worker (BSV batch), eldersafe-cron (breach checks).
  • Build Logging: structured JSON logs. Rotated. Separate error log.
  • Build Backup: pg_dump daily, off-site to Hetzner Storage Box. Test restore.
  • Test Reboot server. Verify all services auto-start. Verify signal flow still works.
  • Test Kill PostgreSQL. Verify Gunicorn returns 503. Restore PostgreSQL. Verify recovery.
Week 10 — Monitoring + SMS + Email Goal: Alerting works. SMS and email channels are live.
  • Build Better Uptime monitoring: health checks every 30s. Public status page.
  • Build Alerts: Redis queue depth > 1000, failed BSV broadcasts > 5, DB down, disk > 80%.
  • Build SMS gateway integration (GatewayAPI.dk). Real SMS for breach escalation.
  • Build Email delivery (SendGrid). Magic link emails. Breach notification emails.
  • Build 2-of-3 channel auth: app + SMS + email. Implement channel verification flows.
  • Test Trigger breach → SMS sends. Verify delivery. Verify cost logged.
  • Test Kill the server → Better Uptime alerts fire within 60s.
Week 11 — Onboarding Flow + Member Documentation Goal: A new member can join without human assistance.
  • Build Activation flow: member_number + email → verification email sent → BSV wallet generation → activation contract on-chain.
  • Build Welcome sequence: confirmation email, first-time dashboard tour (Danish), "try your first check-in" prompt.
  • Docs Member guide (Danish, paper-friendly PDF): "Hvad er Eldersafe?" — what it is, what it does, what it costs, your rights.
  • Docs Privacy notice: what data goes on-chain, what stays off-chain, how to request erasure. GDPR-compliant.
  • Test Onboard 10 test members end-to-end. Zero human help. Time the process. Fix friction points.
  • Partner Coordinate with Ældre Sagen on pilot member recruitment. Who? How many? When? How will they be contacted?
Week 12 — Dry Run + CHECKPOINT #3 Goal: Full pilot simulation. 100 simulated members. 7 days of operation.
  • Build Member simulator: scripted 100 members, realistic check-in patterns (some miss days, some have streaks, 2 trigger breach).
  • Test Run 7-day simulation. Collect: signal completion rate, breach cascade accuracy, reward payout accuracy, BSV fee total, infra cost.
  • Test Verify treasury reconciliation: BSV in = BSV out + treasury balance. 100% match required.
  • Test Load test: 500 concurrent signals. Verify response time < 500ms. Verify queue drains within 5 minutes.
  • Docs Dry run report: all KPIs measured, all projections updated, all issues logged.
  • Docs CHECKPOINT #3 report: pilot-ready. Handoff package for Ældre Sagen.
★ CHECKPOINT #3 (Week 12): System has run for 7 days with simulated members. All KPIs green. Ready for real members.

Phase 4 — Pilot Launch (Weeks 13–16)

Real members. Real life signals. Real BSV transactions. The data that proves the model.

Week 13 — Soft Launch (10 Members) Goal: First real members. Gentle ramp. Watch everything.
  • Partner Onboard first cohort: 10 members (possibly Ældre Sagen volunteers or staff, tech-comfortable).
  • Test Active monitoring: watch every signal, every BSV tx, every dashboard view. Log every anomaly.
  • Test Daily standup: review previous day's data. Any missed signals? Any failed broadcasts? Any member confusion?
  • Build Fix issues immediately. Short feedback loop. Deploy daily if needed.
  • Docs Soft launch log: every issue, every fix, every member interaction.
Week 14 — Expand to 50 Members Goal: Scale stress test. Member diversity.
  • Partner Onboard second cohort: 40 more members. Include less tech-comfortable seniors. Test the UX thesis.
  • Test Compare signal rates: cohort 1 (tech-comfortable) vs. cohort 2 (typical senior). Identify UX gaps.
  • Test SMS escalation: ensure it only fires for real breaches. Zero false positives.
  • Test Email deliverability: magic links arrive. Breach notifications arrive. Not spam-foldered.
  • Docs Mid-pilot report: 2 weeks of data. Cost per signal. Member retention. Streak distribution.
⚠ Watch: If signal completion rate drops below 80% at 50 members, the UX needs major work before going to 100.