Architecture and operations
What the components are, how value flows between them, how the service is secured, and what records it keeps.
-
Read first
Architecture and value flow
The work path and the reward path as two diagrams, the data model, the operational-key posture, and the interfaces that deliberately do not exist.
Start here -
Operations
Operational security
Web, Stratum, node, admin, key, monitoring, audit-log, incident-response, DDoS, and release-integrity recommendations. RPC is never exposed to the internet.
-
Operations
Records the service keeps
Every record, why it is kept, and its proposed retention — enough to show that each payout was calculated from mining participation, and no more than that.
Product
The miner-facing surface: how someone starts mining without an account, what the dashboard shows, and what it is called.
-
Workflow
Onboarding workflow
The address-is-the-identity model, step by step. No accounts, no passwords; an optional email registered by signed message.
-
Interface
Mining dashboard wireframe
The tiles, tables, labels, and empty states — and the buttons that are intentionally absent.
-
Language
Terminology
Recommended mining terms, prohibited banking and investment terms, and the exact wording of the pending-mining-reward explanation.
Compliance
How each feature was evaluated, what may never be added without review, and the questions counsel must answer before launch.
-
Evaluation
Compliance-by-design matrix
Every proposed feature against custody, money-transmission, exchange, securities-marketing, OFAC, consumer-protection, and privacy risk.
-
Rule
Regulatory change control
The list of features that change what the service is, the review process, the schema and API rules, and the pre-merge checklist.
Binding -
Open questions
Issues requiring attorney review before launch
Thirteen concrete questions, the source that raises each, and what the design currently assumes. Pennsylvania licensing is first.