Research Documents
đź“– Unfamiliar terms? See the glossary for definitions.
Research documents supporting Asgaya’s design decisions.
About This Directory
Research documents are numbered sequentially (RS###) and represent exploratory work, API testing, market analysis, and technical feasibility studies conducted during Asgaya’s development.
Document numbering: RSxxx (Research Study #xxx)
Important Historical Context
Architecture Pivot (May 9, 2026): Asgaya pivoted from an escrow-based model to a covenant-based model for MiCA compliance (avoiding CASP licensing).
What this means for research docs:
Pre-Pivot Documents (RS016-RS045)
Documents created before May 9, 2026 may reference concepts from the old escrow architecture:
- Liquidity Providers (LPs) instead of BCH Sellers
- Escrow settlement instead of covenants
- 1/3 fee splits (sender, merchant, LP) instead of 2-way splits (BCH seller 0.5%, merchant 0.5%)
- Different state machine flows
These documents are retained for historical reference and to show the research that informed later decisions, but may not accurately reflect current architecture.
Post-Pivot Documents (RS047+)
Documents from May 2026 onward reflect the current covenant architecture:
- BCH Sellers (not LPs)
- Covenant + volatility buffers (107%)
- EUR-denominated cash buy orders, BCH settlement
- 24-hour timeout cascade
- 2-way fee split
Key Research Documents (Current Architecture)
Exchange Rates & Markets
Payment Rails & Automation
Volatility & Risk Management
Future Tech
UX & Implementation
- RS081: Multi-Wallet Management Patterns — Research on multi-wallet UX patterns from production BCH wallets (MetaMask, Trust Wallet, Bitcoin.com). Informed Asgaya’s hybrid HD + imported key approach. Implemented August 2-3, 2026.
- RS083: Transaction Broadcast UI Patterns — Research from Selene/Paytaca on transaction state: navigate-on-success, DB persistence, rebroadcast on resume,
viewModelScope. Implemented Aug 17-18; foundation of the v0.2 hybrid architecture (Aug 20-21).
- RS075: Android App Health Detection — Detecting when wallet app is killed/frozen on Android
Oracle & Data Feeds
Historical Documents (Pre-Pivot)
The following documents describe the old escrow architecture and are retained for historical reference:
Why kept? These documents show the research process and constraints that informed the eventual covenant architecture.
Other Research
How to Read Research Docs
- Check the date — Documents from before May 9, 2026 may reference old architecture
- Look for terminology — “LP” = old, “BCH Seller” = current; “escrow” = old, “covenant” = current
- Cross-reference — Most research informed design decisions documented in Why This Design?
Contributing Research
New research documents should:
- Use next sequential number (RS066, RS067, etc.)
- Include date and author
- Reference current covenant architecture (payment-first, H€/HAu, 7-day contracts)
- Link to relevant documentation in Why This Design? or Unknowns
Research is iterative. These documents show the path to the current design, including dead ends and pivots.
Navigation
In this section:
Related sections: Unknowns · Why This Design?