Here is something that I just realised from reading on the comments. People say how it is difficult to understand about locking down the protocol because is not a good definition et cetera.
What complete bullshit.
You are not protocol developers. The protocols not being developed. This is not a community project. You have no fucking say in changes to the protocol because there won’t be changes to the protocol. If you don’t like that, go away. Honestly, you think you have an opinion that matters on the protocol. As hard as this may seem to you, you fucking don’t. There is a set protocol and when I was mortgaging my bloody properties nobody helped me choose.
So very simply and finish this because I have work to do… You have no right to fucking even comment on the protocol, to expound on it. It’s there, you can use it. If it changes, you have a right to sue. If you develop something to date and is for now you can’t run it because some minor change to the protocol happened then you can sue the fuck out of the DA and every developer who’s ever had anything to do with that change personally and corporate waste and everything else.
That’s all you get to do. You have a promise and a contract that says this is a fixed fucking protocol. That means anything you can build today will run tomorrow, a decade from now, I century from now if the dam protocol still running.
That is the only thing you have a right to.
You don’t even have a right to documenting. You wanted and I would like you to have documented protocols because I want you to use my fucking protocol. But you don’t have a right to it.
If you build something on BTC and that changes that constantly happen break it you have a right to sue them like I’m doing. They are not I distributed nothing group they are a bunch of fucking assholes who are pretending and defrauding people in believing that they have no control when they are fucking autocrats.
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644775707601989?thread_ts=1644775707.601989&cid=C5131HKFX
https://t.me/CSW_Slack/3991
What complete bullshit.
You are not protocol developers. The protocols not being developed. This is not a community project. You have no fucking say in changes to the protocol because there won’t be changes to the protocol. If you don’t like that, go away. Honestly, you think you have an opinion that matters on the protocol. As hard as this may seem to you, you fucking don’t. There is a set protocol and when I was mortgaging my bloody properties nobody helped me choose.
So very simply and finish this because I have work to do… You have no right to fucking even comment on the protocol, to expound on it. It’s there, you can use it. If it changes, you have a right to sue. If you develop something to date and is for now you can’t run it because some minor change to the protocol happened then you can sue the fuck out of the DA and every developer who’s ever had anything to do with that change personally and corporate waste and everything else.
That’s all you get to do. You have a promise and a contract that says this is a fixed fucking protocol. That means anything you can build today will run tomorrow, a decade from now, I century from now if the dam protocol still running.
That is the only thing you have a right to.
You don’t even have a right to documenting. You wanted and I would like you to have documented protocols because I want you to use my fucking protocol. But you don’t have a right to it.
If you build something on BTC and that changes that constantly happen break it you have a right to sue them like I’m doing. They are not I distributed nothing group they are a bunch of fucking assholes who are pretending and defrauding people in believing that they have no control when they are fucking autocrats.
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644775707601989?thread_ts=1644775707.601989&cid=C5131HKFX
https://t.me/CSW_Slack/3991
Telegram
CSW - Slack Channel
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644775707601989?thread_ts=1644775707.601989&cid=C5131HKFX
https://t.me/CSW_Slack/3991
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644775707601989?thread_ts=1644775707.601989&cid=C5131HKFX
https://t.me/CSW_Slack/3991
1/2
Unilateral contracting
When it comes to any bitcoin related all Blockchain -related protocol, there is no such thing as community driven development. This entire term is something created by Ethereum and BTC to remove the liability that comes with developing software and to act in a way that doesn’t take responsibility for the changes they create. In regards to bitcoin, there is a promise that the protocol will not change. It is not that it can’t be changed, it is a contractual agreement for it not to be changed.
The reason for this has to do with the cost to all users of the system and it is a choice that I made. BTC follow this line of reasoning without enacting the underlying necessity not to change and this is a form of misleading and deceptive conduct and a breach of contract. This is what people don’t seem to understand. It is not a community project it is a project made by a small group of developers. Developers have liability. If those developers change the protocol, they are liable for the damage they make in changing the protocol.
It is not that it is difficult to change the protocol. It is really simple to change any Blockchain based protocol. The BTC cord have stood on a weekly basis. The problem is that every other user of the system needs to also change. The only way to not control the system and to have power over the users is to not change. If the system is built with a promise that it will change over time and grow and issue new versions, then that is part of the contract and any changes are to be expected and the users of the system have no rights to sue the developers.
Conversely, if a Blockchain-based system is set in stone, like bitcoin is, like BTC proposes to be, then it is very simple, any change comes with liability. This is the very heart of what they don’t want to admit, this is not a technical control, it is basic every day contract law. If you are a developer and you make a change that negatively impact a single user on the system, and there is a promise that the system won’t change, you have liability to that user. You are in breach of contract.
I don’t feel like taking on any liability for these changes. You’re not paying me to make changes. The changes to the protocol could run into tens of millions of dollars from a single source and could be in the order of billions of dollars over the system. Not something I want to be responsible for. So, this is very simple, if the protocol set in stone is no liability issue. It has nothing to do with community. It has nothing to do with all this other bullshit you to keep hearing about, it is purely contract law.
So when you ask me about when OP_Return will be changed and you come to me without offering something to offset that change and the risk and the damages that will follow, fuck off you lazy greedy parasitical asshole.
If you think I’m being too hard, fuck off parasitical asshole.
You are making an assumption that I should take on risk so that something you want to do and you want to make money on can happen and I can bear the liability and the cost. Fuck off you parasitical asshole.
I hope that makes it clear. The only reason not to change protocol is that it is contractually bound not to change. That makes it nice and simple for lots of people to build. If you can’t, come up with a way of buying off everyone in the global ecosystem, I estimate an investment of $5 billion US should do a very simple change and pay off everybody who needs that solved or around 100 billion for a complex one. If you’re not going to come up with that money, if you’re not willing to even have it planned, get the fuck out of my life.
In case you don’t get it, you are asking me to take on liability on a global basis for your change that you might want so that you can experiment at my expense.
That is the definition of a scumbag parasite.
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644777134224419?thread_ts=1644777134.224419&cid=C5131HKFX
1/2
https://t.me/CSW_Slack/3995
Unilateral contracting
When it comes to any bitcoin related all Blockchain -related protocol, there is no such thing as community driven development. This entire term is something created by Ethereum and BTC to remove the liability that comes with developing software and to act in a way that doesn’t take responsibility for the changes they create. In regards to bitcoin, there is a promise that the protocol will not change. It is not that it can’t be changed, it is a contractual agreement for it not to be changed.
The reason for this has to do with the cost to all users of the system and it is a choice that I made. BTC follow this line of reasoning without enacting the underlying necessity not to change and this is a form of misleading and deceptive conduct and a breach of contract. This is what people don’t seem to understand. It is not a community project it is a project made by a small group of developers. Developers have liability. If those developers change the protocol, they are liable for the damage they make in changing the protocol.
It is not that it is difficult to change the protocol. It is really simple to change any Blockchain based protocol. The BTC cord have stood on a weekly basis. The problem is that every other user of the system needs to also change. The only way to not control the system and to have power over the users is to not change. If the system is built with a promise that it will change over time and grow and issue new versions, then that is part of the contract and any changes are to be expected and the users of the system have no rights to sue the developers.
Conversely, if a Blockchain-based system is set in stone, like bitcoin is, like BTC proposes to be, then it is very simple, any change comes with liability. This is the very heart of what they don’t want to admit, this is not a technical control, it is basic every day contract law. If you are a developer and you make a change that negatively impact a single user on the system, and there is a promise that the system won’t change, you have liability to that user. You are in breach of contract.
I don’t feel like taking on any liability for these changes. You’re not paying me to make changes. The changes to the protocol could run into tens of millions of dollars from a single source and could be in the order of billions of dollars over the system. Not something I want to be responsible for. So, this is very simple, if the protocol set in stone is no liability issue. It has nothing to do with community. It has nothing to do with all this other bullshit you to keep hearing about, it is purely contract law.
So when you ask me about when OP_Return will be changed and you come to me without offering something to offset that change and the risk and the damages that will follow, fuck off you lazy greedy parasitical asshole.
If you think I’m being too hard, fuck off parasitical asshole.
You are making an assumption that I should take on risk so that something you want to do and you want to make money on can happen and I can bear the liability and the cost. Fuck off you parasitical asshole.
I hope that makes it clear. The only reason not to change protocol is that it is contractually bound not to change. That makes it nice and simple for lots of people to build. If you can’t, come up with a way of buying off everyone in the global ecosystem, I estimate an investment of $5 billion US should do a very simple change and pay off everybody who needs that solved or around 100 billion for a complex one. If you’re not going to come up with that money, if you’re not willing to even have it planned, get the fuck out of my life.
In case you don’t get it, you are asking me to take on liability on a global basis for your change that you might want so that you can experiment at my expense.
That is the definition of a scumbag parasite.
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644777134224419?thread_ts=1644777134.224419&cid=C5131HKFX
1/2
https://t.me/CSW_Slack/3995
Telegram
CSW - Slack Channel
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644777134224419?thread_ts=1644777134.224419&cid=C5131HKFX
https://t.me/CSW_Slack/3995
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644777134224419?thread_ts=1644777134.224419&cid=C5131HKFX
https://t.me/CSW_Slack/3995
2/2
Even the 21 million coins is purely a contractual agreement. There is nothing in software, nothing in code that held this. The only thing is that it isn’t changed because of contractual liability. That’s it. Nothing technical. Not even slightly technical. Not cryptographic. It is purely an economic and legal argument based on contract.
So am I. There is nothing for them to change and not one of them is offering me money or negotiating with me for the change. By definition, that puts them in the bucket of parasites.
From now on, I am not mincing words ever again. I’m being completely honest and open in all of this. If you want to be a parasite, go to bloody Ethereum I don’t want you.
if you are too dumb to understand that this is not technical that it is contractual then honestly go back to school and try and educate yourself a little and get away from me
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644777134224419?thread_ts=1644777134.224419&cid=C5131HKFX
2/2
https://t.me/CSW_Slack/3995
Even the 21 million coins is purely a contractual agreement. There is nothing in software, nothing in code that held this. The only thing is that it isn’t changed because of contractual liability. That’s it. Nothing technical. Not even slightly technical. Not cryptographic. It is purely an economic and legal argument based on contract.
So am I. There is nothing for them to change and not one of them is offering me money or negotiating with me for the change. By definition, that puts them in the bucket of parasites.
From now on, I am not mincing words ever again. I’m being completely honest and open in all of this. If you want to be a parasite, go to bloody Ethereum I don’t want you.
if you are too dumb to understand that this is not technical that it is contractual then honestly go back to school and try and educate yourself a little and get away from me
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644777134224419?thread_ts=1644777134.224419&cid=C5131HKFX
2/2
https://t.me/CSW_Slack/3995
Telegram
CSW - Slack Channel
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644777134224419?thread_ts=1644777134.224419&cid=C5131HKFX
https://t.me/CSW_Slack/3995
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644777134224419?thread_ts=1644777134.224419&cid=C5131HKFX
https://t.me/CSW_Slack/3995
If you ask for a change to a protocol, let us say TCP, you force everything in the system to change.
Let us say that we change the session size by 1 bit in the TCP header, it is now 128k from 65k.
Small as possible a change.
Now, everyone on the entire Internet needs to update their system, any and all old code stops working.
Now, everyone on the entire Internet needs to update their system, any and all old code stops working.
There are Lynx browsers that are over 30 years old and telnet based control systems that stop functioning.
Every router on earth needs to be replaced.
Every firewall needs to be recoded, and many old applications will not ever again function..
All because someone thought, a small change... just a small change
and smartcards
and embedded applications
because, in your hubris, you have course know better
Imagine changing everything on the Web...
And, there is no reason to fix these. The code still works
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644842616111969?thread_ts=1644842616.111969&cid=C5131HKFX
https://t.me/CSW_Slack/4000
Let us say that we change the session size by 1 bit in the TCP header, it is now 128k from 65k.
Small as possible a change.
Now, everyone on the entire Internet needs to update their system, any and all old code stops working.
Now, everyone on the entire Internet needs to update their system, any and all old code stops working.
There are Lynx browsers that are over 30 years old and telnet based control systems that stop functioning.
Every router on earth needs to be replaced.
Every firewall needs to be recoded, and many old applications will not ever again function..
All because someone thought, a small change... just a small change
and smartcards
and embedded applications
because, in your hubris, you have course know better
Imagine changing everything on the Web...
And, there is no reason to fix these. The code still works
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644842616111969?thread_ts=1644842616.111969&cid=C5131HKFX
https://t.me/CSW_Slack/4000
Telegram
CSW - Slack Channel
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644842616111969?thread_ts=1644842616.111969&cid=C5131HKFX
https://t.me/CSW_Slack/4000
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644842616111969?thread_ts=1644842616.111969&cid=C5131HKFX
https://t.me/CSW_Slack/4000
As soon as you allow ANY changes, you remove ALL infrastructure use from a system
SCADA systems date back to the 80s, why, as the plant, the infrastructure can take 60 years to be deprecated.
A change, a small change can collapse nuclear power plants, and this is not melodramatic, it is real world infrastructure
Bitcoin is not designed by a silicon Valley loser... it is designed using waterfall and a person who grew up on critical systems
It is not a Break things, move fast system
It is, fixed, unchanged and static
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644842854291859?thread_ts=1644842854.291859&cid=C5131HKFX
https://t.me/CSW_Slack/4002
SCADA systems date back to the 80s, why, as the plant, the infrastructure can take 60 years to be deprecated.
A change, a small change can collapse nuclear power plants, and this is not melodramatic, it is real world infrastructure
Bitcoin is not designed by a silicon Valley loser... it is designed using waterfall and a person who grew up on critical systems
It is not a Break things, move fast system
It is, fixed, unchanged and static
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644842854291859?thread_ts=1644842854.291859&cid=C5131HKFX
https://t.me/CSW_Slack/4002
Telegram
CSW - Slack Channel
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644842854291859?thread_ts=1644842854.291859&cid=C5131HKFX
https://t.me/CSW_Slack/4002
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644842854291859?thread_ts=1644842854.291859&cid=C5131HKFX
https://t.me/CSW_Slack/4002
👍1
But hey... ask for changes. Tell me, you know better, that your little idea is going to be worth having companies that ARE building now, and that will not be ready for at least 2 to 3 years that my promise to keep a static system was crap.
Say that, a toy Silicone Valley style app will save bitcoin... and not something that may end as global plumbing... you must understand the world, everything in it, all that is being done... you ask for changes, it means, you must understand that your application beats everything else possible...
If you think I am being condescending....
You really should not be here
Even again
There are sewers in London that date to the Roman occupation
CSW
Feb 14,. 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644843209582209?thread_ts=1644843209.582209&cid=C5131HKFX
https://t.me/CSW_Slack/4004
Say that, a toy Silicone Valley style app will save bitcoin... and not something that may end as global plumbing... you must understand the world, everything in it, all that is being done... you ask for changes, it means, you must understand that your application beats everything else possible...
If you think I am being condescending....
You really should not be here
Even again
There are sewers in London that date to the Roman occupation
CSW
Feb 14,. 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644843209582209?thread_ts=1644843209.582209&cid=C5131HKFX
https://t.me/CSW_Slack/4004
Telegram
CSW - Slack Channel
CSW
Feb 14,. 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644843209582209?thread_ts=1644843209.582209&cid=C5131HKFX
https://t.me/CSW_Slack/4004
Feb 14,. 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644843209582209?thread_ts=1644843209.582209&cid=C5131HKFX
https://t.me/CSW_Slack/4004
(Set in stone)
When I was with the ASX (Stock Exchange) we had HP systems from the 80s and VAX systems from the 70s operating in the 2000s.
They worked, and, these allowed a 99.999999 uptime.
Many devs look at this and scoff. However, the desired goal was a reliable system. This was achieved.
The silicone Valley version of code is more problematic. Google has gone down multiple times despite 100x the level of server redundancy as the ASX. Facebook, the same.
But, global money and an underlying control system needs to be designed with not 6 9s but 9 x9 reliability. Any downtime must be seen as a true black Swan once in a 500 year event.
That is the Core of bitcoin, and no Silicone Valley designer will ever understand that.
It is engineered for stability. In this, change is not an option.
Terra node is a means to scale, but it does not change any part of the protocol.
The node consensus protocol will remain, and nodes voted just beef up hardware to try to keep up. It is faster, not different.
The last sentence of the WP references law, through rules. This is not a change, the nodes could assign a tx differently on Jan 3, 2009. This does not impact an transactions ever created.
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644849975402729?thread_ts=1644849975.402729&cid=C5131HKFX
https://t.me/CSW_Slack/4006
When I was with the ASX (Stock Exchange) we had HP systems from the 80s and VAX systems from the 70s operating in the 2000s.
They worked, and, these allowed a 99.999999 uptime.
Many devs look at this and scoff. However, the desired goal was a reliable system. This was achieved.
The silicone Valley version of code is more problematic. Google has gone down multiple times despite 100x the level of server redundancy as the ASX. Facebook, the same.
But, global money and an underlying control system needs to be designed with not 6 9s but 9 x9 reliability. Any downtime must be seen as a true black Swan once in a 500 year event.
That is the Core of bitcoin, and no Silicone Valley designer will ever understand that.
It is engineered for stability. In this, change is not an option.
Terra node is a means to scale, but it does not change any part of the protocol.
The node consensus protocol will remain, and nodes voted just beef up hardware to try to keep up. It is faster, not different.
The last sentence of the WP references law, through rules. This is not a change, the nodes could assign a tx differently on Jan 3, 2009. This does not impact an transactions ever created.
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644849975402729?thread_ts=1644849975.402729&cid=C5131HKFX
https://t.me/CSW_Slack/4006
Telegram
CSW - Slack Channel
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644849975402729?thread_ts=1644849975.402729&cid=C5131HKFX
https://t.me/CSW_Slack/4006
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644849975402729?thread_ts=1644849975.402729&cid=C5131HKFX
https://t.me/CSW_Slack/4006
Has bitcoin been locked how I wanted, no. And?
The issue is that it is fixed, not that it is perfect.
Today, there is NOTHING that cannot be done on a tx that will change, ever. If you code an application today, it will work in 2150.
Do I know what is possible, no.
Should I... fuck no.
I did not predict HTTP as it developed, why should I know what people will create in 20 years on TODAY'S transaction base?
So, it must be documented, honestly, what crap. That is a nice to do... but this is reality. You don't need a deep understanding of TCP to build web apps.
There are things to do. But not one of these eill change a single tx or application in existence now or in the past.
If it works today.
It will work in 100 years
Only miners NEED to verify difficulty
The total difficulty is separate from the way nodes adjust
The AS system sux, but again. It is not a rush
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644850729617549?thread_ts=1644850729.617549&cid=C5131HKFX
https://t.me/CSW_Slack/4008
The issue is that it is fixed, not that it is perfect.
Today, there is NOTHING that cannot be done on a tx that will change, ever. If you code an application today, it will work in 2150.
Do I know what is possible, no.
Should I... fuck no.
I did not predict HTTP as it developed, why should I know what people will create in 20 years on TODAY'S transaction base?
So, it must be documented, honestly, what crap. That is a nice to do... but this is reality. You don't need a deep understanding of TCP to build web apps.
There are things to do. But not one of these eill change a single tx or application in existence now or in the past.
If it works today.
It will work in 100 years
Only miners NEED to verify difficulty
The total difficulty is separate from the way nodes adjust
The AS system sux, but again. It is not a rush
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644850729617549?thread_ts=1644850729.617549&cid=C5131HKFX
https://t.me/CSW_Slack/4008
Telegram
CSW - Slack Channel
CSW
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644850729617549?thread_ts=1644850729.617549&cid=C5131HKFX
https://t.me/CSW_Slack/4008
Feb 14, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644850729617549?thread_ts=1644850729.617549&cid=C5131HKFX
https://t.me/CSW_Slack/4008
Rational Argument around Nodes.
By Craig Wright
16 Feb 2022
https://craigwright.net/blog/bitcoin-blockchain-tech/a-rational-argument-around-nodes/
By Craig Wright
16 Feb 2022
https://craigwright.net/blog/bitcoin-blockchain-tech/a-rational-argument-around-nodes/
craigwright.net
A Rational Argument around Nodes