Why?
Login to reply
Replies (4)
The proposed solution seems worse to me than the problem.
Problem(s): nonmonetary data on chain; TapRoot seems to have introduced unknown, unknowns
Proposed solution: temp softfork, limiting rules with only 55% signal threshold; with a very small client dev team maintaining code; some supporters claiming its an *emergency*, and even hinting at legal threats to devs/miners/others who don't join their team
The proposed solution seems worse to me than the problem.
Problem(s): nonmonetary data on chain; TapRoot seems to have enabled unforeseen non-monetary use cases
Proposed solution: temp softfork, limiting rules with only 55% signal threshold; with a very small client dev team maintaining code; some supporters claiming its an *emergency*, and even hinting at legal threats to devs/miners/others who don't join their team
The proposed solution seems worse to me than the problem.
Problem(s): nonmonetary data on chain; TapRoot seems to have enabled unforeseen non-monetary use cases
Proposed solution: temp softfork, limiting rules with only 55% signal threshold; with a very small client dev team maintaining code; some supporters claiming its an *emergency*, and even hinting at legal threats to devs/miners/others who don't join their team
The proposed solution seems worse to me than the problem.
Problem(s): nonmonetary data on chain; TapRoot seems to have enabled unforeseen non-monetary use cases
Proposed solution: temp softfork, limiting rules with only 55% signal threshold; with a very small client dev team maintaining code; some supporters claiming its an *emergency*, and even hinting at legal threats to devs/miners/others who don't join their team