Conversation
|
This appears fundamentally broken by design. Softfork signals should only ever come from the node. Not from an external config file. Not from hashing devices. |
|
That's is a position. But it also means bits will get set a lot less. Most regular solo miner users are not going to download and use a forked node. I'm sure there are some who will. Letting people who use my pool software easily just set the option, or for them to allow their users to choose to set the bit or not seems a lot more democratic. Either way, if the behavior is undesired the node could/should just reject the the submitblock IMO. Although, that would just give people even more reason to consider using a fork instead. |
|
I'm sure there has been plenty of discussion around it already... But transmitting data is one thing and persisting the data in a non-temporary manner is another. If I don't have a way to easily remove content that isn't legal it will become a liability. If a take down request came my way the only choice is to stop running a node. It really becomes a legal quagmire. |
2 participants
No description provided.