Software and network layer for offline device-to-device communication, identity verification, service discovery, file transfer and opt-in telemetry across multiple transports.
Software and network layer for offline device-to-device communication, identity verification, service discovery, file transfer and opt-in telemetry across multiple transports.
Common useMessagingMessaging / OfflineOperator dataHosted
CAUTIONThe marketing site uses consent-gated PostHog analytics and short-lived server logs. Product data practices vary: the MINE app requires an email account and collects device, service, rewards, wallet and security metadata, while some location and mesh metrics stay on-device. Review the policy for the specific Offline Protocol product.
AUDITED BYNo audit listed
OPERATOR DATAHosted operator recorded
SOURCE COVERAGE
△Partial evidenceTHIRD-PARTY REPORTED5/9Reviewed 5 Sep 2026 · Source → official site
LAST CHECKED2026-06-23
LAST UPDATED2026-09-05
Specs
DOCUMENT CHECKlight
IDENTITY EXPOSURELevel 1/4
KYC TRIGGERSNo document-KYC policy found, but identity/reputation and account/data-request surfaces are core to the product; treat as light identity exposure rather than pure anonymous messaging.
FEEAGPL community evaluation; commercial SDK and production use priced by quote; supported pilot lasts 6 to 10 weeks
NETWORKSBluetooth LE, Wi-Fi Direct, Internet, Reticulum, Nostr
CATEGORIESMessaging, Offline, Payments, Identity
FEATURESAGPL community SDK, Commercial SDK licensing, Bluetooth and Wi-Fi Direct mesh networking, Offline identity, Service discovery, Supported 6 to 10 week pilots
TORNot listed
REGIONSGlobal availability
Review analysis, source material, related services, and history
Analysis
OVERVIEW
Offline Protocol combines mesh messaging, an OfflineID identity layer and peer-to-peer payments in one offline-first stack, with 1.1 million dollars raised toward what its own materials call the Sovereign Stack.
LIMITS
The codebase is currently closed-source and investors are undisclosed, and the record notes the identity and reputation layer plus token incentives require trusting the provider and a still-maturing SDK rather than independent verification.
USEFUL FOR
Early adopters of offline mesh identity and payments who accept a closed-source, unaudited stack with a recorded light identity exposure.
The recorded KYC level is "light". No document-KYC policy found, but identity/reputation and account/data-request surfaces are core to the product; treat as light identity exposure rather than pure anonymous messaging.
Which payment methods are accepted?
Accepted payment methods: Bluetooth LE, Wi-Fi Direct, Internet, Reticulum, Nostr.
Where is it available?
Recorded availability: GLOBAL.
Is the operator based in a Five Eyes country?
Yes. The recorded jurisdiction is US, a Five Eyes country (US, UK, CA, AU, NZ). This is jurisdiction context and does not by itself establish that a service is safer or less safe.
How are identity, operator, and evidence fields reported?
Identity exposure is level 1 of 4. A hosted operator is recorded. Jurisdiction is shown as context, not a safety verdict. Source coverage is partial evidence, last reviewed 2026-09-05, and recorded risk is caution.
Which payment networks are supported?
Accepted networks: Bluetooth LE, Wi-Fi Direct, Internet, Reticulum, Nostr.
No changes to the documents we watch since we started checking on 9 Aug 2026. Last checked 9 Aug 2026.
Evidence basis: Claims on this page are linked to published sources for comparison, not certification, audit, endorsement, or recommendation; read the methodology and coverage map before relying on an entry.
Service history
Latest meaningful changes to the facts shown on this provider page.
Review overdue providers against current sources
Features, Fee, KYC last checked, Last reviewed, and 3 more
Reconcile score 4.0 evidence
Audited by, Description, Evidence status, Fee, and 3 more
Corporate registry information updated
Corporate
Full service history
updated
Review overdue providers against current sources
Features
not set → AGPL community SDK, Commercial SDK licensing, Bluetooth and Wi-Fi Direct mesh networking, Offline identity, Service discovery, Supported 6 to 10 week pilots
Fee
AGPL community evaluation; commercial deployment priced by quote → AGPL community evaluation; commercial SDK and production use priced by quote; supported pilot lasts 6 to 10 weeks
KYC last checked
2026-06-22 → 2026-09-05
Last reviewed
2026-06-22 → 2026-09-05
Privacy warning
Identity/reputation layer, token incentives and still-maturing SDK/protocol surfaces require trust in the provider and implementation. → The marketing site uses consent-gated PostHog analytics and short-lived server logs. Product data practices vary: the MINE app requires an email account and collects device, service, rewards, wallet and security metadata, while some location and mesh metrics stay on-device. Review the policy for the specific Offline Protocol product.
Source reviewed
official site → https://www.offlineprotocol.com/pricing
Offline-first mesh stack documenting OfflineID, mesh SDKs, peer-to-peer payments and privacy credentials. → Software and network layer for offline device-to-device communication, identity verification, service discovery, file transfer and opt-in telemetry across multiple transports.
Evidence status
verified → partial
Fee
Free → AGPL community evaluation; commercial deployment priced by quote
Jurisdiction
?? → US
Networks
Mobile, Bluetooth Mesh, Proprietary → Bluetooth LE, Wi-Fi Direct, Internet, Reticulum, Nostr
Score review
not set → Outcome: HOLD; Checked at: 2026-08-27; Inputs: Operator data exposure: limited; Control model: local-self-custody; Source model: open; Audit: Score eligible: no; Reason: No dated, scoped independent audit of the score-critical core was evidenced; no audit points are granted.
The 'Sovereign Stack' for offline environments. Features DORS (Bluetooth/WiFi mesh routing), OfflineID, and OfflinePay. Raised $1.1M in March 2025 and features Binance wallet integration. The Fernweh messaging app is built natively on top of this protocol. → Offline-first mesh stack for communication, identity and payments. Official docs describe OfflineID, mesh SDKs, peer-to-peer payments, privacy-preserving credentials and support/data-request flows.
Jurisdiction
not set → ??
KYC requirement
none → light
KYC last checked
2026-03-13 → 2026-06-22
KYC level
0 → 1
Kyc note
Advertises No-KYC, but strictly adhere to OPSEC rules. Access via Tor, pay with XMR. → No document-KYC policy found, but identity/reputation and account/data-request surfaces are core to the product; treat as light identity exposure rather than pure anonymous messaging.
Last reviewed
2026-03-13 → 2026-06-22
Privacy warning
Codebase is currently closed-source (plans to open-source in the future). Requires trust in the provider's cryptography. → Identity/reputation layer, token incentives and still-maturing SDK/protocol surfaces require trust in the provider and implementation.
Source reviewed
older source, not independently verified → official site