peetah哥 (SP: 🥷🏿Kilobyte Ken)

S Class Hero | Scaling to Infinity = Blocksize to Zero. It's maths folks. Do not stop at 1MB. Perseverance builds resilience. 私家英雄-總策劃 [email protected]

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@LukeDashjr Finally. Somebody with the smart timing to move us in the right direction. Kilobyte Blocks is the future. Scarcity breeds definition. Definition begets value.

[Luke Dashjr @LukeDashjr]

The OP_RETURN discussion is not new and dates back to 2014 when Bitcoin Core 0.9.0 was released with the OP_RETURN policy included which was intended to discourage more egregious forms of spam. At that time, 40 bytes was the default max datacarriersize limit across all node implementations; this was and still is sufficiently large for tying data to a transaction (32 bytes for a hash and 8 bytes for a unique identifier). Core subsequently increasing the default to 80 bytes was an entirely voluntary decision and in no way contradicts the design objective that OP_RETURN creates a provably-prunable output to minimise damage caused by data storage schemes, which have always been discouraged as abusive. There are also other good technical reasons which I have chosen to retain the lower default in Bitcoin Knots, and no justification for increasing it.

It is not my intention, nor that of my team at @ocean_mining, to filter coinjoins. These present an innovative tool for increasing Bitcoin’s privacy and, when constructed properly, coinjoins can easily stay within the OP_RETURN limit (indeed, there is no reason for them to have *any* OP_RETURN data at all). I have some ideas on how to alleviate the recent issue where some coinjoin transactions were flagged as spam from Knots v25, and I am willing, with the full resources of my team, to work collaboratively on a solution in good faith.

Bitcoin does and always has allowed nodes to set filters based on multiple sets of criteria and Knots v25’s defaults are IMO what is best for Bitcoin at this time. Others may disagree and that is ok. They are free to (and should) run their own nodes - it is good for Bitcoin to have more people running nodes, including miners, and there should be a natural diversity in node policies. As was stated before, OCEAN is on a path to decentralization and very soon we are going to be in a position where hashers will be able to fully participate as miners and perform the intelligent parts of mining such as deciding which version of node software to run and what filters or other policies to apply to block template construction.

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

We’re heading to kilobyte blocks folks! Remember. It’s feasible! Three txs per block. One channel open. One channel close. One for liquidity swaps. That’s all we need. Every ten minutes. Still better than SWIFT which is less than 200 times a year.

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@BCHdotgames Bali Gee

[moledao @moledao_io]

On our Twitter Space tomorrow, it's about the Web3 Hong Kong Reboot!

Our speakers will discuss the Post-JPEX Landscape, ETFs vs STOs and crypto payment adoption trends.

With individuals from backgrounds such as entrepreneurship, ETF providers and legal, this Twitter space is one that's not to be missed!

📅15th November (Wednesday)
🕗8pm (GMT +8)

Set your reminders below!

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@peterktodd They didn’t choose BTC layer 1 either because RBF makes any sender able to freeze and seize their funds at will. Instantly. For 1 sat extra.

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@Ba1i9ee Rain baby rain!

[Bali Gee @Ba1i9ee]

BCH MOON! #IndependenceDay

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@cculianu MOAR TECHNICAL DEBT! Is Todd even considered core Core? RBF does *nothing* to help scaleability, we should instead make miners do 0.5M by default or 0.8-0.4-0.2M progression.

[Calin Culianu @cculianu]

Bitcoin Core wants to do full RBF on by default for all txns, even if they don't have the RBF flag set. Thus further hobbling BTC as a reliable form of payment. I hope they merge this ASAP. This is good for Bitcoin Cash. https://t.co/M9WD9d4iHk

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@cotta3 @FiendishCrypto Cash Is King.

Or

Core Is Weak.

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

Cash is King

[Sam Altman @sama]

day 3 of @worldnetwork launch, crazy lines around the world. one person getting verified every 8 seconds now.

[PSY ᵀᵃᴹᵃ (SP: 🥊 Fulcrum Punch) @TamaPsy]

@Hermetics_ Anonymity is NOT the shield. It is only a title people use while hiding behind the real sword AND shield of PSEUDONYMITY. The gatekeepers that go toe-to-toe with tyranny cos they are the providers of true utility that humanity needs. #bch

Within pure anonymity is just chaos.

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@srust99 @BlockpartySh @SatoshiSeasons

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

SLP Foundation Announcement:

1.) We are fully supporting BCHD flipstarter as a thanks to their commitment to us in the early days to provide token infrastructure for BCH Ecosystem (~100 BCH)

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

We would like to thank SLP devs, supporters, token teams and users. Simple Ledger Protocol was designed to be simple: a stepping stone for Smart Tokens which we have today. Special mention of gratitude to all the builders in BCH Ecosystem. Please carry on building!

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@ChrisPacia @elonmusk I presume that’s what’s eventually gonna happen here? Are we seriously gonna X instead of tweeting and rx instead of rt?

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@peterktodd The circle jerking does not stop. Especially with these single loop jerks. If you thought luke was just one of them. Think again.

[peetah哥 (SP: 🥷🏿Kilobyte Ken) @1kBKen]

@ShitcoinDotCom Yo. What’s a new character