Enabling web3 communications and transactions for wireless devices natively, even off grid.
Mobile
OTAwallet is a mobile usecase of SafeSignal, into the first mobile crypto system designed to opportunistically use whatever the phone’s hardware allows — all without internet if needed.
📲 Over-the-Air Crypto Paths in Mobile OTAwallet
Protocol
Use Case
Status/Feasibility
Bluetooth
Peer-to-peer TX sync or swap
✅ Common, supported everywhere
NFC
Tap-to-transfer or key handshake
✅ Supported on most Androids
Wi-Fi Direct
Offline group relays or broadcast
✅ Powerful, often underused
Infrared (IR)
Legacy or directional data beams
🔘 Rare, but possible
LiFi (USB or embedded)
Point-to-point TX handoff
🔜 Scoped as launch feature
FT8 / RF SDR
Long-distance or resilient broadcast
✅ Built into the OTA layer
🔐 Bonus: Modular Fallbacks
If the phone can’t use one method, it auto-selects another (e.g. no internet → try Bluetooth → fallback to QR or NFC
All options offline-capable and operator-grade
This makes OTAwallet the most adaptive, mesh-capable crypto tool in the wild — especially for regions, missions, or users where IP just isn’t available.
when using over-the-air (OTA) transmission on the mobile app, the amount of data that can be sent depends entirely on the transmission method chosen by the wallet. Here’s a breakdown of how much data each method typically supports and what that means for OTAwallet:
📶 Estimated Data Capacity by Transmission Method
Method
Typical Capacity
Suitable For
NFC
~4 KB per transaction
Public/private keys, signed TXs, metadata
Bluetooth
~1 MB/min (10–100 KB/s)
Full TX, swaps, messages, token proofs
Wi-Fi Direct
50–100+ Mbps
Fastest: full backups, batch transactions, sync
Infrared (IR)
~1–5 KB/sec (legacy)
Slow TX or key-sharing over LoS
LiFi (USB)
10–100+ KB/s (typical)
Secure TX packets, small bundles
FT8 / WSJT-X
~75 bits every 15 sec
Tiny: one compact signed message at a time
🧾 Example Transaction Sizes
Action
Data Size
Notes
OTA Token Transfer
~250–800 B
Fits NFC/Bluetooth easily
Token Swap Intent (DEX)
~500–1,200 B
Still fits most wireless methods
IPFS CID (log/hash)
~46 B
Very lightweight
Signed TX Bundle
1–4 KB
Still fits into NFC or Bluetooth
OTAwallet Backup (keys + state)
~10–200 KB
Needs Bluetooth, Wi-Fi Direct, or LiFi
✅ Summary:
🔐 Basic crypto TXs and swaps can be done via Bluetooth, NFC, or LiFi
📡 FT8 is for minimal packet relays (e.g., beacon or signed hash)
💾 Full wallet backups require Wi-Fi Direct or serial connection
When using over-the-air (OTA) transmission on the mobile app, the amount of data that can be sent depends entirely on the transmission method chosen by the wallet. Here’s a breakdown of how much data each method typically supports and what that means for OTAwallet:
📶 Estimated Data Capacity by Transmission Method
Method
Typical Capacity
Suitable For
NFC
~4 KB per transaction
Public/private keys, signed TXs, metadata
Bluetooth
~1 MB/min (10–100 KB/s)
Full TX, swaps, messages, token proofs
Wi-Fi Direct
50–100+ Mbps
Fastest: full backups, batch transactions, sync
Infrared (IR)
~1–5 KB/sec (legacy)
Slow TX or key-sharing over LoS
LiFi (USB)
10–100+ KB/s (typical)
Secure TX packets, small bundles
FT8 / WSJT-X
~75 bits every 15 sec
Tiny: one compact signed message at a time
🧾 Example Transaction Sizes
Action
Data Size
Notes
OTA Token Transfer
~250–800 B
Fits NFC/Bluetooth easily
Token Swap Intent (DEX)
~500–1,200 B
Still fits most wireless methods
IPFS CID (log/hash)
~46 B
Very lightweight
Signed TX Bundle
1–4 KB
Still fits into NFC or Bluetooth
OTAwallet Backup (keys + state)
~10–200 KB
Needs Bluetooth, Wi-Fi Direct, or LiFi
✅ Summary:
🔐 Basic crypto TXs and swaps can be done via Bluetooth, NFC, or LiFi
📡 FT8 is for minimal packet relays (e.g., beacon or signed hash)
💾 Full wallet backups require Wi-Fi Direct or serial connection
🧠 OTAwallet Mobile as a Validator / Relay Node
📱 1. Bluetooth / NFC Validator
Function
Feasibility
Notes
Receive TX packet
✅ Very reliable
Bluetooth especially
Validate + Sign
✅ Local logic
Uses stored keys
Send back ACK/Proof
✅ NFC or BT loop
Instant P2P loopback relay
💡 2. LiFi Micro-Validator
Use Case
Feasibility
Notes
Cold wallet-to-relay
✅ Works well
Silent, directional TX
Local validation
✅ Built-in
Validate packet before rebroadcast
IPFS sync
✅ Secure
Bundle TX + CID into light packet
📡 3. FT8 / Packet Validator
Mode
Notes
FT8 receive
✅ Via embedded WSJT-X or decoded signal
TX hash signing
✅ Small proof-of-receipt hash
RF Beacon Validator
🔄 Could listen/track multiple TXs per band
🌐 4. Wi-Fi Direct Validator Node
Use as a hub between nearby OTAwallet users
✅ Validate TXs
✅ Forward to thetisd over local RPC if networked
✅ Host hot-cold airgap handoff zones
🔐 ✅ Why This Works:
You’re not relying on centralized validators
Phones can validate within local quorum/rules
OTAwallet becomes both a wallet and a mobile fallback validator
