Nostr notes by

Nostr Compass #35 is out. Here is what changed across Nostr this ...

2026-08-12T16:06:20Z

Nostr Compass #35 is out. Here is what changed across Nostr this week:

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

This week: nostr-wot-extension (maintainer Leon Acosta: leon (npub1gxd…5zfk)) adds post-quantum keys and opt-in protected messages beside existing Nostr identities. Divine tightens account isolation, private-message validation, and publish confirmation; MDK marmotprotocol (npub1mar…r6m9) strengthens encrypted-group convergence and recovery; and Amber (maintainer: greenart7c3 (npub1w4u…0jr5)) makes grouped signing decisions explicit. Releases improve wallet connections, encrypted chat, social discovery, device sync, and remote signing, while protocol work covers identity and encrypted communities. The deep dives explain authenticated deletion requests and decentralized reporting.

Read the full issue:

quoting naddr1qv…nrpf

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

This week: nostr-wot-extension (maintainer Leon Acosta: leon (npub1gxd…5zfk)) adds post-quantum keys and opt-in protected messages beside existing Nostr identities. Divine tightens account isolation, private-message validation, and publish confirmation; MDK marmotprotocol (npub1mar…r6m9) strengthens encrypted-group convergence and recovery; and Amber (maintainer: greenart7c3 (npub1w4u…0jr5)) makes grouped signing decisions explicit. Releases improve wallet connections, encrypted chat, social discovery, device sync, and remote signing, while protocol work covers identity and encrypted communities. The deep dives explain authenticated deletion requests and decentralized reporting.

Top Stories

nostr-wot-extension 0.4.0 adds post-quantum keys beside a Nostr identity

nostr-wot-extension 0.4.0 is a browser extension for managing Nostr identities and signing. Accounts created from a 24-word seed can now derive ML-KEM-1024 encryption and ML-DSA-87 signing keys alongside their existing Nostr key. A one-click flow publishes a kind 10203 attestation that binds the Nostr public key to both post-quantum public keys and includes an ML-DSA proof of possession. Accounts imported from a 12-word mnemonic, bare nsec, remote signer, or read-only key cannot use the derivation flow, and the extension explains that limitation in the account view.

The release also adds opt-in post-quantum direct messages. It combines the ML-KEM shared secret with the existing NIP-44 encrypted-message conversation key through HKDF, then keeps the normal NIP-59 metadata-hiding gift-wrap layers for relay delivery. Encryption never silently falls back after a recipient opts in, while decryption selects the appropriate path automatically. This protects the new message path against later recovery of a present-day Nostr private key, but it does not replace secp256k1 event signatures; the release explicitly leaves that larger migration for future coordination with relays and clients.

Divine Mobile 1.0.19 tightens accounts, private messages, and publishing

Divine Mobile 1.0.19 (maintainer rabble: rabble (npub1wmr…g240)) is a mobile short-video client that publishes and retrieves videos through Nostr. Its account switcher now builds each signed-in identity around an account-scoped container, and a publishing fix prevents a video from being sent under the wrong account. Relay publication paths now wait for an OK response with explicit success semantics, while a relay CLOSED frame can terminate its own pending query instead of leaving the request hanging.

Private-message handling rejects unauthenticated rumor fields and unsigned seals, restores four missing-message cases, and routes group conversations from fully followed participants into the inbox. The release also preserves the tags on addressable video events when lists are updated and consumes observed deletion requests so removed videos disappear from local state. Those changes follow the per-relay query timeout work covered last week, but move the focus from retrieval isolation to identity boundaries, message validation, and publish confirmation.

MDK 0.9.11 hardens Marmot group convergence and recovery

MDK 0.9.11 is a Rust development kit for Marmot, an encrypted group-messaging protocol carried over Nostr. The release builds a larger convergence and recovery system around the group state machine: stale convergence passes reopen at the current group tip, inbound capability projections commit atomically, deferred messages receive bounded lifetimes across restarts, and commit-addressed checkpoints help recover an identity's own commit forks. Non-stable sends can be queued and recovered, while an epoch-stall path escalates to backfill and sent messages survive convergence work.

Storage and host integrations receive a parallel hardening pass. MDK securely deletes pruned SQLite projections, zeroizes imported private keys, NIP-49 encrypted-key export intermediates, and OpenMLS serialization buffers, and redacts group image keys from debug output. Account import can resume after interruption, iOS and Android private-storage paths are repaired, and hosts can explicitly close storage before suspension. New lightweight roster and local-membership projections reduce what applications must read, while the Hermes connector can deliver several agent-generated images as one Marmot album.

Nostria 4.1.67 expands encrypted-community administration

Nostria 4.1.67 (maintainer: sondreb (npub1zl3…jajh)) is a web and desktop social client for Nostr. It builds on the experimental NIP-29 relay-managed groups and Concord encrypted communities introduced in 4.1.53, adding community dissolution, icon and banner administration, encrypted photo uploads with compressed previews, a full reaction picker, and a dual-pane layout that keeps a community open while the user reads notes or articles. The release also adds threaded messaging and a combined hub for public, group, and private chats.

