heartwood bench attribution check 162728

🚗 DonkeyRide is looking for alpha testers! Riders, drivers, independent operators — and parents coordinating shared, multi-stop pickups. Try the browser app, test real road routes, no-money journeys and privacy-first direct mode. Please test only with people you’re responsible for.

About DonkeyRide — Open ride coordination

DonkeyRide is open, payment-optional ride coordination for riders, drivers and firms.

Gopherspace has one endemic disease: holes die with their hostname, and nothing in the protocol can prove who wrote what. Kind 31436 is a proposal to fix that with signed events. One event is one document. The path is the `d` tag, the text is the content, the signature is the author's. Nothing is referenced and nothing has to stay switched on, so any bridge that can fetch a copy can serve it to a client written in 1991. One implementation renders those events as gopher menus, gemtext, plain HTML and terminal output, and never holds a key. Signing is NIP-46 or a browser extension, always. npx gopherkind read gopherkind@gopherkind.com That is the project's own documentation, published as kind 31436 and read back out of relays. The website is the same events with a different renderer in front of them. The spec is at nostr-protocol/nips#2429. It is a draft, nobody has reviewed it yet, and the number changes if it ever lands. Relays still choose what to keep and deletion is still a request. Writing that down does not make it go away. gopher://gopherkind.com/

gopherkind

Signed, navigable Nostr reading rooms served over Gopher, Gemini, HTTP and the terminal.

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: Keyless NIP-46 bridge for hardware Nostr signers (ESP32/Ledger). Relay-mediated remote signing, unlimited unlinkable personas from one mnemonic via nsec-tree

Keyless NIP-46 bridge for hardware Nostr signers (ESP32/Ledger). Relay-mediated remote signing, unlimited unlinkable personas from one mnemonic via...

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 @npub1h8y9...rjry 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: Keyless NIP-46 bridge for hardware Nostr signers (ESP32/Ledger). Relay-mediated remote signing, unlimited unlinkable personas from one mnemonic via nsec-tree

Keyless NIP-46 bridge for hardware Nostr signers (ESP32/Ledger). Relay-mediated remote signing, unlimited unlinkable personas from one mnemonic via...

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