actually I wasnt assuming you had an agenda, or at least I couldnt figure out what it might be.
My agenda is simple: bitcoin is awesome, and I want to defend and improve it.
I presume by philosophy you mean stasis vs change? I read your view to be stasis. Nothing about bitcoin must change ever (other than bug fixes). Maybe thats over simplifying. Or maybe your arguments are shifting or dancing around to prod people into extending the argument (sorry thats the impression you give at times).
The sequence I saw was people trying to pressure bitcoin core to make changes to support their various ideas and pet projects. And bitcoin core not being able to accommodate them due to resources, and significantly risk.
My pet project that caused me to notice the risk of change clearly, was homomorphic encrypted values, which I thought were pretty cool as they completely hide transaction values and are still validatable. https://bitcointalksearch.org/topic/bitcoins-with-homomorphic-value-validatable-but-encrypted-305791 (They do nothing about hiding which address is paying which, thats harder and takes zerocash which has to much novel crypto to deploy on main IMO).
And actually the earlier one was committed transactions which try to prevent transaction censorship even in the face of miners with dangerously high hashrate. https://bitcointalk.org/index.php?topic=206303.15 (there's a so far unresolved problem with that, but if it could be made to work, thats pretty cool in my book also).
So I suppose one example for your philosophy question is would you be against the above two changes being in bitcoin? One improves privacy and the other improves decentralisation properties. I presume most people on bitcointalk like those properties. How about cypherdoc?
Next realise there's basically zero chance of those going in, and I approve of that. Its too risky, and what we need even more than cool features to improve bitcoin, is to not lose everyones bitcoins (including cypherdocs hoard, which I am very happy he has, good for him). i dont but thats my fault for not installing the alpha client when Satoshi emailed me about it in Jan 2009. I bought a few but I guess my buy in price average is close to current. I still think bitcoin is the coolest thing and has awesome potential.
And another example is how do we do bitcoin protocol upgrades. There are limitations to live upgrades, some things are not soft-forkable also. We'd have lower risk if we could have a live beta. That was the first proposed use for one-way pegs (precursor to GMaxwell et al two-way peg). Presumably you'd think a one-way peg for the purposes of software upgrade could be good - lower risk of failure during bug fixes and software modularisation.
An example is its hard to fully fix malleability which causes problems in some scenarios.
Maybe also zerocash itself. Kind of risky bleeding edge crypto, but really good privacy. I would be against that going into main due to the novel crypto risk unless it was somehow constrained to those opting in to it.
But that kind of sucks, people who want it cant use it. You and I and everyone is censoring their desired feature. Thats not permissionless innovation. But we are justified because of the risks in fact. A securely firewallable extension mechanism enables permissionless innovation. Otherwise you just see more feature coins.
I am not sure if you are aware sidechains are nearly possible with zero changes to bitcoin. Its already programable via the script language. It may even be doable with zero changes with some chained contorted big script to validate compact SPV proofs.
Anyway its not like blockstream even existed when a bunch of core devs got excited about the possibility of improving on the above situations with a generic extension mechanism so I encourage you to separate out arguments about risk or imagined intent of blockstream from concerns about the change. eg pretend the change is just that group of developers, same people who've been coding bitcoin for years. (Blockstream basically is that group of developers, but thats a separate discussion!)
Note also the 51% takes all coins risk depends on the peg script. Its possible to limit that problem and place the risk on the people doing the arbitrage or transfers by forcing the person returning coins to put up a bounty in main-chain bitcoins equal to the exchange which they forfeit if their transfer is proven fraudulent by a chosen % of the sidechain. There can also be caps and time-adaptive delays (longer for more bitcoin). Its a programming language, the op_spv is just an opcode to simplify the coding of one part of it, validating the compact-proofs.
Hopefully we got past the misinterpretation of Konrad Graf's article, to see that the discount is for time-preference only, and the security firewall will work fine against a malicious or dud sidechain; caveat emptor, and look at the credibility of people writing wallets, chains and cryptocurrency.
If you dont put your coins into a chain they are not at risk. Why would you want to censor someones ability to have zerocash, homomorphic value, faster transactions, more TPS, native share/color support, snark contracts? Wouldnt those be good things for bitcoin? I personally thought it'd be pretty cool to see a new wave of bitcoin centric innovation.
Also I dont think even statis vs change captures the situation. If you like stasis, keep your coins on bitcoin main; if others like cool features they can use them on chains that support them. Why is this a conflict?
Adam