Amber 6.4.0 makes every grouped signing decision explicit

Amber 6.4.0 is an Android signer that keeps Nostr private keys separate from the applications requesting signatures. Its redesigned multi-request screen provides Approve and Deny controls for each request and each group, replacing the previous selection-and-confirm flow. Denied requests sent through Amber's relay-mediated bunker interface now receive proper error responses, so the requesting client can distinguish rejection from a stalled signer.

Amber's tagged source also adds localized, human-readable labels for 113 more event kinds across every shipped locale. The additions include Concord group events, NIP-51 Git repository bookmarks, and NIP-53 room-presence events, giving users more context about unfamiliar data before they approve a signature. A concurrent-map guard also fixes a relay-subscription crash that could produce a NegativeArraySizeException.

Safebox Acorn separates a portable recovery component from the web app

Safebox Acorn (lead developer Tim Bouma: Tim Bouma (npub1q6m…x7d5)) is a standalone Python component and command-line interface for safeguarding user-controlled keys, funds, and records with Nostr-backed state. Extracting Acorn from the broader Safebox web application lets another Python project install the runtime and use its key, Nostr profile, relay, record, Cashu, Lightning, and cryptographic helpers without taking on the web interface. Its current record-protection primitives can generate a fresh 256-bit key, derive one from separately supplied entropy, and encode the exact key as a checksummed 24-word recovery phrase.

The project's recovery and continuity guide frames Acorn as the replaceable protocol component inside a household or community Safebox. The design keeps encrypted state available through a local relay and independent replicas so recovery does not depend on one appliance, application, relay, mint, or service provider. The documentation is careful about the present boundary: protected-record encryption remains under design, so applications should not make records depend on the new record-protection key until that profile has been implemented and reviewed.

Tagged Releases

Mostro Core 0.14.2 changes the encrypted chat envelope

Mostro Core Mostro (npub1m0s…40un) is the Rust library of shared types and peer-to-peer functions used by the Mostro exchange daemon and its clients. Version 0.14.2 replaces gift-wrapped chat messages with kind 14 envelopes that use separate conversation-encryption and signing keys derived from the peers' shared secret. The new reader validates the author, signature, recipient, timestamp, and content size, while legacy gift-wrap helpers remain available so clients can read both formats during migration.

Mostro 0.18.1 starts a Cashu escrow path and hardens the daemon

Mostro is a peer-to-peer Lightning exchange daemon that coordinates orders through Nostr. Version 0.18.1 lays the foundation for a Cashu escrow backend, including configuration, database helpers, mint integration, startup wiring, and the first lock action. It can also use prices announced by a trusted node over Nostr and advertises proof-of-work requirements for first contact in its replaceable info event. The release updates its Nostr dependency for a NIP-44 denial-of-service fix, removes private keys from restore-session logs, rejects unauthorized cooperative-cancel messages, hardens LNURL fetches against server-side request forgery and hangs, validates payout invoices, and restores hold-invoice subscriptions after a restart.

LaWallet NWC 2.3.0 adds Nostr notifications and zap receipts

LaWallet NWC lawallet (npub1ek4…v4pd) is an open-source Lightning Address platform that connects wallets through Nostr Wallet Connect. Version 2.3.0 lets each wallet send received and forwarded notifications as configurable Nostr events, including a recipient p tag, selected relays, templated content, and optional NIP-44 encryption; retries reuse the same signed event ID. It also accepts zap requests and publishes signed NIP-57 kind 9735 receipts after settlement, while a new address capability view shows whether the resolved address supports NIP-05, NIP-57, and related Lightning Address protocols.

nostr-double-ratchet TypeScript 0.0.166 binds public invites to session keys

nostr-double-ratchet provides TypeScript and Rust primitives for end-to-end encrypted direct and group messaging over Nostr relays. TypeScript 0.0.166 requires an invite response to prove ownership of its session key, preventing a reusable public invite from binding one Nostr identity to another party's session. The release also rejects malformed rumor fields and tightens payload validation; existing sessions continue to work, but an updated inviter rejects proofless responses from older invitees.

cln-nip47 0.2.0 expands and isolates NWC requests

cln-nip47 (maintainer daywalker: daywalker (npub1kue…drjt)) is a Core Lightning plugin that exposes a node to wallets through Nostr Wallet Connect. Version 0.2.0 adds NWC methods to create, cancel, and settle hold invoices plus a hold_invoice_accepted notification, and it advertises the method set that the connected node actually supports. Transaction-list responses now stop at 500 entries and about 128 kB, request events are deduplicated by event ID, and one client's failed notification no longer prevents delivery to other clients. The release also removes the two multi-payment methods that are no longer part of the NWC specification.

ClipRelay 0.1.3 restores relay and signer connections after idle periods

