Hey you probably don’t remember me from back in the hotel shuttle in 2013 in Buenos Aires, LaBitConf, but thanks for being a part of spear-heading OP_Return and p2sh back in 2014 because it made a lot of the prunable layer apps like Omni possible, since I was a part of that I guess I owe you a coke. I think it’s a meaningful precedent for this debate because that too was driven by the conservatives backlashing against layer protocols and their supposed “graphiti” of bringing assets and financial exchange to blockchains as a killer-app. Then as now, the fear of wasteful data usage prompted an engineering improvement based on provably prunable outputs.
Preaching to the centrist choir but since we’re on the same team, let me play devil’s advocate — the very rationale you’re presenting here is also the reason many are cautious about the SegWit2x build. Fast rollout ect.
It would behoove many billions in market cap. to put some resource allocations to the point and have you supervising more developers than it seems there are now — or trying to more broadly source developers via bounties et al. to plug lots of unit testing cases, reg test, and testnet scripts and swarm all over possible break-down scenarios for this client. Take care of that and we’ll probably see BTC considerably higher yet next year, and with perhaps millions of daily transactions.
