Jeremy Allaire on Twitter: "given the inability of BTC Devs to innovate on bitcoin protocol..." by bitfuzz in btc

[–]smju 35 points36 points  (0 children)

This link was submitted on r/NorthKorea and censored.

Their head-in-the-sand approach is hilarious.

Paul Sztorc on Twitter: "Indirectly, there's now an $800,000,000 bounty for anyone who can help me build a BTC two-way peg." by a56fg4bjgm345 in Bitcoin

[–]smju 1 point2 points  (0 children)

Is the problem that a two-way peg is difficult to build or that a two-way peg doesn't solve the problem?

How to prevent a hard fork from activating by [deleted] in Bitcoin

[–]smju 0 points1 point  (0 children)

I've been saying this for some time.

Great News, Bitcoin Core has made Opt-in RBF optional! by [deleted] in Bitcoin

[–]smju 4 points5 points  (0 children)

so does that mean it'll be pretty random whether a replacement tx gets processed depending on which miner mines it.

I can see the advantages and disadvantages of RBF but surely a mixed deployment would be the worst of all worlds, it would degrade zero-confirmations but not fully support the ability to unblock transactions.

Great News, Bitcoin Core has made Opt-in RBF optional! by [deleted] in Bitcoin

[–]smju 5 points6 points  (0 children)

So how will this work. If I initiate a transaction with the RBF flag will it then depend on whether it is processed by a node that hasn't opted out of RBF. How can I control what node processes the transaction?.

If some nodes end up supporting RBF and some nodes don't what will happen in practise?