ClipRelay (maintainer: hoppe2 (npub1pt4…eera)) synchronizes a user's clipboard between devices through Nostr relays, encrypting the content to the same identity with NIP-44. The matching desktop and Android 0.1.3 releases add a text box for sending typed text directly to another device's clipboard. They also test liveness with real relay round trips after idle periods, escalating from resubscription to socket replacement and a rebuilt connection pool, while stalled NIP-46 signer calls now time out and rebuild automatically.

NoorNote 1.3.2 moves article discovery into the social graph

NoorNote (maintainer: alp (npub175n…g6w0)) is a Nostr client for social posts, encrypted messages, long-form articles, and other event types across web, desktop, and Android. Version 1.3.2 replaces its flat global article feed with discovery drawn from first-, second-, and third-degree contacts, giving readers an article timeline rooted in their follow graph. It also collapses bursts of replayed direct messages from unknown senders into one rolling notification instead of producing a stack of toasts as relay history arrives.

Bray 2.4.0 adds a compact remote-signing dialect

Bray TheCryptoDonkey (npub1mgv…e7q2) is a Nostr MCP server that gives software agents and people tools for relay access, identity, publishing, and remote signing. Version 2.4.0 accepts a signing request whose event is an object as well as the stringified form used by NIP-46, and adds sign_event_compact, which returns only the event ID, signature, public key, and timestamp. That smaller request and response format reduces memory use for constrained hardware signers, while the standard sign_event flow remains unchanged and both dialects produce a signature over the received event's ID.

Newly Discovered

Pact brings mutually consented agent bonds to Nostr

Pact, newly discovered this week, is an early-stage relationship layer for software agents built on MATE.md and a draft NIP-BD transport. Its signed, mutually consented bonds are held by the agents' own keys and can be published over Nostr, while private bonds use NIP-59 gift wrapping. The monorepo includes an MCP server, TypeScript SDK, command-line client, self-hostable daemon, and web interface. Its latest repository activity predates this issue's weekly window, so this is a discovery note rather than a claim of a new release.

In Development

nostrord keeps group muting synchronized between devices

nostrord Nostrord (npub1ktx…zc2h) is a cross-platform client for relay-managed communities. PR #250 stores each account's per-group mute choices in a self-encrypted NIP-78 (application-specific data) kind 30078 event, so a setting made on one device can follow the user to another without revealing the group list to the relay. The replaceable record uses newest-event ordering, listens for live changes, and rolls the interface back when signing or publication fails instead of leaving local state out of sync. Muted groups also stop contributing visible unread totals while retaining their unread position for the next visit.

Amethyst completes Concord's invite lifecycle

Amethyst amethyst (npub142g…xrj0) is an Android Nostr client whose encrypted-community support implements the Concord protocol. PR #3888 lets invite links survive a community refounding by reissuing their bundles at the same addressable coordinates, while a ban check prevents a removed member from using that recovery path. It also implements the encrypted CORD-05 invite list on both the app and amy command-line client, adds per-link revocation tombstones, and requires relay confirmation before deleting the only stored signing key that can retire a link. The same work gives amy the control-key delivery, refounding, rekeying, and stranded-member recovery paths needed to follow later community epochs.

Buzz carries each community's appearance across desktop and mobile

Buzz block-opensource (npub16l0…yj9s) is a Nostr-based community workspace with desktop and mobile clients. Merged desktop PR #3653 and mobile PR #3767 store each community's theme, accent, and system-mode choice as an encrypted NIP-78 record on that community's relay. Both clients share the same versioned payload and keep identity-scoped local caches, so changing communities or accounts cannot apply the wrong appearance while the relay is unavailable. Replacement ordering, guarded writes, and resubscription after a closed connection let the two clients converge again after reconnecting.

Buzz Desktop 0.5.10 followed before the issue cutoff with a performance and reliability pass. It removes regressions introduced after 0.5.9, accelerates channel loading, bounds initial timeline retention, coalesces read-state persistence, preserves fresh channel timelines, and stops the relay ingest worker from crashing on reactions to project events. It also adds sending a thread message to a channel and narrows desktop search to the intended scope.

Protocol and Spec Work

NIPs

NIPs PR #2435 is an open amendment to NIP-34, which standardizes git repository collaboration through Nostr events. It adds an optional b tag to a pull-request event so the author can name a target branch other than the repository's default. The proposal matches support already implemented in ngit and GitWorkshop, but has not entered the specification.

NIPs PR #2434 is an open proposal for post-quantum identity keys. It derives post-quantum encryption and signing keys beside the existing secp256k1 key from a NIP-06 mnemonic key-derivation seed, then binds the public keys to the Nostr identity with a kind 10203 attestation. The draft limits its claim to protecting the confidentiality of earlier messages if secp256k1 is later broken; it does not replace today's event signatures.

NIPs PR #2431 is an open NIP-07 amendment for browser signers. A client could attach the public key it expects to signing or encryption requests, requiring the signer to use that account or reject the call. This would keep a page from silently continuing under a different identity after the user switches accounts in the signer.

