A public source review of the Hasher client and the messaging trust model behind it.
This page presents the current Flutter client, a focused server reference, and supporting docs used to review and build the app. It is organized so reviewers can trace authentication, encrypted messaging, calls, recovery, subscriptions, media, and current client capability paths through the same public bundle.
Overview
11
Client App
182
Crypto Files
19
Server Files
7
Core files
Flutter client, server reference, crypto services, calls, recovery, store, media, dev and VIP paths
Review use
architecture review, trust-model tracing, local builds, and feature inspection
Review Model
What this public release helps explain.
These notes are organized to make the application stack easier to inspect: how the client boots, where protected state lives, which services back the app, and how the main features fit together.
What this review shows
The release shows the client and server-reference paths behind auth, encrypted messaging, groups, calls, recovery, subscriptions, and profile or media features.
Focus
Startup flow, protected state, API boundaries, realtime channels, and feature wiring.
How data moves
Client state, API requests, websocket updates, background events, and persisted relay records can all be followed from source.
Reading order
Follow a feature from the client screen to its service layer and then into the matching server reference file.
Project structure
The pack is arranged as docs first, then a buildable client package, then a server reference focused on the encrypted messaging trust model.
Reading lens
Read this section as a map for moving between UI, service, and server-reference code.
Pack structure
The public pack is arranged around the real application source and the docs that explain how to read and build it.
Key review areas
- Buildable Flutter client app
- Authentication and protected local state
- Direct messages, groups, and calls
- Recovery, privacy, and decoy flows
- Subscriptions, store flows, and media features
- Server reference files for keys and ciphertext
Reading path
- Start with the overview and build guide
- Follow `main.dart`, `app_config.dart`, and `api_service.dart`
- Move into feature screens and matching client services
- Finish with the server reference models and routers
Server reference
The server reference on this page focuses on the files that show how public keys, prekeys, direct-message ciphertext, and encrypted group payloads reach the relay.
What this shows
Device public keys, signed prekeys, one-time prekeys, ciphertext, per-device encrypted message keys, and encrypted group payload storage can all be traced from source.
Public Review Files
Browse the files included in the public review pack.
The viewer covers the current client source, the server reference for encrypted messaging, build configuration, and the review guides published with this release.
Included Files
219
Client App
182
Client Crypto
19
Server Ref
7
Source Viewer
Open a dedicated viewer for the public review files, with swipeable file cards and compact navigation controls.
README.md
README.md
Introduces the public source pack, its folders, and the recommended reading order for reviewers and builders.
The pack makes it possible to trace where protected data is prepared on-device, how it moves through the app, and how the relay-facing server reference receives it.
Client files cover app startup, encrypted messaging, recovery, calls, notifications, media, and customization flows.
Server reference files show where public keys, ciphertext, and encrypted group payloads are represented once they reach the relay.
Release structure
Buildable client and server reference in one review pack.
The public release is arranged as a readable application bundle: docs first, then the client package, then the server reference that explains the messaging trust model.
Client app
Buildable Flutter application source with screens, services, widgets, models, and platform projects.
Server reference
Published server-side files that show public-key handling, ciphertext relay, and encrypted group payload storage.
Review docs
Guides that map the main flows and show where to start when reading or building the project.
Public pack
- Buildable Flutter client source
- Server reference for prekeys and ciphertext flows
- Review and build guides for the full public pack
Reading context
- Start with the README and build guide
- Follow the client flow from startup into chats and settings
- Open the server reference after the matching client path
Review intention
The public pack is intended for inspection, understanding, and local builds of the current client alongside the server reference used for trust-model review.
Download the pack
Download the same public review bundle shown here.
The downloadable archive matches the files listed on this page. It includes the public client source package, the server reference package, and the same guides used by the explorer.
Pack item
Client app source package
Pack item
Server reference package
Pack item
Review and build guides
Pack item
Runtime and review entry points
Recommended order
Step 1
README.md
Step 2
Review guides
Step 3
Client, then server reference