Segregated Witness + Lightning Network
Bitcoin Unlimited
Segwit2Mb (Segregated Witness + Hardfork 2Mb)
Hardfork 2Mb / 4Mb / 8Mb
UASF Segwit (user-initiated softphone)
Yes, at least something is already giving birth!
Do not touch anything, Satoshi's code is sacred
I vote for segwit + 2mb. Not because I consider it a panacea, but because now the community is in a situation where it is necessary to choose between greater and lesser evil!
This solution is palliative, but closest to implementation. It will give time to self-organize the community in order to reach a consensus on current issues, or prolong the agony, but in any case, for some time will be accompanied by the attraction of new users, capital, growth rate.
It is very important that this decision allowed to reach agreement on 80% of the network hashrate. I am even pleased with the lack of core when it is achieved, because their position is unconstructive and directed against the interests of the community, the last one about 2mb through uasf is another confirmation of that. If core participated in the agreement, we would undertake its implementation in the client, and then sabotage it. The current agreement was first achieved in the confrontation with the core, it rallied all groups of influence on the hashed network, so it is much closer to practical implementation than the previous one. Core generally attach too much importance, they are servants of the community, imagining themselves to be steering coaches. Their opinion, like the opinion of any other virgins by the nature of bitcoin, is of an advisory nature exclusively on technical issues. This opinion is not a guide to the action that determines the vector of network development. When the core is told to jump, they should ask - on what foot? Here is their real place in the community. What split in connection with the irreconcilable position of the core speech, I hesitate to ask ?! Let their position, what they want to do, the market their shit UASF fork will appreciate.
On scaling, I think it is critically important for bitcoin to maintain a balance between on-line and off-line solutions. They must necessarily be competitive. As for the block size, it should be economically justified, here too, the balance of interests of the miners and users must be observed, this balance can not be kept constant in principle, to maintain this balance there is a mathematical description - Pareto optimality. Therefore, the block must be dynamic.
According to the developers, it is necessary that there be a transparent structure for the selection of proposals from various teams of programmers, on the next gangplank of influence groups on the network hash, some of these proposals (or even all) could receive funding from these groups. Thus, we would get a developer market, where the best solution would be to support a key part of the community. And it would not be once and for all, and the developers would have to fight for it every time in a new way.
About the impact of technical problems on the course, I think, at the current stage, when brokers start giving the opportunity to enter bitcoin via ETN, when the decision on ETF is revised, will not reconsider the US, so there will be more loyal jurisdictions, the pumping will continue despite all. They do not care how much the commission will be.
About the impact of current problems on use cases - I used to translate money to local programmers in Kazakhstan through localbitcoins, bought for rubles, he showed it to QIWI (the payment system working in our countries), was cheaper than 3.9% when replenishing its QIWI purse directly, now more expensive. However, it does not affect the diversification of my crypto-currency portfolio - bitcoin dominates in it.
P.S.
Maybe bitcoin, and with all the current problems and technical backwardness, will for a long time be the leader in hashed and capitalization, at least until the ETNs and ETFs are only bitcoins, and while in the minds of people it is gold 2.0
https://forum.bits.media/index.php?/topic/39181-opros-kak-masshtabirovat-bitcoin/page-2#entry730507