Skip to content

adds topics #1

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Nov 7, 2025
Merged

adds topics #1

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
36 changes: 32 additions & 4 deletions _posts/2025-11-13-socratic-seminar-70.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,11 +13,19 @@ Doors open at 6pm with discussion starting shortly after!

[Follow ChiBitDevs on twitter](https://x.com/chibitdevs)

# BIP 444
## BIP 444 - Reduced Data Temporary Softfork

## [Reduced Data Temporary Softfork](https://github.com/bitcoin/bips/pull/2017)
This BIP written by Dathon Ohm introduces a temporary softfork to limit the size
of data fields at the consensus level.
This BIP written by Dathon Ohm introduces a temporary softfork to limit the size of data fields at the consensus level.

- New output scriptPubKeys exceeding 34 bytes are invalid, unless the first opcode is OP_RETURN, in which case up to 83 bytes are valid.
- OP_PUSHDATA* with payloads larger than 256 bytes are invalid, except for the redeemScript push in BIP16 scriptSigs.
- Spending undefined witness (or Tapleaf) versions (ie, not Witness v0/BIP 141 nor Taproot/BIP 341) is invalid.
- Witness stacks with a Taproot annex are invalid.
- Taproot control blocks larger than 257 bytes (a merkle tree with 128 script leaves) are invalid.
- Tapscripts including OP_SUCCESS* opcodes anywhere (even unexecuted) are invalid.
- Tapscripts executing the OP_IF or OP_NOTIF instruction (regardless of result) are invalid.

<https://github.com/bitcoin/bips/pull/2017>
Inspired by Luke-JS's [mailing list post](https://gnusha.org/pi/bitcoindev/aN_u-xB2ogn2D834@erisian.com.au/T/#mb71350c5dfb119efeb92c5ee738b6c8225bf15b6)

## [BIP444-Airdrop](https://github.com/mikekelly/BIP444-Airdrop)
Expand All @@ -34,3 +42,23 @@ signature aggregation

## [Pheonix wallet adds taproot channel support](https://x.com/PhoenixWallet/status/1983524047712391445)
Pheonix wallet announced that they are adding taproot channel support!

## Arkade on Mainnet
Arkade launches on Bitcoin mainnet in public beta.

<https://x.com/arkade_os/status/1980607782945485056>
<https://arkade.money>
<https://docs.arkadeos.com>

## libbitcoinkernal Library C Header API Merged
This is a first attempt at introducing a C header for the libbitcoinkernel library that may be used by external applications for interfacing with Bitcoin Core's validation logic. It currently is limited to operations on blocks.

<https://github.com/bitcoin/bitcoin/pull/30595>

## Chain Code Delegation for Private Collaborative Custody
Collaborative custody and multisig setups have long faced a tradeoff between safety and privacy. Sharing a key with a third party—whether for recovery, policy enforcement, or convenience—has traditionally meant giving that party visibility into a user’s wallet balance and transaction history.

A new proposal called Chain Code Delegation aims to remove that tradeoff.

<https://bitkey.build/chain-code-delegation-improving-privacy-in-collaborative-multisig/>
<https://github.com/bitcoin/bips/pull/2004>