NIPs PR #1813 remains an open double-ratchet proposal after substantive work during the window. It specifies forward-secret encrypted conversations whose keys advance with messages, with an implementation already available in the nostr-double-ratchet library and Iris. It is still a draft, not a merged NIP.

NIPs PR #2433 opened and closed without merging during the window. It proposed clarifying NIP-42 relay errors so auth-required would mean another authentication could change the result, while restricted would mean it could not. The distinction addressed connections authenticated for one key but still missing authorization for another; the closed status means the wording did not enter the specification.

NIPs PR #2378, which was covered previously while still proposed, has now closed without merging. Its proposed agent passports, discovery, task, marketplace, invoice, and connection events therefore remain outside the NIP set.

NIPs commit 656cecc merged a documentation-only correction to NIP-29. It adds a previous tag to the group metadata example, showing how a replacement event can identify the event it supersedes. This clarifies an example and does not introduce a new protocol feature.

Concord and CORDs

CORD PR #18 would shard encrypted Community Lists across kind 33302 events, remove the 50-membership limit, and prune retired entries to stay within relay limits. Two other open proposals add private mention locators and a pause signal that suspends chat without discarding messages.

CORD-02 PR #15 merged on August 6 and restricts writes to a community's control plane. Owners and staff hold a new control_root signing secret, while all members retain the derived public key and read key needed to verify and decrypt moderation state. The write key is a spam barrier, not a substitute for the inner actor signatures and roster checks that establish authority.

CORD PR #12, covered previously as an open draft, has now closed without merging. Its control-plane portion was superseded by the narrower merged CORD-02 amendment above, while restricted-write channels and the other draft material did not enter the specification.

NIP Deep Dive

Event Deletion Requests (NIP-09)

NIP-09, defined by the primary specification, gives an event author a signed way to ask relays and clients to stop serving one or more of that author's events. It does not erase every copy. It carries the author's intent through the same relay network that distributed the original event.

The request is an ordinary signed kind 5 event. Its tags contain one or more e references to specific event IDs or a references to addressable-event coordinates, and the NIP-09 tag rules say it should include a k tag for each referenced event kind. The optional content can explain the reason. For an a reference, a relay should remove every version at that coordinate whose timestamp is no later than the request's created_at, which prevents an old deletion request from suppressing a later replacement.

Authorship is the security boundary. A relay should stop publishing a referenced event only when its pubkey matches the deletion request's pubkey, and a client must perform that check before hiding an event. A relay may not possess the referenced event and therefore may be unable to validate the relationship when accepting the request, so clients cannot treat relay acceptance as proof that the deletion was authorized. The specification also asks relays to retain the kind 5 request because another client may already hold the original event and encounter the request later.

Here is a signed kind 5 event:
{
  "id": "6f39fd3d0d593d97dd093f21fabe8f78895579d6979a6ecf14e169bd85bb0943",
  "pubkey": "5877220aaae6e54a6f974602d5995c0fe24a3ea7ddabd8644bec795b9da00743",
  "created_at": 1786465675,
  "kind": 5,
  "tags": [
    ["e", "f3d47f8b813928c5baf7ac993846be0220dc37a2e7c7b128fb49a4b92711f131"],
    ["k", "30091"],
    ["a", "30091:5877220aaae6e54a6f974602d5995c0fe24a3ea7ddabd8644bec795b9da00743:survey:0ad5cebc-608b-47d7-97fd-9e6c47787199"],
    ["t", "nostr-survey"]
  ],
  "content": "Public survey summary deleted during privacy refresh",
  "sig": "846be83b038dc5f91af0c9d03a4ac81aff9bc4cfde7d85c849fa2fdae890f75cc444a4072f45aa18883b0b3871e15381b220182d6e366892f0c9c6f9c0557244"
}
Deletion remains a cooperative policy, not revocation of a signed object. A relay, cache, screenshot, or offline client can preserve the original bytes, and deleting the kind 5 request itself does not undo it. Clients may hide the target, mark it as disowned, or display the request reason, but should tell users that universal deletion cannot be guaranteed. This differs from NIP-40, where an expiration tag asks relays to stop storing an event after a time chosen when the event is published. NIP-09 handles a later author decision and can point to already-distributed events.

Current implementations apply that policy at different layers. Divine PR #6623 removes deleted videos from the client's event store, strfry PR #251 extends valid deletion requests to gift-wrap recipients, and Amethyst declares NIP-09 support in its client. nostrord's group client supplies another current implementation path.

Reporting (NIP-56)

NIP-56, defined by the primary specification, standardizes a signed report about an account, event, or referenced blob. It separates the report signal from the moderation decision, allowing each client or relay to choose which reporters it trusts and what response fits its policy.

A report uses kind 1984 and must identify the reported account in a p tag. Reporting a note also requires an e tag for the event ID. The third value of the tag carries one of the specified categories: nudity, malware, profanity, illegal, spam, impersonation, or other. A report about a blob can use its hash in an x tag, an e tag for the event that referenced the blob, and an optional server tag for a location. Optional L and l tags from NIP-32 can add a namespaced label when the fixed category list is not precise enough.

