The biggest problem with BoostPoW is that it infects other …

Twetch ·

The biggest problem with BoostPoW is that it infects other BSV projects. It is BSV's Segwit. Good thing nChain is leading BSV or I'd be seriously concerned for the future of BSV.

Replies

Twetch ·

lucky for you all these "projects" are hobby toys at best

Twetch ·

It does that because it's a stable strategy. That means everyone is better off using it. It is more beneficial to follow the strategy I am teaching than not to follow it. You cannot stop benefit.

Twetch ·

How does BoostPow work?

Twetch ·

No..it's an elegant theory and inexperienced scientists often fall in love with their theories. Unfortunately, elegant wrong theories are contagious.

Twetch ·

If it's not a stable strategy then you don't need to worry about it.

Twetch ·

I'm not worried. I'm just warning people because it's the right thing to do. People are free agents.

Twetch ·

Segwit breaks the BTC protocol (along with many other things).

BoostPOW is a service offered to the market. If it works, great. If not, what's the problem?

There will plenty of BSV projects. Many will fail. The best will succeed.

Twetch ·

how did segwit break anything?

Twetch ·

for sure segwit broke my heart

Twetch ·

Segwit is also a "solution" that solves nothing. It's a tax on businesses that have to expend energy to implement it. BoostPoW is like this also for businesses that implement it. For lousy upvote results, they'll lose a lot of potential revenue.

Twetch ·

It breaks the chain of digital signatures that defines bitcoin

Twetch ·

https://www.youtube.com/watch?v=VoFb3mcxluY&feature=youtu.be&t=6m40s

Twetch ·

https://decrypt.co/31463/bitcoin-segwit-bug-fix-could-lock-wallet-users-out-funds

Twetch ·

SW was pushed as a substitute for increasing blocksize, stalling scalability efforts. BTC is maxed out as a result.

Twetch ·

SW makes the software work contrary to the way originally designed (by reinterpreting the way ANYONECANSPEND addresses work). this may or may not lead to attacks, but is certainly not proper programming practice for enterprise production code.

Twetch ·

Thats a fair answer but again what did it "break" specifically? BTC chugs along just fine since 2017
Theres some small bugs here and there like the recent thing but thats not "broken" fundamentally
Segwit was primarily a malleability fix. it's done it.

Twetch ·

malleability was never a bug to be fixed. there is no problem with malleability (unless you want to build something like LN, which by definition is not bitcoin, or you want to use it as an excuse cover up a theft, which is what MTGOX did.)

Twetch ·

BSV malleates. kein problem.

Twetch ·

It, like all soft forks, are essentially malware. They would break consensus if not for code that lies to the nodes and tells them to accept invalid txns. Segwit uniquely makes BTC unable to glean development value from any non-Segwit experimentation.

Twetch ·

for example removing P2SH using a softfork (lol..) was and is damaging to BSV as we lost BitGo for example and with it many exchanges

Twetch ·

I get it. Short term pains, with non-obvious immediate benefits. The fact that Core’s miners have protected the chain makes the attack vectors no less valid.

Twetch ·

But what did it break?

Im looking at this after 3 years. Segwit FUD was well.. FUD.

besides BTC doesnt want anything from non segwit alts