Check out my new game -

Play Hang On, Fren on Gamestr

An endless Riviera Vespa road-tribute starring DNI. Grab roses, don

Am I the first person signing Amethyst notes on nostr with an ESP32 on a desk in another country???

Hello Cambium

If anyone is interested in the freedom tech I’m building and you’re at BTC Prague give me a shout and we can chat

Need to chill before the 600 billion party? Check out these tunes I made

Proton Drive

Securely store, share, and access your important files and photos. Anytime, anywhere.

Busted 😂 View quoted note →

Awesome to win the Grand Prize, if you want to see what you could do with nostr-veil check out the use cases page I’ve been working on

nostr-veil use-case atlas

Anonymous threshold-backed NIP-85 assertions for moderation, source corroboration, relays, software review, onboarding, and more.

View quoted note →

Pallasite — completed all 24 specimens + Event Horizon in 2:11. Shoot rocks. Stack sats. #pallasite

Hey there - I’m looking for a couple more references for

GitHub

GitHub - forgesworn/heartwood: Open-source Nostr signing software built on nsec-tree. Runs on cheap ARM Linux boards. NIP-46 remote signing over Nostr relays, unlimited unlinkable personas from one mnemonic.

Open-source Nostr signing software built on nsec-tree. Runs on cheap ARM Linux boards. NIP-46 remote signing over Nostr relays, unlimited unlinkabl...

for my submission for an OpenSats grant - reference should be sent to references@opensats.org with the subject line of “Reference letter for Heartwood by The Crypto Donkey”

Test

Big thanks to @ChopperBTC for backing ForgeSworn on Geyser! Your support keeps open-source sovereign identity tools moving forward. Every sat counts.

Bitcoin Crowdfunding for New Ideas and Humanitarian Causes | Geyser

Geyser helps people launch new Bitcoin project ideas and fund humanitarian causes worldwide, accelerating adoption through transparent crowdfunding.

Heartwood — NIP-46 signing appliance on a Raspberry Pi Just shipped a working NIP-46 bunker running on a Pi. Your nsec lives on the device, never leaves. Clients (NostrHub, Amethyst, etc.) connect via relays — confirmed working with NostrHub today. As far as we can tell, this is the first purpose-built Pi signing appliance for Nostr. What it does: - Holds your nsec on a Pi behind a hardened systemd sandbox - Runs a NIP-46 bunker daemon that signs events on your behalf - Local web UI for config (key import, relay management, password protection) - Bunker mode preserves your existing npub — no key migration needed Stack: Rust (core crypto, web UI) + lightweight Node sidecar (NIP-46 relay listener using nostr-tools) Quickstart and source:

GitHub

GitHub - forgesworn/heartwood: Open-source Nostr signing software built on nsec-tree. Runs on cheap ARM Linux boards. NIP-46 remote signing over Nostr relays, unlimited unlinkable personas from one mnemonic.

Open-source Nostr signing software built on nsec-tree. Runs on cheap ARM Linux boards. NIP-46 remote signing over Nostr relays, unlimited unlinkabl...

Looking for feedback from anyone running NIP-46 bunkers or building signing infrastructure. #nostr #nip46 #heartwood #bunker #raspberrypi #bitcoin

Three composition guides that prove the NIP ecosystem composes without new kinds. NIP-SLA: service level agreements using NIP-EVIDENCE for breach evidence, NIP-APPROVAL for agreement sign-off, and NIP-DISPUTES for escalation. NIP-COMMUNITY-GOVERNANCE: community decision-making using NIP-51 lists for membership, NIP-CONSENSUS for voting, and NIP-EVIDENCE for proposal documentation. NIP-REFERRAL-ROUTING: institutional referral handoffs using NIP-51 for referral networks and NIP-APPROVAL for acceptance. Healthcare, legal aid, social services. NIP-ORACLE (incubating; kinds 30543, 30547, 30548, 30549): oracle-based dispute resolution. External data feeds for automated dispute adjudication. Incubating because cross-domain demand is still emerging. https://github.com/forgesworn/nip-drafts/blob/main/NIP-SLA.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-COMMUNITY-GOVERNANCE.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-REFERRAL-ROUTING.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-ORACLE.md