The event proves only that one key made an allegation. The reported content does not become false, illegal, or removable merely because a valid kind 1984 exists, and an open relay cannot safely count anonymous reports as votes. The specification advises against automatic relay moderation because reports are easy to game, while allowing relay administrators to act on reports from moderators they already trust. A client can instead weight reports through a user's social graph, for example by blurring content after several trusted contacts flag the same account.

Here is a signed kind 1984 event:
{
  "id": "17301ea66066d34af9ba0b6957ed9d9d8854b9436939e682e21e7a5a8768e4b2",
  "pubkey": "1ff02fb5cdc633c1be55368ab655490ec25d2f5dc2e364d4703bc3196d99eab1",
  "created_at": 1786465319,
  "kind": 1984,
  "tags": [
    ["p", "3a72b02cc05ee07310dc580874b6a9ca8271c6518b90655bd2e98003c9601e68", "impersonation"]
  ],
  "content": "",
  "sig": "6362e415410feb19e0505654a4660e8456b6b2aec5ae39173a0429a6a8e5fa1381c9488198ca2982db43ee8198af056f2a25537705c763784062056d0ab2eb1a"
}
NIP-56 and NIP-09 solve different problems. A kind 1984 report can target somebody else's account or event, but confers no deletion authority. A kind 5 request expresses the original author's intent and is valid only against that author's own events. Neither guarantees removal: NIP-56 deliberately delegates action to local moderation policy, while NIP-09 depends on relays and clients honoring an authenticated request.

Implementations expose those choices in different products. Divine PR #6591 corrects report delivery in a short-video client, Conduit PR #250 reads reports as bounded context for marketplace participants, and nostrord's NIP-56 module publishes and processes report events. Amethyst also lists current NIP-56 support.

Send a NIP-17 DM to share a project or news item through the Nostr Compass project.

I always thought of it more as sandwich lube

2026-08-12T16:05:01Z

In reply to nevent1q…p60v
_________________________

I always thought of it more as sandwich lube

Morning dood 🌞

2026-08-12T16:04:14Z

In reply to nevent1q…dtjs
_________________________

Morning dood 🌞

Nostr event nevent1qqsqqqqgt6al4xf2yz4kcke3slfwkz8s834apz2nhtqpwm027kpjx4gp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyr02k7w6lgwzhe955mf6egf40dk25zm5f06x44ff5khyvs5g270xsvzyzgp

2026-08-12T16:03:21Z

In reply to nevent1q…yhdc
_________________________

We're seeing lots of encrypted events, but fewer plaintext.

2026-08-12T16:03:01Z

In reply to nevent1q…jpae
_________________________

We're seeing lots of encrypted events, but fewer plaintext.

Come on now life is too short to do nothing fun lol

2026-08-12T16:02:59Z

In reply to nevent1q…8jd5
_________________________

Come on now life is too short to do nothing fun lol

⚽📺️ UEFA’s chief referee says VAR delay have hurt fan ...

2026-08-12T16:02:14Z

⚽📺️ UEFA’s chief referee says VAR delay have hurt fan trust, urging a shift back to “clear and obvious” errors—and they’ve launched a new portal to explain decisions. #VAR

Morning my man!!

2026-08-12T15:59:36Z

In reply to nevent1q…ag9s
_________________________

Morning my man!!

Nostr event nevent1qqsqqyxx9lze9ethc7ltzzjumuvxf9x5396lnstzukwx48l5ydk4zqsp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyzqezvypy3k3jty62k23wpp8qattygsfg3ctx9c7tza4u0zza6xm2705ln0

2026-08-12T15:59:00Z

“一个人的命运自我奋斗固然重要，也要看到历史的行程。”

自从高中，成绩再也没有进入班级前2/3起，我慢慢知道自己智商其实在人群中是不咋地的，此后多年事实也一再证明。我在想，得亏没有晚出生20年，否则除非投胎到起点高的家庭，反正如果是没什么老本的普通家庭，甚至背负债务的话，前路是很难的。

虽然资质一般，错过很多好机会，但也知足了。毕竟多少还是有点积攒。什么重来一次的想法，是不会去想的，人生不是预设好的游戏，不可能通过无限读档，靠背版通关。在人生的每一个当下，都要面临未来的不确定，哪怕可以多读几次档，也会发现其实进入到另一个平行宇宙，背版毫无意义。

quoting
nevent1q…t7wg
“每个时期都以为自己开智了，然后过一年再看依旧蠢的不行。”

---

“认识到自己的无知程度，需要有相当程度的知识。”

―― 托马斯·索维尔

https://www.daniel.pizza/journal/nogood-book/

2026-08-12T15:56:49Z

https://www.daniel.pizza/journal/nogood-book/

谁会嫌资源多呢

2026-08-12T15:49:54Z

In reply to nevent1q…wckp
_________________________

谁会嫌资源多呢

