Monetize your app without ads, paywalls, or data sales.
Your users granted Bluetooth® and location so your features work. The Encrypted Energy SDK puts those grants to work between features: it hears BLE packets from sensor networks, stamps them with a fresh fix, and relays them up. Every device your users' phones hear first pays a discovery bounty, in Bitcoin, to your org. Your users opt in once, and nothing else about your app changes.
2 lines of code · Apache-2.0 · Pays in Lightning sats
You built the app. Monetizing it shouldn't wreck it.
The median app earns under $50 a month. Maybe 5% of users ever pay for anything, and every ad you bolt on costs you reviews, retention, and a little pride. If your app runs a staffing crew or a delivery fleet, it earns nothing at all: it's a cost center with a login screen.
Meanwhile the permissions are granted and the radio sits idle. That idle radio is ground coverage an open network will pay for.
A whole lot of Bluetooth packets are looking for a home.
Asset trackers, environmental sensors, shipment tags. Billions of cheap radios that need a ground gateway to reach the cloud. AirTags solve this in cities by riding on a worldwide fleet of smartphones, but most of the world doesn't have that. Open Bluetooth networks are filling in the gaps, and they need ground coverage from phones that are already out there moving around. Apple's fleet only listens for Apple's tags; everything else needs an open one. Your users carry exactly that, the same trick AirTags pull, working for an open network instead.
Where it fits best.
The SDK never asks for anything. It only wakes up if your app already holds Bluetooth and location grants, so it fits apps that hold them for real features.
Apps on the move.
- Driving apps: OBD scanners, EV companions, trip logs, dashcams
- Fitness and outdoors: running, cycling, golf GPS, hiking
- Wearable and tracker companions with a standing BLE link
- Workforce apps: staffing, delivery, field service, retail ops
Apps built to earn.
- Rewarded and earn apps: pass the revenue through to your users as a new earn stream
- Move-to-earn and step counters that already track motion
- Any app where "your phone earns while you go about your day" is the pitch
Rule of thumb: if your users' phones cross a city with your app installed, there's revenue in the radio. A delivery driver's route sweeps more airspace in a shift than a fixed gateway hears in a month.
Built to survive App Review. Yours and theirs.
SDKs that quietly harvested location got their host apps banned, and they earned it. We designed against that history. The packet payload is encrypted by the device owner's key before your app ever hears it: we can't read it and neither can you. What travels in the clear is the location stamp that proves where coverage happened. We use it to pay bounties and draw the coverage map, we don't sell it, and the legal page says so in writing.
The SDK never prompts, never throws, and never starts a service of its own. Your lifecycle drives it, and a remote kill switch pauses every install if you ever want out. You also get the user-disclosure copy and the exact data-safety wording for both stores to ship with it.
The code is Apache-2.0. Your counsel can read every line, and so can you.
How the money works.
First-to-forward bounties are live. Every distinct BLE broadcast identifier your installs hear first in a UTC day mints a sat. Earnings pool at the org level across every install, settlement runs daily at 00:05 UTC, and once your org clears 1,000 sats they land at a Lightning address you control: no custody, no IOU, no off-chain promise we can renege on.
One honest heads-up: beacon fleets are still building out, so early coverage runs ahead of early revenue. That's exactly why we're signing founding apps now, on terms that reward being early. Tell us about your app and we'll walk you through the math for your install base.
Three steps. Then it runs.
An afternoon from signup to a build with a new revenue line.
Sign up
Email and a password. Then mint an org key, formatted ee_org_…, and your backend provisions a gateway identity per install.
Add the SDK
2 lines from your existing service on Android, the same 2 at app launch on iOS. Zero dependencies on either platform. The SDK page has the snippets.
Point the payouts
Set your org's Lightning address and daily settlement does the rest. Watch packets, devices, and sats per install on the dashboard.
No app of your own? Run a gateway yourself.
The network started with people running gateways on their own phones and Umbrels, and that path isn't going anywhere. Install the EE Gateway app, paste a token, and the phone in your pocket earns the same bounties the SDK does. Fleet operator without your own app? A spare phone at each site, or the app on every work phone, does the same job.