👀 Holy Shit! Blossom stores the app bytes, Citrine stores the manifest and the kind1 note announces it, the naddr is the bridge between the two and Amber signed all three pieces (the blossom blob, the manifest and the note). Amethyst is rendering the kind1 note from Citrine tor relay placed in my outbox. The nostr: naddr in the content is a nip19 reference and the a tag points at the manifest coordinate 30078:<pubkey>: tip-calculator. Any The Glass user can REQ the manifest from the relay, verify the scope hash, GET /<sha256> the artifact from blossom and run it in the sandbox! The artifact is the mini-app's self contained html on blossom, the manifest is the metadata on Citrine, the announcement is the kind1 social note 🔥 View quoted note →

The surface is a commodity, the spine is the product.

This is a crazy outcome I did not plan on! I asked The Glass 🪩 for a simple note taking app and it one shotted a Kind1 publisher lmfao! This is fucking wild! View quoted note →

The Glass 🪩 is getting so clean 🫧

Talk → it resolves → the lightest artifact appears → the durable spine keeps what matters 🪩

You don't need to write, build, publish and download a million apps. You just need a surface and a state!

You just ask The Glass 🪩 and it appears! The generated app on The Glass is a nostr event! The data is signed by Amber and sent to Citrine!

The Glass 🪩

The Glass🪩 A **generative surface** for Android. You ask for something in ordinary words, it resolves to the lightest artifact that can do the job, a declarative L-0 view, a portable L-1 mini app, or a generated L-2 web app, runs a opaque origin sandbox with no network, and keeps its state as kind 30078 nostr events on the user's own Citrine relay. Private provider is the substrate and is a separate application. It owns the identity, amber, nip 55, the wallet, attested inference from Routstr D, the local relay citrine, and the on-device build chain. This repo links nothing from it. The surface reaches compute only through the host's binder bridge to private providers exported service. The Glass surface never holds keys, and never does crypto. No Android, Intense, Nip55, Nip46 or Curve Crypto in the surface renderer. Host services arrive through the adapters, never by reaching into app. The host consumes the surface only as assets. Ask for what you need. It appears. Throw it away. If you need to keep it, keep it. Really want to share with someone, upload to blossom. No need to build apks, publish to app stores for simple things. The app is a nostr event. The surface is transient, the state is yours.

Surface is the commodity; the spine is the product. 🪩+🔐 View quoted note →

The Glass 🪩 A generative surface over a durable personal substrate ( Private Provider + Citrine + Amber ) The Glass turns a plain language ask into the lightest artifact that can do the job -- a declarative view, a reviewed mini-app or a generated one -- sandboxed with no network, keeping its state as ordinary Nostr events on your own relay. It runs end-to-end on android now: ask - > resolve - > generate - > sign ( nip55/Amber) - > publish - > reopen with the state intact. The artifact is disposable; the events are not!

The Glass 🪩 Surface is the commodity, the spine is the product.

Chat + Pi Agent + Ngit Workspace + Wallet + Monitor

Generation is commoditized, and Nostr already made data portable — so the scarce layer is the spine: identity, event graph, wallet, scope, compute, outliving every surface. The Glass makes a view signed, addressable JSON that a generic renderer executes under substrate-enforced scope, so a surface never holds your key or sees your whole store. The app *is* the event: share it, fork it by replying. Surface is the commodity; the spine is the product. Stay tuned 👀

I ate the dogfood to make Private Provider 🐶 ▪️ I only used @routstr to access open weight SI models ▪️ I paid per query for inference in #bitcoin #cashu ▪️ I used open source Pi Agent on Linux ▪️ I signed remotely with Amber for every #ngit action ▪️ I published the code via ngit to blossom servers ▪️ I published the app to Zapstore ▪️ I made an nsite the official project page The entire project is nostr native freedom tech ✅

In its simplest form, Private Provider is a mobile Super Intellingence chat app. Choose any model and pay per query in #cashu to speak with it ✅ View quoted note →

Use any model you want with no subscriptions or kyc

The original inspiration of the app was so that I could use GrapheneOS to agentically code with Pi and Routstrd. I wanted to break free from the laptop and VPS connections. I wanted it all local. I wanted to just talk to it right here. So I put it all in my pocket. TEE SI via @routstr + Pi Agent + #ngit + #cashu all in one app on Android. @Private Provider.nsite.lol

Develop in private. Publish without permission.

Private Provider v0.7.7 🔐 ▪️Internal security and reliability updates

Zapstore

Private Provider — Zapstore

Private Provider is an Android app that runs a full ARM64 Linux runtime — routstrd, Node, Bun, the Pi coding agent, git, ngit and a real shell to...