Build and share a modest Android app under a chosen identity using phone-operated agents, encrypted messaging, ecash, and project-specific signing keys.
Build something useful and give it to the world. Whether you reveal your name should be up to you.
In his 1993 manifesto, Eric Hughes tied privacy to choosing what we disclose. "Cypherpunks write code," he declared, calling for tools shared freely worldwide. That ambition reaches beyond experienced programmers: a beginner can now build and share a modest Android app under a chosen identity, directing an open-source coding agent from a phone.
I want that freedom available to anyone with an idea worth trying. A laptop handles implementation and builds; you make decisions and test the result. Payment, messaging and publishing can proceed without enrolling your personal identity, though each has limits. Once configured, the laptop can stay home while you take your phone into the forest.
Leave the computer at home
Give the laptop power, stable internet and permission to stay awake. Install Android build tools and an open-source coding harness such as Hermes or OpenCode. It needs enough memory and disk space for Android builds; remote inference keeps model hardware requirements elsewhere.
Use Hermes for this worked route because its MDK connector supports documents and APK attachments. The agent can edit files, run builds and attempt fixes after reading errors. Keep it in a separate user account or isolated environment, with access to the project and no access to personal documents or unrelated credentials.
Pay for AI with electronic cash
Routstr nostr:npub130mznv74rxs032peqym6g3wqavh472623mt3z5w73xq9r6qqdufs7ql29s provides model access funded through Cashu ecash or Lightning. Fund a session and configure the agent to use its API. Routstr requires no personal account or identity verification; inference remains paid, and selected models may be proprietary. The provider sees your prompts, so exclude identifying information and secrets.
Cashu nostr:npub17fzkepv3q2szsvdefmws9znhhpzx9kvhgl2p3jqk9tm5z6sjalvsg49yxv uses blind signatures to separate token issuance from spending. The mint custodies the backing funds, so hold only a working balance you are comfortable entrusting to it.
Talk to your agent through White Noise
Install White Noise nostr:npub1whtn0s68y3cs98zysa4nxrfzss5g5snhndv35tk5m2sudsr7ltms48r3ec from Zapstore and create a fresh messaging identity. It requires no phone number or email; the profile can remain unnamed. Give the agent a separate identity.
Marmot nostr:npub1marm0t9qkmv8lq7pe7vdx60ed8fl2d876a2ytk3ade208dlyfweqg5r6m9 supplies the encrypted messaging protocol used by the agent connector. Authorize your messaging identity as an allowed sender so strangers cannot command the laptop.
Both devices connect outward to Nostr relays, avoiding public ingress or router port forwarding. Marmot encrypts the phone-to-agent conversation, while relays can still observe IP metadata; network anonymity needs separate protection. Encryption also stops at the agent: instructions forwarded to cloud inference reach that provider. See White Noise's privacy documentation.
Enable disappearing messages if you want shorter phone retention; local project files and agent memory follow separate retention rules.
Build something small, then try it
Suppose you want an offline notes app that opens quickly and exports your writing. Tell the agent what the first version should do and which features to leave out. Ask for an installable Android package, delivered through the chat.
Install the APK and write a note. Close and reopen the app to check persistence, then try exporting. Report the actual failure when something breaks: an empty export file gives the agent a clearer target than "it doesn't work." Test the next build against the same requirement.
You can begin without years of training because the agent handles much of the implementation. Keep learning: ask it to explain changes and judge the app's behavior yourself. AI-produced code needs review; apps handling sensitive data or money need experienced security scrutiny before people depend on them. Keep release approval separate from build completion.
Give the project its own identity
Install Amber nostr:npub1am3ermkr250dywukzqnaug64cred3x5jht6f3kdhfp3h0rgtjlpqecxrv7 from Zapstore and create a dedicated project key on Android. Publish a profile with your chosen project name. Those details are public; your legal name can stay out.
Amber's NIP-46 remote signing lets the agent request scoped signatures while the publishing key stays on your phone. Grant the authority it needs and keep the pairing token secret. The raw nsec stays out of chat.
Back up that identity and the independent APK signing keystore, which Android needs for updates. Have the agent document both before release. Check Git author details and screenshots for personal information.
Publish source using ngit and browse it through GitWorkshop; their shared maintainer, also associated with the related GRASP standard, is DanConwayDev nostr:npub15qydau2hjma6ngxkl2cyar74wzyjshvl65za5k5rl69264ar2exs5cyejr. GRASP servers host Git objects, while Nostr carries collaboration metadata. ngit's documented bunker support lets the publishing key remain in Amber.
Zapstore nostr:npub10r8xl2njyepcw2zwv3a6dyufj4e4ajx86hz6v4ehu4gnpupxxp7stjt2p8 provides zsp to accept a local APK, upload artifacts and sign Nostr release metadata, including through a bunker.
Check catalog admission before promising availability: the default catalog requires supported conventional repository verification for a fresh key, unless reputation or allowlisting qualifies it. An ngit-only repository with a fresh key is not automatically accepted; use a supported repository for verification or an alternative compatible catalog.
Announce the approved release from the project identity with app and source links. The same identity gives readers continuity across updates without requiring your legal name.
Take your work outside
A laptop can compile at home while you walk beneath the trees. When you stop, open the chat, test the latest build and send a correction. More of your working day can happen somewhere you chose.
For decades, cypherpunks have imagined a world where useful software and private exchange are available to everyone. Now we have more of the tools to help build it ourselves, with an old computer at home and a phone in our pocket.
I want more people to try. Pick a small problem and build a tool that solves it. Share it under a name you chose. We can build the tools for a freer world with a phone in our pocket and our feet on a forest path. That future is close enough to start working on today.