Socratic Seminar 33
2023-01-30
Housekeeping
- This meetup is generously sponsored by Digital Garage and Bitrefill.
- Questions are encouraged, including basic ones!
- Socratic Seminars are held under the Chatham House Rule: share the information you receive, but do not reveal the identity of who said it.
- For the privacy of other attendees, please refrain from taking photographs of other people without their permission.
- Socratic seminars are best when the moderator can let the conversation flow, so try to keep things concrete and focused.
- The reading list covers November 28th to January 30th.
Chain Weather Report
News and Announcements
- BinaryWatch.org - Coinkite's Checksum Checker
- Bitcoin Binary
- Ledger Supports Miniscript
- Bitcoin Taproot address now supported on Kraken
- Liana Wallet
- Optech
- Luke Jr. was hacked & PGP key compromised. Don't download/trust Bitcoin Knots.
- Bitcoin Knots signing key compromised
- LastPass pwned
Research and Development
- OP_VAULT Proposal
- BIP324: v2 P2P Transport Protocol merged
- SIGHASH_GROUP vs Ephemeral anchors
- bitcoin-inquistion 23.0: evaluating soft forks on signet
- Samourai Whirlpool Client Rust Crate
- Coldcard Mk4 Security Model and Secure Element Use
- Wallet Label Export Format BIP Merged
- NIP-47: BIP-47 payment code notification via Nostr DM
Bitcoin Core
- Ephemeral anchors implementation in Bitcoin Core
- POLICY: Relax MIN_STANDARD_TX_NONWITNESS_SIZE to 65 non-witness bytes
- rpc, gui: bumpfee signer support
- rpc: Enable wallet import on pruned nodes and add test
- rpc: Allow named and positional arguments to be used together
- Getting off of GitHub
RBF
- Full-RBF Peering Bitcoin Core v24.0.1 Released
- At least 17% of v24.x listening nodes are running full-rbf This data is also an underestimate: I'm only measuring successful propagation.
- RBF Replacement Monitor
- miners who have made a long-term capital investment in mining equipment might instead prefer to optimize fee income over multiple blocks It's also possible that owners of ASICs or pool operators will decide that they're in this for the long term, and therefore that it's smarter to look at fee income over multiple blocks, rather than taking each block as its own entity. Similar to treating the prisoner's dilemma as a one-off game (where the dominant strategy is to always defect) versus an iterated game (where cooperation or tit-for-tat may be better strategies).
- Why Full-RBF Makes DoS Attacks on Multiparty Protocols Significantly More Expensive
- Full RBF double-spend mined
Lightning
- Factory-Optimized Protocols Proposal
- Jamming against Channel Jamming
- Swap-in-Potentiam: Moving Onchain Funds "Instantly" To Lightning
- Mitigating Channel Jamming with Reputation Credentials: a Protocol Sketch
- Accept feerate increases even if they aren't high enough for us
- Factory-Optimized Protocols For Lightning
- Taproot Lightning Channel
- Possible Attack IF we add BOTH upfront AND negative routing fees to the Lightning Network
- WoS doing 20k payments/day
Ordinals
- Inscriptions hit mainnet
- ord
- inscriptions
- bitcoin-dev notices
- Development driven by illicit inscriptions.
Q&A
- Why is connecting bitcoin exclusively over Tor considered bad practice?
- Why aren't 3 party (or more) channels realistically possible in lightning today?
- When is a Miniscript solution malleable?
- BLS signatures vs Schnorr
- PR Review Club: Bump unconfirmed ancestor transactions to target feerate
- Follow-up to Segwit: Arbitrary data storage in witness?