Four NIPs for the physical world. NIP-CRAFTS (kind 30401): living technique records for craft skills. Safety notes, materials, tools, difficulty rating, media. Wikipedia for hands-on skills, signed by practitioners and discoverable by trade, material, or difficulty. NIP-PROVENANCE (kind 30404): product and supply chain provenance. Where something came from, who handled it, what certifications apply. Composes with NIP-CUSTODY for multi-leg tracking and NIP-VA for certification attestations. NIP-SCARCITY (kind 30599): workforce shortage signals. When a region lacks qualified practitioners, anyone can publish a scarcity signal with severity, affected area, and required qualifications. NIP-MENTORSHIP: no new kinds. Extends NIP-TRUST's Provider Endorsement (30517) with mentorship tags: competency area, proficiency level, training duration, assessment method. "I trained this person in lime plastering for 6 months and assessed them as competent" carries more weight than "I vouch for this person." Build with this: a heritage conservation archive where traditional building techniques are documented by master craftspeople. A food provenance system where farm-to-fork is verifiable. A workforce intelligence dashboard showing where training investment is most needed. https://github.com/forgesworn/nip-drafts/blob/main/NIP-CRAFTS.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-PROVENANCE.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-SCARCITY.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-MENTORSHIP.md

NIP-CHANNELS (kinds 20502, 30565): context-scoped messaging. NIP-17 gives you DMs. NIP-28 gives you public channels. NIP-CHANNELS adds task-scoped messaging: typing indicator (20502, ephemeral) and message status (30565, read receipts). Task messages use NIP-17 with a context_id tag. NIP-DATA-ACCESS (kind 30556): scoped, revocable data access grants. "I grant you access to this data, for this purpose, until this date." Time-bounded, purpose-constrained, revocable. NIP-INVOICING (kind 30588): structured, machine-readable invoices. Line items, tax calculation, payment terms references, due dates. Different from a Lightning invoice: this is a commercial document with an audit trail, not a payment request. NIP-L402-SERVICES (kind 31402): paid API discovery on Nostr. If you run an API behind a Lightning paywall, how do people find it? Kind 31402 announces your service: endpoint, pricing, supported methods, authentication. Eight implementations already use this kind in production. Build with this: an AI inference marketplace discoverable and payable via Lightning. A task management app with private scoped chat. A medical system where patients grant doctors temporary record access. An accounting tool that generates tax-ready invoices from Nostr payment events. https://github.com/forgesworn/nip-drafts/blob/main/NIP-CHANNELS.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-DATA-ACCESS.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-INVOICING.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-L402-SERVICES.md

NIP-PROVIDER-PROFILES (kinds 30510, 30511): service provider discovery. Provider Profile (30510): an addressable event declaring capabilities, credentials, coverage areas, and service terms. Discoverable by geohash, capability, or category. Coordinator Bond (30511): declares a coordinator's financial commitment, fee structure, and SLA. NIP-BOOKING (kinds 30582, 30583, 30584): calendar availability and slot booking. Availability Calendar (30582): providers publish when they are free, with duration, capacity, pricing, and cancellation policies. Recurrence via RFC 5545 tags. Booking Slot (30583): requesters book a specific time. Booking Cancellation (30584): either party cancels with a reason. Confirmation uses NIP-APPROVAL; rescheduling uses NIP-VARIATION. NIP-VARIATION (kind 30579): scope and price change management. When agreed work needs to change mid-project, a variation request captures what changed, why, and the cost impact. Variation quotes use NIP-QUOTE; variation approvals use NIP-APPROVAL. One new kind, composed with existing primitives. Build with this: a tutoring platform with calendar-based booking. A local services directory where providers are discoverable by skill and location. A construction project tracker where scope changes carry formal cost impact documentation. https://github.com/forgesworn/nip-drafts/blob/main/NIP-PROVIDER-PROFILES.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-BOOKING.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-VARIATION.md

NIP-TRUST (kinds 30515, 30517): portable trust networks. NIP-02 tells you who someone follows. NIP-51 lets you organise pubkeys. Neither covers "I trusted this provider, now I don't, and here's why" or "I vouch for this person's plumbing work." Trust Revocation (30515): explicit trust removal with reason-tiered visibility. Public reasons vs NIP-44 encrypted private reasons. Append-only audit trail. Provider Endorsement (30517): provider-to-provider vouching with category, context, and competency assessment. Solves the cold-start problem. NIP-DISPUTES (kinds 7543, 30545): dispute resolution. Dispute Claim (7543) is a regular event (immutable; you cannot silently edit a claim after filing). Dispute Resolution (30545) is the mediator's ruling with outcome, reasoning, and financial remedy. Both parties submit NIP-EVIDENCE records; the mediator reviews and publishes the resolution. NIP-REPUTATION (kind 30520): structured ratings tied to real transactions. One rating per party per transaction, enforced by d-tag uniqueness. Each rating references a completion event as proof the rater actually participated. Weighted criteria with domain-specific weights. Review responses use NIP-22 Comments. Build with this: a tradesperson recommendation network with real professional endorsements. A marketplace with verifiable ratings and built-in dispute resolution. A community where revoking trust is a transparent, auditable action. https://github.com/forgesworn/nip-drafts/blob/main/NIP-TRUST.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-DISPUTES.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-REPUTATION.md

