Skip to content
CUNICULA

Offline Protocol

Software and network layer for offline device-to-device communication, identity verification, service discovery, file transfer and opt-in telemetry across multiple transports.

offlineprotocol.com

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
Identity checkslight KYCDocument check: light · identity exposure level 1/4
Evidence and riskPartial evidenceCautionSome material claims still need confirmation.; those sources show trade-offs worth reading.
Last reviewedReviewed 5 Sep 2026KYC checked 5 Sep 2026 · unknown jurisdiction · Source → official siteHow to cite this pageSource coveragePartial evidenceRecorded riskCaution
Evidence and facts

Evidence and facts

CUNICULA SCORE 4.0
73/100Limited evidencePrivacy 18/25 · Control 20/20 · Transparency 12/20 · Security 17/25 · Accountability 6/10 · Method
JURISDICTIONUS
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.

Sources · reviewed 2026-07-16

Corporate identity

Registry-sourced, not audited. The facts below come from cited web research rather than a direct registry query. Each claim links its own source.

LEGAL ENTITY
Offline Protocol, Inc.source ↗
REGISTRATION NO.
7545189source ↗
INCORPORATED IN
Delaware, United Statessource ↗
REGISTERED ADDRESS
131 Continental Dr, Ste 305, Newark, Delaware 19713-4324, United Statessource ↗
OFFICERS
  • Satvik Sethi

    Founder & CEO

source ↗
Registry research · reviewed 2026-08-09

Frequently Asked Questions

Is identity verification required?

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.

Related Services

Sources and history

Terms and privacy policy

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.