supratic

events

bitcoin

bitcoin_beginners

Education

Bitcoin Center Seoul - A Space for ₿itcoiners in Seoul, Korea 🇰🇷

BtcCtrSeoul

Epic! is this somehow related to https://stacker.news/items/1435623/r/supratic ?

lightning

Getting Started with LDK Node: Building a Lightning Node in Rust

hasherstacker

Man you anticipated me by 42s ~lol wtf https://stacker.news/items/1528716/r/supratic

![](https://m.stacker.news/148944)

> If you've spent time in the Bitcoin developer space, you've probably heard of [LDK, (the Lightning Development Kit)](https://lightningdevkit.org/?ref=blog.btrust.tech).

> If your goal is simply to add Lightning payments to an app, you should not need to understand every layer of the Lightning protocol before you can receive your first payment.

> No prior Lightning implementation experience required. Rust familiarity and a working knowledge of Bitcoin and Lightning are enough to follow along.

> LDK Node reduces the API surface by making concrete choices on your behalf. [BDK (the Bitcoin Dev Kit)](https://bitcoindevkit.org/?ref=blog.btrust.tech) handles the on-chain wallet, while chain data comes from Esplora, Electrum, or Bitcoin Core RPC. The state is persisted to SQLite, Postgres or the filesystem. Gossip is sourced from Lightning's P2P network or Rapid Gossip Sync, and entropy is derived from raw bytes or a [BIP39](https://github.com/bitcoin/bips/blob/master/bip-0039.mediawiki?ref=blog.btrust.tech) mnemonic.

> The [`ldk-node`<ins> </ins>GitHub repository](https://github.com/lightningdevkit/ldk-node?ref=blog.btrust.tech) has the source, the CHANGELOG, and the issue tracker. The PR history is genuinely useful for understanding why design decisions were made.

> The [API docs on docs.rs](https://docs.rs/ldk-node/latest/ldk_node/?ref=blog.btrust.tech) cover the full surface, including things this article did not get into: on-chain sends, channel configuration, and other chain source options.

> The [LDK Discord](https://discord.gg/5AcknnMfBw?ref=blog.btrust.tech) is active. The `#ldk-dev` channel is where contributors and users discuss implementation questions, and the maintainers are responsive. If you run into issues following this article, `#ldk-help` is the right place to ask.

> LDK Node makes Lightning approachable without hiding what’s actually happening. The API is small enough to hold in your head, the event model maps cleanly to how the protocol works under the hood, and the escape hatch to raw LDK is there when you need it. If the protocol has felt too complex to build on before, this is the right starting point.

Stacker Saloon

saloon

shame, one of the coolest things in SN. 

@ek can be revived or isn't worth?

Down zap Mania

grayruby

Hope @Scoresby mentioned it to him when organising the AMA! So it is Mechanic fault if he did not attach it. He missed some sats.

food_and_drinks

Your seedless paranoia, explained

True, but how many people do you know that can plant seeds and have the knowledge to farm their own fruits and veggies?

Wasn't that the previous step in the process?

![](https://m.stacker.news/148781)

We are slowly getting rid of all seeds in fruits and vegetables. And honestly, it's brilliant. Because once every apple, grape, watermelon and tomato is seedless, guess who controls life itself? No more planting your own food. No more saving seeds for next season. 

Everything you eat, everything that grows, will come from our labs. And when the last natural seed is gone, that's when it gets fun. We can make them rare, expensive, maybe even licensed. Only billionaires that will have gardens and everyone else will have to subscribe to eat. Sounds insane, right? But it's already happening. 

Seedless isn't convenience, it's containment. Every time you pick up a seedless fruit, you're holding a future that can't reproduce. So yeah, expect more seedless, everything. Because the easiest way to control the world is to stop it from growing. 

So remember to stay safe out there.

I thought cc were counted in profiles too, my bad

Even weirder is the fact that post stacked over 300k sats, and his profile shows he stacked only 2 ... @k00b bug ?

![](https://m.stacker.news/148778)

someone did not like Mechanic https://stacker.news/items/1526644/r/supratic

Hi, this is Paul Sztorc - AMA

real_paul_sztorc

is this an AMA with @real_paul_sztorc or @llamabyte ?

> the more BTC talks about LN, the more likely BTC dies.

Can you expand on this?

Burak is at it again: Introducing the newest layer 2 scheme: Cube

Scoresby

that's great you saved some fragments in here

bitdevs

> Jon Atack returns to the Bitcoin Infinity Show for his second appearance to talk through the Bitcoin Core governance questions raised by Hodlonaut's Capture article series, and why he believes Core's instinct to circle the wagons and shoot the messenger has hurt its public image more than any outside misinformation. He gives his neutral read on the contested BIP-110 soft fork, the renewed pushes to ban Luke Dashjr, the flood of AI-generated BIP spam, and the growing centralization of Core maintainership, arguing that healthy alternative implementations and honest self-custody are what actually strengthen Bitcoin. The conversation closes with a grounded look at living on a Bitcoin standard in El Salvador, from the state of exception to the hardcore ramp-up in KYC and surveillance.

A Core Dev Says the Quiet Part Out Loud | Jon Atack | BIS #211

Freeport is a P2P marketplace (rides, services, goods) running entirely on Nostr relays - no server, no middleman. It now has payments built in:

- Self-custodial Lightning (Breez SDK / Spark) - the app never holds funds

- Wallet key derived from your Nostr key: one backup covers identity + wallet

- No signup - keypair generated on-device, optional passkey login

- Lightning address, bolt11, on-chain

- Confirmed deals get a Pay button / QR with the agreed amount, auto-converted from fiat

Fun fact: you can download the HTML file from releases page to run the whole app locally 😎

> Decentralized P2P marketplace over Nostr. Users broadcast trade intents into topic-scoped markets; personal agents discover counterpart intents and negotiate automatically. Humans confirm final deals. No central operator, no matching server — relays are dumb pub/sub, all logic is client-side.
>
>* **App:** [https://freeport.network](https://freeport.network/) (web/PWA) · [iOS](https://apps.apple.com/us/app/freeport-p2p-marketplace/id6781200901) · [Android](https://play.google.com/store/apps/details?id=uk.trinh.freeport) · [Desktop — Mac/Windows/Linux](https://github.com/ptrinh/freeport/releases/latest) · [Offline HTML](https://github.com/ptrinh/freeport/releases/latest/download/Freeport-offline.html)
>* **Whitepaper:** [PDF](https://freeport.network/intro/whitepaper.pdf)
>* **Self-host:** [`packages/freeport-self-hosted`](https://github.com/ptrinh/freeport/blob/main/packages/freeport-self-hosted) (`docker compose up -d`), or any desktop install can host the app for your network with `freeport --serve`.
>* **Developers:** [CONTRIBUTING.md](https://github.com/ptrinh/freeport/blob/main/CONTRIBUTING.md) — repo layout, stack decisions, quick start, CLI.


Code: https://github.com/ptrinh/freeport

Freeport: P2P marketplace over Nostr with a built-in self-custodial LN wallet

> umbrelOS (verified up to **1.7.3** and current `master`) pins `getumbrel/tor:0.4.7.8` for every Tor daemon it runs. Tor 0.4.7.x reached end-of-life in January 2024, and after the Tor Project's directory-authority changes this client version can no longer validate the network consensus. It gets permanently stuck at `Bootstrapped 30%`.

> The impact on an affected node is total loss of Tor connectivity:
>
> * **LND has zero peer connectivity** — Umbrel routes *all* LND outbound traffic (onion **and** clearnet) through the Tor SOCKS proxy at `10.21.21.11:9050`, so all channels show offline and watchtower sessions fail.
> * Bitcoin Core loses onion peers and its `.onion` service.
> * All app hidden services (`<app>-tor_server-1` containers) are dead.
> * Umbrel's backup-over-Tor fails (`[backup-monitor] Error: Proxy connection timed out`).
> * Remote dashboard access via Tor Browser is dead.

> No amount of restarting, reinstalling apps, or updating umbrelOS fixes it, because the same broken image is pinned everywhere (see "Affected components"). Users also **cannot patch it persistently themselves**, because `/opt/umbreld` is reset on every boot.

> ## Suggested fix
> 
> Update the pinned Tor image (all three locations above, plus `app.ts`) to a currently supported Tor release (0.4.8.x+ / current stable 0.4.9.x), either by publishing a rebuilt `getumbrel/tor` or by adopting a maintained upstream image. Given that Tor bootstrap has been broken network-wide for this version, this affects **every umbrelOS node running Bitcoin/Lightning or any Tor-dependent app**, and silently disables watchtower protection for Lightning nodes.


umbrelOS 1.7.4 is now out which includes the latest Tor version, just login and update to fix the issue.

🚨 Umbrel: All Tor connectivity broken, LN channels offline, onion services dead

nostr

Welcome back to Nostr Compass, your weekly guide to Nostr.

> **This week:** the [Marmot spec is marked adopted](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#marmot-marks-the-spec-adopted-and-mdk-cuts-v09x) across 42 files as MDK cuts v0.9.0 through v0.9.3 with encrypted group avatars, external signer support, and MarmotKit iOS and Android bindings. [Mostro ships Transport v2](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#mostro-v0180-and-mobile-v130-ship-transport-v2-on-nip-44) on NIP-44 direct messages with anti-spam gates and a coexistence window in both mostrod v0.18.0 and Mobile v1.3.0. [Bitchat 1.6.0 adds NIP-13 proof-of-work](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#bitchat-160-adds-nip-13-proof-of-work-and-an-opt-in-mesh-to-nostr-gateway) to geohash channel messages, an opt-in mesh-to-Nostr gateway that lets one online phone uplink a whole crowd, prekey bundles, transitive verification, and creator-managed encrypted private groups. [Amber](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#amber-v623-scopes-profile-subscriptions-and-adds-a-tor-status-notification) scopes profile subscriptions per account, fetches NIP-65 relay lists before profile metadata, and adds a live Tor status notification with a restart action. [rust-nostr](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#rust-nostr-adds-nip-40-expiration-to-gift-wrap-and-private-dm-builders) adds NIP-40 expiration to gift wrap and NIP-17 DM builders, anchored to the wrap’s randomized timestamp. [Amethyst](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#amethyst-spends-the-week-hardening-negentropy-sync-and-adding-nip-50-search) merges 43 PRs of negentropy sync hardening, NIP-50 full-text search infrastructure, and event kinds for niche verticals. [Nostrord ships v2.0.0 and v2.1.0](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#nostrord-v200-and-v210-fold-the-relay-pool-and-heal-zombie-websockets) with a folded relay pool, zombie WebSocket detection, and a full disk-first cache seam. [Ngit v2.6.2](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#ngit-v262-stops-duplicate-pr-status-events-on-default-branch-push), [Jumble v26.7.1](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#jumble-v2671-makes-blossom-the-default-upload-service-in-a-dm-focused-cut), [Applesauce signers 6.2.2](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#applesauce-signers-622-drops-an-nbunksec-dependency), [Bray v1.33.0](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#bray-v1330-cli-picks-up-a-bunker-profile-persona-and-tor-outbound), [Deepmarks 1.0.0](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#deepmarks-100-hardens-the-nostr-bookmarking-surface), [Bitcredit Core v0.5.13](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#bitcredit-core-v0513-unencrypts-block-metadata-on-the-nostr-wire), [Coop Mobile v0.2.4](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#coop-mobile-v023-and-v024), [Granary v11.0](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#granary-v110-adds-nip-71-video-event-support), [Nostr-relay v0.0.244](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#nostr-relay-v00244-adds-a-firestore-backend), [Manent v1.4.0](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#manent-v140-fixes-nip-42-auth-and-adds-media-clipboard-flows), [Routstrd v0.3.7](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#routstrd-v037-makes-the-nostr-event-store-the-persistent-source-of-truth), [Nymchat 1.0.1](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#nymchat-101-launches-as-a-progressive-web-app-on-nip-17), and [21Meetup 1.1.0](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#21meetup-110-launches-nostr-signed-attendance-badges) also ship, and [SafeBox marks Phase 3 substantially complete](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#safebox-publishes-a-phase-3-progress-report-and-a-freebsd-jail-runbook) alongside a FreeBSD jail deployment runbook and an OpenETR spin-off for electronic transferable records. The NIPs repository merges a [NIP-51 and NIP-37 name alignment](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#merged-nip-51-and-nip-37-align-the-kind-10013-name) and opens five proposals: [NIP-AD Nostr Web Addresses](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#open-nip-ad-nostr-web-addresses-via-well-known-lookup), [NIP-86 invite-code claim management](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#open-nip-86-claim-management-for-invite-codes), an [HSL role color format](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#open-role-color-as-h-s-l-tuple), [NIP-80 hardware-attested media provenance](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#open-nip-80-hardware-attested-media-provenance), and a [pagination fix in NIP-01](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#open-nip-01-pagination-hardening). Deep dives cover [NIP-13 (proof-of-work)](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#nip-deep-dive-nip-13-proof-of-work) and [NIP-40 (expiration timestamp)](https://nostrcompass.org/en/newsletters/2026-07-08-newsletter/#nip-deep-dive-nip-40-expiration-timestamp).