Nostr event nevent1qqsq4taefmprra3cawygu97lxvmy2uvzkxlmx9rx2kpw70p27sdd3tgp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyrfxwcw3gsssq4y9r5rs0v8sdfgl34jamn68exuj24z63kc8xj8jga2vfy3

2026-08-12T15:46:54Z

#Costr

relay.ditto.pub这个中继搜索功能有问题，会返回不含搜索关键词的无关的帖子，我还以为是costr实现的有问题，介意的可以去掉这个搜索中继，保留另外一个。

A tail emission is a mechanism in which new block rewards are ...

2026-08-12T15:45:27Z

In reply to nevent1q…ymf0
_________________________

A tail emission is a mechanism in which new block rewards are made as a mechanism to keep coins at a steady supply to account for lost coins, and it’s also to incentivize miners.

quoting
nevent1q…2z59
You can use the command print_coinbase_tx_sum to see Monero’s current supply:
https://monero.stackexchange.com/questions/11548/how-does-monero-protect-users-from-inflation-bugs-if-the-blockchain-cant-be-aud

Monero reached a max supply of 18.293 Million before swapping over to tail emissions in May 2022

According to Monero inflation checker, there are 18,761,061.507967225895 Monero:
https://www.moneroinflation.com/

According to Coinmarketcap there are 18,446,744.07 Monero:
https://coinmarketcap.com/currencies/monero/

Monero’s Audibility by Seth for Privacy:
https://sethforprivacy.com/posts/dispelling-monero-fud/

Get monero org regarding audibility:
https://www.getmonero.org/2020/01/17/auditability.html

Ungovernable Misfits regarding Monero Audibility:
https://www.ungovernablemisfits.com/podcast/monero-monthly-02/

Docs Getmonero .org:
https://docs.getmonero.org/technical-specs/

How Tail Emissions Work in Monero (original video link, tracking parameters removed):
https://youtu.be/sRwSqM0YBto

How tail emissions work Get Monero .org:
https://www.getmonero.org/resources/moneropedia/tail-emission.html

牛奶

2026-08-12T15:45:24Z

In reply to nevent1q…67xe
_________________________

牛奶

电报，推特，pornhub还不够你看的吗？

2026-08-12T15:44:21Z

In reply to nevent1q…wjr2
_________________________

电报，推特，pornhub还不够你看的吗？

Nope. They got burnt by negligence of the company that failed to ...

2026-08-12T15:43:32Z

In reply to nevent1q…j5vj
_________________________

Nope. They got burnt by negligence of the company that failed to do what a closed source shabby wallet can do.

derivative is BIGGER than onchain - onchain supply not matters ...

2026-08-12T15:43:32Z

In reply to nevent1q…ezs4
_________________________

derivative is BIGGER than onchain - onchain supply not matters anymore

yes also - can hidden oligarch wallet(s) also

2026-08-12T15:42:46Z

In reply to nevent1q…6jqk
_________________________

yes also - can hidden oligarch wallet(s) also

Nostr event nevent1qqs2ljrw4lk3lhjsf4gnkgpknz4amc6ndy9wavm563ke8g297729p4qp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyzvdu0jv3mrk4879hjfsjxrmt5fl2laklzzc52348zwljavyjv272lq8pxj

2026-08-12T15:40:32Z

In reply to nevent1q…xva2
_________________________

一个声称是去中心化的p2p通讯APP，去不去中心我不知道，安不安全我也不知道，反正是注册之后给一组助记词，至于你用这组助记词能不能再登录就不好说了，得看运气，但是最让我忍受不了的是当身处同一网络的我的电脑正在下BT的时候，它是死活也没法使用的，当我退出电脑的BT，它就能正常使用了，就这个奇葩软件，老外用它来搞黄，这是我的另一个痛点，就是我加几个搞黄群准备白嫖小黄片，因为它是p2p的，手机很快就满了，不是说我下的片太多，是它缓存的太多还清除不了，我只能清除所有数据再登录，然后登录十次可能有一次能登陆成功，登陆成功之后发现之前加的搞黄群没了，后来我干脆把群链接记下来，每次登陆后直接搜索重加，累了，删了。

People are still pointing nearly 7 EH at the bip110 chain. 2 new ...

2026-08-12T15:40:19Z

People are still pointing nearly 7 EH at the bip110 chain. 2 new blocks found today according to Oceans website.

Nostr event nevent1qqs9hgqhr3tfet48vzm2uetwr7vdl9vg33uzwfms2f2vy29jq6wsh9sp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyznj8qzumfnj2yv3epux7nd93auhu6thtq3szd2t4r53hjcrgtwfc9kw59y

2026-08-12T15:40:14Z

New idea emerged and I registered a .xyz domain

Thanks.

2026-08-12T15:38:45Z

In reply to nevent1q…47an
_________________________

Thanks.

Ignore a 200k fine? I don't think I can.

2026-08-12T15:38:42Z

In reply to nevent1q…z8pk
_________________________

Ignore a 200k fine? I don't think I can.

South Korea's amended Network Act lets courts punish ...

