josh's avatar
josh
josh@westernbtc.com
npub1pc57...dmza
Loved by Jesus
josh's avatar
josh 8 hours ago
WORD5 #552 4/6 ⬛⬛⬛🟧🟧 🟪⬛⬛⬛🟪 🟪⬛⬛🟧🟪 🟪🟪🟪🟪🟪
WORD5
josh's avatar
josh 12 hours ago
Titan browser update - demo at the bottom 👇 ⚠️ v0.1.0 users must install this update manually. Checkout the release here:
GitHub
Release v0.1.3 · btcjt/titan
Full Changelog: v0.1.2...v0.1.3
 What's new across 0.1.1, 0.1.2, and 0.1.3? Built-in Nostr signer (NIP-07) — create or import an nsec once, and window.nostr works on every nsite automatically. No external extensions needed. Your nsec is stored in the OS keychain and never leaves the Rust process. Per-site permission model — every signature, encrypt, and decrypt request goes through a focus-stealing approval prompt with the full event preview, kind warnings, and scope selector (allow once / for session / always). Stored permissions are manageable from the signer panel. Auto-updater — from 0.1.1 onwards, Titan checks for updates on startup and shows an in-app banner. The install-and-restart flow works end-to-end with minisign-verified signed artifacts. Existing v0.1.1 installs should get v0.1.3 automatically. Dev console REPL — top-level await, up/down history, evaluates in the active tab's context. Try await window.nostr.getPublicKey(). Rust log forwarding — internal tracing events now appear in the dev console, making Windows debugging actually possible. Site info panel — click the 🔒 icon to see Bitcoin name, pubkey, owner UTXO, relays, and full profile metadata for any nsite. Interactive register/transfer — on nsite://titan, step-by-step bitcoin-cli command builder with wallet name support and a "first time? how to fund your wallet" walkthrough. Kind 1129 name history events — the NSIT indexer now publishes non-replaceable history events alongside the replaceable kind 35129 state events, giving names a full chain of custody. Windows improvements — WebView2 runtime bundled offline, blank-screen fix. NIP extension proposal — extending NIP-5A with the Bitcoin Name Resolution protocol is open at
GitHub
NIP-5A: Add Bitcoin Name Resolution (NSIT) by btcjt · Pull Request #2306 · nostr-protocol/nips
Summary Extends NIP-5A (Pubkey Static Websites) with a Bitcoin-native name system that maps human-readable names to Nostr pubkeys using OP_RETURN t...
josh's avatar
josh 21 hours ago
Next release will have button for viewing information about the nsite. @Jared Logan thanks for trying out NSIT name registration.
josh's avatar
josh 21 hours ago
3 more names forever taken. "sandwich" 😂. image
josh's avatar
josh 2 days ago
WORD5 #551 3/6 ⬛⬛⬛⬛⬛ ⬛⬛🟪🟪🟪 🟪🟪🟪🟪🟪
WORD5
josh's avatar
josh 2 days ago
4 more names taken forever. image
josh's avatar
josh 2 days ago
3 names registered. Forever registered. Yes, you can trade them too. image
josh's avatar
josh 2 days ago
I'm giving everybody a 1 hour head start. Two names have been registered for testing: `titan` and `bitcoin`. Everything else is unclaimed. Keep reading to see what I'm talking about. https://2zrgjemvgxppn2jwgm61w6yrqqlcmm8njvhby68a9cj7ooo5phshakespeare.nsite.lol/ NSite's currently have two glaring problems. DNS dependency and names you can't remember. Try to type that from memory. Titan is a native desktop browser that resolves nsite:// URLs. See the video below. When you type nsite://titan, the browser looks up "titan" in a name index, gets the associated Nostr pubkey, fetches the site manifest from relays, downloads the content from Blossom servers, and renders it. No DNS. No certificates. No hosting providers. Like normal domain names, I bet you can remember nsite://titan. You can also use the underlying npub directly for navigating. E.g., nsite://2zrgjemvgxppn2jwgm61w6yrqqlcmm8njvhby68a9cj7ooo5phshakespeare. Titan is still in early alpha. It's missing essential features and will have bugs. Feel free to contribute. The name "titan" is registered on Bitcoin using an OP_RETURN transaction. As long as it's up to me, it's permanent. The protocol allows for transferring this name. You can learn more about this in the README and docs (https://github.com/btcjt/titan/tree/main/docs). How it works: Every name registration is a single Bitcoin transaction with an OP_RETURN output containing an NSIT payload — a protocol prefix, the name, and the Nostr pubkey it points to. First-in-chain wins. The first valid registration claims the name. Duplicates are ignored. The blockchain is the arbiter. Names are controlled by a Bitcoin UTXO. Whoever can spend that output controls the name — update the pubkey or hand off ownership entirely. Every step from name to rendered page is cryptographically verified. Name to pubkey is secured by Bitcoin proof-of-work. Pubkey to manifest is signed by the site owner's Nostr key. Manifest to content is addressed by SHA256 hash. The browser doesn't need Bitcoin Core. Name lookups happen through Nostr events published by an indexer service that watches the blockchain. Anyone can -- and maybe should -- run their own indexer. The Titan browser uses the titan npub by default, but you can change it to point to yours. You can register names at nsite://titan/register — it walks you through step-by-step generating the register transaction using Bitcoin Core (bitcoin-cli). nsite:// is an open scheme. Other browsers can implement it. Other indexers can publish the same name events. Titan is the reference client. Two names registered for testing: `titan` and `bitcoin`. Everything else is unclaimed. Insert cringy Satoshi quote about getting some -- just in case. Open source:
GitHub
GitHub - btcjt/titan: A native nsite:// browser for the Nostr web. Named after Titan, moon of Saturn.
A native nsite:// browser for the Nostr web. Named after Titan, moon of Saturn. - btcjt/titan
↑