Max

2.7K posts

Max

Max

@max3dwards

Nostr: npub1w4hx7dykxxz2430xh6twgzmht8gp3alczzpp96xfkj0wtl7tag0qn9ztxu

参加日 Mart 2010
596 フォロー中309 フォロワー
Max がリツイート
Alexander Leishman 🇺🇸
At @River we will continue to run Bitcoin Core because it is the only properly maintained Bitcoin node software. The Bitcoin Core dev team is highly competent and dedicated to the long-term success of the network. The current state of the debate around OP_RETURN relay rules is the result of overdramatizing a nuanced technical decision regarding tx standardness rules. Running poorly maintained forks of Bitcoin (with their own large flaws) because of this minor technical debate is an overreaction IMO. No Bitcoin Core dev wants the blockchain spammed with data because they are the ones forced to deal with the scaling issues and edge cases that follow. However, the reality today is that consensus rules allow transactions with large amounts of data in OP_RETURN, regardless of mempool policy! So, the broader debate here is twofold: 1. People want to put data onchain and they will do so with or without OP_RETURN limits. There is nothing stopping these people from skipping the mempool and submitting nonstandard txs directly to a mining pool today, or using even uglier approaches that bloat the UTXO set (even worse for the network). If we want to actually “fix” this, we would need a consensus fork, not a mempool rule change. The decision to change the standardness rules to allow these txs to be relayed seems reasonable and not a big deal. 2. The divergence between standardness rules and consensus rules: There are many transactions one could make that are valid by consensus rules that cannot be broadcast to the network today because they are “nonstandard”. This does not stop a miner from including the transactions in a block. High divergence between standardness rules and consensus rules leads to complexity in the Bitcoin Core software and causes problems for block relay efficiency when people start sending non-standard transactions direct to miners. Starting to move away from this divergence seems reasonable, but needs to be done carefully. We can likely never fully delete standardness rules but I understand the goal to reduce complexity here. This debate should remain objective and technical. It’s being blown way out of proportion. Remember, the vast majority of Bitcoin Core devs deeply care about the long-term health of Bitcoin and have dedicated their careers to getting Bitcoin where it is today.
English
217
186
1.4K
276.3K
Max がリツイート
Murch
Murch@murchandamus·
Could you please not conflate the transphobia in your self-selected personal bubble with “Bitcoin’s ethos”? Just because we share Bitcoin as an interest doesn’t mean that we share other worldviews.
English
28
19
339
22K
Max がリツイート
Cøbra
Cøbra@CobraBitcoin·
Bitcoin Core Version 27.0 is now available for download at bitcoin.org/en/download. The block on UK users downloading it is also now removed. For those that didn't know, it previously wasn't possible to download Bitcoin Core from the UK because of litigation. A good day. 🎉
English
32
96
564
29.1K
Max がリツイート
Hennadii Stepanov
Hennadii Stepanov@hhebasto·
Excited to announce progress on migrating Bitcoin Core's build system from Autotools to CMake! 🚀 Staging branch is packed with almost all features and primed for extensive testing. Big strides ahead! #BitcoinCore #CMake
English
7
13
74
3.8K
Max がリツイート
Murch
Murch@murchandamus·
BTW, the pull request github.com/bitcoin/bitcoi… proposes adding a coin selection algorithm to Bitcoin Core wallet that minimizes the input weight for a transaction. Review welcome.
English
0
10
51
3.3K
Max
Max@max3dwards·
@achow101 Mondays it looks like?
English
1
0
0
19
Ava Chow
Ava Chow@achow101·
@max3dwards 2 PM US Eastern Time, sometimes late, usually no more than 30 minutes though.
English
1
0
0
32
Carla Kirk-Cohen
Carla Kirk-Cohen@actuallyCarlaKC·
SimLN is a tool for simulating active lightning networks in any test environment: regtest or signet, local or cloud! Its goal is to allow LN app and protocol devs to test code in more realistic environments. BYON(etwork) and let SimLN do the rest ⚡ simln.dev
English
4
81
175
23.8K