Quote from: bitserve on June 28, 2018, 06:20:35 PM

Quote from: mymenace on June 28, 2018, 06:13:27 PM

Quote from: bitserve on June 28, 2018, 06:06:16 PM

Quote from: infofront on June 28, 2018, 04:28:17 PM

I've been reading anonymint's writings for the past week or so, which also prompted me to dive into some other rabbit holes.

I'm more convinced now of the dangers of segwit. Don't mistake that for being a promotion of bcash.

Could you be more verbose about that? What are those dangers?

P.S.: But not as much verbose as a thousands words dissertation. Just a simple explanation of your own thinking about the subject.

it goes against the very idea, that is all

https://bitcointalk.org/index.php?topic=423.msg3819#msg3819

Quote from: satoshi on July 17, 2010, 10:29:13 PM

I believe it'll be possible for a payment processing company to provide as a service the rapid distribution of transactions with good-enough checking in something like 10 seconds or less.

The network nodes only accept the first version of a transaction they receive to incorporate into the block they're trying to generate. When you broadcast a transaction, if someone else broadcasts a double-spend at the same time, it's a race to propagate to the most nodes first. If one has a slight head start, it'll geometrically spread through the network faster and get most of the nodes.

A rough back-of-the-envelope example:
1 0
4 1
16 4
64 16
80% 20%

So if a double-spend has to wait even a second, it has a huge disadvantage.

The payment processor has connections with many nodes. When it gets a transaction, it blasts it out, and at the same time monitors the network for double-spends. If it receives a double-spend on any of its many listening nodes, then it alerts that the transaction is bad. A double-spent transaction wouldn't get very far without one of the listeners hearing it. The double-spender would have to wait until the listening phase is over, but by then, the payment processor's broadcast has reached most nodes, or is so far ahead in propagating that the double-spender has no hope of grabbing a significant percentage of the remaining nodes.

I don't follow you.... How do Segwit impairs detecting/blocking double spendings?

allow double spending

The idea was to implement a double spend that would have no way of reaching its intended target

A self imploding virus