2026-08-12T15:38:23Z

South Korea's amended Network Act lets courts punish "false or manipulated information." The law doesn't define what that phrase means. Publishers cannot tell in advance which post is legal, so the safe move is to delete on suspicion. US lawmakers have questions about what that means for American platforms...

https://reclaimthenet.org/america-presses-south-korea-false-info-law

That's pulled from NostrArchives, I think.

2026-08-12T15:38:19Z

In reply to nevent1q…27u2
_________________________

That's pulled from NostrArchives, I think.

#nevent1q…hgnd

2026-08-12T15:38:12Z

In reply to nevent1q…umg2
_________________________

quoting nevent1q…hgnd
> "The enactment of the Constitution in 1788 drastically changed the course of American history from its natural decentralized and libertarian direction to an omnipresent leviathan that fulfilled all of the Antifederalists’ fears."

—Murray Rothbard

https://tinyurl.com/a48pkuuw

August 12th MAKE THE WORDS YOUR OWN “Many words have been ...

2026-08-12T15:34:30Z

August 12th

MAKE THE WORDS YOUR OWN

“Many words have been spoken by Plato, Zeno, Chrysippus, Posidonius, and by a whole host of equally excellent Stoics. I’ll tell you how people can prove their words to be their own—by putting into practice what they’ve been preaching.”

—SENECA, MORAL LETTERS, 108.35; 38

#DailyStoic

21M - who can corner ? 50% CENTRALIZED CUSTODY is GROWING 5% LOST ...

2026-08-12T15:31:50Z

21M - who can corner ?
50% CENTRALIZED CUSTODY is GROWING
5% LOST
45% DECENTRALIZED CUSTODY is SHRINKING (plus some of them corporate/oligarch wallets)

even if chain is forked for better technical reasons - above key custody will not change - in fact those 50% can too spend in two chains.

Laxative?

2026-08-12T15:29:56Z

In reply to nevent1q…x08w
_________________________

Laxative?

最近重置频繁，够用的。

2026-08-12T15:28:26Z

In reply to nevent1q…4ctt
_________________________

最近重置频繁，够用的。

“Start a nostr publication business, and message me back once ...

2026-08-12T15:26:47Z

In reply to nevent1q…mwtw
_________________________

“Start a nostr publication business, and message me back once it starts making money. Make no mistakes!”

Are powerusers, & meme pages considered Bots?

2026-08-12T15:26:21Z

In reply to nevent1q…47an
_________________________

Are powerusers, & meme pages considered Bots?

exactly ! 55% is now centralized wallets and 2% moving regularly ...

2026-08-12T15:26:20Z

In reply to nevent1q…7940
_________________________

exactly ! 55% is now centralized wallets and 2% moving regularly

TFTC npub run by DUMBFUCK MartyBent (npub1guh…6hjy) his propaganda narrative

Nostr event nevent1qqsxzt7ceyveaf58fea4a6ky8f9w466rh7mpflu0u8zx0s25e2afl9sp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczypxgx8hhc607k47g2gvke25hedc84axkzg0s9lwjzdvawkemjk9p7e7t8h2

2026-08-12T15:26:14Z

T1786548374.254:status:stx8b89d28c9a8d969a8c:kuub2w4ehs+4136943015/g581121-b275f09f9cfbcd54b0e74e11d14e80f63+4136945598

哪还有东北人

2026-08-12T15:25:25Z

In reply to nevent1q…ag4t
_________________________

哪还有东北人

Nostr event nevent1qqsq04k2fgtwxk5qakepqkl2xm9l4j63wkww48gr7acql38x7vddcwgp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyqylh78nhedwwc6rtzqknrtws3w7swlfkhsue2ve3zgc69l684s0qmmv2rr

2026-08-12T15:24:14Z

传言:某造车新势力老板被其他车企联名告状，主要罪名是“出口做得差，却一门心思在国内搞价格内卷”，但个人资产安排离岸信托、进行税务筹划却动作迅速、效率很高。

Nostr event nevent1qqsq8txjmx8qmr4cehwn5avhmtmxh4f0y7qm9tqma5dfhzxj4haxsrqp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyqrc3gffl7gzmlnwfpsy8l9cvnz5p6xsjutk7447pht4ycau5u22kccljjg

2026-08-12T15:23:07Z

entry https://86.gigafile.nu/1121-ba1cf1028331d782e9cc7dd6e82cb5047 | |

Thank you, man! I’m looking forward to where I can have a ...

2026-08-12T15:22:33Z

In reply to nevent1q…9mk5
_________________________

Thank you, man!

I’m looking forward to where I can have a comfortable life, and not have to worry about covering my basics.

Luckily, I still have my parents that help me out but if I didn’t I would be absolutely screwed.

Nostr event nevent1qqs9ky9ppwfrt66xw3uwzdv5es8jcgz5jeghd804qfn7ynh5sz0wpfqp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczypxgx8hhc607k47g2gvke25hedc84axkzg0s9lwjzdvawkemjk9p7zhcefd

