Bitcoin Liberty Live's avatar
Bitcoin Liberty Live
SatoshisMilitia@BitcoinNostr.com
npub1756j...jv6a
Join Us Live: Every Saturday at 10am Pacific. Take Self Custody with MicroSeed! https://MicroSeed.io
Great writeup on the OP_RETURN issue, by @Daniel 21e15 https://medium.com/gravity-boost/bitcoins-op-return-is-the-enemy-at-the-gates-or-over-the-wall-d49a3909803c … with recommendations below on how to wade forward carefully to balance technical merits with community concerns 👇👇 1. Phased Implementation: Increase OP_RETURN size to 200 bytes for one release cycle, retaining the single-output limit, to monitor adoption, spam, and node impacts, as /dev/fd0 suggested. 2. Relay Safeguards: Define “reliably mined” thresholds (e.g., 5% hashrate) and allow miner rejection of harmful transactions to prevent hostage scenarios (Towns, Maxwell). 3. Configurability Retention: Retain datacarrier and datacarriersize or introduce new knobs (e.g., max OP_RETURN size) to preserve node autonomy (Burnett, /dev/fd0). 4. Communication Strategy: Conduct pre-merge outreach (e.g., AMAs, podcasts, social media) to explain motivations, disclose conflicts, and rebuild trust, as PandaCute and jonatack proposed. 5. Data-Driven Research: Publish analysis of UTXO-bloating transactions and projected OP_RETURN usage, addressing PandaCute’s and nsvrn’s demands. 6. Incentive Adjustment: Adjust fees to make OP_RETURN competitive with inscriptions (e.g., higher witness data fees) and promote off-chain solutions (e.g., Lightning) to reduce bloat. 7. Spam Protections: Monitor fee spikes via a task force, implementing dynamic fee thresholds and priority lanes for financial transactions (Guida). 8. Centralization Mitigations: Fund pruning campaigns, introduce size-based fee penalties, and offer fee subsidies for small-scale users (Hughes, Burnett). 9. Community Consensus: Draft a BIP, hosting public forums to address ideological concerns and offer optional strict policies (e.g., -datacarriersize) for purists, ensuring inclusive governance (PandaCute, Burnett)
Mid-2008… I get an email from some Asian guy @ gmx.com with a story about citing me in a paper he’s writing, wants it to be more ‘academic sounding’ but needs to confirm some of my personal info (LOL classic phishing) says he wants to spell it right… while doxxing me 😂 so I reply, nah actually I’m good, that was a while ago & I’ve moved on, kinda busy staying poor right now, cool story bro & use what you like of the time chain stuff but just keep me out of it, no worries. Anyway like 9 months later he sends me a link to his corn bits project along with a 64 character hex string to use. Says he just points all his ‘miners’ to that ‘address’ now 🤷🏻‍♂️ My point is that it could be something important I’d not want to ever lose, so I used MicroSeed to stamp those characters into steel, protecting it forever and giving me peace of mind. It’s the BEST way to store and easily transport your most important codes, phrases, etc. View quoted note →