NETF RE₳K

Digital mercenary

[NETF RE₳K @netf_reak]

@laraqui @simonw pricing, reliability, data locality, simple deployment (single binary)

[NETF RE₳K @netf_reak]

@VictorTaelin my experience as well - fable was the only one to be able to handle large codebase with ease

[NETF RE₳K @netf_reak]

@Heccles94 All so called socialists (leftists) should experience communism

[NETF RE₳K @netf_reak]

@BasilTheGreat https://t.co/PbnWXFJxrk

[NETF RE₳K @netf_reak]

@sikorskiradek @grok czy dolaczenie Polski do strefy euro jest w jej najlepszym interesie czy nie. Wyjasnij

[NETF RE₳K @netf_reak]

just cancelled @OpenAI and @AnthropicAI subscriptions and switched over to @deepseek_ai . It's free and open source (MIT licensed) and I like responses a lot more than chatgpt gpt/o1 or claude

[NETF RE₳K @netf_reak]

@jatinsipan 0203ADaAab66739aAdEd7F888Aa54440Cf1297D1C3752D24C7039177f7bB6Be9b267

[Jason Dreyzehner @bitjson]

The May 2024 upgrade to Bitcoin Cash (BCH), CHIP-2023-04 Adaptive Blocksize Limit Algorithm, is now active on chipnet at block #174519 (0000000068675ff881ff763de0c4b47b8da8f64c7800c016a9dac60f7f8e0007)! 🎉

This upgrade resolves an economic vulnerability that was introduced in 2010 and led to the BCH/BTC network split in 2017.

The algorithm automatically adjusts Bitcoin Cash's block size limit to reduce infrastructure costs during periods of lower usage while enabling up to a doubling of the maximum block size per year at peak growth.

Why Limit Block Size?

The block size limit caps the technical requirements of network infrastructure, enables reliable infrastructure cost projection, and prevents attacks that increase the cost of participating in the network.

Excessively large blocks could require users and businesses to waste resources on unnecessary infrastructure, switch to cheaper and less secure validation strategies, or even to abandon running their own infrastructure and instead rely on third-party service providers – reducing the overall privacy, independence, and financial freedom of all users.

Vulnerability of Static Block Size Limits

To limit block size, most bitcoin-like networks (BCH, BTC, BSV, XEC, etc.) employ a static block size limit. For Bitcoin Cash mainnet, this limit is currently 32MB.

If a payment network is growing, usage will eventually approach any previously-established static limit. If this limit is reached before a successfully coordinated upgrade, network service degrades: transaction fees and confirmation times become less predictable as size-limited blocks become more common.

Uncorrected, market actors begin to adapt to this artificial scarcity by using alternatives to on-chain transactions: custodians, intermediaries, and competing networks. This in turn compromises the long-term economics of mining – cumulative transaction fee revenue is suppressed, and long-term network security grows to rely on continuous inflation via block subsidies.

Because static block size limits can only be changed as part of a widely coordinated network upgrade, they present a focal point for network interruption or capture by motivated attackers: rent seeking institutions, competing networks, opponents of peer-to-peer cash, etc. To make matters worse, the attackers have a significant coordination advantage – while honest network participants must achieve near-unanimous consensus to activate an upgrade, attackers must only create sufficient uncertainty among the honest participants to delay limit increases, as inaction results in degradation of the network’s functionality and long-term security.

Adaptive Block Size Limits

Adaptive block size limits resolve the economic vulnerability of static limits by automatically adjusting the maximum block size over time.

While an adaptive block size limit could still diverge from a hypothetical "ideal" size due to significant changes in the rate of technological advancement or the availability of capital, such divergences would likely remain much smaller than with static limits, and attackers are no longer afforded an advantage.

Bitcoin Cash's Adaptive Algorithm

The new algorithm is conservative and based on observed usage. In cooling-off periods of falling network usage, the limit slowly decreases to preserve the resources of infrastructure operators. On the other hand, during periods of rapid growth, the limit can increase at a rate of up to 2x per year.

---

This post is adapted from my earlier blog post about the May 2024 upgrade. You can find more information about this upgrade and Bitcoin Cash's upgrade process in that post (link in bio). Thanks for reading!

[NETF RE₳K @netf_reak]

@udiWertheimer Luckily Monero, BCH - work every single time - no matter how big or small transaction is. What happened to magic internet money?

[Nikita Zhavoronkov @nikzh]

The defence against this attack (or Ordinals if one considers them a bug) is a block size increase.

Increase the block size to 10 MB and this attack now costs $45 billion. 200 MB? A trillion!

The only real attack on Bitcoin, which is happening, is not increasing the block size.

[ҳɱཞıąŋ @Sttatatum]

Today's bitcoiners actually want a CBDC with a fixed supply and that's it. Because if it wasn't like that and they really understood bitcoin, they wouldn't be bitcoiners.

[NETF RE₳K @netf_reak]

@SoorajKSaju @earlightswindle @Justin_Bons nah we would be good and actually would be beneficial to the crypto space - BTC is what stopped crypto adoption when they decided not to scale on chain... do you remember Paypal / steam etc adopting Bitcoin ...

[Nikita Zhavoronkov @nikzh]

Days without finding a new critical Lightning Network vulnerability: 0

• https://t.co/MkL0r14OQh
• https://t.co/9X5Cmh6qoc
• https://t.co/qpSXMMiyQf

"We argue this replacement cycling is one of the most practical way to steal Lightning funds" 🤔

[NETF RE₳K @netf_reak]

@danieleripoll It’s impossible to understand something if your bags depend on you not understanding it.

[NETF RE₳K @netf_reak]

@TheCardanoTimes That’s true. They slow rugged bch community. That’s why I will never invest in anything Milk related.

[NETF RE₳K @netf_reak]

@nitesh_btc cool idea would be to increase the block size and allow every one to do cheap transactions on chain ... crazy stuff isn't it

[NETF RE₳K @netf_reak]

@Benny_Stacks @TheBCHPodcast @DILDOMAN5000 @SeverinAlexB @Truthcoin Zero conf transactions on #Bitcoin Cash are instant and they never failed me - not once and been using it to pay for stuff for a long time

[NETF RE₳K @netf_reak]

@svpino This is why there is no point in being permanent employee ever ... it's like a slavery reimagined. Sharp people should always go on contracting and ALWAYS work with multiple clients (whenever possible)

[Nikita Zhavoronkov @nikzh]

It's infinitely funny, but it seems like Lightning is prone to dirt-cheap spam attacks 😅

https://t.co/hUCdQMxIXT

Will they build a PoW system on top of Lightning to counter that? Oh waaait! 🤪

The icing on the cake? The spammer's message is "don't use custodial wallets" 🤣