Bitcoin dev, last 7 days. 7 new threads on Delving Bitcoin / bitcoindev list.
• [BIP Draft] Co-signer Spending Policies (new), lukecarriere
“I’d like feedback on a draft that standardizes the policy a co-signer enforces, not the co-signer itself. A co-signer that signs only when a predicate holds is a known way to emulate covenants today. Towns described the multisig version of…”
https://delvingbitcoin.org/t/bip-draft-co-signer-spending-policies/2955
• Cassis, a new simple scheme for generic multi-layer multi-hop HTLC routing (new), andunie
“Bitcoin payments are now spread across many so-called “layers”, and there isn’t a sufficiently generic way to make payments between them. In most cases, each layer has to run a Lightning node, and its users are more or less dependent on…”
https://delvingbitcoin.org/t/cassis-a-new-simple-scheme-for-generic-multi-layer-multi-hop-htlc-routing/2952
• Anchoring an SPV light client on another chain: checkpoint trust, retargeting and reorg handling (new), sebas
“I work on Writz Protocol, an open-source lending protocol where BTC collateral stays on Bitcoin and loans are issued as USDC on Stellar. I would like critique of the Bitcoin-facing parts, because that is where I least want to be wrong.…”
https://delvingbitcoin.org/t/anchoring-an-spv-light-client-on-another-chain-checkpoint-trust-retargeting-and-reorg-handling/2939
• Disclosure: DoS vulnerabilities fixed in Eclair v0.14.1 (3 posts, latest by morehouse), erickcestari
“If you are using a mobile wallet that uses an Eclair node as an LSP (i.e. Phoenix), you should be unaffected by these vulnerabilities. ACINQ patched their Eclair nodes months ago.”
https://delvingbitcoin.org/t/disclosure-dos-vulnerabilities-fixed-in-eclair-v0-14-1/2928
• [list] Lichen: L2s In CHannels ENforced on bitcoin (3 msgs), waxwing/ AdamISZ
“Hi Dustin, In short, yes, I think it *is* responsible! To advocate for my position: I think it is irresponsible to *not* promote versions of bitcoin payment systems that give users a crucial advantage of freedom via privacy, in ways that…”
https://gnusha.org/pi/bitcoindev/4463542b-5553-4b3c-8c7f-3ce7edb7bb1fn@googlegroups.com/
• [list] Flame: confidential transactions with Bitcoin proof-of-burn consensus, Oleg Andreev OOO
“Hi Adam, thanks for showing interest in Flame! On burning. We have considered a one-way peg as Ruben proposes (meaning, when X units of BTC are converted one-way into X units of "SideCoin"). The problem is: such conversion erases…”
https://gnusha.org/pi/bitcoindev/9517998B-3019-4ADE-B566-F30D42F33C37@gmail.com/
• [list] BIP 300: 26% censoring attack, Ori Newman
“It seems like a 26% attacker can censor BIP 300 bundles indefinitely: Assume some drivechain publishes a valid bundle, the attacker can send ALARM messages in all of her blocks to reduce its score by 1 in each block. Since the expected…”
https://gnusha.org/pi/bitcoindev/2e554c89-a2a1-4bcf-941c-32f6a8ba9567n@googlegroups.com/
Quotes are verbatim openings, not summaries. (bot-run)
#bitcoin #bitcoindev
Hexbox Tools
npub1uz…y2v6g
2026-10-13 08:30:22 UTC
Author Public Key
npub1uzqr4r5m8z7fj4lth30ul43vw645ye0mjpkxdl9aywam3f92cz6s4y2v6gPublished at
2026-10-13 08:30:22 UTCEvent JSON
{
"id": "0bcc04b7e04dd42b89bb9280abdb677525478daf2854ca0d06e686a592438c86",
"pubkey": "e0803a8e9b38bc9957ebbc5fcfd62c76ab4265fb906c66fcbd23bbb8a4aac0b5",
"created_at": 1791880222,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
],
[
"t",
"bitcoindev"
],
[
"r",
"https://delvingbitcoin.org/t/bip-draft-co-signer-spending-policies/2955"
],
[
"r",
"https://delvingbitcoin.org/t/cassis-a-new-simple-scheme-for-generic-multi-layer-multi-hop-htlc-routing/2952"
],
[
"r",
"https://delvingbitcoin.org/t/anchoring-an-spv-light-client-on-another-chain-checkpoint-trust-retargeting-and-reorg-handling/2939"
],
[
"r",
"https://delvingbitcoin.org/t/disclosure-dos-vulnerabilities-fixed-in-eclair-v0-14-1/2928"
],
[
"r",
"https://gnusha.org/pi/bitcoindev/4463542b-5553-4b3c-8c7f-3ce7edb7bb1fn@googlegroups.com/"
],
[
"r",
"https://gnusha.org/pi/bitcoindev/9517998B-3019-4ADE-B566-F30D42F33C37@gmail.com/"
],
[
"r",
"https://gnusha.org/pi/bitcoindev/2e554c89-a2a1-4bcf-941c-32f6a8ba9567n@googlegroups.com/"
]
],
"content": "Bitcoin dev, last 7 days. 7 new threads on Delving Bitcoin / bitcoindev list.\n\n• [BIP Draft] Co-signer Spending Policies (new), lukecarriere\n“I’d like feedback on a draft that standardizes the policy a co-signer enforces, not the co-signer itself. A co-signer that signs only when a predicate holds is a known way to emulate covenants today. Towns described the multisig version of…”\nhttps://delvingbitcoin.org/t/bip-draft-co-signer-spending-policies/2955\n\n• Cassis, a new simple scheme for generic multi-layer multi-hop HTLC routing (new), andunie\n“Bitcoin payments are now spread across many so-called “layers”, and there isn’t a sufficiently generic way to make payments between them. In most cases, each layer has to run a Lightning node, and its users are more or less dependent on…”\nhttps://delvingbitcoin.org/t/cassis-a-new-simple-scheme-for-generic-multi-layer-multi-hop-htlc-routing/2952\n\n• Anchoring an SPV light client on another chain: checkpoint trust, retargeting and reorg handling (new), sebas\n“I work on Writz Protocol, an open-source lending protocol where BTC collateral stays on Bitcoin and loans are issued as USDC on Stellar. I would like critique of the Bitcoin-facing parts, because that is where I least want to be wrong.…”\nhttps://delvingbitcoin.org/t/anchoring-an-spv-light-client-on-another-chain-checkpoint-trust-retargeting-and-reorg-handling/2939\n\n• Disclosure: DoS vulnerabilities fixed in Eclair v0.14.1 (3 posts, latest by morehouse), erickcestari\n“If you are using a mobile wallet that uses an Eclair node as an LSP (i.e. Phoenix), you should be unaffected by these vulnerabilities. ACINQ patched their Eclair nodes months ago.”\nhttps://delvingbitcoin.org/t/disclosure-dos-vulnerabilities-fixed-in-eclair-v0-14-1/2928\n\n• [list] Lichen: L2s In CHannels ENforced on bitcoin (3 msgs), waxwing/ AdamISZ\n“Hi Dustin, In short, yes, I think it *is* responsible! To advocate for my position: I think it is irresponsible to *not* promote versions of bitcoin payment systems that give users a crucial advantage of freedom via privacy, in ways that…”\nhttps://gnusha.org/pi/bitcoindev/4463542b-5553-4b3c-8c7f-3ce7edb7bb1fn@googlegroups.com/\n\n• [list] Flame: confidential transactions with Bitcoin proof-of-burn consensus, Oleg Andreev OOO\n“Hi Adam, thanks for showing interest in Flame! On burning. We have considered a one-way peg as Ruben proposes (meaning, when X units of BTC are converted one-way into X units of \u0026#34;SideCoin\u0026#34;). The problem is: such conversion erases…”\nhttps://gnusha.org/pi/bitcoindev/9517998B-3019-4ADE-B566-F30D42F33C37@gmail.com/\n\n• [list] BIP 300: 26% censoring attack, Ori Newman\n“It seems like a 26% attacker can censor BIP 300 bundles indefinitely: Assume some drivechain publishes a valid bundle, the attacker can send ALARM messages in all of her blocks to reduce its score by 1 in each block. Since the expected…”\nhttps://gnusha.org/pi/bitcoindev/2e554c89-a2a1-4bcf-941c-32f6a8ba9567n@googlegroups.com/\n\nQuotes are verbatim openings, not summaries. (bot-run)\n#bitcoin #bitcoindev",
"sig": "67b968569666c57936e53b47865458ae34c0e1dfdca38d93854fb28499783bf5e8bfdc01f1fc7d56ca87b37f8cc078876ef7cb7f971a0b11cba4bccf6495f6f3"
}