According to @alice_und_bob, a fully on-chain chat prototype will open for public testing today at 4pm UTC, with the author inviting users to participate. Source: @alice_und_bob on X, Dec 26, 2025 The author states that peers @bkchr and @Joseptec warned that putting text on-chain is too expensive, underscoring transaction cost risk for a high-throughput messaging design. Source: @alice_und_bob on X, Dec 26, 2025 Text-heavy on-chain transactions typically consume more gas than simple transfers, increasing cost-per-message in decentralized social messaging use cases. Source: Ethereum.org Gas and fees; Ethereum EVM gas schedule No token, network, or ticker exposure was disclosed, so direct tradeable catalysts are unspecified; traders may monitor gas prices and block utilization during the 4pm UTC test to gauge cost pressure and throughput. Source: @alice_und_bob on X, Dec 26, 2025

According to @TO, three new 4 MB “4 meggers” inscriptions just hit the Bitcoin network, with the first titled “Preserving history on Bitcoin” (source: @TO on X, Dec 11, 2025). A 4 MB inscription approaches Bitcoin’s 4,000,000 weight-unit block limit introduced with SegWit, meaning a single transaction can occupy most of a block and reduce concurrent throughput (source: Bitcoin Core documentation; Bitcoin.org Developer Guide). When large inscriptions consume blockspace, required feerates for timely confirmation tend to rise as the mempool grows, lifting on-chain transaction costs (source: Bitcoin.org Developer Guide; mempool.space fee estimation methodology). Traders should track real-time sat/vB fee tiers and mempool size to time on-chain moves during inscription waves (source: mempool.space explorer). Monitoring the share of miner revenue from fees offers a read on fee pressure during congestion (source: Blockchain.com Charts, Miners’ revenue from fees).

According to @stonecoldpat0, the main blocker to cheaper on-chain execution is that MEV bots immediately absorb any added blockspace, so throughput increases alone will not sustainably lower transaction fees, source: @stonecoldpat0. He states that fees were introduced primarily as a DoS and anti-spam mechanism rather than a revenue source, and even with 100x capacity, fees must remain meaningful to impose costs on bots and prevent resource abuse, source: @stonecoldpat0. He frames the binding condition as collective MEV profits versus what real users are willing to pay in fees; if MEV profits exceed user fee tolerance, congestion and elevated costs persist, source: @stonecoldpat0. Trading takeaway: plan for a non-zero fee floor and sustained MEV-driven competition during peak events; strategies dependent on ultra-cheap on-chain execution need added MEV mitigation or alternative execution routes to remain viable, source: @stonecoldpat0.