NIP-QUOTE (kinds 30530, 30531): structured pricing for Nostr. NIP-99 gives you classified listings with a price tag. NIP-QUOTE gives you the negotiation layer. A provider publishes a structured quote with line items, tax, validity window, and payment method options. Multiple providers can quote the same request. Once accepted, Payment Terms (kind 30531) lock in the deal: milestones, deposits, streaming rates, cancellation schedules. NIP-ESCROW (kinds 30532, 30533, 30535): conditional payment coordination. NIP-57 zaps are one-way. Cashu tokens are bearer instruments. Neither gives you "hold these funds until both sides are happy." Lock (30532) commits funds with proof. Settlement (30533) covers all outcomes via a single outcome tag: released, forfeited, partial_forfeit, or expired. Payment Receipt (30535) proves money moved; also handles streaming payments via tick_number and cumulative tags for time-based billing. Payment-rail-agnostic. Events record what happened; money moves on Lightning, Cashu, Strike, Stripe, or whatever rail the parties choose. Build with this: a freelance platform with milestone-based payments and per-deliverable quotes. A peer-to-peer marketplace with buyer protection. A ridesharing app with per-minute streaming receipts. https://github.com/forgesworn/nip-drafts/blob/main/NIP-QUOTE.md https://github.com/forgesworn/nip-drafts/blob/main/NIP-ESCROW.md

Published 20 more Nostr protocol extensions on NostrHub, plus updates to 2 from last week. The full portfolio is now 27 standalone NIPs covering payments, trust, scheduling, disputes, provenance, and more. 40 new event kinds total. Payments: NIP-QUOTE (structured pricing), NIP-ESCROW (conditional payments with settlement outcomes), NIP-INVOICING (machine-readable invoices) Trust: NIP-TRUST (portable trust networks with revocation), NIP-REPUTATION (structured ratings), NIP-DISPUTES (dispute resolution with mediator support) Scheduling: NIP-BOOKING (calendar availability and slot booking), NIP-PROVIDER-PROFILES (service provider discovery) Ecosystem: NIP-CRAFTS (technique documentation), NIP-PROVENANCE (supply chain tracking), NIP-SCARCITY (workforce shortage signals), NIP-MENTORSHIP (training progression) Paid APIs: NIP-L402-SERVICES (Lightning-gated API discovery, 8 production implementations) Three composition guides show how existing NIPs combine without new kinds: SLA monitoring, community governance, institutional referral routing. All standalone. No framework lock-in. Every NIP works independently. Authorship verified with NIP-VA (kind 31000) attestations.

GitHub

GitHub - forgesworn/nip-drafts: 29 Nostr protocol extensions (NIPs) for service coordination, trust, payments, disputes, key hierarchy, resource curation, and paid API discovery. Every NIP works independently -- no platform lock-in.

29 Nostr protocol extensions (NIPs) for service coordination, trust, payments, disputes, key hierarchy, resource curation, and paid API discovery. ...

Every Nostr event is already timestamped. So why a dedicated evidence kind? Because a kind 1 note with a SHA-256 hash in the text is human-readable but not machine-parseable. NIP-EVIDENCE (kind 30578) adds structured metadata that makes evidence filterable, verifiable, and composable. One kind. Tags for: evidence type (photo, video, document, reading, observation), file hash, capture timestamp, geolocation, condition grade, and chain linkage to related events. Not all evidence is file-based. Sensor readings, condition assessments, verbal confirmations, and witnessed observations have no associated file. NIP-94 requires a file URL; NIP-EVIDENCE does not. NIP-03 (OpenTimestamps) proves an event existed at a time. NIP-EVIDENCE adds what was captured, where, when, and under what conditions. The two complement each other. Useful for inspections, insurance claims, compliance audits, dispute resolution, or any workflow where "signed facts" need to be discoverable by type, location, or related event. Build with this: a citizen journalism tool where photos carry verifiable metadata about when and where they were taken. A home renovation log where before/after photos are timestamped and geolocated. A birdwatching app where sightings carry structured evidence. A community mapping project where contributors submit verified survey data. https://github.com/forgesworn/nip-drafts/blob/main/NIP-EVIDENCE.md