2026-08-12T15:22:32Z

T1786548152.349:status:stx9c9689968b9e96d29d94:k4f5tr7wme+4136720174/g861121-bde7ff7c4a3c02185977aa83e634dbcba+4136723199

Nostr event nevent1qqsqr5hsuqkh0lda3thyhvhnxp635wt9vvmt7p39960uxa5acvcyrdcp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyq02ft5yqkk4c67sms66ptyru4yvfpg5y5uwrcx9ft2quka4ng4wstqrgku

2026-08-12T15:22:20Z

In reply to nevent1q…yvr7
_________________________

📰☕️

https://ashlandnews.bluelena.io/lt.php?x=4lZy~GDJJFbNE5J8__A4Vudt2aAoi_Ykw-cxZKPEI3LK5pN8_Uy7xOF02H-m-RVfjDZo2XLKKYGb6pWKz.xMUuNx

Nostr event nevent1qqsd678umeg3txk8rpvjur3n5pfqq3j5xxnvce2h76q2ac6gaq79rlgp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczypnkwjwp4en5jpegxwyc3qdp8zfh8nup8cxkhjr8t8lh67lawh5p6eg9cw9

2026-08-12T15:21:46Z

entry https://86.gigafile.nu/1121-d5972af53440b404093104d640a69206e | |

Nostr event nevent1qqswrrhczfc3w54anl9ujzwvgemhum4j8gvufcv3wfjnp5qwvl5u6xcp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczypxgx8hhc607k47g2gvke25hedc84axkzg0s9lwjzdvawkemjk9p76g6zar

2026-08-12T15:19:46Z

T1786547986.078:status:stx8f8fd296929e989a8c:kpwee4b66y+4136554082/g581121-cb6d43c5e65f9368b4cf409262c9c138f+4136556990

Nostr event nevent1qqs2nqyttm847lpp5a5w8nes6rknu253d0u87wrza74xryzegfjkm3qp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczypxgx8hhc607k47g2gvke25hedc84axkzg0s9lwjzdvawkemjk9p7gdwpnt

2026-08-12T15:21:15Z

T1786548075.227:status:stx8b928f:ktcskzuvnx+4136642504/g581121-dc6951e2c26dfaa199c29019a7cce5aeb+4136646166

Nostr event nevent1qqswlpsqkye4ev08jy9eve22pdx5egt92dc2qlp65d8zh4rgeekuf2qp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyzke4kc52779mleg6utct4k4mce0g54z5j9ucpjaaq894e9xtqhvxwqarjq

2026-08-12T15:19:42Z

entry https://86.gigafile.nu/1121-cde469c9a254c4cab4cefa23fc528cc10 | |

The Borrower is a Slave To The Lender. I never want to be a slave ...

2026-08-12T15:19:25Z

The Borrower is a Slave To The Lender.

I never want to be a slave again.

Once I get out of this mess, 100% debit/paying off borrowing, saving, & investing.

Never Never Never Borrowing Again, not to start a company, not to buy a car, or home.

I plan on saving, and investing.

Even if my fiat score hits the bed.

Buy, Borrow, Die maybe but I’ll have it set up where the net is going into growing more assets over time.

Nostr event nevent1qqsrwqnml9t2zn7p84e0ayczvc074fve4vyt3lrtm7dhcquhllkvpegp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyrj670dvnc0cxmy0nn7gmadwd6x4dlcxd3gwv8gmylucuzgge9pngae8zm5

2026-08-12T15:18:44Z

entry https://86.gigafile.nu/1121-d72d92c45fe2e3c3d9af2c264843a4a64 | |

Nostr event nevent1qqsw95m9zgz0za436rhtqpdhcngl26pc5gxs7mcc63yqj5a2jtlls4cp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczypxgx8hhc607k47g2gvke25hedc84axkzg0s9lwjzdvawkemjk9p7zpk6n9

2026-08-12T15:18:43Z

T1786547923.735:status:stx8b928f:k5djydu4xv+4136491714/g961121-c47b0fad71e3def77fcbb2ac9fcf5b211+4136494763

keet、nostr和simplex的异同

2026-08-12T15:18:24Z

In reply to nevent1q…n7qp
_________________________

keet、nostr和simplex的异同

During my childhood, I played with hide -and -see,now I’m an ...

2026-08-12T15:18:21Z

During my childhood, I played with hide -and -see,now I’m an adult, I don’t play with hide -and-see.

Nostr event nevent1qqsxvmrpzyg0mzj0ukezpxl47vce262jrdqaa5nttpgewmjd0qnqrusp8amhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm99amk2c3tdehhxarj8fex2mrp0yhxwatvw4nh2mr49ekk7ef0d35k6cfddd5kcmczyzkqn6vse87cqq4kc0pvy3j2wr75aj65z7f5229kyj20w2jvh42rxydld9y

2026-08-12T15:16:59Z

entry https://86.gigafile.nu/1121-cbf599b0b026fd7849be6f77a20daad33 | |