How block-core/angor works
Project type and purpose
• Angor is a decentralized, full-stack P2P funding platform. There is no central backend: all business logic lives in client applications (desktop, mobile, browser, Tauri wrapper) and shared libraries. Bitcoin nodes (and indexers) plus Nostr relays provide persistence and communication.
Top-level file‐structure analysis
• Clients/UI:
• src/Angor.Avalonia – cross-platform desktop/mobile (Avalonia) with CompositionRoot, Contexts (Funding, Wallet), UI features, ViewModels, Views
• src/Client – Blazor PWA (WebAssembly) hosted via wwwroot, razor pages, services, storage abstractions
• src-tauri – Rust/Tauri-based desktop wrapper exposing native capabilities to a web UI
• Core libraries:
• src/Shared – .NET Standard “business engine”: derivation, protocol scripts, transaction builders, application logic, services (IndexerService, NetworkService, RelayService, SignService), models
• Tests:
• src/Angor.Test – unit tests for protocol, derivation, services
• src/Testing – Cypress end-to-end tests for the PWA
• Infrastructure bootstrap:
• docker/ – ready-to-spin Docker Compose setups for Bitcoin explorers (Electrs), Nostr relays, proxy (nginx), and angor-app container
Key README insights
• Angor uses Bitcoin Taproot for time-locked contracts and Nostr for metadata and messaging.
• There is no monolithic server; clients interact directly with Bitcoin nodes (via JSON-RPC) and Nostr relays (via WebSocket events).