element-x-ada/BLOCKERS.md
Kayos 880454847e docs: resolve Phase 1 design decisions and add emulator info
- Q1 RESOLVED: per-session wallet scope (Phase 3: optional sharing)
- Q2 RESOLVED: invalidate keys on biometric change (intentional)
- Q3 RESOLVED: testnet first, single config point for mainnet swap
- Added Android emulator connection info (ADB + noVNC)
2026-03-27 10:34:48 -07:00

2.7 KiB

BLOCKERS.md - Phase 1 Implementation Blockers

Task 1: Module Scaffolding

Completed

  • Module structure created (api/impl/test)
  • Metro DI setup following Element X patterns
  • WalletEntryPoint and WalletState APIs defined
  • PaymentFlowNode placeholder with Appyx navigation
  • FakeWalletEntryPoint for testing
  • Cardano client library dependencies added
  • ProGuard rules configured
  • Basic unit tests added
  • Pushed to Gitea phase1-dev branch

Not Verified (No Android SDK in build environment)

  • ⚠️ ./gradlew :features:wallet:impl:assemble - compilation not tested
  • ⚠️ ./gradlew ktlintCheck --continue - code style not verified
  • ⚠️ ./gradlew :features:wallet:impl:test - unit tests not run

Action Required

When a developer with Android SDK runs this code:

  1. Run ./gradlew :features:wallet:impl:assemble to verify compilation
  2. Run ./gradlew ktlintCheck --continue and fix any code style issues
  3. Run ./gradlew :features:wallet:impl:test to verify tests pass

Resolved Decisions

Q1: Wallet Scope RESOLVED

Decision: Per-session (each Matrix account has its own wallet)

Each Matrix session maintains its own independent wallet. This aligns with Matrix's account-centric model and provides proper isolation between accounts.

Phase 3 Planned: Optional wallet sharing between accounts — will be implemented as a user preference, not default behavior.

Q2: Key Storage on Biometric Change RESOLVED

Decision: INVALIDATE keys and require re-authentication/re-setup

When biometric enrollment changes (fingerprints added/removed, face re-enrolled, etc.), stored wallet keys are invalidated. Users must re-authenticate and re-setup their wallet access. This is intentional security behavior, not a bug — it prevents unauthorized access if a device is compromised or biometrics are changed by an attacker.

Q3: Network Configuration RESOLVED

Decision: TESTNET first, with easy mainnet swap

Development and initial testing will target Cardano testnet. The network configuration must be a single constant or build flavor — no scattered hardcoded values throughout the codebase.

Implementation requirements:

  • Single source of truth: Constants.NETWORK_MODE or build variant
  • All network-dependent URLs/configs derived from this single value
  • Clean swap to mainnet via config change or release build flavor
  • No hunting through code for hardcoded "testnet" strings

Android Emulator

Development Android emulator is live and available:

Service Address
ADB 192.168.0.5:5555
noVNC (browser access) http://192.168.0.5:6080

Connect via: adb connect 192.168.0.5:5555


Last updated: 2026-03-27