I propose a new BIP, to limit spam. - reduce max block size | Truthcoin on Binance Square

Trending Articles

Bookmarked and Liked

--

I propose a new BIP, to limit spam.
- reduce max block size from 4 MB to 400 KB
- retain all conversions between bytes, vbytes, weight etc
Since I already have BIPs 300 and 301 I humbly request this as "BIP 302"

Disclaimer: Includes third-party opinions. No financial advice. May include sponsored content. See T&Cs.

55

0

Explore the latest crypto news

⚡️ Be a part of the latests discussions in crypto

💬 Interact with your favorite creators

👍 Enjoy content that interests you

Email / Phone number

Relevant Creator

@Truthcoin

Explore More From Creator

Its actually the P2P network that is filtered out, by MARA slipstream (and direct submission and private mempools). Today, MARA will "pre-announce" the next block, for free. This is useful. But they could (theoretically) charge $ for that service. And then Luke would be saying that Mara should pay him [ and each of his nodes] -- but he would be wrong. It is the full nodes which need the mempool of the mining nodes (to save on bandwidth)

--

Yet another reason why Luke is wrong: Luke claims that for any node to *wait* to upgrade to the latest version, is a "failure of Bitcoin". And -- to *wait* to upgrade to the latest soft fork, is a colossal failure, and "regression to SPV". However: 1) every node is a full node of itself, but it is also equal to "SPV mode" of an infinity of closely-related protocols. These may not be used by anyone, but they still exist theoretically. For example, Bitcoin Core v 25 is a full node of itself, but an SPV node of a hypothetical soft fork (of 25) where we always reject a block if the last 4 bytes are 1234 + the versionbits end in 5678 2) Every full node, is **using SPV** on the question: will this block be orphaned ? There is NO way to KNOW the answer to that question using just your node. The ONLY source of illumination, on this question, is to do what spv nodes do: wait for more block headers to roll in, count them, and hope for the best. So: the "heaviest chain" rule -- is a rule that is only enforced at SPV level. Even the full nodes only enforce it at SPV security. And so -- Luke's nightmare scenario, --which he aims to prevent via his theory that we must all run the latest version, etc-- that bad outcome is actually the one we are all permanently stuck in, forever. It is inexorably linked to proof-of-work itself.

--

Every day we waste on op return is further proof that BTC is doomed

--

At this rate, every cab driver will have his own Bitcoin Holding Company

--

Bitcoin Core might be dead. It isn't about OP RETURN per se -- it is about *the reaction* to OP RETURN. The mob justice. It seems to me, that you can't get anything useful done under these conditions. OP RETURN is a very small fry -- very very small. So -- what does it mean, for Core to be dead? In the short run, I don't know. In the long run, miners will run the software that **maximizes their revenue**. The devs of **that software** will obviously allow all OP RETURN sizes, sorting them by fee. People who care about DoS protection (or something else), might run different nodes (or no node at all). If they try to reject a *valid*, block that is accepted by 51% hashrate -- then they are hardforking off the network, like BCH. Empty threat.

--

Latest News

Musk Addresses X Platform Outage and Operational Challenges

--

Cryptocurrency Market Experiences $266 Million Liquidation in 24 Hours

--

X Platform Faces Major Network Disruption Due to Data Center Fire

--

Phishing Attack Results in Significant Financial Loss

--

U.S. President Trump Announces Progress in International Agreements

--

Trending Articles

/_$DOGE SPOT token is being distributedd_/ [CLICK HERE TO G

Treat Crypto Trading Like a Real Job — Clock In, Trade Smart

Blockchain Titan

Don't miss $PEPE ,👇👇👇 [https://www.binance.com/support/an

BREAKING 🚨 Ripple CEO Brad Garlinghouse just reignited the

In the second half of the year, there may be interest rate c

Cookie Preferences

Cookie Preferences