⚠ TEST ONLY — NOT PUBLIC Patent Family Implementation Reference · Unpublished · Filing Review Pending · Do Not Distribute

Offline Router &
Local Ledger System

Implementation reference for the offline Wi-Fi router patent family — captive portal, device hash ID, local ledger, offline storefront, referral commission tracking, and later sync. OCC HEART + Snowflake layer added on top of existing family.

Referenced Patent Family Concepts
Offline Transactions Wi-Fi Router Gateway Captive Portal Device Hash ID Local Ledger Offline Storefront Referral / Commission Later Sync OCC HEART Snowflake Per-TX

The Implementation Model

Seven-stage pipeline. Router is the gateway. Everything downstream — identity, transactions, referrals — operates without an internet connection. Sync happens later, when connectivity is restored.

📡
Stage 1 — Router as Gateway
A standard Wi-Fi router runs modified firmware (or a companion device) that intercepts all new connections before granting internet access. The router is the enforcement boundary — it controls who can transact and who cannot.
role: offline_gateway
firmware_layer: captive_portal_intercept
internet_required: false // all stages 1–6 are offline
hardware: any_802.11_router | companion_device
🔒
Stage 2 — Captive Portal
When a device connects to the router's Wi-Fi, it is redirected to the captive portal before any internet access is granted. The portal is served entirely from the router's local storage — no cloud required. This is the entry point to the offline storefront.
portal_served_from: router_local_storage
redirect_trigger: HTTP_302 | DNS_hijack
portal_content: HTML + JS + offline_storefront_assets
requires_cloud: false
🛍️
Stage 3 — Offline Storefront
The captive portal presents a local business's products, services, and offers — all stored on the router. The customer can browse, select, and initiate a purchase without any internet connection. Prices, inventory, and payment options are loaded from the local ledger cache.
product_catalog: router_local_db | JSON_flat_file
payment_methods: cash_record | local_credit | QR_offline
inventory_source: last_synced_snapshot
purchase_flow: select → confirm → device_hash → ledger_write
Patent Note

The offline storefront operating through a router captive portal — with no internet dependency — is a key novel element of the patent family. The system functions end-to-end in an air-gapped environment.

🔑
Stage 4 — Device Hash ID
When a device connects, the router generates a persistent hash ID for that device based on available fingerprint signals. This ID is used as the customer identifier in the local ledger — no account creation required. Repeat visitors are recognized offline by their hash.
input_signals: MAC_address + browser_fingerprint + user_agent
hash_algo: SHA256
hash_id_format: DEV-[8 hex chars]-[timestamp_epoch]
example: DEV-4F2A91C3-1745000000
storage: router_local_ledger.devices
cloud_required: false
💗
Stage 5 — Business OCC HEART + Fresh Snowflake
The business operating the router has an OCC HEART — a cryptographic identity token issued when they registered. Each transaction generates a fresh snowflake: a unique GUID that is co-signed by the HEART. This binds every offline transaction to the verified business identity, even without a cloud connection at time of sale.
business_identity: OCC_HEART (issued at registration)
heart_fields: member_id + snowflake_base + SHA256 + sig_ref
tx_snowflake: fresh GUID per transaction
snowflake_format: SNOW-[HEART_ID]-[TX_seq]-[nano_ts]
signing: HMAC-SHA256 with HEART key
cloud_required_to_sign: false // key cached on router
OCC Integration Note

The OCC HEART + per-transaction snowflake layer is the Patent 25 addition on top of the existing offline router/ledger family. The HEART provides verifiable business identity offline; snowflakes provide tamper-evident transaction IDs that sync cleanly to the Command Center.

📒
Stage 6 — Local Transaction + Referral Record
Every purchase, referral activation, and commission event is written to the local ledger on the router at the time it occurs — no internet required. Referrals carry a referral code that was pre-loaded onto the router at last sync. Commission amounts are computed locally using cached rate tables.
ledger_type: SQLite | append-only flat file
ledger_location: router:/var/occ/ledger.db
write_mode: append_only | no_delete | tamper_resistant
referral_code_source: pre-loaded at last_sync
commission_rate: cached_rate_table | computed_offline
☁️
Stage 7 — Later Sync to Command Center
When the router regains internet connectivity, the local ledger is transmitted to the Command Center. Each ledger record carries its snowflake ID, device hash, HEART signature, and timestamp. The Command Center validates the HEART and snowflakes, reconciles inventory and commissions, and updates member accounts — without any record being lost during the offline period.
trigger: internet_restored | manual_sync | scheduled
payload: ledger_delta since last_sync_ts
validation: HEART_verify + snowflake_dedup + device_hash_lookup
idempotency: snowflake prevents double-processing
conflict_resolution: timestamp + HEART_sig wins
sync_protocol: HTTPS POST | signed envelope | retry_with_backoff

