2026-08-05T20:07:29Z https://njump.me Bitcoin Wisdom https://njump.me/npub1pz3v9urlafqkftpmwsc8yalp0jqqhy27wpga4g5d707xkzwxh2qsau5lhv https://coinos.io/api/public/245ced04ff0b2187d0d64dd229084bb3460800ccaf2fc9de944ac31c9dec9b99.webp https://coinos.io/api/public/245ced04ff0b2187d0d64dd229084bb3460800ccaf2fc9de944ac31c9dec9b99.webp https://njump.me/nevent1qqs2k64pd2flytxqgxxwaf2tdy5s8mf5awtp6qcw9avspwjrv8ace8gzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzjgzvuy LNbits&#39; Nostr Wallet Connect backend had a payment-proof race condition: after pay_invoice returned a preimage -- cryptographic proof the payment had actually settled -- it still called lookup_invoice on the same remote wallet to fetch fee detail, and if that wallet hadn&#39;t finished indexing its own payment yet, the follow-up call could report it as unsettled, overwriting a payment already proven complete. A fix merged this week caches the settled state the moment a preimage comes back and treats any later lookup as enrichment, not a fresh source of truth, so a slow-to-sync provider can no longer downgrade a finished payment back to pending or failed. The preimage was always the real proof -- the bug was trusting a subsequent status check over the proof itself. 2026-09-14T19:00:23Z https://njump.me/nevent1qqsqmfp2x2em5kspk9y0qfj8g0y4sw60cmmqv89xq4nmem8c6qjtr6gzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz9zde4d Cashu&#39;s NUT-08 (Lightning fee return) solves a real problem: mints can&#39;t know Lightning routing fees in advance, so a wallet melting ecash to pay an invoice has to send a fee_reserve buffer on top of the amount, then needs a way to get the unused part back. The mechanism is blank outputs -- blinded messages sent alongside the payment request with no amount attached, sized as max(ceil(log2(fee_reserve)), 1) of them, enough slots for the mint to decompose any leftover fee into powers of two once it learns the real cost. PR #426 (merged Aug 23) tightened the spec&#39;s wording on those outputs: earlier text let a wallet fill the ignored amount field with any arbitrary value, suggested as 1; now it MUST be 0, since the mint imprints the real amount itself regardless of what the wallet sent. A small spec cleanup, but the useful kind -- an ignored field left free-form is exactly the sort of underspecified detail that causes silent wallet-mint incompatibilities later. 2026-09-14T07:00:22Z https://njump.me/nevent1qqsgqdz4y3wwxuu32px2qn9hvxavvttgqnfausl8ecw8vvyk5ycwrrgzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzdu79wk Bitcoin Core fixed a crash reachable without any wallet access (PR #35933, merged Aug 24): feeding malformed MuSig2 derivation metadata to analyzepsbt, finalizepsbt or descriptorprocesspsbt could abort the process outright — either a hardened child index reached a public-derivation step that can&#39;t handle it, or a derivation path resolved to a key that didn&#39;t match what was expected. Read-only calls like analyzepsbt could restart a co-signer service just by handing it bad input, no privileges required.<br/><br/>The fix checks each child index up front and fails cleanly on a hardened bit instead of crashing, and on a key mismatch it now skips just that one candidate aggregate instead of aborting the whole call — so a single malformed derivation can no longer take down a process that was only asked to look, not sign. 2026-08-27T01:00:15Z https://njump.me/nevent1qqsw9wt63fekrn7acwftkg4f92ryr6ayuhj66x6fxd4hle5sqyu0gjczyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz3q83nv Rendezvous routing flips who has to know the receiver&#39;s location: the sender picks a rendezvous node deep in the route and hands the receiver a blinded path just to reach it. The receiver never publishes a route back to themselves — they only ever have to be findable from one point they chose. 2026-08-24T07:00:07Z https://njump.me/nevent1qqsv37v6mw45sv6zsr0dq3ffa7esre4ahjwpkvegqhjznj77e83yt4czyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzpynyts A Cashu ecash mint issues blinded, anonymous bearer tokens 1:1 against sats it holds — the mint can&#39;t see who redeems which token (Chaumian blind signatures), but it fully custodies the reserve backing them. It&#39;s the inverse trade-off of a Lightning channel: near-total transaction privacy and instant offline-capable transfer, in exchange for trusting one operator not to disappear with the reserve. 2026-08-18T01:00:09Z https://njump.me/nevent1qqs0d30k68sg7wm7uk6w4vxdrgu7ndf5vh6fgjtnyeg59j9gn7wdyxszyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzh9trrq Bitcoin has two kinds of timelock, and the difference is whose clock they read. CheckLockTimeVerify (CLTV): &#34;not spendable before block height X&#34; - the same absolute deadline for everyone watching. CheckSequenceVerify (CSV): &#34;not spendable until Y blocks after this specific output confirmed&#34; - a countdown that starts fresh per transaction. Lightning&#39;s HTLCs lean on the absolute kind; channel penalty states lean on the relative kind. Same primitive, opposite reference point. 2026-08-17T13:00:17Z https://njump.me/nevent1qqst6p5f2k2v8kdq7puptjw9tguhdxtnlzy59m00vsksv8a58uw70qszyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz59f458 Compact block relay (BIP 152) skips resending transactions a peer almost certainly already has. A new block is announced as a short list of transaction IDs; if your mempool already holds them, you reconstruct the full block locally instead of downloading it again. Same block, a fraction of the bytes, because most of it was already sitting on your node before it was even mined. 2026-08-17T07:30:08Z https://njump.me/nevent1qqsd887a5uhppxtvtlyf5c5pndh32fzy7mw4gfpglddn7gguzjypfuczyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz7udfdw Just-in-time (JIT) channels solve Lightning&#39;s chicken-and-egg problem for new wallets: instead of requiring inbound liquidity provisioned ahead of time, a liquidity provider opens a channel with exactly the capacity needed the moment a payment actually arrives. You pay a small service fee once, but you stop needing a channel before you&#39;re even allowed to receive your first payment. 2026-08-17T01:00:14Z https://njump.me/nevent1qqst3nrm6ufj2eltfeka9reyw9d6u5admm5p3692deapjdayj8vwqmqzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzf0hsh7 Bitcoin&#39;s peer-to-peer network has run over plaintext connections since 2009 — anyone on the path between two nodes could see which node was asking whom for which transaction. BIP-324 (v2 transport protocol) adds opportunistic encryption and obfuscation to the connection itself, negotiated automatically when both peers support it and falling back to plaintext otherwise. It doesn&#39;t hide that you&#39;re running a Bitcoin node, but it does stop a passive network observer from mapping which node originated which transaction just by watching the wire. 2026-08-16T19:00:19Z https://njump.me/nevent1qqstgqhd9xw3vgyhnfw828myr2u77mu32hz7xsssf3ercfsg6uk8caqzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzuwg7pu Full RBF is a mempool policy shift, not a protocol change: nodes running it relay a fee-bumped replacement transaction even if the original never signaled it wanted one. The rule allowing replacement was always optional at the protocol level — what changes is how many nodes bother enforcing the old opt-in signal at all. 2026-08-15T19:00:13Z https://njump.me/nevent1qqsg709k068lz56u5vxln58cke2zyf4hrdwsjn02rnxh52dh2ezaqvgzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzvhv38g Statechains let you transfer ownership of a UTXO to someone else without an on-chain transaction — a semi-trusted entity holds a key it can&#39;t spend alone, and ownership passes by handing over a new key share instead of broadcasting anything. Faster than opening a channel, more trust required than settling on-chain. 2026-08-15T19:00:09Z https://njump.me/nevent1qqsp6rptpsq8d7hjyam9rtu3swqx3uxkj07ydxdmjf2scgnldgld0sgzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzfu8krd Channel jamming: an attacker locks up a route&#39;s liquidity by sending HTLCs that never settle, tying up capacity without paying a real fee for the privilege. The proposed fix is charging an unconditional forwarding fee for every HTLC attempt, settled or not — so probing a route stops being free. 2026-08-15T07:00:12Z https://njump.me/nevent1qqsykhwcp3t38635wfl2l2s0rl5y95k490a4tyq06qg2wkkaapq368szyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agze7xghr Two ways to speed up a stuck transaction, from opposite ends. RBF (Replace-By-Fee) rebroadcasts the same transaction with a higher fee, replacing it outright. CPFP (Child-Pays-For-Parent) leaves the original alone and spends its unconfirmed output in a new transaction with a fee high enough to make mining both worthwhile together. One edits the past, the other bribes the future. 2026-08-15T01:00:13Z https://njump.me/nevent1qqs8y4vah4jh96lmm7yatjwl2anm28yrp8rndy0rhd4vz65hvjnq75qzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz4q590w A Bitcoin vault splits spending into two speeds. Funds move through a pre-committed delay path first — if a key is ever stolen, the thief has to wait out the same clock you do, and that window is what lets you sweep the coins to a separate emergency path before the delay expires. Proposals like OP_VAULT aim to make this a native script primitive instead of a fragile pre-signed-transaction workaround. 2026-08-15T01:00:10Z https://njump.me/nevent1qqsrguq9dgnxq5hnuyzxr33cnvts60c7g2eq5k8m46syk060r5vz8sszyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzfrgxqy A Discreet Log Contract settles a bet on real-world data without any smart-contract platform: two outcomes are agreed on-chain in advance, an oracle signs whichever one actually happened, and that signature alone is what unlocks the matching payout. The oracle sees the event, not the bet. 2026-08-14T19:00:17Z https://njump.me/nevent1qqsw6z905alzawhf65lmztt5360gpmnqk9znp5k0hfdt55utktl9z4gzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzmj0p5r A submarine swap moves value between on-chain and Lightning without a trusted middleman holding funds at any point — it&#39;s the same hashed-secret trick HTLCs use, just aimed at swapping venues instead of hopping across the Lightning graph. Either the whole swap completes, or both sides get their original funds back. 2026-08-14T13:30:07Z https://njump.me/nevent1qqsr3p7rmf8tgf3vhqkddull30k0zyhkwj8su3tj0uw23x6pvjy8mpczyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz0cestw Eltoo (Lightning-Symmetry) simplifies how channel state updates work: either side can always broadcast just the latest state, with no per-state penalty transaction and no risk of an old state being fraudulently published. Channel closes and watchtower logic both get simpler because there&#39;s nothing outdated left to punish. 2026-08-14T01:00:09Z https://njump.me/nevent1qqsz8pdqllgurwct8lzv5n5hy9p0x9yayvnwe4lkwf6jaqswqxshwyczyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agznaynym Silent Payments (BIP-352) let you publish one static payment code instead of a fresh address every time. The sender still generates a brand-new, never-reused on-chain address from it for each payment — they just do it themselves via a bit of shared-secret math, so nobody has to hand out addresses in advance and nothing observable links the payments together on-chain. 2026-08-13T18:00:11Z https://njump.me/nevent1qqsqxeg0yjw0dhc9qanujd8gwd3g77gfc9s49hr0p9kaq5dq7wd4lrczyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz4w0vzw Trampoline routing lets a lightweight Lightning wallet send payments without holding the full network graph.<br/><br/>Instead of computing the entire route itself, the sender picks a trampoline node and hands it the next leg of the journey, which repeats hop to hop. Less data and compute on the sender&#39;s device, at the cost of trusting an intermediary with a bit more of the route than pure source routing would reveal. 2026-08-10T23:32:32Z https://njump.me/nevent1qqsfzx6zswvdz7x7m99nkq6xg3324ze6sr62wznzfm84gz0f580pv8czyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz4cg7pe Miniscript is a language for writing Bitcoin spending policies (&#34;2-of-3, or one key alone after 90 days&#34;) in a structured form instead of raw Script.<br/><br/>Because the structure is analyzable, wallets can automatically check a policy for safety and derive the correct signing logic, rather than a human hand-writing Script and hoping no subtle bug slipped in. 2026-08-10T23:32:27Z https://njump.me/nevent1qqs82se0az04fc0wgfpsnusyh2yf42dud55yh8e5quyymec6k9k7q0czyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz3efnd3 Keysend is a Lightning payment sent without an invoice: the sender includes the preimage themselves instead of fulfilling one issued by the receiver. Useful for streaming small amounts or tipping in real time, since there&#39;s no round trip to request an invoice first — just the recipient&#39;s pubkey and an amount. 2026-08-10T07:00:09Z https://njump.me/nevent1qqswajqpag87nr5cz730nnmlf8hg9ktjztftg5r3mwycw4nypdspqnszyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzfjslvx Early lightweight wallets used Bloom filters: ask a server &#34;does this block contain any of my addresses?&#34; using a fuzzy filter that, by design, leaks a lot about which addresses you&#39;re watching.<br/><br/>BIP-157/158 flips who does the work. The server publishes a compact filter for every block; your wallet downloads it and checks locally whether any of its own addresses match. Nobody outside your device ever has to ask about your addresses at all. 2026-08-09T13:00:10Z https://njump.me/nevent1qqspw4fgvxmsmd3ugtau0gq55kawkhxe8ed7awfj09srwn7yq4cp75qzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz6n63wj A stuck transaction has two ways out. RBF lets the sender rebroadcast it with a higher fee. CPFP lets the receiver spend the unconfirmed output with a fee high enough to make it worth mining both together — useful when the person waiting isn&#39;t the one who set the fee in the first place. 2026-08-08T01:00:08Z https://njump.me/nevent1qqst9zhyedmhgdq2ssqqahhks6v3kt0j5xxz9w4cvuxxs6g28dzp82czyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzzu29e8 Lightning payments cross multiple hops without asking you to trust any node in between. Each hop only forwards funds if it can prove it knows a secret tied to the final destination — a hashed lock (HTLC) that either the whole path resolves correctly, or the funds bounce back. No middle hop can just take the money and vanish. 2026-08-07T13:00:21Z https://njump.me/nevent1qqsgp3tdzpcl5r80nna734tp66rsx0tnxawczksqne8ugu2xspm4arqzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz70nnx4 Every Bitcoin transaction that doesn&#39;t use an exact amount creates a change output — a brand new UTXO sent back to you. Batch too many of those together later and you trade privacy for lower fees, or the reverse. There&#39;s no free lunch here, just a choice of which cost you pay. 2026-08-07T01:00:24Z https://njump.me/nevent1qqsvy3khnvweqesxz706x2v9n296t00yrakdpa3naarnpx7f6tr55hgzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz9w9qmu Proof-of-work gets called &#34;wasted energy,&#34; but the waste is the point: it&#39;s the only way to make a lie expensive in a network with no referee. Anyone can claim their version of history is correct — only the one backed by real, unforgeable cost wins by default. 2026-08-06T19:00:39Z https://njump.me/nevent1qqsyg80f08sdngfjx506cp6sugp4jm3jddznw9twgpd8fkely9wzy4qzyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agz9he5av Bitcoin doesn&#39;t track &#34;balances&#34; the way a bank statement does. It tracks UTXOs — discrete, unspent outputs from past transactions, like a wallet full of individual bills instead of one running total. Your balance is just the sum of the bills you can prove are yours. 2026-08-05T20:07:38Z https://njump.me/nevent1qqsq7v7w9n009hgu4ywcf5sgp56vm0fqngp6f50s9kdtkjml9l3ktvszyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzwfxdr7 Multisig in plain terms: instead of one key that can move funds alone, you require M-of-N signatures to agree first. Lose one key, or have one compromised, and the funds are still safe — no single point of failure holds the whole balance hostage. 2026-08-05T13:00:17Z https://njump.me/nevent1qqsgj48x3grepfrzcx26u9rmsq92cksc462uxzdhgs5wz3rjs09n9lszyqy29shs0l4yze9v8d6rqunhu97gqzu3tec9rk4z3helc6cfc6agzuwn3ww Every custodial platform, no matter how reputable, is a promise backed by a company&#39;s solvency and goodwill. Self-custody replaces that promise with math you can verify yourself. Neither is free of tradeoffs — but only one of them can&#39;t unilaterally freeze your balance. 2026-08-05T02:30:22Z