Protocol issues in Bitcoin are simple, you don't have a say. It is fixed. Features used in a tx are not to change.
Law is and always was a part of the node Protocol.
This is not an issue I will debate. If you want to ANY access to me, if you want me here, it is simple. No Protocol changes. No discussion.
If you want to discuss, fuck off. Very easy.if people discuss this, I leave, for good. At all.
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644716467690259
https://t.me/CSW_Slack/3975
Law is and always was a part of the node Protocol.
This is not an issue I will debate. If you want to ANY access to me, if you want me here, it is simple. No Protocol changes. No discussion.
If you want to discuss, fuck off. Very easy.if people discuss this, I leave, for good. At all.
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644716467690259
https://t.me/CSW_Slack/3975
Telegram
CSW - Slack Channel
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644716467690259
https://t.me/CSW_Slack/3975
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644716467690259
https://t.me/CSW_Slack/3975
If an OP_Code is currently disabled, right now, stop giving a shit. If, and this is a Huge If, Op_Ver is re-enabled in the next year, 5 years, decade... so be it.
Op_Return is used, it is set, it is fixed, it is in stone, and if you even think of wanting to suggest changes, go to hell.
If you want it enabled, that is you. I don't care, I don't give a shit.
If you are basing your life on Op_Ver in ANY way you are fucking daft, it matters IF there is a major change such as because of SHA256 being compromised. It has not been, it is not likely to be
If you cannot build a solution, study, hire someone better.
Nothing you suggest that will make your life even a little easier is going to EVER happen if it is linked to protocol changes.
Nothing, and I mean NOTHING you may want to build is in anyway, remotely, distantly linked yo enabling Op_Ver. If you think this, you are deluded.
If you cannot do encryption in script (fucking why) that is your failure, I can. Now
Dust is an issue
Mention zero token exchanges, notice not an exchange at all....
You are hone, not a week... life
If you cannot figure out that exchanging 1 sat for 1 sat is not difficult, go away.
If you are too dumb to work it out, not my fault, I do not care, I do not want to know
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644719471240389?thread_ts=1644719471.240389&cid=C5131HKFX
https://t.me/CSW_Slack/3979
Op_Return is used, it is set, it is fixed, it is in stone, and if you even think of wanting to suggest changes, go to hell.
If you want it enabled, that is you. I don't care, I don't give a shit.
If you are basing your life on Op_Ver in ANY way you are fucking daft, it matters IF there is a major change such as because of SHA256 being compromised. It has not been, it is not likely to be
If you cannot build a solution, study, hire someone better.
Nothing you suggest that will make your life even a little easier is going to EVER happen if it is linked to protocol changes.
Nothing, and I mean NOTHING you may want to build is in anyway, remotely, distantly linked yo enabling Op_Ver. If you think this, you are deluded.
If you cannot do encryption in script (fucking why) that is your failure, I can. Now
Dust is an issue
Mention zero token exchanges, notice not an exchange at all....
You are hone, not a week... life
If you cannot figure out that exchanging 1 sat for 1 sat is not difficult, go away.
If you are too dumb to work it out, not my fault, I do not care, I do not want to know
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644719471240389?thread_ts=1644719471.240389&cid=C5131HKFX
https://t.me/CSW_Slack/3979
Telegram
CSW - Slack Channel
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644719471240389?thread_ts=1644719471.240389&cid=C5131HKFX
https://t.me/CSW_Slack/3979
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644719471240389?thread_ts=1644719471.240389&cid=C5131HKFX
https://t.me/CSW_Slack/3979
When any change is made to the protocol, to node software, etc...
Every system needs to change.
A small change ripples.
Personally, the easiest, BEST change is to add the Op_True condition that was removed as a bug and add conditions into the node software that note a consensus of why etc, things OUTSIDE the Blockchain as it should be.
Then, it would be easy, but no. Development teams complicate as they want to account for everything, and still have NO FUCKING CLUE.
Code is nor law, and stop thinking that code solves law, economics or even human issues and political governance
It doesn't
It is a tool
Not a bloody god
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644720193546839?thread_ts=1644720193.546839&cid=C5131HKFX
https://t.me/CSW_Slack/3981
Every system needs to change.
A small change ripples.
Personally, the easiest, BEST change is to add the Op_True condition that was removed as a bug and add conditions into the node software that note a consensus of why etc, things OUTSIDE the Blockchain as it should be.
Then, it would be easy, but no. Development teams complicate as they want to account for everything, and still have NO FUCKING CLUE.
Code is nor law, and stop thinking that code solves law, economics or even human issues and political governance
It doesn't
It is a tool
Not a bloody god
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644720193546839?thread_ts=1644720193.546839&cid=C5131HKFX
https://t.me/CSW_Slack/3981
Telegram
CSW - Slack Channel
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644720193546839?thread_ts=1644720193.546839&cid=C5131HKFX
https://t.me/CSW_Slack/3981
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644720193546839?thread_ts=1644720193.546839&cid=C5131HKFX
https://t.me/CSW_Slack/3981
👍1
Last, why the fuck fo people keep bloody using Op_Return AT ALL, OP_PUSHDATA should be used, it should be the 99.999999999% method for every crap idea in op_return.
I say it over and over. Yet, the dumb stupid method Core added, why, lack of fucking thought.
So. If you are arguing about Op_Return, I will say, you fucking absolutely imbecilic bloody wanker.
Use the fucking push data system, it bloody works, stop trying to fuck with my system as you are too daft to do it using the right method.
All of the do called crap people want can be fine today in script.
Honestly, if you cannot do it, it is you and NOT the protocol. You
Basically, you write data to a TX.
There are 3 data sizes. You can manipulate data in scripts... what people say needs yo happen to op return.
There are no real limits, there is nothing set. This is layer 2, bitcoin itself is layer 1.
There is NOTHING to explain as nobody is creating it. This is it, data in a tx. Like, tcp is JUST data in IP. And HTTP is JUST data in TCP.
I have discussed at least 1000 ideas that vould be viable businesses.
NFTs should be tickets, and the like, there are an endless stream of uses
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644720897551449?thread_ts=1644720897.551449&cid=C5131HKFX
https://t.me/CSW_Slack/3985
I say it over and over. Yet, the dumb stupid method Core added, why, lack of fucking thought.
So. If you are arguing about Op_Return, I will say, you fucking absolutely imbecilic bloody wanker.
Use the fucking push data system, it bloody works, stop trying to fuck with my system as you are too daft to do it using the right method.
All of the do called crap people want can be fine today in script.
Honestly, if you cannot do it, it is you and NOT the protocol. You
Basically, you write data to a TX.
There are 3 data sizes. You can manipulate data in scripts... what people say needs yo happen to op return.
There are no real limits, there is nothing set. This is layer 2, bitcoin itself is layer 1.
There is NOTHING to explain as nobody is creating it. This is it, data in a tx. Like, tcp is JUST data in IP. And HTTP is JUST data in TCP.
I have discussed at least 1000 ideas that vould be viable businesses.
NFTs should be tickets, and the like, there are an endless stream of uses
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644720897551449?thread_ts=1644720897.551449&cid=C5131HKFX
https://t.me/CSW_Slack/3985
Telegram
CSW - Slack Channel
CSW
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644720897551449?thread_ts=1644720897.551449&cid=C5131HKFX
https://t.me/CSW_Slack/3985
Feb 13, 2022
https://metanet-icu.slack.com/archives/C5131HKFX/p1644720897551449?thread_ts=1644720897.551449&cid=C5131HKFX
https://t.me/CSW_Slack/3985
👍1
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