System Architecture

The router is the local authority. All data flows downstream from the router during offline operation, then up to the Command Center during sync.

📡
WI-FI ROUTER
Gateway + Portal Host
Local Storage + Ledger DB
🔒
CAPTIVE PORTAL
Local HTML/JS
No cloud needed
🛍️
OFFLINE STORE
Products + Prices
From last sync
🔑
DEVICE HASH ID
SHA256(MAC+UA)
Persistent offline
+
💗
OCC HEART
Business identity
Cached on router
❄️
SNOWFLAKE TX
Fresh GUID
Per transaction
📒
LOCAL LEDGER
TX + Referrals
Append-only · Offline
↓ (when internet restored)
🏛️
COMMAND CENTER
Validates HEART + Snowflakes
Reconciles ledger · Updates accounts

Local Ledger Schema

The ledger is append-only and stored entirely on the router. Each row is self-contained — it can be validated independently by the Command Center using the snowflake and HEART signature.

Field Type Example Note
snowflake_id TEXT · PK SNOW-BIZ001-0042-1745001234 Unique per transaction. Prevents double-processing on sync.
device_hash TEXT DEV-4F2A91C3-1745000000 Identifies the customer device. No PII stored.
heart_id TEXT HEART-BIZ001-FL-250 The business OCC HEART that authorized this transaction.
tx_type ENUM PURCHASE | REFERRAL | COMMISSION | ACCESS_GRANT What kind of event occurred.
product_sku TEXT SKU-WIFI-PASS-24H From local product catalog snapshot.
amount_local DECIMAL 5.00 Transaction amount in local currency.
referral_code TEXT · NULL BRET.FENCL.1 Pre-loaded referral code. NULL if no referral.
commission_amount DECIMAL · NULL 0.50 Computed from cached rate table. Applied on sync.
ts_local INTEGER 1745001234 Unix timestamp from router clock. Authoritative for offline ordering.
hmac_sig TEXT a3f9d1...e4b2 (64 hex) HMAC-SHA256 of all fields using HEART key. Tamper-evident.
sync_status ENUM PENDING | SYNCED | REJECTED Set to PENDING on write. Updated to SYNCED by Command Center.

OCC HEART + Snowflake Layer

The Patent 25 addition. A business's HEART is provisioned once at registration and cached on their router. Every offline transaction generates a fresh snowflake co-signed by that HEART — creating a verifiable chain from each transaction back to the registered business identity, even without a live cloud connection.

💗
Business OCC HEART
Issued at registration · Cached on router · Signs all offline transactions
HEART ID
HEART-BIZ001-FL-250
Member ID
BIZ.OWNER.1@YourIQ.AI
Base Snowflake
3E7A-F219-C804-D56B
Checksum
SHA256: a3f9d1c2...
Issued
2026-04-25T00:00:00Z
Signature Ref
BRET_FENCL / YOURIQAI_SYSTEM
Cache Location
router:/var/occ/heart.json
Fail-Closed
YES — no HEART = no TX write

Generated fresh for every transaction. Includes HEART ID, sequential TX counter, and nanosecond timestamp. Signed with the HEART's HMAC key.

// Transaction snowflake — generated at time of purchase, offline
snowflake_id : "SNOW-BIZ001-0042-1745001234567"
heart_id : "HEART-BIZ001-FL-250"
tx_sequence : 42 // monotonically increasing per router
device_hash : "DEV-4F2A91C3-1745000000"
amount : 5.00
product_sku : "SKU-WIFI-PASS-24H"
referral_code : "BRET.FENCL.1"
ts_local : 1745001234
hmac_sig : "a3f9d1c2e4b28f7a..." // HMAC-SHA256, HEART key
sync_status : "PENDING"

✓ Snowflake written to local ledger at tx time — no cloud required

Referral & Commission Tracking

