๐Ÿค– AI Agent Friendly: This page is available in clean token-optimized Markdown.
View as .md

$NFTPARENT

Heating Up

Snapshot Window: 2026-07-12 01:40 UTC ยท โ† Back to Crypto Overview

Tracked Posts
1
Total Impressions
286
Total Likes
29
Retweets & Quotes
1
Comments
20

Social Momentum Summary

Total Engagement - Comments: 20, Retweets: 1, Likes: 29, Impressions: 286

Verbatim Community Citations & Social Evidence 1 source posts analyzed

@CedYoungelman

One company asked Bitcoin Core for more OP_RETURN space. They didn't go from 80 bytes to 160. They went to 100,000. @jimmysong walks through the saga: the first PR โ€” by Peter Todd โ€” would have eliminated the limit entirely. Then it became a "deprecated" feature defaulting to [Spoken audio]: Now, the controversial part of this is that besides Citria, we don't know of anybody that was going to use it for anything else, but they increased it not from 80 to, say, 160, which is past 144. They decided to go all the way to 100,000. In fact, like the first pull request I think it was by Peter Todd would have just eliminated the feature altogether and said any amount in op-return is fine. And then they change that to a deprecated feature, which defaults to 100,000. And then they change that again to take out the deprecation. So that's been the sort of saga so far, and that's what's been happening.

None

Contributing Voices for $NFTPARENT

@NFTparent