Every line. In the open.
Review wallet creation, imports, storage, Bitcoin discovery, transaction preparation, PSBT handling, localization, and interface behavior directly in the public repository.
Source you can inspect.
Public source makes implementation details reviewable: the supported wallet formats, the services the app calls, the data passed to them, and the tests around critical Bitcoin behavior.
A Bitcoin wallet should be specific about what its code does.
Public implementation details make broad security and privacy statements testable against real storage, network, and signing paths.
A codebase built to be read.
The project separates wallet models, service clients, storage, localization, navigation, and screens so behavior can be traced without relying on marketing copy.
Wallet types, address derivation, transaction building, fees, PSBTs, QR transport, and Electrum behavior live in clearly scoped modules.
Shared application logic is written in TypeScript, with native iOS integration where platform behavior requires it.
Unit and interface tests document expected behavior for wallet storage, credentials, address handling, sending, pricing, security access, and RTL layouts.
What openness buys you.
Concrete information that can be checked against the implementation.
Developers and researchers can inspect the repository, reproduce issues, and discuss findings through public project channels.
SatPak API routes, Supabase access, Electrum configuration, market-data providers, and explorer links can be traced in source.
Repository history shows when wallet behavior, network integrations, translations, tests, and documentation change.
Public issue reports can point to exact files, tests, and commits instead of relying on an opaque support description.
Read it. Build it. Verify it.
Use the repository to verify supported formats, review service boundaries, run tests, and understand how each wallet action is implemented.