Bitcoin Optech's avatar
Bitcoin Optech
_@bitcoinops.org
npub1hkuk...432p
We provide weekly newsletters, workshops, case studies, and research for the #Bitcoin community.
Bitcoin Optech newsletter #256 is here: - summarizes a discussion about extending BOLT11 invoices to request two payments - includes 'Waiting for confirmation #6: Policy Consistency' from our series about policies for transaction relay and mempool inclusion - summarizes changes to services/client software - add Submarine swaps and Just-In-Time (JIT) channels topics - Optech Newsletter #256 Recap on Twitter Spaces Thomas Voegtlin posted to the Lightning-Dev mailing list to suggest BOLT11 invoices be extended to optionally allow a receiver to request two separate payments from a spender, with each payment having a separate secret and amount... Waiting for confirmation #6: Policy Consistency Last week’s introduced policy, a set of transaction validation rules applied in addition to consensus rules. These rules are not applied to transactions in blocks, so a node can still stay in consensus even if its policy differs from that of its peers. Just like a node operator may decide to not participate in transaction relay, they are also free to choose any policy, up to none at all... Changes to services and client software: - Greenlight libraries open sourced - Tapscript debugger Tapsim - Bitcoin Keeper 1.0.4 announced - Lightning wallet EttaWallet announced - zkSNARK-based block header sync PoC announced - lnprototest v0.0.4 released Submarine swaps are trust-minimized atomic swaps of offchain bitcoins for onchain bitcoins. A payment secured by an HTLC is routed over LN to a service provider who creates an onchain output paying the same HTLC... JIT channels are virtual LN channels hosted by a service provider. When the first payment to the channel is received, the service provider creates a funding transaction and adds the payment to it, creating a normal channel... Bitcoin Optech will be hosting an audio recap discussion of this newsletter with special guest Thomas Voegtlin on Twitter Spaces Thursday at 15:00 UTC. Join us to discuss or ask questions! https://twitter.com/i/spaces/1djxXloOldkxZ
Bitcoin Optech newsletter #255 is here: - summarizes discussion about allowing relay of txs containing taproot annex data - links to a silent payments draft BIP - includes 'Waiting for confirmation #5: Policy for Protection of Node Resources' from our series about policies for transaction relay and mempool inclusion - recaps the "Allow inbound whitebind connections to more aggressively evict peers when slots are full" PR Review Meeting - #255 Recap on Twitter Spaces Joost Jager posted to the Bitcoin-Dev mailing list a request for a change in the Bitcoin Core transaction relay and mining policy to allow storing arbitrary data in the taproot annex field... Josie Baker and Ruben Somsen posted to the Bitcoin-Dev mailing list a draft BIP for silent payments, a type of reusable payment code that will produce a unique onchain address each time it is used, preventing output linking... Waiting for confirmation #5: Policy for Protection of Node Resources A node that fully validates blocks and transactions requires resources including memory, computational resources, and network bandwidth. We must keep resource requirements low in order to make running a node accessible and to defend the node against exploitation... Allow inbound whitebind connections to more aggressively evict peers when slots are full is a PR by Matthew Zipkin (pinheadmz) that improves a node operator’s ability in certain cases to configure desired peers for the node... Bitcoin Optech will be hosting an audio recap discussion of this newsletter with special guests Gloria Zhao, Joost Jager, Josie Baker, Ruben Somsen, and Matthew Zipkin on Twitter Spaces Thursday at 15:00 UTC. Join us to discuss or ask questions! https://twitter.com/i/spaces/1ynKOaqgqOWJR
Bitcoin Optech newsletter #254 is here: - summarizes mailing list discussion about using the MATT proposal to manage joinpools and replicate functions of the OP_CHECKTEMPLATEVERIFY proposal - includes 'Waiting for confirmation #4: Feerate estimation' from our series about policies for transaction relay and mempool inclusion - Optech Newsletter #254 Recap on Twitter Spaces