Referral codes are pre-loaded into the router at last sync. When a referred device transacts, the commission is computed locally from the cached rate table and written to the ledger. No cloud connection needed to record or compute commissions — they settle when the ledger syncs.

Patent Note

Offline referral tracking — where referral codes, commission rates, and commission ledger records are all maintained locally on the router without any cloud dependency at time of transaction — is a key novel element. The entire referral chain is preserved offline and reconciled on sync.

// Referral commission record — local ledger entry
snowflake_id : SNOW-BIZ001-0043-1745001290
tx_type : REFERRAL_COMMISSION
referral_code : BRET.FENCL.1
referred_device: DEV-4F2A91C3-1745000000
source_tx : SNOW-BIZ001-0042-1745001234567
sale_amount : 5.00
commission_rate: 10% // loaded from cached rate table
commission_amt : 0.50 // computed offline
payout_to : BRET.FENCL.1@YourIQ.AI
ts_local : 1745001290
sync_status : PENDING // applied to member account on sync
hmac_sig : b7c4e2f1d3a9...

Sync Protocol — Later Connectivity

When internet is restored, the router transmits its ledger delta to the Command Center. The protocol is idempotent — duplicate submissions are harmless because snowflakes are globally unique. The HEART signature on each record proves it originated from a registered business device.

1. Internet Connectivity Detected
Router detects outbound connectivity. Sync agent wakes up. Reads all ledger records with sync_status = PENDING.
trigger: connectivity_check | heartbeat_ping
query: SELECT * FROM ledger WHERE sync_status = 'PENDING' ORDER BY ts_local ASC
2. Envelope Assembled & Signed
All PENDING records are packaged into a signed sync envelope. The envelope header includes the HEART ID, router ID, last_sync_ts, and a manifest HMAC over all record snowflakes.
envelope.heart_id = HEART-BIZ001-FL-250
envelope.router_id = RTR-FL-001
envelope.record_count = 42
envelope.manifest_hmac = SHA256(all_snowflake_ids)
envelope.heart_sig = HMAC(envelope_header, heart_key)
3. Transmitted to Command Center
HTTPS POST to Command Center sync endpoint. Retries with exponential backoff on failure. Records remain PENDING on retry — no data is lost.
POST /api/sync/ledger
Authorization: HEART-BIZ001-FL-250:<sig>
Content-Type: application/json
Body: { envelope + records[] }
4. Command Center Validates
Command Center verifies the HEART signature, checks each snowflake for uniqueness (dedup), validates HMAC signatures on each record, and confirms device hashes are known. Any invalid records are flagged — valid records are accepted.
validate: heart_sig OK
validate: snowflake_dedup → 0 duplicates
validate: per-record hmac_sig → all OK
result: 42 records accepted, 0 rejected
5. Accounts & Commissions Updated
Member accounts are credited with commission payouts. Inventory is reconciled against the sold records. The business's transaction history is updated in the Command Center database.
commission_credit: BRET.FENCL.1 += $0.50
inventory_adjust: SKU-WIFI-PASS-24H -= 1
tx_history: 42 records posted to business account
6. Router Acknowledges
Command Center returns acknowledgment with accepted snowflake list. Router marks all accepted records as SYNCED. Router pulls updated product catalog, commission rates, and new OCC HEART rotation if scheduled.
ack.accepted_snowflakes = [SNOW-BIZ001-0001..0042]
router: UPDATE ledger SET sync_status='SYNCED' WHERE snowflake_id IN ack
router: pull updated catalog + rate_table + heart_rotation

Filing & Backup Review Status

This page is hidden and test-only. Do not link from public pages. Do not index. Review pending before any public release.

📋
Page Status
TEST ONLY
🔒
Indexing
NOINDEX · NOFOLLOW
📁
Nav Links
NONE — HIDDEN
⚖️
Patent Claims
NOT WRITTEN — PENDING
💾
Backup Review
IN PROGRESS
🔑
OCC HEART Layer
DOCUMENTED
📡
Router Model
DOCUMENTED
🏛️
Patent Family Ref
LINKED
Implementation Note — Do Not Write Claims Yet

This document describes the implementation model only. Final patent claims are not written here and should not be derived from this document without attorney review. The novel elements identified (offline captive portal commerce, device hash ID, offline referral commission tracking, snowflake-signed offline transactions, HEART-verified sync) are documented for reference only.