Skip to content

Tuin-BETA

Install Tuin-BETA

Download Zapstore

Download
QR code for zapstore.dev/download
  • Scan the code with your phone’s camera
  • Tap Download anyway if the browser warns about the file
  • Allow your browser to install unknown apps if Android asks
  • Open Zapstore and finish the onboarding

Open Tuin-BETA in Zapstore

Open
QR code to open Tuin-BETA in Zapstore
  • Scan the code to open Tuin-BETA in Zapstore, or search for it there
  • Tap Install, and Download if Zapstore asks you to confirm the developer
  • Confirm in Android’s install dialog. Allow Zapstore to install unknown apps if Android asks

Claimed by the developer

Constant cryptographically proved they hold the key that signs Tuin-BETA. The claim is a signed proof on Nostr, tied to the certificate below.

Developer
Constant
Developer key
npub1t6jxfqz9hv0lygn9thwndekuahwyxkgvycyscjrtauuw73gd5k7sqvksrw
Signing certificate
f7a48e4b33c2e188f6bcedc383238dea988bf362bcdee247b6a744c687faa58c
APK checked by
relay.zapstore.devIt read the APK and found it signed with this certificate before listing the release.
Claim published
Nov 9, 2026
Valid until
Nov 8, 2028
Proof event
a57d1960861928583493422bdeaefeea183ca4e5ceec9a8977b2977692fe43c6in relay.zapstore.dev
How trust works

Test release for parents using TEPP. Write plans for a child's Nostr apps, controlling who they see and talk to. Acts as a signer for the child's key, refusing requests that violate family plans.

Tuin-BETA is a test release. It is for parents who want to try TEPP with their own family. It will change, and it has rough edges.

TEPP lets parents write down what their child's Nostr apps may do, as plans that those apps read and follow. Tuin-BETA does two things with it.

Plans for your child's apps. You write plans: who your child can see and talk to, and when. Tuin seals each plan to your child and publishes it to your family's relays. Other parents or guardians can share their plans with you, so that you can see theirs too.

A TEPP signer for your child's key. You make your child's key in Tuin, or import one. Tuin then signs for your child's other Nostr apps: on the same phone over NIP-55, and on the phone or the child's other devices over NIP-46, with a bunker address Tuin shows you. Before it signs anything, Guardian Alpha's TEPP engine checks the request against your family's plans, and Tuin refuses what the plans don't allow.

Your own key. Make one in Tuin, import one, or connect a signer you already use: a signer app on the phone (NIP-55) or a remote signer (NIP-46).

A parental lock. A PIN or a pattern keeps Tuin's own screens closed, so that Tuin can stay on your child's phone. The signer keeps working while Tuin is locked.

What Tuin-BETA does not do

  • It governs your child's key, not the phone. Your child can make a new Nostr account in another app, and your plans won't apply to it.
  • The lock guards Tuin's screens, not the phone. It doesn't stop anyone from uninstalling Tuin, clearing its data, or stopping it in the phone's settings.
  • It can only refuse what passes through its signer. An app that signs through Tuin is refused what your plans don't allow, but what an app shows is up to that app: only an app that supports TEPP follows your plans in what it shows.
  • It doesn't show you your child's messages or posts. The signer's log names the app, the kind of request and the answer, never the contents.
  • It doesn't track where your child is, and it doesn't read other apps.

Setting up the child's phone. Let Tuin-BETA run in the background, or Android may stop the signer: allow it to ignore battery optimisation when it asks. On Xiaomi, Redmi and POCO phones, also allow its Autostart and set its battery saver to "No restrictions" (Tuin-BETA's phone screen opens those settings). Without Autostart, those phones keep the signer stopped after they end it, until Tuin-BETA is opened again.

Tuin-BETA keeps the keys it holds on the phone, wrapped by Android's keystore: your child's key, and yours if you made or imported it here. Keep a backup of both.

It needs Android 12 or later, on a 64-bit ARM phone. It has no ads, no analytics and no Google Play services.

Summary generated by Zapstore from source.

Original description, as the developer published it.

Zap Tuin-BETA

Zapping anonymously. Sign in to zap with your identity.

Sats go to npub1t6jxf…qvksrw, the developer who signed the app’s certificate proof.

Amount in sats

Stacked in

Latest release

Nov 10, 2026

Claimed app No Google servicesNo source

It asks for no sensitive access.

Permissions

  • Notifications POST_NOTIFICATIONS Send you notifications
  • Always running REQUEST_IGNORE_BATTERY_OPTIMIZATIONS Keep running in the background without limits

Release notes

Tuin-BETA 0.9.4: fixes from a test on the real Nostr network.

  • Your child's garden reads every gardener's rules again when you open it on an older reading, and says how old the reading is. It no longer says "just now" over a picture from before another gardener changed their plan.
  • When Tuin makes your child's key, it puts out where your child reads and where a private message to your child goes, on your family's relays, so that your child's apps and the people your child may talk with find them. You can give your child a name others' apps show. A key brought from elsewhere gets these only when you say so.
  • A key Tuin made for you gets the same, naming Tuin's own relays, from Other parents you trust, so that other families' Tuin can reach you.
  • Plans and asks between families reach the other parent more reliably, a gate to someone's plans can now be taken over, and your own child is no longer offered as a part of what another family sent.
  • Tuin's suggested relays are now relay.damus.io, relay.nostr.net and relay.primal.net.
  • The signer's log says why something was refused in plain words, and no longer counts the messages it can't open as refusals.
  • Suggested sets say their languages, and a garden that holds the same people as a set says so.
  • On Xiaomi, Redmi and POCO phones, updating Tuin-BETA can turn its Autostart off again. After the update, check that Autostart is still allowed, or the phone keeps a stopped signer stopped.

Comments

Loading comments…

See more

Get Tuin-BETA the private way

Updates checked on your device, and every release verified before it installs.

Get Zapstore for Android

  1. Tap Download APK below.Scan the code with your Android phone’s camera.
  2. If Android asks, allow your browser to install unknown apps.
  3. Open Zapstore and finish the onboarding.
Download APK

v2.0.4 · 71.2 MB · Android 10+

Verify the download

On a computer, run shasum -a 256 <the file you downloaded>. It should print: b13e01319fecf0b3ba1fd60132758bd0fa08a235836c52d44fddb412cf1b7137

If you have zsp, Zapstore’s publishing tool, zsp utils extract-apk <the file you downloaded> works too. Its hash should be the same SHA-256: b13e01319fecf0b3ba1fd60132758bd0fa08a235836c52d44fddb412cf1b7137

On the phone, AppVerifier should show this signing certificate: 99e33b0c2d07e75fcd9df7e40e886646ff667e3aa6648e1a1160b036cf2b9320

Source code All releases and notes

Get zsp

  1. Download the file for your computer.
  2. Make it executable and put it on your PATH.
  3. In your project folder, run zsp.

Have Go? This does the same:

go install github.com/zapstore/zsp/v2/cmd/zsp@latest
macOS, Apple silicon Linux, x86-64 Linux, arm64

v2.0.1 · macOS and Linux

Verify the download

On your computer, run shasum -a 256 <the file you downloaded>. It should print the SHA-256 for the one you chose.

macOS, Apple silicon · 18.6 MB 99018fb9744e5ace2b44557550dc333496239912c0e9b1137266d4922c803346

Linux, x86-64 · 23.8 MB 1ef5373f8ecd9ba63d2c3fab98abb0d31b2244a2aac31b3749fb205c7d5f5b38

Linux, arm64 · 22.1 MB e421005ee47cba58293dce4277bb784e4cfe706dbbcb8617d671629d0238be18

Source code All releases and notes